UML Notations for Object-Oriented Software Development

This report discusses the importance of UML notations in object-oriented software development. It covers the different types of UML diagrams and their uses, system modeling, and its advantages. The report also includes examples of UML diagrams and their applications in software development.

Running Head: UML Notations 0
UML Notations
Report
Student name

UML Notations 1
Question A
Object-oriented (OO) approach is best approach for software development. It provides a
better solution for the different problems of software development. Unified Modeling Language
(Referred as UML) is providing better software platform for developing different applications.
Now days, UML is necessary for software development. It has different advantages for software
development.
System modeling is the process, which provides helps in developing models of system.
Every model is representing different perspective of particular system. It is an abstract view of a
system that is helpful for understanding the system workflow with different details. It is an
important factor of system modeling in object-oriented approach ( ELGABRY, 2017).
The UML is providing different model based on the graphical notations. These models
are used for analysis process for describing system requirements to the designer ( Ceta, 2019).
There are four perspectives are mainly considered for system modeling, which are as mention
below:
1. External perspective: it will provide details in context of the system environment.
2. Interaction perspective: it will provide interaction between different components
of a system or environment of a system.
3. Structural perspective: it will provide structure of the data, which are processes by
the system.
4. Behavioral perspective: it will provide dynamic behavior of the system and it
provides responses of the system for different events.
UML language is having different notations for designing of different models of a system
for better understanding of the environment of the system. Software development is based on the
requirements of system. It is so necessary to understand complete requirements of a system then
start software development. In case of OO approach, there is a huge requirement of system
modeling for understanding different perspectives of the system ( Oliver, 2017).

UML Notations 2
In many cases, there is lack of understanding of system requirements. Therefore, that
software is facing failure in future. Projects are failure because of less understanding of system
requirements. However, many projects are failure because of huge cost. All the problems are
generated because of lack of system modeling ( Pericherla, 2013).
System modeling is also accepts new challenges of business. It will provide changes in
the working of the system as well as module of the system. Developer can change in model of
the system as per user request. It is not having any cost. It is reduce loss of cost and time.
Sometimes, system is facing failure because of huge cost and taking long time to implement. It is
a way to reduce time and cost for software development.
UML is providing a system model for software development. Before starting of software
development, system model is providing all the details for designing and implementation
processes of the system. Therefore, user can change their requirements based on the system
model. Software developer can also change their mind for designing a system (Van Lamsweerde,
2009).
Object-oriented system development life cycle is having three macro processes, which
are analysis, design, and implementation. All these processes are required better understanding
and clarification by the programmer. Therefore, at the time of final handover of project, there
will be no issues in front of client as well as designer. Java is providing a better support to UML
diagrams for their generated source code (Bruegge, 2008).

UML Notations 3
QUESTION B
Unified Modeling Language (UML) is providing a system model for projects through
different diagrams or notations. UML is having different types of diagram for understanding the
requirement of the client for their project. UML diagram’s purpose is visually representing a
system along with classes, actors, artifacts, roles and actions. These diagrams are used for the
better understand different information about the system (Conallen, 2012).
Modeling is categorized in three parts, which are conceptual, logical, and physical.
Conceptual model is representation of the real world based on the user’s conception. It highlights
level of abstraction in the modeling hierarchy. Logical model shows what a system must do or
have, without regard for hoe it is to be done, built, and represented. Physical model is shows how
things will be done or built. It provides platform details, implementation details and data storage.
Business modeling is a domain model and requirements are fulfill in use-case model. Different
disciplines are having different artifacts for understand those things in better way (EXISTEK,
2017).
UML has been used for visual representation as well as general-purpose modeling
language in software development area. UML is having different types of language, such as
behavioral and structural UML diagrams. Both behavioral UML diagrams and structural UML
diagram are having also different diagram as shows in below diagram (Gomaa, 2011).

UML Notations 4
Source: (DRAW, 2019)
A class diagram is a basic diagram type for documentation in software development
process. Object-oriented programming approach is directly related class diagrams for software
development as it is based on the object and classes. Classes contain their attributes, which are
related to their data and behaviors that is member functions of that class and are related to each
other with a variety of connectors (Satzinger, Jackson, & Burd, 2011).
Source: Author

UML Notations 5
In above class diagram different classes are created for library management system.
Those classes are having data types and member functions. In the above diagram, student,
faculty member, alert, books, member, librarian, and catalog are classes that are uses in the
software development. Student class is having two data types, which are student name sName
and studentcoll. It has two functions, which are checkoutbk( ) and returnbk( ).
Book class is having sub fields for reference book and general book. These facilities are
used for understanding the requirements of a system. Member class is having two sub classes
that are student and faculty member. Therefore, all the process will be managed by the system.
Librarian can have different functions for managing library operation (Liang, 2003).
UML is famous and popular business process modeling approach for better understands
system requirements. It shows better flow of control and error in software development. UML is
used for the documentation of several workflows or processes of business. Use case diagrams are
created based on the requirements of the system. They represent different functions, actors and
their relationship (Larman, 2012).
Source: Author

UML Notations 6
Above use case diagram is designed for inventory system. It cover different use cases,
such as view availability, other products, delivery control, update product quality information,
make an invoice, view location information, and change products location. There are different
actors that are warehouse worker, supervisor, sales person, truck driver, forklift driver, and
customer. Use-cases are used as couplings of different classes from the requirements of the client
for software development (Jacobson, 1993).

UML Notations 7
QUESTION C
In this case, different use cases are designed for completing the requirements of the
system. In this case different actors are created, which are guest, member, customer service,
finance, database system, shoemaker, production manager, supplier, purchasing department,
courier, and shopping department (Powell-Morse, 2017).
Source: Author
In this use-case diagram, a product gallery is provided to customer, which is having
different types of product. All those products are having full description, such as quantities,
discount, original price, and price after discount. It provides shoes to customers in different size
that are available. Product can be search based on their size, price, and manufacturer.
It provides a facility to customers in which customers can easily add, edit, and delete
their cart. Customers can purchase multiple products with different categories. Customers can
select desired products as well as they can provide required shipping address for home delivery
of their selected products. It is also provide coupon codes for selected products for their

UML Notations 8
promotion. In this project, payment can be done though credit card or mayban2u.com.my portal.
This system is running for 24*7 with excellent security features.
References
Ceta, N. (2019). All You Need to Know About UML Diagrams: Types and 5+ Examples.
Retrieved from https://tallyfy.com: https://tallyfy.com/uml-diagram/
ELGABRY, O. (2017). Object-Oriented Analysis And Design — Introduction (Part 1). Retrieved
from https://medium.com: https://medium.com/omarelgabrys-blog/object-oriented-
analysis-and-design-introduction-part-1-a93b0ca69d36
Oliver, R. (2017). Why the Software Industry Has a Love-Hate Relationship with UML
Diagrams. Retrieved November 17, 2018, from
https://creately.com/blog/diagrams/advantages-and-disadvantages-of-uml/
Pericherla, S. (2013, Augest 5). Importance of Modeling. Retrieved from
https://www.startertutorials.com: https://www.startertutorials.com/uml/importance-of-
modeling.html
Bruegge, B. a. (2008). Object-Oriented Software Engineering Using UML, Patterns and Java (4
ed.). London: Prentice Hall.
Conallen, J. (2012). Building Web applications with UML. (6 ed.). New York: Addison-Wesley
Longman Publishing Co., Inc..
DRAW. (2019). UML diagrams – which diagram to use and why. Retrieved from
https://about.draw.io: https://about.draw.io/uml-diagrams/
EXISTEK. (2017). SDLC Models Explained: Agile, Waterfall, V-Shaped, Iterative, Spiral.
Retrieved November 22, 2018, from https://existek.com/blog/sdlc-models/
Gomaa, H. (2011). Software modeling and design: UML, use cases, patterns, and software
architectures. (2 ed.). New York: Cambridge University Press.

UML Notations 9
Jacobson, I. (1993). Object-oriented software engineering: a use case driven approach. (2 ed.).
New Delhi: Pearson Education India.
Larman, C. (2012). Applying UML and patterns: an introduction to object oriented analysis and
design and interative development. (5 ed.). New York: Pearson Education.
Liang, Y. (2003). From use cases to classes: a way of building object model with UML.
Information and Software technology, 45(2), 83-93.
Powell-Morse, A. (2017). Object-Oriented Analysis and Design: What is it and how do you use
it? Retrieved November 22, 2018, from https://airbrake.io/blog/design-patterns/object-
oriented-analysis-and-design
Satzinger, J., Jackson, R., & Burd, S. (2011). Systems analysis and design in a changing world
(6th ed.). New York: Cengage learning.
Van Lamsweerde, A. (2009). Requirements engineering: From system goals to UML models to
software (Vol. 10). (2 ed.). Chichester: John Wiley & Sons.