RAGHU ENGINEERING COLLEGE DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Subject:-Uml and Design Patterns-IV th Btech-1-Sem

Syllabus:Unit-2: Structural Modeling: Classes, Relationships, common Mechanisms, and diagrams, Advanced classes, Advanced relationships, Object diagrams: common modeling techniques

1) What is Structural Model?Ans) A view of a system that emphasizes the structure of the objects, including their relationships, attributes and operations.2) Explain classes.Ans) Classes are the most important building block of any object-oriented system. A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics. A class implements one or more interfaces. The UML provides a graphical representation of class with its name, attributes and operations.3) Explain name, attribute and operation as part of class?Ans) Name: Every class must have a name that distinguishes it from other classes. Attribute: It is a property of a class. Operation: Represents behavior of class or some actions Graphical Representation:

4) Define Relationship?Ans) a relationship is a connection among things.

5) What are the various relationships?Ans) In object-oriented modeling, the three most important relationships are dependencies, generalization, and associations

6) Explain dependencies relationship?Ans) A dependency is a using relationship that states that a change in specification of one thing (for example, class Event) may affect another thing that uses it (for example, class Window), but not necessarily the reverse. Graphically, a dependency is rendered as a dashed directed line, directed to the thing being depended on. Use dependencies when you want to show one thing using another.Graphical Representation

7) Explain Generalization.Ans) A generalization is a relationship between a general thing and a more specific kind of that thing.Generalization is sometimes called an "is-a-kind-of" relationship: one thing is-a-kind-of a more general. Generalization means that objects of the child may be used anywhere the parent may appear.Graphical Representation

8) Explain Associations.Ans) An association is a structural relationship that specifies that objects of one thing are connected to objects of another. Given an association connecting two classes, you can navigate from an object of one class to an object of the other class, and vice versa. This means that, given an object of the class, you can link to other objects of the same class.

Beyond this basic form, there are four adornments that apply to associations:1) Name 2) Role 3) Multiplicity 4) Aggregation

Name:An association can have a name, and you use that name to describe the nature of the relationship.

Role:When a class participates in an association, it has a specific role that it plays in that relationship.

Multiplicity:In many modeling situations, it's important to state how many objects may be connected across an instance of an association. we can show a multiplicity of exactly one (1), zero or one (0..1), many (0..*), or one or more (1..*). we can even state an exact number (for example, 3).

Aggregation:Sometimes, you will want to model a "whole/part" relationship, in which one class represents a larger thing (the "whole"), which consists of smaller things (the "parts"). This kind of relationship is called aggregation, which represents a "has-a" relationship, meaning that an object of the whole has objects of the part.

University Question:Q) Briefly explain relationship? 10) What are the common Mechanisms in the UML?Ans) Four Common Mechanisms that apply consistently throughout the UML Language.1) Specifications 2) Adornments 3) Common Divisions 4. Extensibility mechanisms

11) Explain Specifications?Ans) We use the UMLs specification to state the systems details. The UML specifications provide a semantic backplane that contains all the models of a system, each part related to one another in a consistent fashion.12) Explain Adornments?Ans) Most elements in the UML have a unique and direct graphical notation that provides a visual representation of the most important aspects of the element. For Example, the below figure shows a class, adorned to indicate that it is an abstract class with two public, one protected and one private operation.

Transaction

+execute()+rollback()+priority() -timestamp()

Adornments

13) Explain Common DivisionsAns) First, there is the division of class and object. A class is an abstraction; an object is one concrete manifestation of that abstraction. In the UML , we can model classes as well as objects.

Graphical Representation:Customer

name addressphone

Jan:Customer

:Customer

Elyse

In the above figure, there is one class, named Customer, together with three objects Jan, :Customer and Elyse.14) Extensibility Mechanisms.Ans) The UML provides a standard language for writing software blueprints. The UML extensibility mechanisms include1) Stereotypes allow us to create new kinds of building blocks that are derived from existing one. 2) Tagged valuesallow us to create new information in that elements specification. 3) Constraints allow us to add new rules or modify existing ones.---------------------------------------------------------------------------------------------------------------------University QuestionQ) Explain Common Mechanisms in the UML.[DEC-2013-SET-4]Ans) Four Common Mechanisms that apply consistently throughout the UML Language.1) Specifications 2) Adornments 3) Common Divisions 4. Extensibility mechanisms

1. Specifications: We use the UMLs specification to state the systems details. The UML specifications provide a semantic backplane that contains all the models of a system, each part related to one another in a consistent fashion.

2. Adornments: Most elements in the UML have a unique and direct graphical notation that provides a visual representation of the most important aspects of the element. For Example, the below figure shows a class, adorned to indicate that it is an abstract class with two public, one protected and one private operation.

Transaction

+execute()+rollback()+priority() -timestamp()

Adornments

3. Common Divisions: First, there is the division of class and object. A class is an abstraction; an object is one concrete manifestation of that abstraction. In the UML , we can model classes as well as objects.

Graphical Representation

Customer

name addressphone

Jan:Customer

:Customer

Elyse

Common DivisionsIn the above figure, there is one class, named Customer, together with three objects Jan: Customer, :Customer and Elyse4. Extensibility Mechanisms. The UML provides a standard language for writing software blueprints. The UML extensibility mechanisms include1)Stereotypes allow us to create new kinds of building blocks that are derived from existing one. 2) Tagged valuesallow us to create new information in that elements specification. 3) Constraints allow us to add new rules or modify existing ones.----------------------------------------------------------------------------------------------------------------15) Explain Diagrams in UMl.Ans) A diagram is the graphical presentation of a set of elements, most often rendered as a connected graph of vertices (things) and arcs (relationships).

16) What are the diagrams in UML?

Ans) The UML includes nine such diagrams:1. Class diagram 2. Object diagram 3. Use case diagram 4. Sequence diagram5. Collaboration diagram 6. Statechart diagram 7. Activity diagram8. Component diagram9. Deployment diagram.17) What is the static part of diagrams (or) Structural Diagrams that UML includes?Ans) Typically, we'll view the static parts of a system using one of the four following diagrams:1. Class diagram 2. Object diagram 3. Component diagram 4. Deployment diagramThe above diagrams are also called as Structural Diagrams

18) What are the Dynamic part of diagrams (or) Behavioral Diagrams that UML includes?Ans) we'll often use five additional diagrams to view the dynamic parts of a system:

1. Use case diagram 2. Sequence diagram 3. Collaboration diagram 4. Statechart diagram5. Activity diagram.The above diagrams are also called as Behavioral Diagrams.

16) Explain Class diagram.Ans) a class diagram shows a set of classes, interfaces, and collaborations and their relationships.These diagrams are the most common diagram found in modeling object-oriented systems. Class diagrams address the static design view of a system. Class diagrams that include active classes address the static process view of a system.

17) Explain Object Diagram.

Ans) An object diagram shows a set of objects and their relationship. We use object diagrams to illustrate data structures. Object diagram address the static design view or ststic process view of a system just as do class diagrams. 18) What are the Common Modeling Techniques?Ans) The Common Modeling Techniques are1) Modeling the Vocabulary of a System.2) Modeling the Distribution of Responsibilities in a System.3) Modeling Nonsoftware Things.4) Modeling Primitive Types.--------------------------------------------------------------------------------------------------------------------- University Question: Q) Briefly explain Common Modeling Techniques. [DEC-2013-SET-1]Ans) The Common Modeling Techniques are 1 Modeling the Vocabulary of a System. 2 Modeling the Distribution of Responsibilities in a System.3 Modeling Nonsoftware Things.4 Modeling Primitive Types.1) To model the vocabulary of a system:Identify those things that users or implementers use to describe the problem or solution. Use CRC cards and use case-based analysis to help find these abstractions.For each abstraction, identify a set of responsibilities. Make sure that each class is crisply defined and that there is a good balance of responsibilities among all your classes.Provide the attributes and operations that are needed to carry out these responsibilities for each class.

Graphical Representation:

2) To model the distribution of responsibilities in a system:Identify a set of classes that work together closely to carry out some behavior.Identify a set of responsibilities for each of these classes.

Graphical Representation: 3) To model non-software things:

Model the thing you are abstracting as a class.If you want to distinguish these things from the UML's defined building blocks, create a new building block by using stereotypes to specify these new semantics and to give a distinctive visual cue.If the thing you are modeling is some kind of hardware that itself contains software, consider modeling it as a kind of node, as well, so that you can further expand on its structure.

Graphical Representation:

4) To model primitive types, Model the thing you are abstracting as a type or an enumeration, which is rendered using class notation with the appropriate stereotype.

Graphical Representation:

PAGE-9