Content deleted Content added
m clean up, typo(s) fixed: 374-389 → 374–389 |
|||
| (5 intermediate revisions by 4 users not shown) | |||
Line 1:
'''Metadata modeling''' is a type of [[metamodeling]] used in [[software engineering]] and [[systems engineering]] for the analysis and construction of models applicable to and useful for some predefined class of problems.
Meta-modeling is the analysis, construction and development of the frames, rules, constraints, models and theories applicable and useful for the modeling in a predefined class of problems.
The meta-data side of the diagram consists of a concept diagram. This is basically an adjusted class diagram as described in Booch, Rumbaugh and Jacobson (1999). Important notions are concept, generalization, association, multiplicity and aggregation.
== Metadatamodeling Concepts==
[[
[[Image:Mm32.gif|thumb|Fig.2 Example of STANDARD, OPEN and CLOSED CONCEPTS]]
First of all, a concept is a simple version of a Unified Modeling Language (UML) class. The class definition<ref>
The following concept types are specified:
Line 14:
* STANDARD CONCEPT: a concept that contains no further (sub) concepts. A standard concept is visualized with a rectangle.
* COMPLEX CONCEPT: a concept that consists of a collection of (sub) concepts. Complex concepts are divided into:
* OPEN CONCEPT: a complex concept whose (sub) concepts are expanded. An open concept is visualized with two white rectangles above each other. (Correction: An open concept is visualized with 2 white rectangles, 1 overlaid over the other, offset to the right, with 3 corners of the rectangle beneath visible. )
* CLOSED CONCEPT: a complex concept whose (sub) concepts are not expanded since it is not relevant in the specific context. A closed concept is visualized by a white rectangle above a black rectangle.
Line 26:
Generalization is a way to express a relationship between a general concept and a more specific concept. Also, if necessary, one can indicate whether the groups of concepts that are identified are overlapping or disjoint, complete or incomplete. Generalization is visualized by a solid arrow with an open arrowhead, pointing to the parent, as is illustrated in Figure 3.
In Figure 4 generalization is exemplified by showing the relationships between the different concepts described in the preceding paragraph. STANDARD CONCEPT and COMPLEX CONCEPT are both a specific kind of CONCEPT. Subsequently, a COMPLEX CONCEPT can be specified into an OPEN CONCEPT and a CLOSED CONCEPT
=== Association ===
Line 82:
== Further reading ==
* [[Grady Booch]], [[James Rumbaugh]] and [[Ivar Jacobson]] (1999). ''The Unified Modeling Language User Guide''. Redwood City, CA: Addison Wesley Longman Publishing Co., Inc.
* M. Saeki (2003). ''Embedding Metrics into Information Systems Development Methods: An Application of Method Engineering Technique''. CAiSE 2003,
* I. Weerd, J. van de, Souer, J. Versendaal and [[Sjaak Brinkkemper]] (2005). ''Situational Requirements Engineering of Web Content Management Implementations''. SREP2005.
| |||