21.07.2013 Views

Modeling with Technology FrameWork

Modeling with Technology FrameWork

Modeling with Technology FrameWork

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Model element comments<br />

objects, some of which are more fundamental than others to its<br />

construction and meaning. <strong>FrameWork</strong> reserves the concept of<br />

model element for the core constructs of a model. These constructs<br />

typically have names and are not dependent on other objects for<br />

their existence. Examples of model elements are classes, activities,<br />

and use cases.<br />

Objects that are not model elements are usually unnamed and are<br />

either objectified relationships or other objects that cannot exist<br />

<strong>with</strong>out the presence of one or more related objects. Examples of<br />

objects that are not model elements are attributes, consumption<br />

relationships, and bidirectional communications.<br />

The #MODEL ELEMENT class is an abstract superclass of a wide<br />

variety of other classes. When you create an object in any of these<br />

classes, that object is automatically an instance of #MODEL<br />

ELEMENT. You can define other individual objects as model<br />

elements by adding them to the #MODEL ELEMENT class. If you<br />

have Enterprise <strong>FrameWork</strong> Professional, you can define an entire<br />

class of objects as model elements by making the class a subclass of<br />

#MODEL ELEMENT or any of its subclasses.<br />

Model element comments<br />

Information on this topic is not yet available.<br />

Model element dependencies<br />

Object constraints<br />

Information on this topic is not yet available.<br />

Information on this topic is not yet available.<br />

Chapter 2: Cross-model Concepts<br />

15

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!