Systems modeling or system modeling is the interdisciplinary study of the use of models to conceptualize and construct systems in business and IT development.[1]
A common type of systems modeling is function modeling, with specific techniques such as the Functional Flow Block Diagram and IDEF0. These models can be extended using functional decomposition, and can be linked to requirements models for further systems partition.
Contrasting the functional modeling, another type of systems modeling is architectural modeling which uses the systems architecture to conceptually model the structure, behavior, and more views of a system.
The Business Process Modeling Notation (BPMN), a graphical representation for specifying business processes in a workflow, can also be considered to be a systems modeling language.
In business and IT development the term "systems modeling" has multiple meanings. It can relate to:
As a field of study systems modeling has emerged with the development of system theory and systems sciences.
As a type of modeling systems modeling is based on systems thinking and the systems approach. In business and IT systems modeling contrasts other approaches such as:
In "Methodology for Creating Business Knowledge" (1997) Arbnor and Bjerke the systems approach (systems modeling) was considered to be one of the three basic methodological approaches for gaining business knowledge, beside the analytical approach and the actor's approach (agent based modeling).[2]
The function model originates in the 1950s, after in the first half of the 20th century other types of management diagrams had already been developed. The first known Gantt chart was developed in 1896 by Karol Adamiecki, who called it a harmonogram. Because Adamiecki did not publish his chart until 1931 - and in any case his works were published in either Polish or Russian, languages not popular in the West - the chart now bears the name of Henry Gantt (1861–1919), who designed his chart around the years 1910-1915 and popularized it in the West.[3] One of the first well defined function models, was the Functional Flow Block Diagram (FFBD) developed by the defense-related TRW Incorporated in the 1950s.[4] In the 1960s it was exploited by the NASA to visualize the time sequence of events in a space systems and flight missions.[5] It is further widely used in classical systems engineering to show the order of execution of system functions.[6]
One of the earliest pioneering works in information systems modeling[7] has been done by Young and Kent (1958), who argued:
Since we may be called upon to evaluate different computers or to find alternative ways of organizing current systems it is necessary to have some means of precisely stating a data processing problem independently of mechanization.[8]
They aimed for a precise and abstract way of specifying the informational and time characteristics of a data processing problem, and wanted to create a notation that should enable the analyst to organize the problem around any piece of hardware. Their efforts was not so much focused on independent systems analysis, but on creating abstract specification and invariant basis for designing different alternative implementations using different hardware components.[7]
A next step in IS modeling was taken by CODASYL, an IT industry consortium formed in 1959, who essentially aimed at the same thing as Young and Kent: the development of "a proper structure for machine independent problem definition language, at the system level of data processing". This led to the development of a specific IS information algebra.[7]
In business and IT development systems are modeled with different scopes and scales of complexity, such as:
Further more like systems thinking, systems modeling in can be divided into:
And all other specific types of systems modeling, such as form example complex systems modeling, dynamical systems modeling, and critical systems modeling.