Sample Sds
Sample Sds
Sample sds
CHAPTER FOUR
SYSTEM DESIGN SPECIFICATION
4.0 Introduction
A System Design Specification is a document that details all the aspects that shall be input in the
system. It describes and shows all data, architectural, interface and component-level design for the
software. This chapter shall show the architecture of the proposed Courier Management System.
The design contains an explanation of a way to carry out each of the product specification written
in the Software requirement specification (SRS). The design will serve as a guide to the developer.
The SDS also shows how the program is separated into modules, how the modules interact with
each other and how users see the program.
4.1 Objective
The objective of this document is to be a reference for the implementers of the proposed system.
The document describes each application’s architecture and its associated interfaces and databases
design. This design will detail the implementation of the requirements as defined in the CMS
specification design.
4.2 System scope
Due to this, there exists an urgent need to shift the mode of manual operations to Automated
operations to a more efficient and reliable system which shall overall improve customer experience
and the performance of the business.
❖ Development of an online Courier Management System that shall handle the courier
services within the Logistics Department.
❖ Setting up the system on the main server ready for deployment.
❖ Training the users on how to use the new system.
❖ Request for an Administrator who shall configure the new Courier Management System.
4.2.2 Outputs:
(a) Enter parcel details
(b) Add new user
(c) Add new driver
(d) Courier client login
(e) Track parcel
4.3 Design Considerations and Constraints
• The client will be operating on Windows platform with a network connection to the
respective branch offices.
• The expected number of users is 200 Personnel.
• The system will require memory of at least 1GB of RAM, Processing speeds of 1.4GHz
and 1TB of available hard disk space.
4.4 Goals and Guidelines
• Simplicity: apply the KISS principle. Simplicity should be a key goal when designing and
avoid unnecessary complexities.
• Emphasis on speed versus memory use.
• Working, looking or feeling like an existing product-innovate rather than invent a product.
Start
User
Login
Enter Search/locate
parcel branch office
number
Main Menu
Display
Report Save data
stop
Courier
management
Customer
management
Delivery
Courier
management
tracking
system
Office management
Parcel
management Fleet management
This is at-a-glance view of the Delivery, office and Tracking showing the system as a single high-
level process with its relationship to external entities of courier, customer and manager.
This is a graphical step by step representation of how a user logs into the system.
start
User is registered
Check
Login ID
Invalid Login/Password
password
This shows the graphical step by step representation of how a user navigates in the main menu.
Start
Display selected
Menu Option
Start
User Login
Select add
shipment
Enter parcel
details
NO Correct parcel
Are customer
details details
correct?
YES
Print receipt
Submit
Parcel
reports
Logout
User Login
Receive Parcel
bookings
Check available
vehicles
Are
NO
Wait for
vehicles vehicles to be
available available
YES
Check available
drivers
NO
Are Wait for
drivers drivers to be
available available
YES
Print job tickets
Respond to booking
officer
logout
Login
Select vehicle
allocation
View vehicle
assigned
logout
• Data Normalization
• Data Dictionary
Telephone No. Years of Experience Sender Phone No. Receiver Phone No.
Destination Vehicle ID
VEHICLE Destination
Engine No.
Destination
Make
Model
Driver Name
Driver ID
ERD show how the entities identified in this section are mapped into tables of the database for the
Courier Management system software.
Department weight
Officer
1 N parcel
Books
parcel Sender
Name
Designation
sender Phone
Driver No
N ID
Receiver
Driver
ID No.
1
StaffID
Department
Assigned
to
Vehicle
Driver
Name
Vehicle ID
Number Plate
registration Destination
The database schema below is derived from the Entity-relation diagram above.
Designation Variable
Character
Name string
Department String
Category Text
Weight Decimal
Rate Float
Destination Text
Driver ID Number
Vehicle ID Integer
Destination Text
Sender name The name of the sender of String 100 No Identifies the No
parcel sender of the
parcel
Destination The place where the parcel String 20 No The unique Yes
is being sent. name of the
place where
the parcel is
being sent.
Driver Name The name of the driver String 50 No The name of Yes
the driver
employment
number
This section models the user interface view with which user interact in-order to use the software.
It is designed such a way to provide the user with insight into the software
LOG IN FORM
Username:
Password:
Office :
OK CANCEL
SEARCH BOX
Search GO