SAD

Assignment 1

Submitted by:
M Waqas Arif
70067876
Section T
Submitted to:
Resp. Sir Yahiyah sb

MARCH 31, 2021

UNIVERSITY OF LAHORE
➢ UML Diagrams
• UML is an acronym stands for Unified Modeling Language.
• UML is the graphical notation used to visualize and draw a model of software systems.
• UML is used to show the relationships, collaborations, and the activities that will be
performed by the software system.
• In easy words, you can say that it is the graphical representation of the whole software
system that helps the developers to understand what kind of software system they are
actually going to build.
• UML helps the developers to visualize the software system before they are going to build it.
• Through UML diagrams stakeholders can see what their software system will look like and
if they want to make any changes, they have the option to make them.

➢ Type of diagrams
• Use case diagram.
• Component diagram.
• Sequence diagram.
• State diagram.
• Activity diagram.
• Class diagram.

➢ Advantages
• UML saves a lot of time.
• UML save a lot of human effort.
• UML eases the development process.
• UML saves the developer from making unnecessary mistakes.

➢ Use case diagram

• Use case diagram is use to identify all types of user that are going to use the software
system.
• It shows the interaction of the user with the system in different scenario.
 • This diagram is also known as the blueprints of the system.
• It is used to gather the requirements.
• It is used to get an outside view of the system.

➢ Component diagram
• UML component diagram is used to wire small components together to form a larger
component.
• Component diagram is used to model physical aspects of a system.
 • This diagram is use to visualize the relationships and collaboration of components with one
another.
• It does not describe the functionality of the system but it describes the elements that are used
to build those functionalities.
• It is used during the implementation phase of the system.

➢ Sequence diagram
 • Sequence diagram shows the interaction between classes in terms of information exchange
over time.
• It is also known as event diagram.
• It is used to validate many runtime scenarios.
• This diagram helps to predict how the system that is going to build will behave.
• This diagram is also used to gather requirements by software engineers.

➢ State diagram
• State diagram is use to state the events responsible for change in state.
• It describes the behavior of a single object in response to a series of events in a system.
• It consists of states, transitions, events, and activities.
• It is also referred to as State machines.
• It shows the changes in state, not the processes that created those changes.
➢ Activity diagram
• Activity diagram is basically a flowchart.
• It represents the flow from one activity to another activity.
• It is also called object-oriented flowchart.
• It visually presents a series of actions or flow of control in a system.
• It has an initial state and a final state.
➢ Class diagram
• Class diagram is use to show many classes are going to be declared in coding phase.
• It also shows the attributes and functions in a class.
• It also shows the communication between the classes.
• It is the main building block of object-oriented modeling.
• Class diagrams can also be used for data modeling.