Unified Modeling Language

Application Architect Program

Concept Note & Problem statement – Case study - Milestone 1

1
Index

S.No Topic Slide No.

1 Objective 3
2 Introduction to UML Notation 4-6
3 Objective of Developing UML Diagrams 7
4 Case Study Deliverables by the Candidate 8-17

2
Unified Modeling Language

Objective:
This case study will help the reader understand the UML and its
application on an application design task. It also shows how, modelling
language works in the field of software engineering and provides a
standard way to visualize the design of a system. Here reader can find a
case study of eCommerce application. Author has tried to explain it on a
step by step manner.

3
Unified Modeling Language

Introduction to UML Notation Name Symbol Description Variation

s/other
Name Symbol Description Variation related
s/other elements
related Active A class whose objects own a process
elements class or execution thread and therefore can
Description of a set of objects that - actors initiate a control activity on their own
Class share the same: attributes, operations,
relationships and semantics. - signals
Compon A component is a physical and
- utilities ent replicable part that conforms to and
Interface A collection of operations that specify a provides the realization of a set of
service of a class or component. interfaces.

Collabor An interaction and a society or roles Node A physical resource that exists in run
ation and other elements that work together time and represents a computational
to provide some cooperative behavior resource.
that is bigger than the sum of all the
elements. Represent implementation of
Interacti Set of messages exchanged among a
patterns that make up the system.
on set of objects within a particular context
to accomplish a specific purpose.
Actor The outside entity that communicates
State A behavior that specifies the
with a system, typically a person
machine sequences of states an object or an
playing a role or an external device
interaction goes through during its
lifetime in response to events, together
Use A description of set of sequence of with its responses to those events.
Case actions that a system perform that Package General purpose mechanism of
produces an observable result of value s organizing elements into groups.
to a particular actor. Used to structure
behavioral things in the model.
Note A symbol for rendering notes and
constraints attached to an element or a
collection of elements.

4
Unified Modeling Language

Introduction to UML Notation

5
Unified Modeling Language

Introduction to UML Notation

6
Developing UML diagram for
eCommerce Application
Objective:
• Provide standards for software development practice for Applications
• Reduce Development time
• Having a large visual element of the application via UML helps in
smooth development and keep the stakeholder in Sync
• Make the change management easier by reducing the change request
• Help to develop more memory and processor efficient systems

7
Case Study: eCommerce
Application - UML
Purpose:
Develop a Functional Block Logical view of an
eCommerce Application with its high-level functionalities.

Note:-
• The candidate needs to ideate on how to come-up with the Functional
Block Diagram
• It can be presented at a high level
• This diagram should have all possible, high level component of an
eCommerce application
• The remaining sections in this case study should be in sync with the
Functional block designed at this stage

8
Case Study: eCommerce
Application - UML
Purpose:
Develop an eCommerce Domain Model UML
Provides a high-level information flow between the
eCommerce functionalities
Note:-
eCommerce Domain Model is a conceptual model of the domain that
incorporates both behaviour and data in between the ecommerce
application

9
Case Study: eCommerce
Application - UML
Purpose:
UML for Customer Login (Sequence)
Provide a Sequence of how to log on to the store

Note:-
Customer will log on to the store to view & purchase item

10
Case Study: eCommerce
Application - UML
Purpose:
UML for online shopping: (Activity Based)
Provide an activity diagram for online shopping

Note:-
Online customer can browse or search items, view specific item, add it
to shopping cart, view and update shopping cart, do checkout.
User can view shopping cart at any time.

11
Case Study: eCommerce
Application - UML
Purpose:
Provide a UML diagram about how to edit shopping cart in
eCommerce application by customer

Note:-
Customer can add/delete/edit product details in the cart

12
Case Study: eCommerce
Application - UML
Purpose:
Business flow - Process order
Provide a business flow activity diagram to process
purchase order in the eCommerce application
Note:-
Requested order is an input parameter of the activity.
After order is accepted and all required information is filled in, payment
is accepted and order will be shipped.

13
Case Study: eCommerce
Application - UML
Purpose:
Class diagram for eCommerce Functionalities
Provide a business flow UML of the component level of
the application
Note:-
Class diagram, defines the functionalities for each component of the
ecommerce application. These components should be based on what is
identified by the candidates in the Model View & Domain Model
Diagram

14
Case Study: eCommerce
Application - UML
Purpose:
Static Model: Customer View UML
Provide a Static Model UML of the customer activities in
the eCommerce application
Note:-
This should give a high-level view of all activities which is performed by
the customer

15
Case Study: eCommerce
Application - UML
Purpose:
Complex Class UML for the eCommerce Application
Provide an Application level UML diagram

Note :-
This gives an application/system level UML Diagram. It is designed
keeping in mind the complete functionalities and component level UML

16
Case Study: eCommerce
Application - UML

During the presentation phase, candidates need to critically articulate

the benefit of preparing the UML for this eCommerce application

17
Disclaimer:
This case study don’t represent the actual system architecture or
system components. This is only for training purpose. It doesn’t
represent any client’s application & its confidential data.
Information are captured by our external SME from public
sources. This document is confidential to our client (HCL) Internal
Use only and not meant for commercial activities.
18