Assignment no 1:
Software engineering
Submission date (Dec 22, 2022)
By :
Zahid Masood (22017156-020)
Talha Ijaz (22017156-01)
Shahzad Mazhar (22017156-024)
BS Information Technology induction
(5th semester)
SUBMITTED TO :
Sir Adeel Shahzad
Department of information Technology
UNIVERSITY OF GUJRAT
(HAFIZ HAYAT CAMPUS)
What is Unified Modeling Language (UML)?
UMLshort for Unified Modeling Language, is a standardized modeling language
consisting of an integrated set of diagrams, developed to help system and software
developers for specifying, visualizing, constructing, and documenting the artifacts of
software systems, as well as for business modeling and other non-software systems.
The UML represents a collection of best engineering practices that have proven
successful in the modeling of large and complex systems. The UML is a very
important part of developing object oriented software and the software development
process. The UML uses mostly graphical notations to express the design of software
projects. Using the UML helps project teams communicate, explore potential designs,
and validate the architectural design of the software. In this article, we will give you
detailed ideas about what is UML, the history of UML and a description of each UML
diagram type, along with UML examples.
OR :
The Unified Modeling Language is a general-purpose, developmental modeling
language in the field of software engineering that is intended to provide a standard way
to visualize the design of a system.
Class Diagram:
The class diagram is a central modeling technique that runs through nearly all object-
oriented methods. This diagram describes the types of objects in the system and
various kinds of static relationships which exist between them.
Relationships:
There are three principal kinds of relationships which are important:
1. Association - represent relationships between instances of types (a person
works for a company a company has a number of offices.
2. Inheritance - the most obvious addition to ER diagrams for use in OO. It has
an immediate correspondence to inheritance in OO design.
3. Aggregation - Aggregation, a form of object composition in object-oriented
design.
Class Diagram Example
Domain model:.
In software engineering, a domain model is a conceptual model of the domain that
incorporates both behavior and data. In ontology engineering, a domain model is a
formal representation of a knowledge domain with concepts, roles, datatypes,
individuals, and rules, typically grounded in a description
State model:
state Testing is basicallya box testing technique that is carried out to observe the
behavior of the system or application for different input conditions passed in a
sequence. In this type of testing, both positive and negative input values are provided
and the behavior of the system is observed.
Sequence Diagram:
The Sequence Diagram models the collaboration of objects based on a time
sequence. It shows how the objects interact with others in a particular scenario of a
use case. With the advanced visual modeling capability, you events which you have
defined in the use case description can create complex sequence diagram in few
clicks. Besides, some modeling tool such as Visual Paradigm can generate sequence
diagram from the flow of
Sequence Diagram Example
Use-case diagrams
In UML, use-case diagrams model the behavior of a system and help to capture the
requirements of the system.
Use-case diagrams describe the high-level functions and scope of a system. These
diagrams also identify the interactions between the system and its actors. The use
cases and actors in use-case diagrams describe what the system does and how the
actors use it, but not how the system operates internally.
Use-case diagrams illustrate and define the context and requirements of either an entire
system or the important parts of the system. You can model a complex system with a
single use-case diagram, or create many use-case diagrams to model the components
of the system. You would typically develop use-case diagrams in the early phases of a
project and refer to them throughout the development process.
Use-case diagrams are helpful in the following situations:
Before starting a project, you can create use-case diagrams to model a
business so that all participants in the project share an understanding of the
workers, customers, and activities of the business.
While gathering requirements, you can create use-case diagrams to capture the
system requirements and to present to others what the system should do.
During the analysis and design phases, you can use the use cases and actors
from your use-case diagrams to identify the classes that the system requires.
During the testing phase, you can use use-case diagrams to identify tests for
the system.
The following topics describe model elements in use-case diagrams:
Use cases
A use case describes a function that a system performs to achieve the user’s
goal. A use case must yield an observable result that is of value to the user of
the system.
Actors
An actor represents a role of a user that interacts with the system that you are
modeling. The user can be a human user, an organization, a machine, or
another external system.
Subsystems
In UML models, subsystems are a type of stereotyped component that
represent independent, behavioral units in a system. Subsystems are used in
class, component, and use-case diagrams to represent large-scale components
in the system that you are modeling.
Relationships in use-case diagrams
In UML, a relationship is a connection between model elements. A UML
relationship is a type of model element that adds semantics to a model by
defining the structure and behavior between the model elements
For example, this use case diagram depicts the different
functions of a banking system for customers:
As an example, this use case diagram portrays how an ATM system
will behave or react when a customer or administrator performs an
action.
