Jump to content
 







Main menu
   


Navigation  



Main page
Contents
Current events
Random article
About Wikipedia
Contact us
Donate
 




Contribute  



Help
Learn to edit
Community portal
Recent changes
Upload file
 








Search  

































Create account

Log in
 









Create account
 Log in
 




Pages for logged out editors learn more  



Contributions
Talk
 



















Contents

   



(Top)
 


1 Overview  





2 History  





3 Types of systems modeling  





4 Specific types of modeling languages  





5 See also  





6 References  





7 Further reading  














Systems modeling






العربية
Eesti
فارسی
Română
Türkçe
 

Edit links
 









Article
Talk
 

















Read
Edit
View history
 








Tools
   


Actions  



Read
Edit
View history
 




General  



What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Cite this page
Get shortened URL
Download QR code
Wikidata item
 




Print/export  



Download as PDF
Printable version
 




In other projects  



Wikimedia Commons
 
















Appearance
   

 






From Wikipedia, the free encyclopedia
 


Example of an IDEF0 function model.
Functional Flow Block Diagram Format.[1]
Decomposition structure.
Static, dynamic, and requirements models for systems partition.
Business Process Modeling Notation Example.

Systems modelingorsystem modeling is the interdisciplinary study of the use of models to conceptualize and construct systemsinbusiness and IT development.[2]

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.

Overview[edit]

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).[3]

History[edit]

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.[4] 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.[5] In the 1960s it was exploited by the NASA to visualize the time sequence of events in a space systems and flight missions.[6] It is further widely used in classical systems engineering to show the order of execution of system functions.[7]

One of the earliest pioneering works in information systems modeling[8] 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.[9]

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.[8]

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.[8]

Types of systems modeling[edit]

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.

Specific types of modeling languages[edit]

See also[edit]

References[edit]

  1. ^ Systems Engineering Fundamentals. Archived 2006-02-11 at the Wayback Machine Defense Acquisition University Press, 2001
  • ^ Research interests Professor Alain Wegmann, Last changed 2006-12-01. Retrieved June 19, 2009.
  • ^ Ingeman Arbnor, Bjorn Bjerke (2007). Methodology for Creating Business Knowledge. Sage Publications, Inc, 1997. Back cover.
  • ^ H.L. Gantt, Work, Wages and Profit, published by the Engineering Magazine, New York, 1910; republished as Work, Wages and Profits, Easton, Pennsylvania, Hive Publishing Company, 1974, ISBN 0-87960-048-9.
  • ^ Tim Weilkiens (2008). Systems Engineering with SysML/UML: Modeling, Analysis, Design. Page 287.
  • ^ Harold Chestnut (1967). Systems Engineering Methods. Page 254.
  • ^ Thomas Dufresne & James Martin (2003). "Process Modeling for E-Business" Archived 2006-12-20 at the Wayback Machine. INFS 770 Methods for Information Systems Engineering: Knowledge Management and E-Business. Spring 2003
  • ^ a b c Janis A. Bubenko jr (2007) "From Information Algebra to Enterprise Modelling and Ontologies - a Historical Perspective on Modelling for Information Systems". In: Conceptual Modelling in Information Systems Engineering. John Krogstie et al. eds. pp 1-18
  • ^ Young, J. W., and Kent, H. K. (1958). "Abstract Formulation of Data Processing Problems". In: Journal of Industrial Engineering. Nov-Dec 1958. 9(6), pp. 471-479
  • ^ Isaksson, Raine (2006-01-01). "Total quality management for sustainable development: Process based system models". Business Process Management Journal. 12 (5): 632–645. doi:10.1108/14637150610691046. ISSN 1463-7154.
  • Further reading[edit]


    Retrieved from "https://en.wikipedia.org/w/index.php?title=Systems_modeling&oldid=1221391355"

    Categories: 
    Enterprise modelling
    Software development
    Systems analysis
    Systems science
    Management cybernetics
    Hidden categories: 
    Webarchive template wayback links
    Articles with short description
    Short description is different from Wikidata
    Commons category link from Wikidata
     



    This page was last edited on 29 April 2024, at 17:18 (UTC).

    Text is available under the Creative Commons Attribution-ShareAlike License 4.0; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Mobile view



    Wikimedia Foundation
    Powered by MediaWiki