Metadata modeling: Difference between revisions

Revision as of 02:23, 22 January 2014

Latest revision as of 02:24, 31 August 2021

(4 intermediate revisions by 3 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==

[[ImageFile:Mm31Metadata modeling - STANDARD, OPEN and CLOSED CONCEPTS.gif|thumb|Fig.1 STANDARD, OPEN and CLOSED 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> Booch, Rumbaugh and Jacobson (1999)</ref> is adopted to define a concept, namely: a set of objects that share the same attributes, operations, relations, and semantics.

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 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, 374-389374–389.

* I. Weerd, J. van de, Souer, J. Versendaal and [[Sjaak Brinkkemper]] (2005). ''Situational Requirements Engineering of Web Content Management Implementations''. SREP2005.