Information architecture, information system vs. information technology in the organisation

There are also simple and obvi­ous conclusions: 

  • there is no point in design­ing an “inform­a­tion sys­tem” without fully under­stand­ing (i.e. also doc­u­ment­ing) the “inform­a­tion system, ”
  • there is no point in pla­cing the ele­ments of the “inform­a­tion sys­tem” on “inform­a­tion sys­tem” mod­els (e.g. There is no point in put­ting the “inform­a­tion sys­tem” ele­ments on “inform­a­tion sys­tem” mod­els (e.g. sym­bols rep­res­ent­ing soft­ware on BPMN models)
  • the rela­tion­ships between the “inform­a­tion sys­tem” ele­ments and the “inform­a­tion sys­tem” ele­ments are described with the help of the trace­ab­il­ity matrix
  • Devel­op­ing the require­ments for the “inform­a­tion sys­tem” is about identi­fy­ing the “busi­ness needs” and devel­op­ing the logic of oper­a­tion and archi­tec­ture of the “inform­a­tion sys­tem” on their basis (MBSE, MDD), and not on col­lect­ing myth­ic­al “user require­ments”, who in fact have no idea about “inform­a­tion sys­tems”, but know very well if and when they need help in the busi­ness pro­cesses being imple­men­ted  this is why meth­ods based on design­ing an “inform­a­tion sys­tem” on the basis of inter­views (work­shops) with future users are doomed to fail­ure from the out­set (because even if some­thing sens­ible is finally cre­ated, it will take a lot of tri­al-and-error work)
  • One thing we have known for years: one of the most dam­aging theses in IT is the one say­ing that a doc­u­ment is a report from a database.

Source: Architek­tura inform­acji, sys­tem inform­acyjny a informatyczny w organ­iz­a­cji – Jarosław Żeliński IT-Consulting

Leave a Reply

Your email address will not be published. Required fields are marked *