Information architecture, information system vs. information technology in the organisation
There are also simple and obvious conclusions:
- there is no point in designing an “information system” without fully understanding (i.e. also documenting) the “information system, “
- there is no point in placing the elements of the “information system” on “information system” models (e.g. There is no point in putting the “information system” elements on “information system” models (e.g. symbols representing software on BPMN models)
- the relationships between the “information system” elements and the “information system” elements are described with the help of the traceability matrix
- Developing the requirements for the “information system” is about identifying the “business needs” and developing the logic of operation and architecture of the “information system” on their basis (MBSE, MDD), and not on collecting mythical “user requirements”, who in fact have no idea about “information systems”, but know very well if and when they need help in the business processes being implemented this is why methods based on designing an “information system” on the basis of interviews (workshops) with future users are doomed to failure from the outset (because even if something sensible is finally created, it will take a lot of trial-and-error work)
- One thing we have known for years: one of the most damaging theses in IT is the one saying that a document is a report from a database.