SRS Sample

Software Requirement Specification for Lost and Found
Software Requirement Specification
For
Lost and Found Items at the Airport
Project Guide: Prepared by:

Mr. Vipin Jain Aishwarya Saxena (15ESKIT002)
Submitted to: Anjali Jain (15ESKIT015)
Mrs. Neha Janu Anshika Gupta (15ESKIT021)
Department of Information Technology

Swami Keshvanand Institute of Technology, Management and Gramothan, Jaipur
Rajasthan Technical University, kota
1
Table of Contents
1. Introduction ..............................................................................................................................3
1.1 Purpose............................................................................................................................................. 3
1.2 Product Scope .................................................................................................................................. 3
1.5 Technologies to be used ............................................................................................ 5
1.6 Overview
2. Overall Description ..................................................................................................................4
2.1 Product Perspective.......................................................................................................................... 4
2.2 Product Functions ............................................................................................................................ 4
2.3 User Classes and Characteristics ..................................................................................................... 4
2.4 Operating Environment .................................................................................................................... 5
2.5 Design and Implementation Constraints .......................................................................................... 5
2.6 User Documentation ........................................................................................................................ 5
2.7 Assumptions and Dependencies ...................................................................................................... 5
3. External Interface Requirements ...........................................................................................6

3.1 User Interfaces ................................................................................................................................. 6
3.2 Hardware Interfaces ......................................................................................................................... 6
3.3 Software Interfaces .......................................................................................................................... 7
3.4 Communications Interfaces ............................................................................................................. 7
4. System Features .......................................................................................................................8

4.1 System Feature 1 .............................................................................................................................. 8
4.2 System Feature 2 .............................................................................................................................. 8
4.2 System Feature 3 .............................................................................................................................. 9
4.2 System Feature 4 ............................................................................................................................ 10
5. Other Nonfunctional Requirements .....................................................................................10

5.1 Performance Requirements ............................................................................................................ 10
5.2 Safety Requirements ...................................................................................................................... 11
5.3 Security Requirements ................................................................................................................... 11
5.4 Software Quality Attributes ........................................................................................................... 11
6. References ...............................................................................................................................12
Appendix A: Glossary..................................................................................................................12
2
1. Introduction
1.1 Purpose
The purpose of this document is to build an online system to manage belonging/s of passengers
which are lost at the airport to ease the items management found at the airport. The current
system in India is not a managed one, thus there is a need of a proper and easy way for the
passengers to claim their item. The project is based on an android app using which the airport
authority can manage the database and passengers can access and claim for their belonging.
1.2 Document Conventions
Bold-faced text has been used to emphasize section and sub-section headings. Highlighting is to
point out words in the glossary and italicized text is used to label and recognize diagrams.
1.3 Intended Audience and Reading Suggestions
This project is a prototype for the Inventory management system for lost and found items at the
airport and it is restricted within the college premises. This has been implemented under the
guidance of college professors. This project is useful for the airport authority and as well as to
the passengers.
1.4 Project Scope
The purpose of the Inventory management system for lost and found items at the airport is to
ease item management and to create a convenient and easy-to-use application for passengers,
trying to locate and claim their item. The system is based on a relational database with its items
lost and found functions. We will have an embedded system whereusing mobile phones
passengers can interact with airport authority easily. Above all, we hope to provide a comfortable
user experience.
3
2. Overall Description
2.1 Product Perspective
An inventory management database system stores the following information.
 User details:
The database consists of the username, password, contact, gender, email id. These details provide
valid login to user after getting registered.
 Item details:
The DB consists of the description of item found at the airport, i.e. the id, name, type, location,
date, and other details including status.
 Admin details:
The DB consists of the username, password, contact, gender, email id, employee id, department,
address. These details provide valid login to an employee (admin) of a particular airport after
getting registered.
2.2 Product Functions
 Lost and found enables the admin of a particular airport to enter the details of items found
at the airport and passengers to claim their lost item at the airport. And using this
function, passenger can easily find their belonging/s (by providing duration and airport)
and thus have to submit a proof as a verification process.
 Also, if item is not present in the list, then the passenger can make a complaint in order to
enquire about their lost item. Further, response is to be given by the airport authority to
his complaint.
 On successful claim, the item is handover to the owner.
 Passengers can give their feedback for the services provided to them.
4
2.3 User Classes and Characteristics
Users of the system should be able to retrieve item name and type between given duration of
item lost from the DB. The system will support two types of user privileges, Passengers and
Admin (Airport Authority). Passengers will have access to passenger functions, and the admin
will have access to both passenger and item management functions.
The passenger should be able to do the following functions:

 Access to the items found by authority in provided duration.
 Can claim his belonging/s.
 If item is not present or not found by the authority, then he can make complaint regarding
his item which has been lost.
 Can track the status of his claim.
 Can give feedback.
The admin should be able to do the following functions:

 PASSENGER FUNCTIONS-
1. Can check which passenger has claim the item.
2. Can check for valid claim or not.
3. Can receive the complaint (item lost) by passenger.
4. Can change the status of item which is to be displayed to the passenger.
 ADMINISTRATIVE FUNCTIONS-
1. Add/delete/update item details (with airport name).
2. Respond back to the Passenger for his complaint.
2.4 Operating Environment
Operating environment for the inventory management system is as listed below.

 Relational database
5
 Embedded System
 Operating system: Android.
 Database: SQLite
 Platform: android/Java/XML (android studio)
2.5 Design and Implementation Constraints
 SQL commands for above queries/applications

 Implement the DB at least using a centralized DBMS.
2.6 User Documentation
For user documentation and information, please consult section 3: External Interface
Requirements.
2.7 Assumptions and Dependencies
Let us assume that this is aninventory management system and it is used in the following
application:
 A claim by passenger for his belonging/s.
 A complaint from passenger to the authority regarding his lost item.
Assuming both the transactions are single transactions, we have designed a database that is
geographically dispersed at four cities Jaipur, Delhi, Mumbai, Chennai, Bangalore, Goa,
Hyderabad, Ahmedabad, Guwahati, Lucknow, Varanasi, and Kolkata.
6
3. External Interface Requirements
3.1 User Interfaces
The Lost and Found user interface has been specifically designed with their customers
(passengers) in mind, giving them convenience to track and find their lost item at the airport.
The home screen offers a menu with a list of functions that the device performs. The user can
select one of the options on the menu, and is taken to the respective screen. Every screen
displays the menu on the bottom. The user can click on any one of the options and is taken to the
screen of their choice. In addition, clicking on the power button displays the home screen with
the menu options.
The device offers easy scroll options to navigate the screens efficiently. To scroll down any
screen, simply touch the scroll bar on the screen, and roll down. If the user does not know how to
use any functionality or has any queries, the help option can be used. The help screen contains a
text field to enter search terms. A list of search results pertaining to the query is displayed.
3.2 Hardware Interfaces
 Android
7
3.3 Software Interfaces
Following are the software used for the flight management online application.
Software used Description
We have chosen Android operating system for its best support and user-
Operating system friendliness.
To save the item records, Passengers records, admin records, we have

Database chosen SQLite database.
To implement the project we have chosen Android Studio for its more
Tools/IDE interactive support.
Platform Android SDK framework
Technologies Used Java, XML, Android
3.4 Communications Interfaces
The users can directly communicate to the authority using the forms which provide them the
feature to enter the details of their item which has been lost and not present in existing list. This
will send a mail to the admin through which he can check for the respective complaints and
actions to be done by them.
8
4. System Features
4.1 USER REGISTRATION
4.1.1 DESCRIPTION AND PRIORITY:
When the application is installed and run for the very first time the user is presented with an
initial registration/welcome screen. This screen prompts the user to create an account on the
LOST AND FOUND ITEMS application using the email address associated with his/her google
account. The priority of this feature is highest because completing this process will create and
store an account for the user on the LOST AND FOUND ITEMS application, enabling all of the
application’s synchronization capabilities.
4.1.2 STIMULUS/RESPONSE SEQUENCE
Step 1 LIFO application launches from the Android home screen.
Step 2 the user is prompted to enter an email address and his/her name. The user’s Google
account info is entered by default
Step 3 this information is stored in database.
Step 4 Registration is completed and user is taken to main screen.
4.1.3 FUNCTIONAL REQUIREMENTS:
The application will ask for a valid e-mail address, user name and password at the time of
registration. If your details are not valid then registration will not be successful.
4.2 Claim
4.2.1 DESCRIPTION AND
9
PRIORITY: The next thing that has to be done after registration and login is claim. As per the
airport city the list of items that are found on airport will be displayed to the user. It will help the
user to select his lost item from the list (if present in the list) and claim it.
Step 1 after login you have to select claim item option.
Step 2 now you have to select your airport id so that the list of items found at that particular
airport could display.
Step 3 you are now supposed to enter the duration in which your product was lost.
Step 4 lastly the application will ask for some item specifications (color, type, etc.)
Step 5 Press claim
4.2.3 FUNCTIONAL REQUIREMENTS
When a user claims any particular item, it is important that it should be there in the list of items
that are found at the airport selected by the user. After that the details provided by him should
match the details of the item. At the end, documents and other proofs will be presented by the
user so that the item could be handed over to him.
4.3 Complaint
The priority of claim and complaint is similar depending upon whether the item lost by the user
is there in list or not. We have discussed that if the user finds his item in list then he can claim it.
But if the item is not there in the list then he can click on complain option wherein he is
10
supposed to fill a form that will ask about his lost item and then if anytime in future that type of
item will be found, the airport authority will inform that used by sending a notification.
Step 1 select complaint option if the item that you want to find is not there in the list.
Step 2 A form will be displayed that will ask about the details of the item that you have lost at
the airport, for example- color, weight, date, time, etc.
Step 3 after filling the form click on submit.
If the user is not able to find his lost product in the item list then he can report his product so that
whenever such product is found at the airport, he will be updated. So for this it is important that
he should fill correct details of his item in the form. If the details are not valid the he would not
be able to find his item.
4.4 Feedback
The feedback is always expected at the end of the process by the user. It includes rating and
review of applications that depends on the reliability and effective performance of the system.
The feedback completely depends on the experience of the user.
11
Step 1 As soon as the process of handing over or complaining about the item will complete, the
application will ask for the feedback from user.
Step 2 the first part of feedback will ask for rating out of 5 and another part will ask about the
review of the user.
Step 3 this feedback will further help other users to know about the performance of the LOST
AND FOUND ITEMS application.
The application will be rated out of 5. There will be a limit on the number of characters that can
be written in the column of review.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
 Normalized data- data redundancy should be minimal which in turn reduces the chances
of insert, delete and update anomalies
 Response time- the overall time beginning with the user action (click on search item
button after filling up the details), the request going to server, the response received from
server, and finally the response processing by the application will not take more than 3
seconds.
 Scalability- according to intended number of passengers at airport and the projected load
scenarios, the system should be able to serve 50 queries / day (in large part during the
peak hours).
12
5.2 Safety Requirements
If there is extensive damage to a wide portion of database due to catastrophic failure, such as
disk crash, recovery method restores a past copy of the database that was backed up to archival
storage (typically tape) and reconstructs a more current state by reapplying or redoing the
operations of committed transactions from the backed up log, up to the time of failure.
5.3 Security Requirements
 Admin login account security-if an admin tries to log into a non-existing account then the
admin should not be logged in.
 Admin login account security-the admin should not be able to login for a certain time
period after 5 attempts of unsuccessful login.
 User create account security-if a user wants to create an account and the desired name is
occupied, the user should be asked to enter a different name.
5.4 Software Quality Attributes
 Availability-the item should be available (found by authority) as per the details given by
user.
 Correctness-the list of the items from the database should be correct according to the
duration provided by the user and should identify correctness of a claim (i.e. should be a
valid claim).
 Usability-the details of items found at airport should satisfy a maximum number of user
needs and let them find their lost items.
 Maintainability-admin should maintain the database and store in updated form.
 Portability- the application should be portable to android and iOS.
 Reliability- the system should give 98% correct search results out of 1000 searches
during testing.
 Extendibility-the application should be easy to extend, code should be written in such a
way that it favors implementation of new functions.
13
References:
https://www.scribd.com
https://krazytech.com
Appendix A: Glossary
ACRONYMS-
DB-Database
14
Appendix B: Analysis Models
E-R Diagram-
 This diagram illustrates how “entities” such as people, objects or concepts relate to each
other within a system.
 Entities in lost and found items application can be user, admin, items with user_activity
and admin_activity as separate behavior on their login.
 User attributes: name, emai_id, user_id/user_name, password while user activity consists
of feedback, status, item list.
 Admin attributes: name, email_id, password, admin_id, while admin activity consists of
add/update/delete items and users.
 Item attributes: name, type, airport _id, item_id.
 After successful login user and admin can perform user activity and admin activity
respectively
 Similarly, on claim or complaint on the basis of item found or not in the item list by the
user, claim/complaint have attributes: id proof, ticket proof, valid/invalid claim,
complaint form, claim details, etc.
 Admin manages item and user list.
15
Figure 1 E-R Diagram
16
UML Models:
Use-case-
 This diagram describe a set of actions (use cases) that some system or systems (subject)
should or can perform in collaboration with one or more external users of the system
(actors). Each use case should provide some observable and valuable result to the actors
or other stakeholders of the system.
 In lost and found item application, user and admin are the actors where user can interact
with front-end of the system and admin handles the interface between database (back-
end) and front-end.
 Both user and admin play their roles on their respective ends. Admin add/update/delete
an item or a user.
 User can enter the duration and airport where he lost the item and then can check for his
belonging/s in the list of items. After that, he can claim for his belonging/s and if not
found then can make a complaint regarding his lost item.
 Extend relationship is to describe that the claim and complaint are the cases generated
from the list of items displayed. Also, include relationship from claim use case to provide
verification details case and from complaint use case to complaint form for item case
shows that the included use case (the addition) is inserted into the behavior of the
including (the base) use case.
17
Figure 2-Use case for LOST AND FOUND ITEMS
18
Class Diagram-
 A class diagram in the Unified Modeling Language (UML) is a type of static

structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among
objects.
 Classes in lost and found items application- Admin, User, Item, Airport, Feedback,
Claim, Complaint.
 Admin-
1. Attributes: name, email password
2. Operations: manage items/users, insert/update/delete items, check valid claim ad

respond to complaint
 User-
1. Attributes: name, email, password
2. Operations: search for item, claim/complaint, feedback
 Similarly, other classes like items, claim, complaint, airport and feedback have their own
attributes and operation in the system.
19
Figure 3-Class Diagram for lost and found items
20
State Machine Diagram-
User side-
 A state machine is any device that stores the status of an object at a given time and can
change status or cause other actions based on the input it receives. States refer to the
different combinations of information that an object can hold, not how the object
behaves.
 User enter the details of airport and duration when he lost the item and then from the
database the details are fetched to show the list of items found by the airport authority to
the user.
 From the list, user can check for his item and if it is there in the list then he can claim for
that particular item and thus have to give a proof for a valid claim else he can make a
complaint for his lost item at the airport by filling a form giving his item details.
 If the claim is valid then he can collect his lost item from airport authority. And give his
feedback on the application for the services provided.
21
Figure 4-State machine-user side for lost and found items
22
Admin Side-
 Admin manages user and item list.
 Admin checks for claim if any received and then check if the claim received is valid or
not and notify user accordingly. If complaint is received then the authority will check it
and notify the user.
 For claim or complaint, after successful operation the item list is to be updated by the
admin.
 After that acknowledgement of feedback is given to the user.
23
Figure 5- State machine -Admin Side for lost and found items
24
25
Activity Diagram-
User Side-
 This diagram describes the dynamic aspects of the system. Activity diagram is basically a
flowchart to represent the flow from one activity to another activity. Theactivity can be
described as an operation of the system. The control flow is drawn from one operation to
another.
 User enter the details of airport and duration when he lost the item and then from the
database the details are fetched to show the list of items found by the airport authority to
the user.
 From the list, user can check for his item and if it is there in the list then he can claim for
that particular item and thus have to give a proof for a valid claim else he can make a
complaint for his lost item at the airport by filling a form giving his item details.
 If the claim is valid then he can collect his lost item from airport authority. And give his
feedback on the application for the services provided.
 Here, actions with sending signal and receive signal is also used.
26
Figure 6User Side Activity Diagram for lost and found items
27
Admin Side-
 Admin manages user and item list.
 Admin checks for claim if any received and then check if the claim received is valid or
not and notify user accordingly. If complaint is received then the authority will check it
and notify the user.
 For claim or complaint, after successful operation the item list is to be updated by the
admin.
 After that acknowledgement of feedback is given to the user.
 Decision is shown with yes and no in the diagram and flow control is also there between
the actions in the activity.
28
Figure 7 Admin Side Activity Diagram for lost and found items
29
Sequence Diagram-
 A sequence diagram shows object interactions arranged in time sequence. It depicts the
objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario. Sequence
diagrams are typically associated with use case realizations in the Logical View of the
system under development. Sequence diagrams are sometimes called event
diagrams or event scenarios.
 A sequence diagram shows, as parallel vertical lines (lifelines), different processes or

objects that live simultaneously, and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of simple
runtime scenarios in a graphical manner.
 Here, the classes are referred by the term lifeline and as shown in the diagram there is a
sequence maintained between the lifelines according to the actions performed by the user
and admin respectively on the system.
 Messages from one lifeline to other are synchronous and asynchronous also as required in
the activity performed.
30
Figure 8 Sequence Diagram for lost and found items
31

SRS Sample

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS Sample

Uploaded by

Copyright:

Available Formats

Software Requirement Specification for Lost and Found

Software Requirement Specification

Lost and Found Items at the Airport

Project Guide: Prepared by:

Department of Information Technology

3. External Interface Requirements ...........................................................................................6

4. System Features .......................................................................................................................8

5. Other Nonfunctional Requirements .....................................................................................10

1.2 Document Conventions

1.3 Intended Audience and Reading Suggestions

1.4 Project Scope

2.1 Product Perspective

An inventory management database system stores the following information.

2.2 Product Functions

2.3 User Classes and Characteristics

The passenger should be able to do the following functions:

The admin should be able to do the following functions:

2.4 Operating Environment

Operating environment for the inventory management system is as listed below.

2.5 Design and Implementation Constraints

 SQL commands for above queries/applications

2.6 User Documentation

2.7 Assumptions and Dependencies

3. External Interface Requirements

3.1 User Interfaces

3.2 Hardware Interfaces

3.3 Software Interfaces

Software used Description

To save the item records, Passengers records, admin records, we have

Platform Android SDK framework

Technologies Used Java, XML, Android

3.4 Communications Interfaces

4.1 USER REGISTRATION

4.1.1 DESCRIPTION AND PRIORITY:

4.1.2 STIMULUS/RESPONSE SEQUENCE

Step 1 LIFO application launches from the Android home screen.

Step 3 this information is stored in database.

Step 4 Registration is completed and user is taken to main screen.

4.1.3 FUNCTIONAL REQUIREMENTS:

4.2.1 DESCRIPTION AND

4.2.2 STIMULUS/RESPONSE SEQUENCE

Step 1 after login you have to select claim item option.

Step 5 Press claim

4.2.3 FUNCTIONAL REQUIREMENTS

4.3.1 DESCRIPTION AND PRIORITY:

4.3.2 STIMULUS/RESPONSE SEQUENCE

Step 3 after filling the form click on submit.

4.3.3 FUNCTIONAL REQUIREMENTS

4.4.1 DESCRIPTION AND PRIORITY:

4.4.2 STIMULUS/RESPONSE SEQUENCE

4.4.3 FUNCTIONAL REQUIREMENTS

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

Appendix B: Analysis Models

 Item attributes: name, type, airport _id, item_id.

 Admin manages item and user list.

Figure 1 E-R Diagram

Figure 2-Use case for LOST AND FOUND ITEMS

 A class diagram in the Unified Modeling Language (UML) is a type of static