Information flow diagram
An information flow diagram (IFD) is a diagram that shows how information is communicated (or "flows") from a source to a receiver or target (e.g. A→C), through some medium.[1]: 36–39 The medium acts as a bridge, a means of transmitting the information. Examples of media include word of mouth, radio, email, etc. The concept of IFD was initially used in radio transmission.[2] The diagrammed system may also include feedback, a reply or response to the signal that was given out. The return paths can be two-way or bi-directional: information can flow back and forth.[2]
An IFD can be used to model the information flow throughout an organisation. An IFD shows the relationship between internal information flows within an organisation and external information flows between organisations. It also shows the relationship between the internal departments and sub-systems.
An IFD usually uses "blobs" to decompose the system and sub-systems into elemental parts.[2] Lines then indicate how the information travels from one system to another. IFDs are used in businesses, government agencies, television and cinematic processes.[citation needed]
IFDs are often confused with data flow diagrams (DFDs). IFDs show information as sources, destination and flows. DFDs show processes where inputs are transformed into outputs. Databases are also present in DFDs to show where data is held within the systems. In DFDs information destinations are called "sinks".[3]: 180
Purpose
[edit]Peter Checkland, a British management scientist, described information flows between the different elements that compose various systems. He also defined a system as a "community situated within an environment".[2]
The main purpose of an information flow diagram is so that sources that send and receive information can be displayed neatly and analysed. This allows viewers to see the forwarding of information and the analysis of different situations.[2] The creation of an IFD is, in most cases, the first step in information analysis.[1]: 37
IFDs are behaviour diagrams that show the exchange of data between systems. They are also used to describe the circulation of information within systems.[4]
Information that moves along the diagram is represented as either information items or by concrete classifiers. IFDs are used to:[2]
- Develop a high level overview of the flow of information in an organisation.
- Highlight detailed flows in an individual task.
- Describe the flow of information inside and around organisations and between departments.[5]
- Understand business process bottlenecks in sequential, deferred, real-time, parallel, wheel, one-to-many, many-to-many and many-to-one-to-many information flows.[6]
Features and construction of IFD
[edit]Construction of an information flow diagram requires the knowledge of different information sources and the connections between them. The sources and targets of information flow are one of the following: actor, use case, node, artefact, class, component, port, property, interface, package, activity node, activity partition, or instance specification.[citation needed]
A dashed line with an open arrow pointing away from the source to the target is used to represent information flow. The keyword "flow" may be written above or below the dashed line. Information items represent the abstraction of data and act as information flow connectors, representing the flow of transfer of information from source to target. Information items do not provide any detail of the information they transfer as they are featureless.[4]
Diagramming software can be used to create IFDs. Examples of diagramming software include Microsoft Visio for Windows or OmniGraffle for OS X.
Successful IFDs should highlight gaps that need improvement, display inefficiencies in information, uncover and highlight risks to information such as data confidentiality and Insecure systems, display unsuitable mediums which are being used, and they should also provide clarity about who should receive which information when, where and how.
Example situation
[edit]
A customer needs to make an order. The customer first posts the order to the sales department. The customer's order details are then entered into a centralised database which can only be accessed by the warehouse to make the order. The goods are handed to the dispatch department with a delivery note attached to them for delivery. On delivery, the customer receives the goods and the delivery note (which are handled by a member of the dispatch department). The sales department then creates an invoice which is posted to the customer. The accounts department then assesses a copy of the invoice from the centralised database. The customer is then required to post the payment to the accounts department.[7]
Limitations
[edit]Limitations of information flow diagrams may include:
- The nature of information that is used in the IFD and the mechanisms by which it is conveyed and exchanged, and the control conditions are not specified.[4]
- The signal given out and the signal received are in many cases different. This also applies to feedback messages, due to distortions.[2]
- The intentions of messages sometimes not understood when receiving a signal and message.[2]
- Information items do not provide details about the information they transfer as they don't have features, generalisations or associations.[2]
- Detail about timing (what happens when) is not given.[3]
See also
[edit]- Access Control Matrix
- Business Process Model and Notation
- Information cascade
- Information systems
- NIAM / Object-role modeling
- System context diagram
- Systems thinking
References
[edit]- ^ a b Wintraecken, J. J. V. R. (1990) [1987]. The NIAM information analysis method: theory and practice. Translation of: Informatie-analyse volgens NIAM. Dordrecht; Boston: Kluwer Academic Publishers. doi:10.1007/978-94-009-0451-4. ISBN 079230263X. OCLC 19554537. S2CID 30209824.
- ^ a b c d e f g h i Schade, Martha Begley. "Information flow diagram guidelines". business-online-learning.com. Archived from the original on 2012-09-23. Retrieved 2016-03-20.
- ^ a b Bocij, Paul; Chaffey, Dave (2003). "Systems analysis" (PDF). Business information systems: technology, development, and management for the e-business (2nd ed.). Harlow, UK; New York: FT/Prentice Hall. pp. 171–189. ISBN 027365540X. OCLC 49383949. Archived from the original (PDF) on 2016-04-04. Retrieved 2015-10-31.
- ^ a b c "UML information flow diagrams". uml-diagrams.org. Archived from the original on 2012-11-18. Retrieved 2016-03-20.
- ^ Yull, Sharon; Jarvis, Alan; Lawson, Jenny (2005). "Information and its use". AS level GCE applied ICT. Oxford: Heinemann. pp. 40–48. ISBN 9780435449957. OCLC 58054511.
- ^ Durugbo, Christopher; Tiwari, Ashutosh; Alcock, Jeffrey R. (June 2013). "Modelling information flow for organisations: a review of approaches and future challenges" (PDF). International Journal of Information Management. 33 (3): 597–610. doi:10.1016/j.ijinfomgt.2013.01.009. Archived from the original (PDF) on 2018-05-16. Retrieved 2015-10-31.
- ^ Alexander, Vincent. "Information flow: an information flow diagram is a useful way of showing how information moves into and out of an organisation and between individuals". slideplayer.com. Retrieved 2016-03-20.