Fundamental modeling concepts: Difference between revisions

Revision as of 09:12, 2 August 2007

Revision as of 14:43, 6 September 2007

Line 1:

'''Fundamental modelingModeling conceptsConcepts''' (FMC) provide a framework to describe software-intensive systems. It strongly emphasizes the communication about software-intensive systems by using a [[semi-formal]] graphical notation that can easily be understood.

== Introduction ==

FMC distinguishes three different [[diagram]] types:

FMC distinguishes three perspectives to look at a software system:

* compositional structure

* Structure of the system

* dynamic structure

* Processes in the system

* value range structure

* Value domains of the system

The diagram type are [[bipartite graph]]s.

FMC defines a dedicated diagram type for each perspective. FMC diagrams use a simple and lean notation. The purpose of FMC diagrams is to facilitate the communication about a software system, not only between technical experts but also between technical experts and business or ___domain experts. The comprehensibility of FMC diagrams has made them famous among its supporters.

The common approach when working with FMC is to start with a high-level diagram of the compositional structure of a system. This “big picture” diagram serves as a reference in the communication with all involved stakeholders of the project. Later on, the high-level diagram is iteratively refined to model technical details of the system. Complementary diagrams for processes observed in the system or value domains found in the system are introduced as needed.

== Compositional structure diagram==