< Border Crossing Management System>

Software Requirements Specification

Version 1.0

  

Group Id: <S2002BE42E (MC160402593>

Supervisor Name :< Usama Ahmed>

 Revision History
Date (dd/mm/yyyy) Version Description Author
04/06/2020 1.0 Border Crossing Management System MC160402593
(BCMS) is a web-based management
system. This system is made to keep
the records about the people and goods
who are crossing the borders of a
country and are going to the other
countries. This system helps the border
control officers in checking those people
who are going through the border to
another countries, might have some
luggage and that luggage also need to
be checked and the passport of the
people also needs to be verified. For
passport might not be required in some
countries, so people going to those
countries should have all the other
documents which are required. This
system has one admin account and only
admin can add officers who are on duty.
It contains some basic parts like
scope of the project, functional and
non- functional requirements, use
case diagram, usage scenario,
adopted methodology and work plan

Table of Contents
1. Scope (of the project)

2. Functional Requirements Non-Functional requirements

3. Use Case Diagram

4. Usage Scenarios

5. Adopted Methodology

6. Work Plan (Use MS Project to create Schedule/Work Plan)

SRS Document
Scope of Project:

Border Crossing Management System (BCMS) is a web-based management system. This

system is made to keep the records about the people and goods who are crossing the
borders of a country and are going to the other countries. This system helps the border
control officers in checking those people who are going through the border to another
countries, might have some luggage and that luggage also need to be checked and the
passport of the people also needs to be verified. For passport might not be required in
some countries, so people going to those countries should have all the other documents
which are required. This system has one admin account and only admin can add officers
who are on duty.
The duty officers have different duty shifts and this system has all the options that helps
the officers in their shifts. Those People who are crossing these borders they do not have
valid documents should be checked through responsible verification departments. In
crossing border, if the people have caught with any illegal activity, then duty officer
should add complain and send it to the related departments. The follow up of complaints
can be seen through department profile. This system also has the option to add and delete
officers as their duty gets keep changing.

Functional and non-Functional Requirements:

Border Crossing Management System (BCMS) is a web-based management system. This

system is made to keep the records about the people and goods who are crossing the
borders of a country and are going to the other countries. This system helps the border
control officers in checking those people who are going through the border to another
countries, might have some luggage and that luggage also need to be checked and the
passport of the people also needs to be verified.

Functional Requirements:

1. Admin Profile is a profile which have all access of the system.

2. Registration system for border crossing people.
3. Login system for each User.
 Duty officer
 Officer
 Admin
 Departments
4. Checking Luggage
5. Add Complaints
 6. Status of Complaints
 Pending
 Completed
 Filled
7. Verification system for required department.
8. Goods Transports
 Import Goods
 Export Goods

9. Medical Reports
 Infected people
 Non-infected people
10. Payments
 Punishments

Non-Functional Requirements:

Non-functional requirement defines the needs in term of performance, logical database,

requirements, design constraints, standard compliance reliability, availability, security,
maintainability and portability.

Hardware Requirements:

 CPU Core 2 Duo OR High

 RAM 4GB OR High
 HDD 80GB OR High
 Printer (laser)
 Barcode scanner
 DSL for internet access

Software Requirements:

While making “Border Crossing Management System” I can user software tools which
are as

 Microsoft Word for documentation.

 Sublime text editor (Source Code editor).

 Microsoft Visio for Use-Case Diagram.

 SQL Server for database.

Web browser:

 Google chrome.

 Firefox.

Sublime Text Editor:

Sublime Text is a proprietary cross-platform source code editor. It natively supports

many programming languages and markup languages, and functions can be added by
users with plugins.

XAMPP (SQL, Apache):

XAMPP is a free and open-source cross-platform web server so2lution stack package
developed by Apache Friends, consisting mainly of the Apache HTTP Server, SQL
database, and interpreters for scripts written in the PHP programming languages.

Microsoft word:

Microsoft Word is a word processor developed by Microsoft. It is use for the

documentation. It is widely used commercial word process. It was initially launched in
1983 and has since been revised numerous times. Microsoft Word is available for both
Windows and Macintosh operating systems.

Programming Language Used:

Html, CSS, PHP, JavaScript

Use Case Diagram(s):

Use case diagram can be used as a behavior diagram which can be used to represent the
overall functionality of the system named as “Border Crossing Management System”
that what the actions user can performed in Border Crossing Management System.

Use Case Diagram

Usage Scenarios:

User Usage Scenarios:

Use-Case Title Add Complaints

Use-Case Id Use case # 1

Action Add Complaints

Description Use case can initiate when the user wanted to

be send the complaint.
Pre-Condition User should be logged in into the System.

Post-Condition complaint application will be sends to the

admin and the user would do wait until
request processed.

Use-Case Title View Status

Use-Case Id Use case # 2

Action View status after send complaint application

to the admin.
Description Use case can initiate when the request will be
processed by the admin side and response
come from admin side.
Pre-Condition User should be logged in into the system.

Post-Condition After processing request by the admin side.

Admin will sends the response either he/she
can accept, reject, or cancel the request then,
the student would be able to see the status.

Admin Usage Scenarios:

Use-Case Title View Complaint applications

Use-Case Id Use case # 3
Action Admin view Complaint applications send by
the particular student.
Description Use case can initiate when the user will send
the Complaint application. Admin will view
to response him/her.
Pre-Condition Admin should be logged in into the system.
Post-Condition Admin will view all the application then
decide either the applications can be accept
or not. Then, the admin will send response
 to the particular student.

Use-Case Title Search applications

Use-Case Id Use case # 4
Action Search application by the name of students
by admin.
Description Use case initiate when the admin wanted to
be search the application sends by the user.
Pre-Condition User should be logged in into the system.
Post-Condition Admin search the application sends by the
students.

Use-Case Title Import Goods

Use-Case Id Use case # 5

Action Admin can see the action of goods import and

export.
Description Use case can initiate when the request will be
processed by the admin side and response
come from admin side.
Pre-Condition User should be logged in into the system.

Post-Condition After processing request by the admin side.

Admin will sends the response either he/she
can import or export the Goods then, the
student would be able to see the status.

Use-Case Title Submit Report

Use-Case Id Use case # 6

Action Admin can see the action of report.

Description Use case can initiate when the request will be

processed by the admin side and response
come from admin side.
Pre-Condition User should be logged in into the system.

Post-Condition After processing request by the admin side.

Admin will sends the response either he/she
sends the list of people then, the student
would be able to see the status.

Adopted Methodology:

Waterfall Model:

Waterfall model is the earliest approach linear sequential life cycle model. It is well
known model. As the name represent progress is seen as flowing steadily downwards
(like a waterfall) through the phases of software implementation. We can only move to
the next stage when the previous stage is complete. We cannot make changes in the
requirement because we cannot move backward to the previous phase in this model.
Diagram of Waterfall-model:

Advantages of waterfall model:

1. Easy to understand and use.
2. In this model only one phase processed at one time. So, phases do not overlap.
3. Suitable for smaller projects.
Disadvantages of waterfall model:
1. Highly risk.
2. Once the application is in the testing phase if we want to make changes. It is very
difficult to go back and handle changes in the requirements.
3. Poor for large projects.
V-Model:

This model is the extension of waterfall model. The major difference between waterfall
model and V-shape model is that testing can be done at each stage. In this way
verification and validation of product ensure at the early stage of product development.

Diagram of V-model:

Advantages of V-Model:
1. Simple and easy to use and understand.
2. High chances of success due to early test planning.
3. Work well where requirements can be completely understood.
Disadvantages of V-Model:
1. Costly, required more time.
2. Required more time in addition to detailed plan.
3. If any changes happen in the midway, then the text documents along with the
requirement documents has to be updated.

Spiral Model:
Spiral model is similar to the incremental model. Risk management is the most important
factor in this model. Spiral model has four phases Planning, Risk Analysis, Engineering
and Evaluation. Project passes repeatedly through these phases in iterations (called
Spirals in this model).
1) Planning phase: Requirements are gathered in this phase it may be business
requirement specifications or system requirements specification.
2) Risk analysis: Risk has been identified in this phase. If any risk found during risk
analysis then alternate solution must be suggested and implemented. After this
phase prototype of software is produced.
3) Engineering phase: In this phase development and testing is to be taken.
4) Evaluation phase: In this phase customer evaluate the output before the project
is going to the next spiral.

Diagram of Spiral Model:

Advantages of Spiral Model

1.Risk management.
2.Good for large and critical projects.

Disadvantages of Spiral Model:

1. Highly expensive model.
2. Do not work well for smaller projects.
Which SDLC Model you choose and Why? :
After several discussion and brainstorming about the project I can choose “Waterfall
model” for this project.

Justification:
The main reason for selecting the waterfall model is the freezing of requirements. While
the submission of project specifications developer has been fixed the requirements of the
system and same case happen in waterfall model which is very well suited to the
developer. In this way developer has to be performed only one action at one time rather
than multiple actions because in waterfall model the next stage start after the completion
of previous stage. And at last project will submitted to after completion of all the phases.

Work Plan (Use MS Project to create Schedule/Work Plan):

Gantt chart is used to explain the timeline of different activities of a project. It includes
the timeframe of each task. The current Gantt chart defines the processes and tasks to
make a web application. It includes different type of tasks which help to complete the
application.