Object diagram: Difference between revisions
Content deleted Content added
m + Link(s) |
←Replaced content with 'cdac kharghar' Tags: possible vandalism blanking |
||
| Line 1: | Line 1: | ||
cdac kharghar |
|||
[[File:Object diagram.png|thumb|Example of an Object diagram.]] |
|||
An '''object diagram''' in the [[Unified Modeling Language]] (UML), is a [[diagram]] that shows a complete or partial view of the structure of a modeled [[system]] at a specific time. |
|||
== Overview == |
|||
{{UML diagram types}} |
|||
In the [[Unified Modeling Language]] (UML), an object diagram focuses on some particular set of [[Object (computer science)|objects]] and [[Attribute (computing)|attributes]], and the links between these instances. A correlated set of object diagrams provides insight into how an arbitrary view of a system is expected to evolve over time. In early UML specifications the object diagram is described as: |
|||
: "''An object diagram is a graph of instances, including objects and data values. A static object diagram is an instance of a class diagram; it shows a snapshot of the detailed state of a system at a point in time. The use of object diagrams is fairly limited, namely to show examples of data structure''."<ref>[[Object Management Group]] (2001) [http://www.omg.org/spec/UML/1.4 UML specification 1.4], September 2001</ref><ref>Anne Banks Pidduck, [[John Mylopoulos]], Carson C. Woo (2002) ''Advanced Information Systems Engineering''. p.776.</ref> |
|||
The latest UML 2.4 specification doesn't provide any definition of the object diagram.<ref>[http://www.uml-diagrams.org/uml-25-diagrams.html Classification of UML 2.5 Diagrams] on uml-diagrams.org. Retrieved Dec 7, 2012</ref> |
|||
Object diagrams and class diagrams are closely related<ref>Marcus Fontoura, Wolfgang Pree & [[Bernhard Rumpe]] (2002) ''The UML profile for framework architectures''. p.19</ref> and use almost identical notation.<ref>Kassem A. Saleh (2009) ''Software Engineering''. p.47</ref> Both diagrams are meant to visualize static structure of a system. While class diagrams show [[Class (computer programming)|classes]], object diagrams displays instances of classes ([[Object (computer science)|objects]]).<ref>Bianca Scholten (2007) ''The Road to Integration: A Guide to Applying the ISA-95 Standard in Manufacturing''. p.155</ref> Object diagrams are more concrete than [[class diagram]]s. They are often used to provide examples or act as test cases for class diagrams. Only aspects of current interest in a model are typically shown on an object diagram. |
|||
==Object diagram topics== |
|||
===Instance specifications=== |
|||
Each object and link on an object diagram is represented by an ''InstanceSpecification''. This can show an object's classifier (e.g. an abstract or concrete [[Class (computer science)|class]]) and instance name, as well as attributes and other structural features using ''slots''. Each ''slot'' corresponds to a single attribute or feature, and may include a value for that entity. |
|||
The name on an instance specification optionally shows an instance name, a ':' separator, and optionally one or more classifier names separated by commas. The contents of slots, if any, are included below the names, in a separate attribute compartment. |
|||
A link is shown as a solid line, and represents an instance of an [[Association (object-oriented programming)|association]]. |
|||
===Object diagram example=== |
|||
[[Image:Object Diagram Initial.png|thumb|right|400px|Initially, when n=2, and f(n-2) = 0, and f(n-1) = 1, then f(n) = 0 + 1 = 1.]] |
|||
As an example, consider one possible way of modeling production of the [[Fibonacci sequence]]. |
|||
In the first UML object diagram on the right, the instance in the leftmost instance specification is named ''v1'', has ''IndependentVariable'' as its classifier, plays the ''NMinus2'' role within the ''FibonacciSystem'', and has a slot for the ''val'' attribute with a value of ''0''. The second object is named ''v2'', is of class ''IndependentVariable'', plays the ''NMinus1'' role, and has ''val = 1''. The ''DependentVariable'' object is named ''v3'', and plays the ''N'' role. The topmost instance, an anonymous instance specification, has ''FibonacciFunction'' as its classifier, and may have an instance name, a role, and slots, but these are not shown here. The diagram also includes three named links, shown as lines. Links are instances of an association. |
|||
[[Image:Object Diagram 2.png|thumb|right|300px|After the first iteration, when n = 3, and f(n-2) = 1, and f(n-1) = 1, then f(n) = 1 + 1 = 2.]] |
|||
In the second diagram, at a slightly later point in time, the ''IndependentVariable'' and ''DependentVariable'' objects are the same, but the slots for the ''val'' attribute have different values. The role names are not shown here. |
|||
[[Image:Object Diagram 1.png|thumb|right|280px|After several more iterations, when n = 7, and f(n-2) = 5, and f(n-1) = 8, then f(n) = 5 + 8 = 13.]] |
|||
In the last object diagram, a still later snapshot, the same three objects are involved. Their slots have different values. The instance and role names are not shown here. |
|||
===Usage=== |
|||
If you are using a [[UML tool|UML modeling tool]], you will typically draw object diagrams using some other diagram type, such as on a [[class diagram]]. An object instance may be called an ''instance specification'' or just an ''instance''. A link between instances is generally referred to as a ''link''. Other UML entities, such as an [[Aggregation (object-oriented programming)|aggregation]] or [[Object composition|composition]] symbol (a diamond) may also appear on an object diagram. |
|||
==References== |
|||
{{reflist}} |
|||
==External links== |
|||
{{Commons category|Object diagrams}} |
|||
* [http://www.uml.org/ General information on UML] including the official UML 2.0 specification. See especially the section on InstanceSpecification. |
|||
* [http://advanceduml.wordpress.com/2008/09/26/what-a-month-in-the-financial-sector/ The Expressive Power of Object Diagrams], an illustration from the real world |
|||
* [http://www.se-rwth.de/materials/mod/ Modal object diagrams], an extension of object diagrams with existential/universal and positive/negative modes. |
|||
{{UML}} |
|||
{{DEFAULTSORT:Object Diagram}} |
|||
[[Category:Unified Modeling Language diagrams]] |
|||
Revision as of 10:13, 1 December 2014
cdac kharghar