All About Static Modeling

About UML:UML is concerned for Unified modeling language. It is a standard language for creating blueprints that depict the structure and design of the software system.UML is a notational language that enables the stakeholders to view the architecture of the system from various perspectives. It is used for software designing we use many type of modeling to design the software. In that static modeling is one type of modeling which is used for software designing.

About Static Modeling:Static modeling is one type of modeling which is used for understand the physical structure of a software. The physical structure of a software system consists of classes, objects, interfaces& their relationships with each other. Static modeling used class diagrams and object diagrams both. In the Unified Modeling Language (UML), a class diagram is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, and the relationships between the classes.

Class Diagram:Class diagrams represent a set of classes, interfaces and their relationships. We can represent a class in a rectangular box with three compartments first compartment shows class name. The second compartment shows the attributes of the class and the third compartment shows the method associated with the class.

Object Diagram:An object diagram represents instances of a class diagram. We represent an object in a rectangular box with two compartments. The object name appears before the class name in first compartment. The second compartment shows the attribute of the objects. Student

Address

Name =Robert

Street = South ex.

Phone Number = +919718549

City = New Delhi

[email protected]

State = Delhi

Student Number = S07000200

Postal Code = 110016

Average mark = 70%

Country = India

Relationship between Class and Object Diagrams:In UML, A relationship is a general term covering the specific types of logically or physically connections. Found on class and objects diagrams

 Association:An Association represents a family of links. It represents the static relationship shared the object of two classes. An association may be unidirectional or bi-directional but by default association is bidirectional. Give Education for

Get education from

Association Relationship Has

Unidirectional Association Relationship 

Multiplicity:-

The association relationship indicates that (at least) one of the two related classes makes reference to the other. The UML representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity.’ Give Education for 1

Get education from

Multiplicity Relationship

*

 Aggregation:Aggregation represents an association between two classes such that class A is a part of class B and A can exist independently. Aggregation is a variant of the Association relationship. Belongs to

Aggregation Relationship

Composition:Composition represents an association between two classes such that class A contains class B and also control the lifetime of class B. It means that the existence of class B depends on class A. Has 

Dependency:-

Composition relationship

A dependency exists between two defined elements if a change to the definition of one would result in a change to the other. This is indicated by a dashed arrow pointing from the dependent to the independent element. Several named varieties exist. A dependency can be between instances, classes, or both. Dependency represents the semantic relationship between two classes it means a change in the attributes and operations of one class affects the attributes and operations of other class.

Dependency Relationship

Generalization:Generalization represents how super classes are related to sub classes. Super classes are called base classes and Sub classes are known as derived classes.

Realization:Realization represents In UML modeling, a realization relationship is a relationship between two model elements, in which one model element realizes the behavior that the other model element specifies. In realization one component specifies a contract and the other component implements the contract.

Realization Relationship

Type of Classes:Abstract class Parameterized class Factory class  Self-linked class

Abstract Class:An abstract class is a class that does not have any direct instances. However the classes inherited from an abstract class can have direct instances. An abstract class is used to define the common features and common behavior of a set of subclasses. The UML notation for an abstract class is same as simple class.

Parameterized Class:A Parameterized class, also called template class, provided a mechanism that enables you to use operations and classes to work with different data types. We cannot create the objects of a parameterized class. To use it there is a need of realize the parameterized class by using classes.



Factory Class:-

A class that has multiple objects having the same attribute values is known as a factory class. To represent the multiple objects of a factory class, we can use symbol of overlapping rectangles. Object Diagram for factory class 

Self-Linked Class:A class that has objects, which fulfill

more than one role, is called self-linked class. Object Diagram for Self-Linked Class

Recursive Aggregation and Qualified Association Relationship 

Recursive Aggregation:-

Recursive Aggregation is an association relationship between two objects of the same class.

Or

Developer

Project Manager Reports to

Recursive Aggregation in a Class Diagram Recursive Aggregation in an Object Diagram

Qualified Association:Qualified Association is an association relationship that relates an object of a class to a Particular object or a set of objects of another class. We use a value, known as qualifier to distinguish the objects of one class from another. A qualifier can be an attribute of the class. -----Qualified Class -----Qualifier

--------- Target Class Qualified Association

Derived Elements:In UML a derived element, can be derived from one or more other elements of the same type. We can use the derived elements to model an explicit detailed design.

Derived Attribute:We calculate the value of a derived attribute from the value of other attributes of the object. The formula to calculate the derived attribute is represented as a constraint in the class diagram. <>

Derived Attribute

Derived Association:We can deduce a derived association from the other associations in a class diagram. 1

1

/Works for

*

* 1 Works for

*

Derived Association

Interfaces:An interface is a collection of operation that is used to represent the services provided by a class or component. An interface provided the declaration of only the public methods and does not provide their implementation. As a result, interfaces do not contain attributes. Interfaces are similar to classes. Like classes interfaces are also contained in a package. We cannot crate objects of interfaces.

Creating Interfaces:In UML, an interface is represented as a circle. Each interface has a unique name that is prefixed with the name of the Package in which it is contained. Storage:: IFile Package name

interface name

Interface Name

UML Provides two notations to realize an interface:-

Lollipop notation:-

This notation shows the interfaces as a circle and displays the class that realizes the interface in a rectangle. The details of the operation contained in the interface or the class are not shown. Accept Input 

Dashed Arrow notation:-

Depict an interface as a class with the help of the <> keyword. The diagram also specifies the operations of the interfaces. A dashed arrow connects the class that realizes with the interface