Академический Документы
Профессиональный Документы
Культура Документы
Elaboration,<br />
Construction, and<br />
Transition.<br />
9.What are the Process Workflows that evolve through these phases?<br />
The Process Workflows that evolve through these phases are<br />
Business Modeling,<br />
Requirement gathering,<br />
Analysis and Design,<br />
Implementation,<br />
Testing,<br />
Deployment.<br />
Supporting Workflows are Configuration, change management, and Project managemen
t.<br />
10.What are Relationships?<br />
There are different kinds of relationships:<br />
Dependencies,<br />
Generalization, and<br />
Association.<br />
Dependencies are relationships between two entities.<br />
A change in specification of one thing may affect another thing.<br />
Most commonly it is used to show that one class uses another class as an argumen
t in the signature of the operation.</p>
<p>Generalization is relationships specified in the class subclass scenario, it
is shown when one entity inherits from other.<br />
Associations are structural relationships that are:<br />
a room has walls,<br />
Person works for a company.</p>
<p>Aggregation is a type of association where there is a has a relationship.<br
/>
As in the following examples: A room has walls, or if there are two classes room
and walls then the relation ship is called a association and further defined as
an aggregation.</p>
<p>11.How are the diagrams divided?<br />
The nine diagrams are divided into static diagrams and dynamic diagrams.</p>
<p>12.Static Diagrams (Also called Structural Diagram):<br />
The following diagrams are static diagrams.<br />
Class diagram,<br />
Object diagram,<br />
Component Diagram,<br />
Deployment diagram.<br />
13.Dynamic Diagrams (Also called Behavioral Diagrams):<br />
The following diagrams are dynamic diagrams.<br />
Use Case Diagram,<br />
Sequence Diagram,<br />
Collaboration Diagram,<br />
Activity diagram,<br />
Statechart diagram.<br />
14.What are Messages?<br />
A message is the specification of a communication, when a message is passed that
results in action that is in turn an executable statement.</p>
<p>15.What is an Use Case?<br />
A use case specifies the behavior of a system or a part of a system.<br />
Use cases are used to capture the behavior that need to be developed.<br />
It involves the interaction of actors and the system.</p>
<strong>Model:</strong><br />
It is a complete description of something (i.e. system).<br />
<strong>Meta model:</strong><br />
It describes the model elements, syntax and semantics of the notation that allow
s their manipulation.</p>
<p><strong>7. What do you meant by static and dynamic modeling?</strong><br />
Static modeling is used to specify structure of the objects that exist in the pr
oblem domain. These are expressed using class, object and USECASE diagrams.<br /
>
But Dynamic modeling refers representing the object interactions during runtime.
It is represented by sequence, activity, collaboration and statechart diagrams.
</p>
<p><strong>8. How to represent the interaction between the modeling elements?</s
trong><br />
Model element is just a notation to represent (Graphically) the entities that ex
ist in the problem domain. e.g. for modeling element is class notation, object n
otation etc.<br />
Relationships are used to represent the interaction between the modeling element
s.<br />
The following are the Relationships.<br />
Association: Its just a semantic connection two classes.<br />
e.g.:<br />
Aggregation: Its the relationship between two classes which are related in the fa
shion that master and slave. The master takes full rights than the slave. Since
the slave works under the master. It is represented as line with diamond in the
master area.<br />
ex:<br />
car contains wheels, etc.</p>
<p>car<br />
Containment: This relationship is applied when the part contained with in the wh
ole part, dies when the whole part dies.<br />
It is represented as darked diamond at the whole part.<br />
example:<br />
class A{<br />
//some code<br />
};</p>
<p>class B<br />
{<br />
A aa; // an object of class A;<br />
// some code for class B;<br />
};<br />
In the above example we see that an object of class A is instantiated with in th
e class B. so the object class A dies when the object class B dies.we can repres
nt it in diagram like this.<br />
Generalization: This relationship used when we want represents a class, which ca
ptures the common states of objects of different classes. It is represented as a
rrow line pointed at the class, which has captured the common states.<br />
Dependency: It is the relationship between dependent and independent classes. An
y change in the independent class will affect the states of t</p>
<p><strong>9. Why generalization is very strong?</strong><br />
Even though Generalization satisfies Structural, Interface, Behaviour properties
. It is mathematically very strong, as it is Antisymmetric and Transitive.<br />
Antisymmetric: employee is a person, but not all persons are employees. Mathemat
ically all As are B, but all Bs not A.<br />
Transitive: A=>B, B=>c then A=>c.<br />
A. Salesman.<br />
B. Employee.<br />
C. Person.<br />
Note: All the other relationships satisfy all the properties like Structural pro
perties, Interface properties, Behaviour properties.</p>