Fundamental modeling concepts: Difference between revisions

Content deleted Content added
m Compositional Structure Diagram: Typo fixing, etc., typo(s) fixed: so called → so-called using AWB
Anetman (talk | contribs)
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1:
{{Primary sources|date=December 2009}}
'''Fundamental Modelingmodeling Conceptsconcepts''' ('''FMC''') provide a framework to describe software-intensive systems. It strongly emphasizes the communication about software-intensive systems by using a [[Formal semantics of programming languages|semi-formal]] graphical notation that can easily be understood.
 
== Introduction ==
Line 14:
== Diagram Types ==
FMC uses three diagram types to model different aspects of a system:
* '''Compositional Structure Diagram''' depicts the static structure of a system. This diagram type is also known as FMC Block Diagram
* '''Dynamic Structure Diagram''' depicts processes that can be observed in a system. This diagram type is also known as FMC Petri-net
* '''Value Range Structure Diagram''' depicts structures of values found in the system. This diagram type is also known as FMC E/R Diagram
 
All FMC diagrams are bipartite graphs. Each [[Bipartitebipartite graph]] consists of two [[disjoint sets]] of vertices with the condition that no [[vertex (graph theory)|vertex]] is connected to another vertex of the same set. In FMC diagrams, members of one set are represented by angular shapes, and members of the other set are represented by curved shapes. Each element in an FMC diagram can be refined by another diagram of the same type, provided that the combined graph is also bipartite. This mechanism allows modeling all relevant layers of abstraction with the same notation.
 
=== Compositional Structure Diagram ===
[[File:FMCBlockDiagram.png|thumb|right|Example of FMC Compositional Structure Diagram]]
 
Compositional structure diagrams depict the static structure of a system, and the relationships between system components. System components can be active or passive. '''Agents''' are active system components. They perform activities in the system. '''Storages''' and '''channels''' are passive components which store or transmit information.
Line 33:
=== Dynamic Structure Diagram ===
Dynamic structures are derived from [[petri net]]s.
:"They are used to express system behavior over time, depicting the actions performed by the agents. So they clarify how a system is working and how communication takes place between different agents." <ref name="fmc-modeling.org">[http://www.fmc-modeling.org/notation_reference/ fmc-modeling.org Notations Reference]</ref>
 
=== Value Range Structure Diagram ===
Value range structure diagrams (also known as FMC Entity Relationship Diagrams) can be compared with the [[Entity-relationship model]].
:"[They] are used to depict value range structures or topics as mathematical structures. Value range structures describe observable values at locations within the system whereas topic diagrams allow a much wider usage in order to cover all correlations between interesting points." <ref name="fmc-modeling.org"/>
 
== References ==
{{Reflist}}
<references/>
*{{cite book
| first= Andreas
Line 53:
 
== External links ==
* [http://www.fmc-modeling.org/ FMC Homepagehome page]
* [http://www.fmc-modeling.org/fmc_stencils/ FMC-Stencils for MS-Visio]
* [http://www.fmc-modeling.org/intervista FMC-Coaching & Training]
*[http://www.alternative-softwaresystemtechnik.de]
 
{{DEFAULTSORT:Fundamental Modeling Concepts}}
Line 61 ⟶ 62:
[[Category:Data modeling languages]]
[[Category:Specification languages]]
[[Category:Modeling languages]]