Scribd
Upload
109 views

Assignment

This document is an assignment submitted by Muhammad Haseeb Farooq for the class BSSE 5(A). It discusses Unified Modeling Language (UML) which is a standard modeling language used to visually represent systems. UML uses diagrams to show different aspects of a system such as classes, activities and interactions. There are behavioral diagrams like activity diagrams and structural diagrams like class diagrams. UML was created in the 1990s to standardize software documentation and has become widely used in software engineering and business process modeling.

Uploaded by

sana farooq
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
109 views

Assignment

This document is an assignment submitted by Muhammad Haseeb Farooq for the class BSSE 5(A). It discusses Unified Modeling Language (UML) which is a standard modeling language used to visually represent systems. UML uses diagrams to show different aspects of a system such as classes, activities and interactions. There are behavioral diagrams like activity diagrams and structural diagrams like class diagrams. UML was created in the 1990s to standardize software documentation and has become widely used in software engineering and business process modeling.

Uploaded by

sana farooq
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Assignment

Name Muhammad Haseeb Farooq

Roll No Fa17-BSSE-191

Class BSSE 5(A)

Assignment Software Design and Architecture

Submitted to Rubaas Qaiser


Unified Modeling Language (UML)
 A UML diagram is a diagram based on the UML (Unified Modeling Language) with the
purpose of visually representing a system along with its main actors, roles, actions,
artifacts or classes, in order to better understand, alter, maintain, or document
information about the system.
 UML is an acronym that stands for Unified Modeling Language. Simply put, UML is a modern
approach to modeling and documenting software. In fact, it’s one of the most popular business
process modeling techniques.
 It is based on diagrammatic representations of software components. As the old proverb says:
“a picture is worth a thousand words”. By using visual representations, we can better
understand possible flaws or errors in software or business processes.

HISTORY
 UML was created as a result of the chaos revolving around software development and
documentation. In the 1990s, there were several different ways to represent and document
software systems. The need arose for a more unified way to visually represent those systems
and as a result, in 1994-1996, the UML was developed by three software engineers working at
Rational Software. It was later adopted as the standard in 1997 and has remained the standard
ever since, receiving only a few updates.

USE
 Mainly, UML has been used as a general-purpose modeling language in the field of software
engineering. However, it has now found its way into the documentation of several business
processes or workflows. For example, activity diagrams, a type of UML diagram, can be used as
a replacement for flowcharts. They provide both a more standardized way of modeling
workflows as well as a wider range of features to improve readability and efficacy.

UML itself finds different uses in software development and business process documentation

Sketch
 UML diagrams, in this case, are used to communicate different aspects and characteristics of a
system. However, this is only a top-level view of the system and will most probably not include
all the necessary details to execute the project until the very end.
 Forward Design
 The design of the sketch is done before coding the application. This is done to get a
better view of the system or workflow that you are trying to create. Many design issues
or flaws can be revealed, thus improving the overall project health and well-being.
 Backward Design
 After writing the code, the UML diagrams are drawn as a form of documentation for the
different activities, roles, actors, and workflows
TYPES OF UML DIAGRAMS
 Behavioral UML Diagram
 Activity Diagram
 Use Case Diagram
 Interaction Overview Diagram
 Timing Diagram
 State Machine Diagram
 Communication Diagram
 Sequence Diagram

 Structural UML Diagram


 Class Diagram
 Object Diagram
 Component Diagram
 Composite Structure Diagram
 Deployment Diagram
 Package Diagram
 Profile Diagram
 EXAMPLES
 Class Diagram
Client
+name
+address
+employment

+owns()

Account
+type
+owner
+account_number

Checking Account
+balance
+withdrawal_limit Saving Account

+debit() +balance
+credit() +rate
+withdraw() +debit()
+credit()
 Activity Diagram
 Use Case Diagram

You might also like