You are on page 1of 5

18.UML - What is UML?

- UML is Unified Modeling Language which is a standardized modelling language which


enables the developers to specify, visualize, construct and document artifacts of a
software system.
- It is a graphical language used for visualizing artifacts of the system.
- It allows to create a blue print of all the aspects of the system

19.what is modeling.what are the advantages of creating a model?


- Model is a simplification of reality.
- Blueprint of the actual system.
- Specify the structural and behavior of the system.
- Templates for designing the system.
- Helps document the system

advantages
- Provides standard for software development.
- Reducing of costs to develop diagrams of UML using supporting tools.
- Development time is reduced.
- The past faced issues by the developers are no longer exists.
- Has large visual elements to construct and easy to follow.

22.What are the three types of modeling in UML?


The three types of modeling in UML are as follows:
1. Structural modeling:

- It captures the static features of a system.


- It consists of the following diagrams:
1. Classes diagrams
2. Objects diagrams
3. Deployment diagrams
4. Package diagrams
5. Composite structure diagram
6. Component diagram

- This model represents the framework for the system and all the components exist
here.
- It represents the elements and the mechanism to assemble them.
- It never describes the dynamic behavior of the system.

2. Behavioral modeling:

- It describes the interaction within the system.


- The interaction among the structural diagrams is represented here.
- It shows the dynamic nature of the system.
- It consists of the following diagrams:
1. Activity diagrams
2. Interaction diagrams
3. Use case diagrams
- These diagrams show the dynamic sequence of flow in the system.

3. Architectural modeling:

- It represents the overall framework of the system.


- The structural and the behaviour elements of the system are there in this system.
- It is defined as the blue print for the entire system.
- Package diagram is used.

What are the different views in UML?


- Use Case view - Presents the requirements of a system.
- Design View - Capturing the vocabulary.
- Process View - Modeling the systems processes and threads.
- Implementation view - Addressing the physical implementation of the system.
- Deployment view - Model the components required for deploying the system.

25.what is SDLC?
- SDLC is Software Development Life Cycle.
- SDLC of a system included processes like Use case driven, Architecture centric,
Iterative and Incremental.
- This Life cycle is divided into phases.
- Phase is a time span between two milestones.
- The milestones are Inception, Elaboration, Construction, and Transition.
- Process Workflows that evolve through these phase are Business Modeling,
Requirement gathering, Analysis and Design. Supporting Workflows are configuration,
change management, and project management.

23.Explain the types of diagrams in UML.


We have nine types of diagram in UML.

Use Case Diagram


Use Case Diagram describes HOW the system works. It identifies the primary
elements and processes that form the system. It shows actors and their roles

Class Diagram
This diagram explores detail design of the system. The class diagram is designed
using Use Case diagram. We can identify all Nouns in use cases as classes and
verbs as method of the classes.

Object diagram
This diagram represents the state of classes in the system and their relationships
or associations at a specific point of time.

State Diagram
This diagram represents different states that objects in the system undergo during
their life cycle.

Sequence diagram
This diagram is used to explore logic of complex operations, function or procedure.
In this diagram, sequence of the interactions between the objects is represented
step by step.

Collaboration diagram
This diagram groups together the interaction between different objects.

Activity diagram
Activity diagram gives detail view of the business logic.

Deployment diagram
It shows deployment view of the system. It shows how hardware and software works
together to run system.

20.what are the different views that are considesred when building an object-
oriented software system.
Building block of UML

Things

- Structural Things
- Behavioral things
- Grouping things
- Annotational things

Relationships

- Dependency
- Association
- Generalization
- Realization

Diagram

- Class Diagram
- Object Diagram
- Use case Diagram
- Sequence Diagram
- Collaboration Diagram
- Statechart Diagram
- Activity Diagram
- Component Diagram
- Deployment Diagram

26.What are Relationships in UML?


- Dependencies, Generalization, and Association.
- Dependencies -a change in specification of one thing may affect another thing.
- Generalization-class subclass scenario, one entity inherits from other.
- Associations-a room has walls, person works for a company.

Dependency
Dependency is the relationship between two things in which a change in one thing
may affect the other thing, but not necessarily the reverse. Graphically, it can be
represented as a dashed directed line, directed to the thing being depended on.

Association
An association is a relationship that connects classes. Example of association is
relationship between person and company. An association is rendered as solid line.

Adornments of association

Name: You can use Name to specify the nature of association


Role: Each class has specific role that participates in the relationship. We can
specify role to the classes involve in the relationship.
Multiplicity: It represents how many objects may be connected across an instance of
an association.
Aggregation: It implies whole/part relationship where one class represents larger
thing which consists of smaller things.

Generalization
In this type of relationship, the child shares the structure and behavior of the
parent. It is represented as a solid line with a hollow arrowhead pointing to the
parent.

Realization
A realization is a relationship where one class specifies a contract which another
class carries out. This kind of interface can be found out between the interface
and the class.

21.Define diagrams in UML?


Graphical representation of a set of elements.

23.Mention the different kinds of modeling diagrams used in UML?


Modeling diagrams that are commonly used are:

Use case diagram, Class Diagram, Object Diagram, Sequence Diagram, statechart
Diagram, Collaboration Diagram, Activity Diagram, Component diagram, Deployment
Diagram.

27.How are the diagrams divided in UML?

The nine diagrams are divided into static diagrams and dynamic diagrams.

Static Diagrams (Structural Diagram): Class diagram, Object diagram, Component


Diagram, Deployment diagram.

Dynamic Diagrams (Behavioral Diagrams): Use Case Diagram, Sequence Diagram,


Collaboration Diagram, Activity diagram, Statechart diagram.

6.can u explain class diagram.


- Class diagram represents a set of classes, interfaces and collaborations and
their relationships.
- Class diagram includes classes, interfaces, collaborations and their
relationships.
- It can be used to model : Collaboration of classes & Database schema.
- It is one of the most common diagrams used.
- The object view of a system in static nature is represented.
- The concurrency of the system is represented by the active class used in this
diagram.
- It is generally used for development purpose.
- It is one of the most widely used diagram during the system construction

16.can u explain object diagram?


- Object diagram represents a set of objects and their relationships.
- It involves objects and links in the diagram.
- An object diagram can be understood as an instance of a class diagram.
- It is used to model object structure.
- They are derived from the class diagrams and are dependent on the class diagrams.
- It represents the instance of the class diagram.
- It also represents the static view of the system which is a snapshot of the
system.
- They are used to render a set of objects and their relationships as instance

2.can you explain use case diagram?


- A use case diagram depicts different users of the system and the functions of the
system. Actors interact with a use case and the functions are called as use cases.
Use cases diagrams describe the interaction between the actor and the use case.
- Use case diagram expose the requirements of the system.
- For e.g. a use case diagram for an ATM would involve the actor to be ATM and the
user. Use cases could be, withdraw money, deposit cheque

17.can you explain Sequence Diagram?


- Sequence Diagram shows structural organization of the objects that send and
receive messages.
- A sequence diagram emphasizes the time ordering of messages.
- The object that initiates the interaction placed at the left and more subordinate
objects to the right.
- It shows how the objects will interact with each other in a given situation.
- It passes from top to bottom.
- They are popularly used to document the dynamics in the object oriented system.

You might also like