what is srs?

Courier Management System Software Requirements Specification Version 1.0

Courier Management System

Software Requirement Specification

Version 1.0

Prepared By

Courier Management System Software Requirements Specification Version 1.0

Document Control Data Sheet

Project Code CMS

Project Name Courier Management System

Document Name Software Requirement Specification

Version 1.0

File Name CourierManagementSystem_SRS.doc

Classification Confidential

Client

Name Signature & Date

Prepared By

Reviewed By

Approved By

Distribution List

Courier Management System Software Requirements Specification Version 1.0

Revision History

Version Date Author Reviewer Change Description

Courier Management System Software Requirements Specification Version 1.0

Table of Contents 1. Introduction.......................................................................................................................5

1.1 Purpose.....................................................................................................................................5 1.2 Intended Audience................................................................................................................5 1.3 Product Scope.........................................................................................................................5 1.4 Definitions, acronyms and abbreviations......................................................................5 1.5 References...............................................................................................................................6

2. Overall Description........................................................................................................7 2.1 Product Perspective..............................................................................................................7 2.2 Product Functions..................................................................................................................7 2.3 User Classes............................................................................................................................7 2.4 Development Environment.................................................................................................8 2.5 Constraints...............................................................................................................................8 2.6 Assumptions and Dependencies.......................................................................................9

3. External Interface Requirements........................................................................10 3.1 User Interfaces.....................................................................................................................10 3.2 Hardware Interfaces...........................................................................................................10 3.3 Software Interfaces............................................................................................................10 3.4 Communications Interfaces.............................................................................................10

4. System Features............................................................................................................10 4.1 Use cases................................................................................................................................11 4.1.1 Use Case – 1: Login.........................................................................................................12 4.1.2 Use Case – 2: Logout......................................................................................................13 4.1.3 Use Case – 3: Search service availability.................................................................14 4.1.4 Use Case – 4: Book consignment...............................................................................16 4.1.5 Use Case – 5: Amount calculation..............................................................................18 4.1.6 Use Case – 6: Payment..................................................................................................20 4.1.7 Use Case – 7: Track status...........................................................................................21 4.1.8 Use Case – 8: View booking details...........................................................................23 4.1.9 Use Case – 9: Register complaint...............................................................................25 4.1.10 Use Case – 10: View complaint reply......................................................................26 4.1.11 Use Case – 11: View user details.............................................................................28 4.1.12 Use Case – 12: Update user details........................................................................30 4.1.13 Use Case – 13: Signup..................................................................................................31 4.1.14 Use Case – 14: View branch details..........................................................................33 4.1.15 Use Case – 15: View employee details....................................................................35 4.1.16 Use Case – 16: Edit branch details...........................................................................37 4.1.17 Use Case – 17: Edit employee details......................................................................39 4.1.18 Use Case – 18: Pickup...................................................................................................41 4.1.19 Use Case – 19: Delivery................................................................................................43 4.1.20 Use Case – 20: Non delivery details.........................................................................45 4.1.21 Use Case – 21: View complaint..................................................................................46 4.1.22 Use Case – 22: Complaint reply.................................................................................47 4.1.23 Use Case – 23: Generate report................................................................................49 4.1.24 Use Case – 24: Print barcode......................................................................................51

5. Other Nonfunctional Requirements...................................................................54 5.1 Performance Requirements................................................................................................54 5.3 Security Requirements.........................................................................................................54

Courier Management System Software Requirements Specification Version 1.0

1. Introduction

1.1 Purpose**

The purpose of the Software Requirements Specification document is to maintain all the functions and the specifications of “Website for study materials”. Besides it contains detailed descriptions of all the requirements specified.

1.2 Intended Audience **

Intended audience of the system include registered users, guest users, administrator.

1.3 Product Scope: **

This website is created in-order to help, aid and support the students, staffs, and other regarded personalities under the umbrella.

We provide you with Updated news, syllabus, curriculum, Announcements, Notification, Syllabus oriented materials and notes, Ordinance etc.. for any courses under any university.

1.4 Definitions, acronyms and abbreviations

1.4.1Abbreviations

CMS - Courier Management System SRS - Software Requirement Specification

1.4.2Definitions

Consignment: The parcel that has to be shipped or delivered.

Pickup staff: The user responsible for collecting the consignment from the sender and to ship the consignment.

Courier Management System Software Requirements Specification Version 1.0

Delivery staff: The user responsible for delivery of consignment.

1.5 References

IEEE Recommended Practice for Software Requirements Specifications-IEEE Std 830-1998.

Courier Management System Software Requirements Specification Version 1.0

2. Overall Description

2.1 Product Perspective

Courier Management System is independent and totally self. The CMS application is customizable and can be used by any courier company with minimal configuration changes.

2.2 Product Functions**

The various functionalities to be dealt by system are classified into different modules.

The proposed website shall have the following modules or functions:

 Sign Up Module  Login Module  Posting Module  Searching Module  Download Module

2.3 User Classes**

The users of this system will include the users, guest and administrator. The user classes for the system being developed have been broadly classified as follows. The actors of the 23 use cases mentioned listed below.

 Registered user  Guest  Admin

User Characteristics Registered user  Login

 Search availability of resources  Delete his uploaded resources  Download and upload resources  View already downloaded

resources

Courier Management System Software Requirements Specification Version 1.0

Guest  Download resources  Search for resources  Sign Up

Administrator  Login  Delete any resources and

Edit details  Download resources  View all resources

2.4 Development Environment

Development environment is as follows. Final decision on the development environment shall be taken during the design phase.

 ASP.NET  Database: Oracle 10g  Web Server: Apache HTTP Server  Business objects Reporting Services  Internet Explorer 7.0

2.5 Constraints

a. Regulatory Policies: NA b. Hardware Limitations: NA c. Interfaces to other application: An external interface for online bill

payment is provided. d. Parallel operations: NA e. Audit Functions: NA f. Control Functions: NA g. Safety and Security Considerations: The password and a valid

username are the security issues. The backup process at the server side shall satisfy data protection.

h. Reliability Requirements: Total number of bugs in the system shall not exceed 1% of the total line number of code, except connection reliability, which is out of range.

i. Criticality of the Application: The server applications shall be available 365 days.

Courier Management System Software Requirements Specification Version 1.0

2.6 Assumptions and Dependencies

The following assumptions are made with regard to this project:

 The user must have credit/debit cards or net banking facility for online booking

 It is assumed that the duration of the project is about 5 months, this is only a rough estimate.

 All the hardware and software requirements of the team to carry out the development activities are not finalised.

Courier Management System Software Requirements Specification Version 1.0

3. External Interface Requirements

3.1 User Interfaces

CMS is a web based online data entry and display system. All users interact with the system using user friendly Graphical User Interfaces (GUI). The formats of various GUIs like screens, web pages and reports of the system shall be furnished in the design document.

3.2 Hardware Interfaces

No hardware interface is required for the system.

3.3 Software Interfaces

Courier management system should integrate online payment interface to enable online transactions using net banking/debit card/credit card.

3.4 Communications Interfaces

Users will access the application using web browsers like Internet Explorer 7.0. The communication will be through standard HTTP protocol and SMTP protocol.

4. System Features This section gives the details of system features and functions identified as different use cases relevant for various users (or actors) of the system. The following sections group and specify the use cases according to the 5 user classes identified and listed under section 2.3.

Courier Management System Software Requirements Specification Version 1.0

4.1 Use cases

Courier Management System Software Requirements Specification Version 1.0

4.1.1 Use Case – 1: Login

Description:

The user can login to the system.

Actors:

The actors include registered user, admin and staff.

Precondition:

The User should be registered to the system.

Main Flow of Events:

1. The system prompts to enter username and password.

2. User enters username and password.

3. System validates username and password.

4. If the details are valid, user logs in to the system.

Alternate Flow of Events:

3.a. If the details are not valid, system displays invalid user message.

Post condition:

The system displays users home page.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Issue_Book

Renew_Book

Return_Book

Reserve_Book

Maintain_Catalog

Propose_New_Book

Borrow_Book Other Librarian

Librarian

Purchase_Book

Intimate_Book_Availability

Member

<<extend>>

<<extend>>

Special Requirements:

NA

4.1.2 Use Case – 2: Logout

Description:

The User can logout from system.

Actor:

The actors include registered user, admin and staff.

Precondition:

The User should be logged in to the system.

Main Flow of Events:

1. The user selects logout option.

2. System logout from users profile.

Courier Management System Software Requirements Specification Version 1.0

Alternate Flow of Events: NA

Post condition: NA

Relationships: NA

Activity Diagram:

Issue_Book

Renew_Book

Return_Book

Reserve_Book

Maintain_Catalog

Propose_New_Book

Borrow_Book Other Librarian

Librarian

Purchase_Book

Intimate_Book_Availability

Member

<<extend>>

<<extend>>

Special Requirements:

NA

4.1.3 Use Case – 3: Search service availability

Description:

The User can search service availability at a given destination.

Actors:

The actors include registered user, guest.

Precondition:

The User should be logged in to the system.

Courier Management System Software Requirements Specification Version 1.0

Main Flow of Events:

1. The user selects search availability option.

2. System prompts to enter destination and pincode.

3. System checks if service is available at the given destination.

4. If yes, system displays service available.

Alternate Flow of Events:

3a. If no, System displays service not available.

Post condition:

NA

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.4 Use Case – 4: Book consignment

Description:

The User can book consignment.

Actor:

The actors include registered user, guest.

Precondition:

The User should log in to the system.

Main Flow of Events:

Courier Management System Software Requirements Specification Version 1.0

1. The user selects book consignment option.

2. System prompts to enter destination address.

3. System checks if service is available at the given destination.

4. If yes, system prompts to enter consignment details.

5. System saves the consignment details.

Alternate Flow of Events:

3a. If no, System displays service not available. 3b. Goto 2.

Post condition:

System calculates amount from weight of the consignment entered

Relationships:

NA

Courier Management System Software Requirements Specification Version 1.0

Activity Diagram:

Special Requirements:

NA

4.1.5 Use Case – 5: Amount calculation

Description:

System calculates total price of consignment.

Precondition:

The User should add the consignment details.

Main Flow of Events:

1. System gets weight of consignment.

2. System multiplies the weight with standard rate per gram.

Courier Management System Software Requirements Specification Version 1.0

3. System displays the amount.

Alternate Flow of Events:

NA

Post condition:

System displays pay option

Relationships:

NA

Activity Diagram:

Special Requirements:

NA

4.1.6 Use Case – 6: Payment

Description:

Courier Management System Software Requirements Specification Version 1.0

User can make the payment.

Actors:

The actors include Registered user, guest.

Precondition:

The User should add the consignment details.

Main Flow of Events:

1. User selects pay option.

2. System redirects to payment interface.

3. Checks if payment is success.

4. If payment is success, redirects to confirmation page.

5. System generates consignment number and barcode.

6. Exit.

Alternate Flow of Events:

3.a. If payment not success, redirects to failure page. 3.b. 6

Post condition:

User receives consignment number and barcode.

Relationships:

Includes: Amount calculation

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Issue_Book

Renew_Book

Return_Book

Reserve_Book

Maintain_Catalog

Propose_New_Book

Borrow_Book Other Librarian

Librarian

Purchase_Book

Intimate_Book_Availability

Member

<<extend>>

<<extend>>

Special Requirements:

NA

4.1.7 Use Case – 7: Track status

Description:

User can track the status of consignment.

Actors:

Actors include Registered user, guest.

Precondition:

Courier Management System Software Requirements Specification Version 1.0

The User should book a consignment.

Main Flow of Events:

1. User selects track status option.

2. System prompts to enter consignment number.

3. System checks if consignment number is correct.

4. If yes, system displays consignment details.

5. Exit.

Alternate Flow of Events:

3.a. If no, system displays invalid consignment number. 3.b. goto 2

Post condition:

NA

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.8 Use Case – 8: View booking details

Description:

User can view the booking details.

Actors:

Actors include Registered user, guest, pickup staff, delivery staff.

Precondition:

The User should book a consignment.

Main Flow of Events:

1. User selects view booking details option.

Courier Management System Software Requirements Specification Version 1.0

2. System checks if there is any booking detail.

3. If yes, system displays booking details.

4. Exit.

Alternate Flow of Events:

3.a. If no, system displays no booking details. 3.b. goto 1

Post condition:

NA

Relationships:

NA

Activity Diagram:

Issue_Book

Renew_Book

Return_Book

Reserve_Book

Maintain_Catalog

Propose_New_Book

Borrow_Book Other Librarian

Librarian

Purchase_Book

Intimate_Book_Availability

Member

<<extend>>

<<extend>>

Special Requirements:

Courier Management System Software Requirements Specification Version 1.0

NA

4.1.9 Use Case – 9: Register complaint

Description:

User can register complaint about late delivery, damaged goods etc.

Actors:

The actors include Registered user, guest.

Precondition:

The User should be the direct participant of a consignment order.

Main Flow of Events:

1. User selects register complaint option.

2. System prompts to enter consignment number.

3. User enters consignment number.

4. System checks if consignment number is valid.

5. If valid, system prompts to enter complaint.

6. User enters complaint.

7. System saves complaint and generates complaint id.

8. Exit

Alternate Flow of Events:

5.a. If not valid, system displays invalid consignment number.

Post condition:

Complaint successfully registered.

Relationships:

NA

Courier Management System Software Requirements Specification Version 1.0

Activity Diagram:

Special Requirements:

NA

4.1.10 Use Case – 10: View complaint reply

Description:

User can view complaint reply by administrator.

Actors:

Courier Management System Software Requirements Specification Version 1.0

The actors include registered user, guest.

Precondition:

The User should register complaint.

Main Flow of Events:

1. User selects view complaint reply option.

2. System prompts to enter complaint id.

3. System checks if there is any reply.

4. If yes, system displays complaint reply.

5. Exit.

Alternate Flow of Events:

3.a. If no, system displays not received any replies.

Post condition:

NA

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.11 Use Case – 11: View user details

Description:

User can view user details.

Actors:

Actors include registered user.

Precondition:

The User should log in to the system.

Main Flow of Events:

1. User selects view user details option.

2. System displays user details.

Courier Management System Software Requirements Specification Version 1.0

3. Exit.

Alternate Flow of Events:

NA

Post condition:

User has viewed his/her details.

Relationships:

NA

Activity Diagram:

Special Requirements:

NA

Courier Management System Software Requirements Specification Version 1.0

4.1.12 Use Case – 12: Update user details

Description:

User can update user details.

Actors:

Actors include update user details.

Precondition:

The User should log in to the system.

Main Flow of Events:

1. User selects update user details option.

2. System navigates to user details page.

3. User updates the details

4. System saves the details

5. Exit.

Alternate Flow of Events:

NA

Post condition:

System updates user details successfully.

Relationships:

Include: View user details

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.13 Use Case – 13: Signup

Description:

User can signup or register.

Actors:

Actors include guest.

Precondition:

The User should have a valid mail id.

Main Flow of Events:

1. User selects signup option.

Courier Management System Software Requirements Specification Version 1.0

2. System prompts to enter details-mail id, username, password, name etc.

3. User enters the details.

4. System validates mail id.

5. If mail id is valid, system saves user details successfully.

Alternate Flow of Events:

4.a. If mail id is not valid, goto 2

Post condition:

User can log in to the system with username and password.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.14 Use Case – 14: View branch details

Description:

Administrator can view the branch details.

Actors:

Courier Management System Software Requirements Specification Version 1.0

Actor is administrator.

Precondition:

The Administrator should login to the system.

Main Flow of Events:

1. Admin selects view branch details option.

2. System prompts to enter branch code.

3. Admin enters branch code.

4. System checks if branch code is valid.

5. If yes, system displays branch details.

6. Exit

Alternate Flow of Events:

4.a. If no, system displays invalid branch code.

Post condition:

Administrator has viewed branch details.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.15 Use Case – 15: View employee details

Description:

Administrator can view the employee details.

Actors:

Actor is administrator.

Precondition:

The Administrator should login to the system.

Main Flow of Events:

Courier Management System Software Requirements Specification Version 1.0

1. Admin selects view employee details option.

2. System prompts to enter employee id.

3. Admin enters employee id.

4. System checks if employee id is valid.

5. If yes, system displays employee details.

6. Exit

Alternate Flow of Events:

NA

Post condition:

Administrator has viewed employee details.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.16 Use Case – 16: Edit branch details

Description:

Administrator can edit the branch details.

Actors:

Actor is administrator.

Courier Management System Software Requirements Specification Version 1.0

Precondition:

The Administrator should login to the system.

Main Flow of Events:

1. Admin selects edit branch details option.

2. System displays add, update and delete options.

3. Admin selects add, update or delete options.

4. Admin add branch details, update or delete branch details.

5. Exit

Alternate Flow of Events:

NA

Post condition:

Administrator successfully edits branch details.

Relationships:

Include: View branch details

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.17 Use Case – 17: Edit employee details

Description:

Administrator can edit the employee details.

Actors:

Actor is administrator.

Courier Management System Software Requirements Specification Version 1.0

Precondition:

The Administrator should login to the system.

Main Flow of Events:

1. Admin selects edit employee details option.

2. System displays add, update and delete options.

3. Admin selects add, update or delete options.

4. Admin add branch details, update or delete employee details.

5. Exit

Alternate Flow of Events:

NA

Post condition:

Administrator successfully edits employee details.

Relationships:

Include: View employee details

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.18 Use Case – 18: Pickup

Description:

Pickup staff can update shipping details of consignment.

Actors:

Actor is pickup staff.

Precondition:

Pickup staff should login to the system.

Courier Management System Software Requirements Specification Version 1.0

Main Flow of Events:

1. staff selects booking detail of consignment. 2. Staff updates the status of consignment to assigned or shipped. 3. System checks if the status is shipped 4. If status is shipped, system sends mail to user that consignment is

shipped. 5. Exit

Alternate Flow of Events:

3.a if status is not shipped, goto 5.

Post condition:

Staff successfully updates status of consignment.

Relationships:

Includes: View booking details.

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.19 Use Case – 19: Delivery

Description:

Delivery staff can update delivery details of consignment.

Actors:

Actor is delivery staff.

Precondition:

Delivery staff should login to the system.

Courier Management System Software Requirements Specification Version 1.0

Main Flow of Events:

1. Staff selects booking detail of consignment. 2. Staff updates the status of consignment to assigned, delivered or not

delivered. 3. System checks if the status of consignment is delivered or not

delivered. 4. If the status is delivered or not delivered, System sends mail to user

that consignment is delivered or not delivered. 5. Exit

Alternate Flow of Events:

3a. If no, goto 5

Post condition:

Staff successfully updates status of consignment.

Relationships:

Includes: View booking details. Extends: Non delivery details.

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.20 Use Case – 20: Non delivery details

Description:

Delivery staff can update details of not delivery of consignment.

Actors:

Actor is delivery staff.

Precondition:

Delivery staff should update status of consignment.

Main Flow of Events:

1. System checks the status of consignment. 2. If not delivered, system prompts to enter reason. 3. Staff updates the details of not delivery 4. Exit

Alternate Flow of Events:

1.a goto 4

Post condition:

Staff successfully updates details of not delivery.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements: NA

4.1.21 Use Case – 21: View complaint

Description:

Admin can view complaints.

Actors:

Actor is admin.

Precondition:

User should register complaint.

Main Flow of Events:

1. User selects view complaint option. 2. System displays complaint details. 3. Exit

Alternate Flow of Events:

Courier Management System Software Requirements Specification Version 1.0

NA

Post condition:

Admin has successfully viewed complaints.

Relationships:

NA

Activity Diagram:

Special Requirements:

NA

4.1.22 Use Case – 22: Complaint reply

Description:

Admin can reply to complaints.

Actors:

Actor is admin.

Precondition:

Courier Management System Software Requirements Specification Version 1.0

User should register complaint.

Main Flow of Events:

1. Admin selects reply to complaint option. 2. System prompts to enter reply to complaint. 3. Admin enters reply. 4. System saves reply. 5. Exit

Alternate Flow of Events: NA

Post condition:

System successfully saves complaint reply.

Relationships:

Includes: View complaint.

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.23 Use Case – 23: Generate report

Description:

Admin can generate report for a specific period.

Actors:

Actor is admin.

Precondition:

Admin should log in to system.

Courier Management System Software Requirements Specification Version 1.0

Main Flow of Events:

1. User selects generate report option. 2. System prompts to select period. 3. Admin selects period. 4. Admin clicks on generate option. 5. System displays report. 6. Exit

Alternate Flow of Events:

NA

Post condition:

Admin has successfully viewed report.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

4.1.24 Use Case – 24: Print barcode

Description:

Pickup staff can print the barcode of a consignment.

Courier Management System Software Requirements Specification Version 1.0

Actors:

Actor is pickup staff.

Precondition:

Staff should log in to system.

Main Flow of Events:

1. Staff selects booking details of the consignment. 2. Staff selects the print barcode option. 3. System prints the barcode. 4. Exit

Alternate Flow of Events:

NA

Post condition:

Pickup staff has taken print out of barcode.

Relationships:

NA

Activity Diagram:

Courier Management System Software Requirements Specification Version 1.0

Special Requirements:

NA

Courier Management System Software Requirements Specification Version 1.0

5. Other Nonfunctional Requirements

5.1 Performance Requirements

Major performance requirements are:

 All webpages should be loaded within 10 seconds  The system should handle 1000 users at a time

5.3 Security Requirements

The access to the software application will be restricted to the authorized users identified by a valid username and password. Guest users can register or signup to the system with a valid mail id. The users will be categorized into various roles like registered user, guest user, administrator, pickup staff, and delivery staff. The modules and functions accessible or available to the users will vary based on their roles. The users will be able to login to the application using the username and password and access the modules or functions based on their role.