Page |1

FYP SRS Document

Final Year Project
Software Requirement Specification
“Seek Everything”
(BSCS)
By

Name Registration #/Roll #/Section Mobile # E-Mail

S#

1. Muhammad Salman Iqbal FA19/BSCS/181/E 0305-4454966 [email protected]

2. Zain ul Abideen FA19/BSCS/182/E 0311-1427681 [email protected]

Supervised by:
Ms. Tayyaba Sultana ___________________ (Signature)

Department of Computer Science

Lahore Garrison University
 Page |2

Table of Contents
1. Introduction 3
1.1 Purpose 3
1.2 Document Conventions 3
1.3 Intended Audience and Reading Suggestions 4
1.4 Product Scope 5
2. Overall Description 5
2.1 Product Perspective 5
2.2 Product Functions 5
2.3 User Classes and Characteristics 5
2.4 Operating Environment 6
2.5 Design and Implementation Constraints 6
2.6 User Documentation 6
2.7 Assumptions and Dependencies 6
3. External Interface Requirements 7
3.1 User Interfaces 7
3.2 Hardware Interfaces 7
3.3 Software Interfaces 7
3.4 Communications Interfaces 7
4. System Features 7
4..1 Categories 8
5. Other Nonfunctional Requirements 9
5.1 Performance Requirements 9
5.2 Safety Requirements 9
5.3 Security Requirements 9
5.4 Software Quality Attributes 9
5.5 Business Rules 10
References 10
 Page |3

1. Introduction
1.1 Purpose
We have designed this mobile-friendly application which will ameliorate the chance of reclaiming
by simplifying the system. The finder just uploads the details of the item on the application by
tagging the location and the losers can simply search via keywords, categories, locations, or stores.
This method is much easier than going to the police station and filing a report. Due to this reason,
the students, employees, as well as visitors face a lot of difficulties to find their missing items. For
these kinds of issues, we have developed mobile application of lost and found system. So, it is
mandatory to develop a system that can help to overcome these problems. This project is helpful
because there is no proper finding of lost item in our country.

As this system’s functionality is described here, whenever a person will lose his item, first of all
he will get register on the app and after successful login a form will appear for describing his lost
item after filling and adding location of lost item his ad of lost item will go live.

View the list of lost and found items. Posts can also be viewed on the map. In this app we have a
feature in which there will be categories like when a pet is lost or any vehicles are lost or any
person is lost our app will provide the user facilities for that. There will be another feature included
in which there will be a registration in NGO option through which users of this app can log in and
make donations directly

1.2 Document Conventions

The documents conventions being followed are, the font style for the SRS is times news roman.
For the headings the heading 1 style is being used for main heading with a font size of 16 while
for sub-headings the heading 2 style is being used with the font no 13. For the paragraph content
the font size is 12.

1.3 Intended Audience and Reading Suggestions

This subjected document is to be intended for the relevant to the field of app developing,
developers, project managers, founder and user. As the project is based on the lost founder app.
Using this app people doesn’t need to have knowledge of the app developing they just need to have
 Page |4

a little knowledge of internet and the knowledge of using the android phones and apps. The topics
discussed in SRS with respect to the project are introduction, overall description, external interface
requirements, system’s features and non-functional requirements. The introduction describes the
basic purpose, document conventions, the reading suggestions for audience and project scope. The
Overall Description describes the product perspective, product functions, user classes, operating
environment, design and implementation constraints, user documentation, assumptions and
dependencies.

The next is External Interface Environment that consists of user interfaces, hardware interfaces,
software interfaces and communication interfaces. Further next is the System Features that
includes the system feature, description and priority, stimulus/response sequences and functional
requirements. Last one is the Other Nonfunctional Requirements that further consists of
performance requirements, safety requirements, security requirements, software quality attributes,
business rules. The reading suggestion for the interior designers and people from interior designing
background is that they should read the overall description part. The developers should read the
external interface environment. The researchers and technologists are suggested to read the system
features and non-functional requirements while, the introduction is to be suggested to all the
readers of this respective SRS document.
 Page |5

1.4 Product Scope

Nowadays most of us go somewhere to visit place and sometimes we forget our valuable item at
that place. This is very stressful for every owner. There are many platforms but sometimes they
neither submit lost items nor return item to its exact owner. Some platforms are paid which are not
suitable for some users. Our project is based on android. Both owner and finder will register
themselves. User needs registration before performing any operation. After registration and login
owner can search his item and can also see all lost items. We have provided form to finder for
providing information regarding the lost item, he will also give the geographical location of that
particular place from where he found the item similarly owner will also give the location where he
lost the item. Both owner and finder can chat with each other for verification. Owner will mark
item found in his profile after he has found his lost item.

2. Overall Description
2.1 Product Perspective
The perspective of this project is that you will have to activate this app and this app will show you the
different categories of lost items. If you find anything you just captured the image of this item and upload
pictures of this application for certain categories. If you lost your item, simply upload your information
about your item and specify where you lost your item.

2.2 Product Functions

The functions of the product are given below,

• Categories
• Maps
• Donation

2.3 User Classes and Characteristics

The user class that are privileged to use this subjected product are people having android phones.
We selected the categories we should be searching for. there are categories of pets, documents,
devices, people, etc. each category provides information in accordance with the class. We may
also set our site where we lost our item.
 Page |6

2.4 Operating Environment

The respective operating environment for the product is homes, rooms, offices, or any place where
you lost you items. Like the application in not for the use of people who do not have the knowledge
of the use of the mobile android and also not a little knowledge of the Internet. The product does
not contain many hardware components only, android tablets and mobiles so all these hardware
components can co-exist in an operating environment.

2.5 Design and Implementation Constraints

The biggest limitation for this project is that giving wrong information on lost items, not being
aware of the use of Android phones from Android apps. As the methodology Is based on the
finding lost items. We need information on lost property where you lost your article and how it
looks. you need to log in to this application and put you information depending on the class and
set the location.

2.6 User documentation

For User documentation, the users will be provided by a complete user manual with all the
information needed by the end users for their guidance. Moreover, video tutorials will also be
provided to the users for their better understanding as the end users are from non-technical
background so they are unaware of the technical perspective of project. Users can also take online
help for this purpose an email will be provided where they can contact to resolve their questions
and queries.

2.7 Assumptions and Dependencies

The most important part in the constructing the project was the requirement gathering relative to
the project as the project includes map location So we need GPS and mobliephone. This project
helps us find our lost object online. The data sets are also the main reason that can affect the project
too as the project is fully depending on them, if anything goes wrong can cause trouble like causing
failures in virtual room created by the app The project is an original and unique in its own domain
so none of the code or other parts are reused or taken from somewhere.
 Page |7

3. External Interface Requirements

3.1 User Interfaces
These are multiple users interfacing with the system. The user will find his missing item. For this
purpose, the software would have a different interface regarding several users' functionality. The
user interfaces have different categories for the list of lost items.

3.2 Hardware Interfaces

The hardware devices needed for this project are android tablets and mobiles. The main emphasis
of the methodology is on the software part the hardware devices are to assist and add more features
to the application.

And another hardware used in this app is the camera of the mobile which is using this app.

3.3 Software Interfaces

Android studio will be used in the coding of this app. As android studio is basic tool used in the
creating of android apps and also data bases will be used to store the data and products used in the
app.

3.4 Communications Interfaces

The primary communication interface is the Internet through which all software, hardware
interface will be connected. More for the founder and receiver communicate through chat box and
its number and location also mentioned in his post. In addition, the communication interfaces will
differ from one user to another.

4. System Features
The system features defined earlier will be explained in this portion as the context that how will
these features work and be applied in the real time scenario.

To lose something special is heartbreaking. Sometimes a bond is formed between us and anything
else like a pet, another human, a belonging etc. But no matter what we do to take care of them
they could be lost. A lost dog, a lost friend, a lost chain or a lost car, they can be the source of
happiness in your life and to bring them back to you “Seek Everything” plays an important role.
 Page |8

Categories
Pet finder: If you have lost your pet you can track it with the help of this app You just need to
click a picture of your pet and upload it.

Friend finder: Whether it is a friend or a family member you can easily track them down with the
help of this app, you can check their locations too.

Device finder: Your lost watch, your car, your air pods, your cell phone they are valuable for you
and to find them back after losing them is possible with the help of “Seek Everything”

Donation
You may contact that person to find your item. You may also make a donation to register an NGO
while you are using this application.

4.3Functional Requirements
Lost and Found management System has following functional requirements.

• User will be Registered and create his/her profile.

• User will be able to login in the app.
• User will enter information of lost items
• Admin will enter information of all found items and as sign id to each found item.
• Admin will match the product description and inform the user through chat if any
description matched.
• The system shall enable the finder to ask for more details of the item to check the
• validity of the ownership of the lost item from the item owner.
• The system shall enable the finder to ask for more details of the item to check the validity
of the ownership of the lost item from the item owner.
• Owner and finder are able to directly communicate with each other
• The system shall enable the finder to ask for more details of the item to check the
• validity of the ownership of the lost item from the item owner.
• The system shall enable the finder to ask for more details of the item to check the
• validity of the ownership of the lost item from the item owner.
 Page |9

5. Other Nonfunctional Requirements

5.1 Performance Requirements
Requirement performance is not high since it is easy to operate and a user-friendly application.
Response speed, throughput, runtime and storage capacity of the application are good enough.
Levels of service with performance requirements are often based on end-user tasks.

5.2 Safety Requirements

The precautionary measure for safety we can do as to be alert and beware that the software might
not get into wrong hands. First, the software is built for general public use. Second, the software
is only designed for people who have lost their important documents and the elements that those
who use this app. Only the concerned people would be using the application These will reduce the
mishandling of the software to some extent.

5.3 Security Requirements

Safety is one of the main functions of finding any product. In the methodology of the topic, there
is only one thing that is very important from a safety point of view, and that is user data. The
application will be linked to a functional secure data base. We can make it secure by restricting
the access and rights to only the admin who will be having the access to update or delete the records
apart from that no user would have the access to the databases.

5.4 Software Quality Attributes

The major software quality attribute is the user-friendly interface. The end users are from a non-
technical background and they do not understand the computer programming or code. In the
context of this, the interface would be easy to use and understand. Moreover, the qualities of the
application are accuracy, speed, efficiency, maintainability, portability, reliability.
 P a g e | 10

5.5 Business Rules

The business rules would be very easy as the project is very easy and friendly base project. The
users would be having different interfaces and roles regarding to the actions they would be
performing within the software ecosystem regardless what the other person is doing. The business
rules would be flexible enough in order to deal with all interface of the users. Anyone is welcome
to approach this application.

References
1. https://www.researchgate.net/publication/352145493_Find_Mine_Find_the_Lost_Ite
ms_via_Mobile_App

2. https://www.researchgate.net/publication/274456237_AN_EMPIRICAL_STUDY
_OF_SMARTPHONE_BASE
D_TRACKING_DEVICES_AND_ANALYSIS_OF_ITs_DEMAND_MARKET

3. http://faculty.washington.edu/jkientz/papers/Kientz-FETCH-ASSETS2006.pdf