Case Study

On
Courier Management System

Prepared by:
Hussamuddin Noorani (17030141026)
Kirat Thakar (17030141033)
Page 1
 Rishi Mukherje (17030141062)
INDEX

S.no Content Page

no

1. Scope 3

1.1 3

1.2 Organization 3

2. Software Requirement Specification 4

3. Activity Diagram 5

4. Use Case Diagram 9

5. UML Interaction Diagram (Sequence and Collaboration Diagram) 12

6. State Chart Diagram 21

7. UML Class Diagram 23

8. Component Diagram 27

9. Deployment Diagram 29

Page 2
Scope :
1. Audience :
Customers, Administrators, Head office.

2. Organization :
COURIER MANAGEMENT SYSTEM

Page 3
 2. Software Requirement Specification:
 System Abstract –

The Courier management system facilitates the user to send parcel to international or
local destination, status of delivery, maintenance & retrieval of records and many more.
The major functionality of system is to allow the customer to send parcel, cancellation of
order, status of delivery.
It also provides the administrator to modify existing order or to introduce a new
customer’s in the system.

 Major features provided by the system are:

 Create New Order

The system allows the admin to create new order and order packets depending upon
the services i.e. International or Local.

 Add Customer
It allows the admin to add a customer so that he can send the parcel.

 Verify and Sort

The system allows the admin to verify the parcel for calculation of charges and sort
the parcel on basis of the destination.

 Assign
The functionality is used by the admin to assign the parcel to the delivery person or
send it to Head Office.

 Check Status
The system allows the customer/admin to check the status and track the shipment of
the parcel.

 Cancellation
The system allows the customer/admin to cancel the order if the order is not yet
delivered.

 Transaction Report
The system allows the admin to generate the summary report of the order as when
required.

Page 4
1. Use-Case Diagram. Documentation?

 The use-case concept was introduced by Ivar Jacobson in the object-oriented software
engineering (OOSE) method.
 A use-case diagram is a graph of actors, a set of use cases enclosed by a system
boundary, communication (participation) associations between the actors and the use
cases, and generalization among the cases.
 Use case diagrams show how users interact with the system.
 Use case diagrams describe what a system does from the standpoint of an external
observer. The emphasis is on what a system does rather than how.

 Used during requirements elicitation to represent external behavior

 Actors represent roles, that is, a type of user of the system
 Use cases represent a sequence of interaction for a type of functionality
 The use case model is the set of all use cases. It is a complete description of the
functionality of the system and its environment.

Page 5
 Use Case Diagram
1) Admin Login

Page 6
 2) SEARCH BRANCH

3)NEW COURIER

Page 7
4) BRANCH MANAGER LOGIN

Page 8
5) DISPATCH COURIER

Page 9
6) SHIPPING STATUS

7) DESTINATION BRANCH

Page 10
8) REPORT GENERATION

9) FEEDBACK

Page 11
Page 12
7. CLASS Diagram :

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of
a system but also for constructing executable code of the software application.

The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling
of object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages.

The class diagram shows a collection of classes, interfaces, associations, collaborations

and constraints. It is also known as a structural diagram.

Page 13
.

Draw using mvc

Page 14
Activity Diagram. Draw for each use case

• An Activity diagram is a visual representation of any system's activities and flows of

data or decisions between activities.
• Activity diagrams provide a very broad view of a business process.
• They represent the dynamics of a system.
• They are flow charts that are used to show the work flow of a system.
• They show the flow of control from activity to activity in the system.
• They show what activities can be done in parallel, and any alternative paths through
the flow.

Page 15
Page 16
5 UML Interaction Diagram (Sequence And Collaboration Diagram).

SEQUENCE Diagram

A sequence diagram is an interaction diagram that details how operations are carried out
-- what messages are sent and when. Sequence diagrams are organized according to time.
The time progresses as you go down the page. The objects involved in the operation are
listed from left to right according to when they take part in the message sequence.

Sequence diagrams contain the following:

– Class roles (subsystem/object/class, actor, and external system roles in the

interaction). These are (usually) drawn across the top of the diagram.
– Lifelines (subsystem/object/class existence). These (usually) extend down the
diagram.
– Activations (show when the subsystem/object/class is doing something)
– Messages (communication between roles)

Page 17
 Create new order:

:Customer :Order
: Customer : Admin : Head Office
:Order Packet Transaction

Visits
createCust(cust_info) :Order :Services

status=chkStatus(cust_name)

sendParcel()
createOrder(order_info) chkQty(id,qty)
chkPrice()
chkType()

chkService()
orderDetails()
sendConfirmation() sendCourier()

Page 18
Delivery charges:

:Order :Order Packet :Services :Order

: Customer : Admin
Transaction

getOrder()
chkType(Orderid,Itemid)

chkWt()

calcAmt(type,wt)

createTrans(orderid,Amt)

produceChrgs(trans)

Page 19
Status:

:Order :Order Packet :Shipment

: Customer : Admin

Status()
getDetails(id)

getItemDetails(itemid,orderid)
getStatus(itemid)

ShipmentDetails()

Page 20
Cancel order:

:Order :Order Packet :Order

: Customer : Admin
Transaction
cancelRequest()
chkOrder(Orderid)
chkStatus()

cancelItem()

orderStatus()

canTransaction()
cancelConfirm()

Page 21
Record details:

:Order :Order Packet :Shipment

: Admin

getOrderId()
getItem(orderid,itemid)

statusofDel(itemid,orderid)

getStatus()

Page 22
COLLABORATION Diagram -

Collaboration diagrams are also interaction diagrams. They convey the same
information as sequence diagrams, but they focus on object roles instead of the times that
messages are sent. In a sequence diagram, object roles are the vertices and messages are
the connecting links.

 Collaboration diagrams show (used to model) how objects interact and their roles.
 They are very similar to sequence diagrams. Actually they are considered as a cross
between class and sequence diagram.
 Sequence Diagrams are arranged according to Time.
 Collaboration Diagrams represent the structural organization of object.
 [Both sequence and collaboration diagrams are called interaction diagrams]
 Forms a context for interactions
– May realize use cases
– May be associated with operations
– May describe the static structure of classes
 Collaboration diagrams contain the following:
– Class roles (subsystems/objects/classes/actors/ external systems) as before.
– Association roles (pathways or links over which messages flow)
– Message flows (messages sent between class roles)

Page 23
Page 24
Page 25
Page 26
Page 27
6 STATECHART Diagram :

A Statechart diagram describes a state machine. Now to clarify it state machine can be
defined as a machine which defines different states of an object and these states are
controlled by external or internal events.

Page 28
8. Component Diagram

Component diagrams are different in terms of nature and behavior. Component diagrams
are used to model physical aspects of a system.

Physical aspects are the elements like executables, libraries, files, documents etc which
resides in a node.

So component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems.

Modify as per your project, don’t copy

Page 29
9. Deployment Diagram add components within deployment node

Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.

So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.

Object Diagram
In the Unified Modeling Language (UML), an object diagram focuses on some particular set
of objects and attributes, and the links between these instances. A correlated set of object diagrams
provides insight into how an arbitrary view of a system is expected to evolve over time.

Page 30
Page 31