Table of Contents

Table of Contents ...........................................................................................................................1 Revision History .............................................................................................................................1 1. Introduction ................................................................................ Error! Bookmark not defined.
1.1 1.2 1.3 1.4 1.5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 3.1 3.2 3.3 3.4 4.1 4.2 4.3 5.1 5.2 5.3 5.4 5.5 Purpose .......................................................................................Error! Bookmark not defined. Document Conventions ..............................................................Error! Bookmark not defined. Intended Audience and Reading Suggestions.............................Error! Bookmark not defined. Product Scope .............................................................................Error! Bookmark not defined. References ..................................................................................Error! Bookmark not defined.

2. Overall Description .................................................................... Error! Bookmark not defined.

Product Perspective ....................................................................Error! Bookmark not defined. Product Functions .......................................................................Error! Bookmark not defined. User Classes and Characteristics ................................................................................................. 5 Operating Environment ..............................................................Error! Bookmark not defined. Design and Implementation Constraints.....................................Error! Bookmark not defined. Project Documentation ...............................................................Error! Bookmark not defined. User Documentation .................................................................................................................... 7 Assumptions and Dependencies .................................................................................................. 7 User Interfaces ............................................................................Error! Bookmark not defined. Hardware Interfaces....................................................................Error! Bookmark not defined. Software Interfaces .....................................................................Error! Bookmark not defined. Communications Interfaces ........................................................Error! Bookmark not defined. System Feature 1 ........................................................................Error! Bookmark not defined. System Feature 2 ........................................................................Error! Bookmark not defined. System Feature 3 (and so on) .....................................................Error! Bookmark not defined.

3. External Interface Requirements ............................................. Error! Bookmark not defined.

4. System Features ......................................................................... Error! Bookmark not defined.

5. Other Nonfunctional Requirements ......................................... Error! Bookmark not defined.

Performance Requirements.........................................................Error! Bookmark not defined. Safety Requirements ...................................................................Error! Bookmark not defined. Security Requirements................................................................Error! Bookmark not defined. Software Quality Attributes ........................................................Error! Bookmark not defined. Business Rules ............................................................................Error! Bookmark not defined.

6. Other Requirements .................................................................. Error! Bookmark not defined. Appendix A: Glossary...................................................................... Error! Bookmark not defined. Appendix B: Analysis Models ......................................................... Error! Bookmark not defined. Appendix C: To Be Determined List .............................................. Error! Bookmark not defined.

Revision History
Name Date Reason For Changes Version

1. Introduction
1.1 purpose
Sri Derana Cab service is the one of the leading cab service in Sri Lanka, which has 13 branches in whole the island. They have been using a manual system (Paper based system and File based system) for their day-to-day processes. Since using a manual system head office has to be patient for calculate profit of each month until they get the particular reports of each branch. We were assigned to come up with web-based system to overcome those problems, which were arisen due to manual system.

1.2 Document Conventions

We have used Times New Roman font style (size 12) for entire document. For the Main Headings Times New Roman font style with size 18. For the Sub Headings Times New Roman font style with size 14. The diagram naming process has handled using Times New Roman

1.3 Intended Audience and Reading Suggestions

The intended readers for this document are as follows: The Owner & staff of the Sri Derana Cab Service. The Lecture-in-charge & project supervisor from SLIIT. Team Members.

SRS document will be examined by above parties frequently to check the process goes in order to requirements. If any changes occur, we will include them in this document. Owner and staff will be referring the SRS document frequently and check whether the expected requirements have included the document. The lecturer-in-charge and project supervisor will be referring almost all the sections of this document. Because they need to get an idea about the project and what will be happening in each phase of the development. Mostly they will be checking the E-ER diagrams and the use case diagrams. But apparently, they will refer to

Introduction, Overall description which includes functions, user classes, design and features and non-functional requirements as well.

1.4 Product Scope

Sri Derana Cab Service has 13 branches in whole the island, being using a manual system head office cannot be able to maintain other branches directly. Therefore to overcome this problem develop team has decided to come up with a web-based system. After developed the system head office will be able to access other branches through the system. Also each branch will be able to access their main functions through the system such as: Hire Vehicles. Customer management. Handling Members. Handling reports. Employee management. User Authentication. Generate Bills.

Being accessing those main functions through the system, head office will be able to calculate profit anytime.

1.5 References
Software Engineering Slides (Second Year). Software Engineering Text book (Second Year)

2.0 Overall Description

2.1 product perspective

Being using a manual system there is no connection between head office and its branches. Therefore come up with a web based system will be able to make a connection between head office and the other branches.

2.2 Product Functions

Administrator Hire vehicles: insert, update, delete, and search. Customer Management: insert, update, delete, and search Handling Members: insert, update, delete, and search Handling Reports: Generate Reports, print reports Profit Calculation Handling System Users: insert, update, delete, set user privileges, handling settings panel Employee management: insert, update, delete, search Generate bills

Employee Hire vehicles: insert, update, delete, and search. Customer Management: insert, update, delete, and search Handling Members: insert, update, delete, and search Generate bills

2.3 User Classes and Characteristics

Administrator should be able to access all the functions through the System such as Hire vehicles, Customer Management, Handling Members, Handling Reports, Profit Calculation, Handling System Users, Employee management and generate bills also he can set some privileges through the settings panel and changing rates as well as other settings. Employee can access some functions through the system under the privileges such as Hire Vehicles, Customer Management, Handling Members and Generate Bills.

2.4 Operating Environment

The proposed system will be operating in any environment. Most of the features will be compatible with Internet Explorer and Mozilla Firefox versions

2.5 Design and Implementation Constraints

2.6 Documentation
Project proposal, software requirement specification and Final report are the documentation components of the client. In our project proposal we suggest the major functions and key benefits of web-based system. Software requirement specification is used to describe the specification process of the project in great detail. Final report will be the summarized documentation of all covered areas of the project.

2.7 User Documentation

During the developing time period project proposal, Software Specification Report and final report will be delivered to the clients for refer. After developed the web-based system project team hopes to have a workshop for staff of the Sri Derana Cab Service with video tutorials.

2.8 Assumptions and Dependencies

4.0 System Features

Figure 4.1

Use Case ID

4.1.1

Use Case Name

Insert Vehicle

Pre-condition

Administrator should be logged into the system.

Actor

Administrator

1. Use case starts when the administrator selects the insert vehicle option. Main Success Scenario 2. Administrator enters the relevant details. 3. The administrator submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.1.2

Use Case Name

Update Vehicle

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information.

3a. Display a message saying no record found. Extensions 5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.1.3

Use Case Name

Delete Vehicle

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects a vehicle number to delete.

Main Success Scenario

2. The user submits the delete option. 3. Display success message.

Extensions

Use Case ID

4.1.4

Use Case Name

Search Vehicles

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator enters a vehicle number into the search bar.

Main Success Scenario

2. Searches through the database. 3. Displays the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Figure 4.2

Use Case ID

4.2.1

Use Case Name

Insert Customers

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the insert customer option.

Main Success Scenario

2. Administrator enters the relevant details. 3. The administrator submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.2.2

Use Case Name

Update Customer

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information. 3a. Display a message saying no record found.

Extensions

5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.2.3

Use Case Name

Delete Customer

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects a customer NIC to delete.

Main Success Scenario

2. The user submits the delete option. 3. Display success message.

Extensions

Use Case ID

4.2.4

Use Case Name

Search Customer

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator enters a Customer NIC into the search bar.

Main Success Scenario

2. Searches through the database. 3. Displays the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Figure 4.3

Use Case ID

4.3.1

Use Case Name

Insert Members

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the insert Member option.

Main Success Scenario

2. Administrator enters the relevant details. 3. The administrator submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.3.2

Use Case Name

Update Member

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information. 3a. Display a message saying no record found.

Extensions

5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.3.3

Use Case Name

Delete Member

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects a Member NIC to delete.

Main Success Scenario

2. The user submits the delete option. 3. Display success message.

Extensions

Figure 4.4

Use Case ID

4.4.1

Use Case Name

Insert Employee

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the insert option.

Main Success Scenario

2. Administrator enters the relevant details. 3. The administrator submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.4.2

Use Case Name

Update Employee

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information. 3a. Display a message saying no record found.

Extensions

5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.4.3

Use Case Name

Delete Employee

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects an employee NIC to delete.

Main Success Scenario

2. The user submits the delete option. 3. Display success message.

Extensions

Use Case ID

4.4.4

Use Case Name

Search Employee

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator enters a Employee NIC into the search bar.

Main Success Scenario

2. Searches through the database. 3. Displays the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Figure 4.5

Use Case ID

4.5.1

Use Case Name

Insert System Users

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the insert option.

Main Success Scenario

2. Administrator enters the relevant details. 3. The administrator submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.5.2

Use Case Name

Update User

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information. 3a. Display a message saying no record found.

Extensions

5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.5.3

Use Case Name

Delete User

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects an employee NIC to delete.

Main Success Scenario

2. The user submits the delete option. 3. Display success message.

Extensions

Use Case ID

4.5.4

Use Case Name

Search User

Pre-condition

Administrator should be logged into the system.

Actor

Administrator

1. Use case starts when the administrator enters an Employee NIC into the search bar. Main Success Scenario 2. Searches through the database. 3. Displays the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Figure 4.6

Use Case ID

4.6.1

Use Case Name

Generate Report

Pre-condition

Administrator should be logged into the system.

Actor

Administrator

1. Use case starts when the administrator enters an Employee NIC into the search bar. Main Success Scenario 2. Searches through the database. 3. Displays the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Use Case ID

4.6.2

Use Case Name

Print Report

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Use case starts when the administrator selects an employee NIC to delete.

Main Success Scenario

2. The user submits the delete option. 3. Display success message.

Extensions

Figure 4.7

Use Case ID

4.7.1

Use Case Name

Calculate profit

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Administrator enters user name and password 2. System shows calculation page

Main Success Scenario 1a Extensions Invalid Username or password ask to retype the username and password

Figure 4.8

Use Case ID

4.8.1

Use Case Name

Generate Bills

Pre-condition

Administrator should be logged into the system.

Actor

Administrator 1. Administrator enters user name and password 2. System shows Bills page

Main Success Scenario 1a Extensions Invalid Username or password ask to retype the username and password

Figure 4.9

Use Case ID

4.9.1

Use Case Name

Insert Vehicle

Pre-condition

Employee should be logged into the system.

Actor

Employee

1. Use case starts when the employee selects the insert vehicle option. Main Success Scenario 2. Employee enters the relevant details. 3. The employee submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.9.2

Use Case Name

Update Vehicle

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Use case starts when the Employee selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information.

3a. Display a message saying, no record found. Extensions 5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.9.3

Use Case Name

Search Vehicles

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Use case starts when the employee enters a vehicle number into the search bar.

Main Success Scenario

2.

Search through the database.

3. Display the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Figure 4.10

Use Case ID

4.10.1

Use Case Name

Insert Customers

Pre-condition

Employee should be logged into the system.

Actor

Employee

1. Use case starts when the Employee selects the insert customer option. Main Success Scenario 2. Employee enters the relevant details. 3. The employee submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a.

user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.10.2

Use Case Name

Update Customer

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Use case starts when the Employee selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information.

3a. Display a message saying, no record found. Extensions 5a. Prompt to update again if incorrect information is entered.

Use Case ID

4.10.3

Use Case Name

Search Customer

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Use case starts when the employee enters a Customer NIC into the search bar.

Main Success Scenario

2. Search through the database. 3. Display the details if the records are found.

Extensions

3a. Displays an error message if the records are not found.

Figure 4.11

Use Case ID

4.11.1

Use Case Name

Insert Members

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Use case starts when the Employee selects the insert Member option.

Main Success Scenario

2. Employee enters the relevant details. 3. The Employee submits the details. 4. Use case ends when the system displays a success message.

Extensions

3a. user is prompted to re-enter the details if the wrong details are entered.

Use Case ID

4.11.2

Use Case Name

Update Member

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Use case starts when the employee selects the update option.

Main Success Scenario

2. Then he searches for the details. 3. System displays the searched details. 4. User updates the relevant details. 5. User submits the information. 3a. Display a message saying, no record found.

Extensions

5a. Prompt to update again if incorrect information is entered.

Figure 4.12

Use Case ID

4.12.1

Use Case Name

Generate Bills

Pre-condition

Employee should be logged into the system.

Actor

Employee 1. Employee enters user name and password 2. System shows Bills page

Main Success Scenario 1a Extensions Invalid Username or password and ask to retype the username and password