INSTITUTE OF SCIENCE & TECHNOLOGY

Chandrakona Town, Paschim Medinipur, W.B.

A Technical Report
for
CONTINUOUS ASSESSMENT 2 (CA2) OF ODD SEM 2024

Introduction to (TOPIC NAME)

PAPER NAME:
PAPER CODE:

Submitted by

(CANDIDATE NAME)
Registration no:
Examination roll no:

In
Department of Computer Science & Engineering
2024
 Table of contents

PAGE NO.

Abstract ..

1. Introduction ..

2. Methodology ..

3. Discussion ..

4. Conclusion ..

5. References ..

LIST OF THE FIGURES

PAGE NO.
FIGURE NO.

Figure 1.
Figure 2.
Figure 3.
Figure 4.
Abstract

UML, short 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 very
important part of developing object oriented software and the software development
process. The UML uses mostly graphical notations to express the designs of the
software projects. Using the UML helps project teams communicate, explore potential
designs, and validate the architectural design of the software. The goal of UML is to
provide standard notations that can be used by all object oriented methods and to select
and integrate the best elements of precursor notations. UML has been designed for a
broad range of applications. Hence, it provides constructs for a broad range of systems
and activities.

Key words: UML, self-administered surveys, visualizing, non-software systems,

business modeling
1. INTRODUCTION

The UML stands for Unified modeling language, is a standardized general-

purpose visual modeling language in the field of Software Engineering. It is used for
specifying, visualizing, constructing, and documenting the primary artifacts of the
software system. It helps in designing and characterizing, especially those software
systems that incorporate the concept of Object orientation. It describes the working of
both the software and hardware systems.

The UML was developed in 1994-95 by Grady Booch, Ivar Jacobson, and James
Rumbaugh at the Rational Software. In 1997, it got adopted as a standard by the
Object Management Group (OMG).
The Object Management Group (OMG) is an association of several companies that
controls the open standard UML. The OMG was established to build an open standard
that mainly supports the interoperability of object-oriented systems. It is not restricted
within the boundaries, but it can also be utilized for modeling the non-software
systems. The OMG is best recognized for the Common Object Request Broker
Architecture (CORBA) standards.

 Goals of UML

 Since it is a general-purpose modeling language, it can be utilized by all the

modelers.
 UML came into existence after the introduction of object-oriented concepts
to systemize and consolidate the object-oriented development, due to the
absence of standard methods at that time.
 The UML diagrams are made for business users, developers, ordinary
people, or anyone who is looking forward to understand the system, such
that the system can be software or non-software.
 Thus it can be concluded that the UML is a simple modeling approach that
is used to model all the practical systems

 Characteristics of UML

The UML has the following features:

 It is a generalized modeling language.
 It is distinct from other programming languages like C++, Python, etc.
 It is interrelated to object-oriented analysis and design.
 It is used to visualize the workflow of the system
2. METHODOLOGY
A software development will have many stakeholders playing a part.
For Example:
 Analysts
 Designers
 Coders
 Testers
 QA
 The Customer
 Technical Authors

1. During 1996, the first Request for Proposal (RFP) issued by the Object Management
Group (OMG) provided the catalyst for these organizations to join forces around
producinga joint RFP response.

2. Rational established the UML Partners consortium with several organizations willing to
dedicate resources to work toward a strong UML 1.0 definition. Those contributing most to
the UML 1.0 definition included:

 Digital Equipment Corp

 HP
 i-Logix
 IntelliCorp
 IBM
 ICON Computing
 MCI Systemhouse
 Microsoft
 Oracle
 Rational Software
 TI
 Unisys

3. This collaboration produced UML 1.0, a modeling language that was well-defined,
expressive, powerful, and generally applicable. This was submitted to the OMG in January
1997 as an initial RFP response.
4. In January 1997 IBM, ObjecTime, Platinum Technology, Ptech, Taskon, Reich
Technologies and Softeam also submitted separate RFP responses to the OMG. These
companies joined the UML partners to contribute their ideas, and together the partners
produced the revised UML 1.1 response. The focus of the UML 1.1 release was to
improve the clarity of the UML 1.0 semantics and to incorporate contributions from
the new partners. It was submitted to the OMG for their consideration and adopted in
the fall of 1997.1 and enhanced 1.1 to 1.5, and subsequently to UML 2.1 from 01 to 06
(now the UML current version is 2.5)

All of these people are interested in different aspects of the system, and each of them
requirea different level of detail. For example, a coder needs to understand the design of
the system and be able to convert the design to a low level code. By contrast, a
technical writer is interested in the behavior of the system as a whole, and needs to
understand how the product functions. The UML attempts to provide a language so
expressive that all stakeholders can benefit from at least one UML diagram.

UML is linked with object oriented design and analysis. UML makes the use of
elements and forms associations between them to form diagrams. Diagrams in UML
can be broadly classified as:

 Structural Diagrams
 Behavior Diagrams

A. Structure diagrams show the static structure of the system and its parts on
different abstraction and implementation levels and how they are related to each
other. The elements in a structure diagram represent the meaningful concepts of a
system, and may include abstract, real world and implementation concepts, there
are seven types of structure diagram as follows:

 Class Diagram
 Component Diagram
 Deployment Diagram
 Object Diagram
 Package Diagram
 Composite Structure Diagram
 Profile Diagram
B. Behavior diagrams show the dynamic behavior of the objects in a system, which
can be described as a series of changes to the system over time, there are seven
types of behavior diagrams as follows:

 Use Case Diagram

 Activity Diagram
 State Machine Diagram
 Sequence Diagram
 Communication Diagram
 Interaction Overview Diagram
 Timing Diagram

Fig 1: Timing Diagram

3. DISCUSSION

A. Structure Diagrams

 A 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 kindsof 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

acompany, 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.

Fig 2: Class Diagram Example

B. Component Diagram

In the Unified Modeling Language, a component diagram depicts how

components are wired together to form larger components or software systems. It
illustrates the architectures of The software components and the dependencies
between them. Those software components including run-time components, executable
components also the source code components.

Component Diagram Example

Fig 3: Deployment Diagram

C. Deployment Diagram

The Deployment Diagram helps to model the physical aspect of an Object-Oriented

software system. It is a structure diagram which shows architecture of the system as
deployment (distribution) of software artifacts to deployment targets. Artifacts
represent concrete elements in the physical world that are the result of a development
process. It models the run- time configuration in a static view and visualizes the
distribution of artifacts in an application. In most cases, it involves modeling the
hardware configurations together with the software components that lived on.

Fig 4: Deployment Diagram Example

 Unified Modeling Language (UML) is a general purpose modeling language.
The main aim of UML is to define a standard way to visualize the way a system has
been designed. It is quite similar to blueprints used in other fields of engineering.

UML is not a programming language, it is rather a visual language. We use

UML diagrams to portray the behavior and structure of a system. UML helps software
engineers, businessmen and system architects with modeling , design and analysis. The
Object Management Group (OMG) adopted Unified Modeling Language as a standard
in 1997. Its been managed by OMG ever since.

International Organization for Standardization (ISO) published UML as an

approved standard in 2005. UML has been revised over the years and is reviewed
periodically.

Do we really need UML

 Complex applications need collaboration and planning from multiple teams and hence
require a clear and concise way to communicate amongst them.
 Businessmen do not understand code. So UML becomes essential to communicate
with non programmers essential requirements, functionalities and processes of the
system.

A lot of time is saved down the line when teams are able to visualize processes,
user interactions and static structure of the system.

4. CONCLUSION
As the strategic value of software increases for many companies, the industry
looks for techniques to automate the production of software and to improve quality and
reduce cost and time-to-market. These techniques include component technology,
visual programming, patterns and frameworks. Businesses also seek techniques to
manage the complexity of systems as they increase in scope and scale. In particular,
they recognize the need to solve recurring architectural problems, such as physical
distribution, concurrency, replication, security, load balancing and fault tolerance.
Additionally, the development for the World Wide Web, while making some things
simpler, has exacerbated these architectural problems. The Unified Modeling Language
(UML) was designed to respond to these needs. The primary goals in the design of
the UML summarize by Page-Jones in Fundamental.
5. REFERENCES
[1] Fuentes-Fernández, L., & Vallecillo-Moreno, A. (2004). An introduction to
UML profiles. UML and Model Engineering, 2(6-13), 72.

[2] Miles, R., & Hamilton, K. (2006). Learning UML 2.0: apragmatic introduction
to UML. " O'Reilly Media, Inc.".

[3] Bell, D. (2003). UML basics: An introduction to the Unified Mo de lin g La

nguage.

[4] Müller, J. P., & Bommel, P. (2007). An introduction to UMLfor modeling in the
human and social sciences. Agent-based modelling and simulation in the social
and human sciences, 273-294.

[5] Seidl, M., Huemer, M. S. C., & Kappel, G. (2012). UML@ Classroom An
Introduction to Object-Oriented Modeling.