COLLEGE OF COMPUTING AND INFORMATICS

UNIVERSITI TENAGA NASIONAL

LOST ITEM TRACKING SYSTEM

HARVEEN A/L VELAN

SW0104101
 LOST ITEM TRACKING SYSTEM

by

HARVEEN A/L VELAN

Project Supervisor: Yunus Bin Yusoff, Assoc. Prof. Ts.

PROJECT REPORT SUBMITTED IN PARTIAL FULFILLMENT OF THE

THE REQUIREMENTS FOR THE BACHELOR OF COMPUTER SCIENCE (SOFTWARE

ENGINEERING) (HONS.)

UNIVERSITI TENAGA NASIONAL

MAY 2021
 APPROVAL PAGE

TITLE: LOST ITEM TRACKING SYSTEM

AUTHOR: HARVEEN A/L VELAN

The undersigned certify that the above candidate has fulfilled the condition of the Final Year

Project in partial fulfilment for the Bachelor of Computer Science (Software

Engineering) (Hons.)

SUPERVISOR:

Signature:

Name: : Yunus Bin Yusoff, Assoc. Prof. Ts.

Date:
 DECLARATION

I hereby declare that this report, submitted to Universiti Tenaga Nasional as a partial

fulfilment of the requirements for the Bachelor of Computer Science (Software Engineering)

(Hons.) has not been submitted as an exercise for a bachelor at any other university. I also

certify that the work described here is entirely my own except for excerpts and summaries

whose sources are appropriately cited in the references.

This report may be made available within the university library and may be photocopied or

loaned to other libraries for the purposes of consultation.

31 MAY 2021

Signature

HARVEEN A/L VELAN

SW0104101
 ABSTRACT

In the era of ubiquitous devices and mobility, students increasingly carry objects of great

value. Because of increased mobility, students are also more inclined to lose these objects.

We support the growth of a community of users able to solve the problem on their own using

their mobile phones. Therefore, the main objective of this project is to create a mobile

application, Lost Item Tracking System, that helps students to retrieve their lost items. The

application will be developed in both ios and android by using Xamarin. The method used to

develop this mobile application is by using the prototyping methodology. The reason this

method is chosen is because the developer will receive feedbacks from the client or the target

user for every prototype the developer has created. Therefore, the developer can refine the

prototype until it fulfils the product requirement. The requirements are gathered by

conducting web study and distributing an online survey. The results from the web study and

the online survey are analyzed. Based on the analyzed results, a Use-Case diagram, Entity-

Relational Diagram and interface design are constructed to be used as a reference for the

development of the mobile application. Features of the application are also based on the

analyzed results.
 ACKNOWLEDGEMENT

In preparation of constructing the documentation for Final Year Project 1 (FYP1), I had to

receive guidance and assistance from some respected people, who deserve my highest

gratitude. Although the completion of this document brings me great relief, I would like to

express my gratitude to my supervisor, Tuan Yunus Bin Yusoff, Assoc. Prof. Ts. for giving

me helpful guidelines and assist me in this project. I would like to also extend my gratitude

to all the peoplewho have either directly or indirectly helped me in writing this document.

Moreover, I would like to express my gratitude to my peers for helping and supporting me

with this project by giving comments and their opinions in improving this document.
TABLE OF CONTENTS

PAGE

APPROVAL PAGE I
DECLARATION II
ABSTRACT III
ACKNOWLEDGEMENT IV

TABLE OF CONTENTS V
CHAPTER 1 INTRODUCTION
ERROR! BOOKMARK NOT DEFINED.
1.1 Project Background 1
1.2 Problem Statements 2
1.3 Project Objectives 3
1.4 Project Scopes 3

CHAPTER 2 METHODOLOGY 4
2.1 Review on Existing Systems 4
2.1.1 System 1 6
2.1.2 System 2 7
2.2 Finding and Analysis 9

CHAPTER 3 REQUIREMENT ELICITATION 10

3.1 Requirements Elicitation 10
3.1.1 Elicitation Technique(s) 10
3.2 Results and Discussion 11
3.3 Requirement Specifications 14

CHAPTER 4 SYSTEM DESIGN 15

4.1 System Design 15
4.2 System architecture 16
4.3 Interface Design 17
4.4 Database Design 54
CHAPTER 5 CONCLUSION AND DISCUSSION 59
5.1 Conclusion 59

REFERENCES 59
APPENDIX A: SOFTWARE REQUIREMENTS
SPECIFICATIONS 61

ii
 CHAPTER 1

INTRODUCTION

1.1 Project Background

Lost property process is time consuming for staff and students. Whether it’s the

university operations team, facilities management team or university security, lost

property is a headache for all. Alongside other important tasks, staff are ill-equipped to

manage lost and found. Lost Item Tracking System is a mobile phone application which

will support all students. The popularity of smartphone has increases over the year. This

could change and speed up the process in universities. When their things are lost,

students can scan the QR code sticker on it, and the details of the code shall be send to

the system. Then, the system shall send the lost thing owner detail to the person who

scans it.

1
1.2 Problem Statements

University students are losing more things than ever, the average student loses 2 items
per year, anything from chargers to student IDs. Firstly, without a reliable lost property
process, losing things means replacing them. This could be a small or hefty price. With
students relying on student loans to stretch across living and academic costs, replacing
items is a huge inconvenience. There is an issue with the awareness of a lost property
process at universities that needs to change. Therefore, adopting a dedicated lost
property software will ensure more items are returned to students. Lastly, the lost
property process has a detrimental effect on student experience. Students trek around
campus, asking different people about their lost item. This time could be spent being
more productive. Furthermore, students are met with clueless staff who can’t offer any
help. This is confusing and frustrating.

2
1.3 Project Objectives

PO-1: Reduce time period of getting back student’s belongings that lost in university

campus.

PO-2: To simplify current lost item recovery process by automating the process.

PO-3: Shred the time spent by university staffs in managing lost and found by 50-80%.

1.4 Project Scopes

1.4.1 User

The target users for this application are students or staff who lose their belongings.

1.4.2 System

The system shall allow user to:

a) Generate their QR code if their personal detail has been filled up.

b) Scan the attached QR code on the belongings.

c) View lost thing’s owner details

d) Receive and view notifications about the details of owner user scanned, and
the people who have scanned their QR code.
e) Edit and customize their account details to their own preferences.

3
 CHAPTER 2

RELATED WORKS

2.1 Review on Existing Systems

QR codes were first invented in 1994 by the Denso Wave company to track their

manufacturing process for vehicles. That’s all there was to QR code usage. Just like

NFC and RFID, tracking items was what QR codes were primarily used for. Inventory

management needs nowadays have far surpassed what was required in the 1960s, so

Barcodes simply aren’t enough anymore. With complex global manufacturing and

logistics systems, QR Codes provide the capability to hold much more comprehensive

information for these systems to function properly.

System 1

QR Inventory is a cloud-based inventory management application designed with small

to midsize businesses in mind. The application’s core feature allows users to create and

track QR codes that can be scanned from mobile devices. As such, additional hardware

accessories such as barcode scanners are not required to use QR Inventory. Beyond QR

label generation, QR Inventory features standard inventory management applications,

such as vendor managed inventory, kitting, lot traceability and reports. Users can create

4
customized inventory transactions and define what they want to track for each type of

inventory transaction. QR Inventory is available as both a perpetual license and as a

monthly subscription, based on the number of items per month that the business is

tracking. It is operating system agnostic and compatible with both iOS and Android

devices.

5
6
 System 2

Asset Panda is a cloud-based platform for facility managers that offers a suite of

applications including asset tracking and maintenance management. It is compatible

with Windows, Mac, iPad, iPhone and can be used from anywhere while updating data

in real-time.

Asset Panda helps users assign contacts by location and track depreciation. The User

can use a qr code scanner to look up asset details and automate pick lists. Role-based

security ensures that employees are granted the appropriate level of access, so they

always see the information relevant to what they are working on. Asset Panda offers

customized exporting and reporting features. Reports can be automated via email, with

the ability to add custom calculation fields (and designate if each field should be

required) before sending.

Asset Panda helps users in auditing, facilities management, equipment support ticketing,

compliance and purchase order management.

7
8
2.2 Finding and Analysis

NO. YEARS NAME SUPPORTED TECHNOLOGY OBJECTIVE

OPERATING
SYSTEM

1 2018 Asset Panda Mac OS, Web QR CODE AND Keep tools from wandering away by
browser (OS BARCODE knowing exactly which crews have
agnostic), what, what job it's assigned to, and
Windows 8 what condition it is in.

2 2018 QR inventory Android QR CODE IN QR Inventory gives you the right tools
software, Mac SMARTPHONE to streamline inventory management
OS, Web and asset tracking process, in the field
browser (OS and warehouse.
agnostic)

9
 CHAPTER 3

REQUIREMENT ANALYSIS

This section will provide information about the techniques that are used to gather

requirement specification to produce a Software Requirement Specification (SRS) for this

project. The purpose of this chapter is to document the system requirements.

3.1 Requirements Elicitation

Techniques that are used to elicit project’s requirements are:

3.1.1 Web Study

Web study is using the Internet to find and analyze information to understand the scope of

the proposed application which is lost item tracking using qr code. Also, this technique is

used to identify the components that are implemented that used to track user’s lost

belongings. Moreover, similar existing applications to the proposed application are

analyzed to identify the features that should be implemented for tracking lost items.

10
3.1.2 Survey

Survey is a method that involves handing out a set of questions to multiple individuals to

gather information about how they track their lost belongings. This survey is conducted

online using Google Forms by sharing a link to other people to answer those questions.

This technique is conducted to analyze how often people lose their belonging and the items

often lost in campus.

3.2 Results and Discussion

3.2.1 Web Study

The result of Web Study is as discussed in 2.2 Review of Similar System.

3.2.2 Survey

The survey that has been conducted has received 15 respondents in total.

11
 Figure 3.1 Results of Survey 1

Figure 3.1 shows the gender of all the respondents. 53.3% of the respondents are male

while the other 46.7% are female.

12
 Figure 3.2 Results of Survey 2

Figure 3.2 shows that only 13.3% of student got back their lost belongings, whereas the

rest 86.7% didn’t get back their lost belongings.

Figure 3.3 Results of Survey 3

Figure 3.3 shows that most lost item by students is pendrive where 33.3% of the respondent has lost

it. Meanwhile, for chargers there are 26.7% of respondent has lost it followed by water bottles for

20% and 13.3% for wallet or purse and least lost item is mobile phone where only 6.7% of

respondent has lost it.

13
3.3 Requirement Specifications

Based on the use case diagram above, the application will have two users which is students and

admin. Users need to enter their personal details into the system. When an item is lost, students can

scan the QR code sticker which stick on it, and code shall be send to the system. Then, the system

shall send the lost thing owner detail to the person that scan it. The system shall also send a

notification to the owner of the lost thing. In other side, administrator may get student details from

the system. Administrator may change and send the student account status back to the system.

14
 CHAPTER 4

SYSTEM DESIGN

4.1 System Design

The purpose of this chapter is to document the system specifications and system design for the

mobile application. The system design is divided into three parts which are system architecture,

interface design and database design. Interface design is included to explain the flow of the

application and the database design with its data dictionary.

4.2 System architecture

System Architecture is a diagram that represents the components and the subcomponents of a

system. Below is a system architecture to show the relationship between different components.

15
 Figure 4.1 System Architecture

Figure 4.1 shows the system architecture that represents the component of the system and

the relationship between these components. The components of this system architecture is

the user, the hardware, the mobile application, the server and the database.

This application has two types of users which is User and Admin. The user will be able to

access the application by using a mobile client which is their mobile phone. The user will

use the application to generate QR code, scan QR code and view the details stored in the

QR code scanned. The second user is the admin. Admin will be able to access the

browser client and the database of the system.

16
Each of these actions requires the interaction between the application, the server and the

database. Whenever the user performs an action, the application will send a request to the

server. Then, the server will perform queries to execute the request from the application

to extract, insert or update the data in the MySQL database.

4.3 Interface Design

Login

Description and Priorities

This function allow system to check either the login user is the account owner or not, by request

their ID and password.

Priorities: High Functional requirements:

1. The system shall allow user to enter id and password to login.

2. The system shall allow user login if both inputs are correct.

3. The system shall allow logged in user to use all the features which provided in their

account.

4. The system shall notify user if either one of the input was wrong.

Name Login

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable account owner to access their account

to the application.

Primary actor(s) UNITEN Undergraduate Student, Admin

17
Other actor(s) NA

Pre-condition 1. The user is UNITEN student or admin.

Post condition NA

Result(s) - The user success to login into their account.

Main Scenario 1. User need to click “login” button in order to access

login page.

2. User need to enter their name and id, and click

“Submit” button.( Figure 4 and 5)

3. The system checks both input in database to read their

level and display correlation menu page.( Figure 6

and 7)

Alternative Scenario NA

Exception Scenario 1. If one of the inputs (ID and password) was invalid value or

empty, the system will perform action of step 2 again.

2. If one of the inputs or both inputs was not found in

database, the system will also perform action of step 2 again.

Related Use case(s) NA

18
Screen Sketches:

Figure 1: Login page undergraduate Figure 3: Main page for student.

student.

19
Figure 2: Login page for admin. Figure 4: Main page for admin.

Generate QR Code

Description and Priorities

This function allow user to generate their QR code which will connect to their personal details page.

Priorities: High Functional requirements:

1. The system shall allow user to generate their QR code if their personal detail have been

filled up.
20
Name Generate QR Code

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable user to generate and get their QR

code.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1.The user is authenticated to login into the system.

Post condition NA

Result(s) - The user QR code have been generated.

Main Scenario 1.The user clicks on “Generate QR Code” button in the main

page to access “Generate QR Code” page.

21
 2.The system will generate a QR code for user if they have

already filled up their personal detail. (Figure 8)

Alternative Scenario NA

Exception Scenario 2.1 If user did not fill up those constraint of personal details,

then the system will not create QR code.

2.2 The system will automatically access to “Enter User Detail”

page.

Related Use case(s) NA

Screen Sketches:

Figure 5: QR code have been generated.

22
Enter User Detail

Description and Priorities

This function allow user to enter their personal details and to be save in database. Priorities : High

Functional requirements :

2. The system shall allow user to enter all their personal details.

3. The system shall allow user to save their key in details.

Name Enter User Detail

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable user to save user detail in database.

Primary actor(s) UNITEN Undergraduate Student

23
 Other actor(s) NA

Pre-condition 1.The user is authenticated to login into the system.

Post condition NA

Result(s) - The user QR code have been saved in database.

Main Scenario 1. The user clicks on “Enter User Detail” button in the

“Generate QR Code” page.

2. User need to fill up specific personal details and clicks

“save” button. (Figure 9)

3. Those user detail will be store in database and under user

account.

Alternative Scenario NA

Exception Scenario 2.1 If user did not fill up those constraint of personal details,

then the system will not allow the “save” button to

be clicks.

Related Use case(s) NA

Screen Sketches:

24
Figure 6: Page of enter user detail.

Scan QR Code

Description and Priorities

This function allow user to scan the QR code which is stick on lost thing. Priorities: High

Functional requirements:

1. The system shall able to scan the QR code which is stick on lost thing.

25
 2. The system shall ask user permission of send their personal detail to lost thing’s owner,

in purpose to get lost thing’s owner detail.

Name Scan QR Code

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable user to scan and read the QR code

which is stick on lost thing.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1. The user is authenticated to login into the system.

Post condition NA

Result(s) - User success to scan QR code and get to view owner

detail.

Main Scenario 1. User clicks on “Scan QR Code” button in the main page.

2. User need to scan the QR Code which stick on the lost

thing. (Figure 10)

3. System find the user detail of the scanned QR code in

database.

4. System require user permission of send their personal

detail to lost thing owner’s. (Figure 11)

5. System display lost thing owner’s details.

Alternative Scenario NA

26
 Exception Scenario 2.1 If the QR code was broken, system will not able to

response and move to next step.

4.1 If the user not allow their details to be send to lost

thing owner, then the system will not show lost thing owner’s

details.

Related Use case(s) NA

Screen Sketches:

27
Figure 7: Page of Scan QR code. Figure 8: Ask permission of send user details to lost thing’s

owner.

Display Owner Detail

Description and Priorities

This function allow user to view lost thing’s owner details. Priorities: High

Functional requirements:

1. The system shall display all the owner detail on user phone.

28
Name Display Owner Detail

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable user to view lost thing owner’s

details.

Primary actor(s) Student

Other actor(s) NA

Pre-condition 1. The user is authenticated to login into the system.

2. User allow of send their personal detail to lost thing

owner’s

Post condition NA

Result(s) - Lost thing owner’s details was showing on user phone.

Main Scenario 1. User clicks on “Scan QR Code” button in the main page.

29
 2. User need to scan the QR Code which stick on the lost

thing. (Figure 10)

3. System find the user detail of the scanned QR code in

database.

4. System require user permission of send their personal

detail to lost thing owner’s. (Figure 11)

5. System display lost thing owner’s details. (Figure 12)

Alternative Scenario NA

Exception Scenario 2.1 If the QR code was broken, system will not able to

response and move to next step.

4.1 If the user not allow their details to be send to lost thing

owner, then the system will not show lost thing owner’s

details.

Related Use case(s) NA

Screen Sketches:

30
Figure 9: Lost thing’s owner detail.

View Notification

Description and Priorities

This function allow user to receive and view notifications about the details of owner user scanned,

and the people who have scanned their QR code.

Priorities : High Functional requirements :

31
 1. The system shall keep all the event about user have scanned who’s QR code and user’s

QR code have been scanned by who.

2. The system shall allow use to view all the history which keep in notification.

Name View Notification

Source(s) System – Lost Item Tracking System

Associated Goal(s) The system shall display all the previous history.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1. Given the user QR code have been scanned by other or user

have scanned other people’s QR code.

Post condition NA

Result(s) - All the history events will be display.

Main Scenario 1. User clicks on “View Notification” button in the main

page.

2. System take data from database and display all the

account’s history. (Figure 13)

Alternative Scenario NA

Exception Scenario NA

Related Use case(s) NA

Screen Sketches:

32
Figure 10: Page of View Notification.

33
Select Setting

Description and Priorities

This function allow user to use “Edit Profile”, “Choose Language”, “Help”, and “Contact Admin”

features, which is extend from function setting.

Priorities: High Functional requirements:

1. The system shall display features use “Edit Profile”, “Choose Language”, “Help”, and

“Contact Admin”.

2. The system shall allow user to use all the four feature.

Name Select Setting

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall access and display the page user wanted to

go.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1. The user is authenticated to login into the system.

Post condition NA

Result(s) - All the features inside Setting page will be display.

Main Scenario 1.User clicks on “Settings” button in the main page. 2.System

access to Setting page.

3.System display features “Edit Profile”, “Choose Language”,

“Help”, and “Contact Admin”. (Figure 14)

Alternative Scenario NA

34
 Exception Scenario NA

Related Use case(s) NA

Screen Sketches:

35
Figure 11: Page of Settings.

Edit Profile

Description and Priorities

This function allow user to edit and customize their account details to their own preferences.

Priorities: Medium Functional requirements:

1. The system displays current user details.

2. The system shall allow user to change and customize their details and save it.

3. The system shall save and replace old details to new user details into database.

36
Name Edit Profile

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable user to edit their current details and

customize the page.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1.The user is authenticated to login into the system.

Post condition NA

Result(s) - The customized profile done by the user will be displayed

and shown to other users who visit their account.

37
 Main Scenario 1. User clicks the “Setting” button and “Profile Setting”

button in the settings.

2. User can customize their account with their own style,

providing relevant information in their own page. (Figure

15)

3. Once the user is done filling up the relevant information

and customized their account, they will click on “Done”

button in the page to update their account.

4. System will save the new user detail to replace the old

one in database.

5. Now the profile visitors are able to view custom design

of the user’s account.

Alternative Scenario NA

Exception Scenario 3.1 If the user does not wish to enter certain details, they can

leave some of the sections blank and continue with the other

parts.

3.2 If the user wishes to change their current profile

information and aesthetics to something different, they can

change it anytime they want.

Related Use case(s) NA

Screen Sketches:

38
Figure 12: Page of Edit Profile.

39
Choose Language

Description and Priorities

This function allow user to change language between English and Malay as application’s default

language.

Priorities : Medium Functional requirements :

1. The system shall display all the possible language that can be choose.

2. The user need to choose what language they wanted to use.

3. The system shall change application’s language to the language which selected by user.

Name Choose Language

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall able user to choose application’s language.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1. The user is authenticated to login into the system.

Post condition NA

Result(s) - The application language which chosen by user will

be use as default language.

Main Scenario 1. User is entered in the setting page of the system.

2. User clicks on “Choose Languages” button. 3.System

shall display possible language that can be

choose. (Figure 16)

4. User choose the application’s language for default language.

5. Application’s language shall be change to the default

40
 language.

6. Application will be refresh and default language will be use.

Alternative Scenario NA

Exception Scenario NA

Related Use case(s) NA

Screen Sketches:

41
Figure 13: Choose language user interface.

Display Help

Description and Priorities

This function acts as a guide and a tutorial that will help explain the user on how to use application

and make their usage of the application much easier.

Priorities : High Functional requirements :

1. The system shall display application guide line for the whole system.

2. The system shall allow user to choose which part they wanted to read.

3. The system shall display the part of guide line which chosen by user.

42
Name Display Help

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall provide relevant information that will guide

the user through the system.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1.The user is authenticated to login into the system.

Post condition NA

Result(s) - The system displays system guide line for user to read.

Main Scenario 1. User is entered to the “Setting” page of the system.

2. User clicks on “Help” button.

43
 3. System shall display system guide line list. (Figure

17)

4. User need to choose the guide line part they wanted to

read.

5. System shall take data from database and display

selected guide line part.

Alternative Scenario NA

Exception Scenario NA

Related Use case(s) NA

Screen Sketches:

Figure 14: Page of Help.

44
Report to Admin

Description and Priorities

This function will be use when user facing problems to the system. User is able to send comment to

admin in purpose to get help.

Priorities : High Functional requirements :

1. The system shall allow user to fill up personal info and comment of system problem.

2. The system shall allow user to submit the report to admin.

45
 Name Report to Admin

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall provide boxes to get user info and comment.

Primary actor(s) UNITEN Undergraduate Student

Other actor(s) NA

Pre-condition 1.The user is authenticated to login into the system.

Post condition NA

Result(s) - User success to send their problem to admin.

Main Scenario 1. User is entered to the “Setting” page of the system.

2. User click “Contact Admin” button.

3. System shall display boxes for user to key in their

detail and comment of system. (Figure 18)

4. User need to fill up all the boxes and clicks “Submit

Request” button.

5. System shall save the report and send it to system

report profile.

Alternative Scenario NA

Exception Scenario 4.1 If user did not fill up all those boxes, then the system will

not allow the “Submit Request” button to be clicks.

Related Use case(s) NA

Screen Sketches:

46
Figure 15: Page of Help.

47
Modify Student Account Status

Description and Priorities

This function allow admin to modify UNITEN undergraduate student account. Priorities : High

Functional requirements :

1. The system shall allow Admin to create account, frozen account, unfrozen account, and

delete account.

2. The system shall update all the change of UNITEN undergraduate student account by

admin.

Name Modify Student Account Status

Source(s) System – UNITEN Lost Item Tracking System

Associated Goal(s) The system shall enable admin to manage and control all

account.

Primary actor(s) Admin

Other actor(s) NA

Pre-condition 1. The user is authenticated to login into the system

Post condition NA

Result(s) - Admin success to modify UNITEN undergraduate

student account.

48
Main Scenario 1. Admin clicks the “Modify Student Account Status”

button in the main page.

2. Admin can view all accounts status and choose to use

either “frozen account”, “unfrozen account”, and

“delete existing account” function. (Figure 19,20,21)

3. Admin need to type in the student account number

which wanted to modify, and clicks “Change”

button. (Figure 22)

4. The new status of the modified account will be saved

in database.

5. The current page will be refresh and display again.

Alternative Scenario NA

Exception Scenario 3.1 If the account number have been typed in was not match.

An error message will be display.

Related Use case(s) NA

49
Screen Sketches:

Figure 16: Page of View frozen account. Figure 17: Page of View unfrozen account.

50
Figure 18: Page of delete existing Figure 19: Page of change student account status.

student account.

Log out

Description and Priorities

This function allows logged in user and admin to log out the system. Priorities: High

Functional requirements:

1. The system shall allow user to log out when they wanted.

Name Log out

Source(s) System – UNITEN Lost Item Tracking System

51
Associated Goal(s) The system shall enable account owner to access their account

to the application.

Primary actor(s) Student, Admin

Other actor(s) NA

Pre-condition 1.The user is logged in user.

Post condition NA

Result(s) - The user and admin successfully to log out from their

account.

Main Scenario 1. User need to click “Exit” button in order to log out

their account. (Figure 23 and 24)

2. System shall display successfully log out message.

Alternative Scenario NA

Exception Scenario NA

52
 Related Use case(s) NA

Screen Sketches:

Figure 20: Log out button is on the main page.

53
4.4 Database Design

Figure 4.2: Data Modeling Diagram of the Lost Item Tracking System

The data descriptions of each of these data entities is as follows:

54
Entity Attribute Description Data Type Constraint

Account StudentID Foreign Key Varchar2(8) Not Null

UNITEN
student’s ID
number

55
 Password Primary Key Varchar2(15) Not Null
UNITEN
student’s
unique
password

Student StudentID Primary Key Varchar2(8) Not Null

UNITEN
student’s ID
number

Name Name of Varchar2(20) Not Null

student

Phone_Number Personal Number(11) Not Null

phone
number of
students

Email_Address Personal Varchar2(20) Not Null

email address
of student

Address Home or Varchar2(25) Null

Hostel
address of
student

QR Code StudentID Foreign Key Varchar2(8) Not Null

UNITEN
student’s ID
number

56
 Phone_Number Primary Key Number (11) Not Null
Personal
phone
number of
students

Name Name of Varchar2(20) Not Null

student

Email_Address Personal Varchar2(20) Not Null

email address
of student

Address Home or Varchar2(25) Null

Hostel
address of
student

Notification Scanner_Phone_Number Primary Key Number (11) Not Null

Phone number
of QR code
scanner

StudentID Foreign Key Varchar2(8) Not Null

UNITEN
student’s ID
number

Scanner_ Name Name of Varchar2(20) Not Null

scanner

Scanner_ Personal Varchar2(20) Not Null

Email_Address email address
of scanner

57
Scanner_ Address Home or Varchar2(25) Null
Hostel
address of
scanner

58
 CHAPTER 5

5.1 Conclusion

For people who lost their things, the Lost Item Tracking System is an information system that

will provide information about the owner of the things that lost to who found it. The system

will store the name and contact information of the thing’s owner in the QR code and people

can simply print it and attached to their belongings. To people who found any things, they

can scan the QR code to contact the person. This system will help people to find their

personal thing’s. Unlike the current situation where people post about their missing product

on social media to find it, our product will help people to find their belongings in a short

period.

In conclusion, the QR Tracking Code System is meant to help the UNITEN Committee by

reducing the effort to find their lost belongings. For the FYP 2 this system will be developed

as a hybrid application that can be used by both android and ios users.

59
 REFERENCES

1- "Two-Dimensional Bar-code Decoding with Camera-Equipped Mobile Phones".

Retrieve from https://ieeexplore.ieee.org › document

2- "Barcode Readers using the Camera Device in Mobile Phones". Retrieve from
https://ieeexplore.ieee.org › document

3- Share and Discover Knowledge on LinkedIn SlideShare. Retrieve from

https://www.slideshare.net

4. https://www.softwareadvice.com/inventory-management/qr-inventory-profile/

60
APPENDIX A: SOFTWARE REQUIREMENTS SPECIFICATIONS

61
 Software Requirements
Specification
for

LOST ITEM TRACKING

SYSTEM
[Version 2.0 ]

Prepared by [Harveen a/l Velan]

[Date :March 19, 2021]

62
63
Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page lxiv

Table of Contents
1. Introduction ..............................................................................................................................1
1.1 Purpose.......................................................................................................................................... 1
1.2 Project Scope and Product Features .............................................................................................. 1
1.3 Definitions, Acronyms, and Abbreviations ................................................................................... 2
1.4 References ..................................................................................................................................... 3
1.5 Overview ....................................................................................................................................... 3
2. Overall Description ..................................................................................................................4
2.1 Product Perspective ....................................................................................................................... 4
2.2 Product Functions ......................................................................................................................... 7
2.3 User Classes and Characteristics................................................................................................... 8
2.4 Constraints .................................................................................................................................... 8
2.5 Assumptions and Dependencies.................................................................................................... 8
2.6 Apportioning of Requirements...................................................................................................... 8
3. System Features .......................................................................................................................9
4. Other Nonfunctional Requirements .....................................................................................14

Revision History
Name Date Reason For Changes Version
HARVEEN 19/03/21 Reason (initial draft) 1.0
HARVEEN 31/05/21 Final draft 2.0

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 1

1.Introduction
This document is System Requirements Specification (SRS) for “Lost Item Tracking System”. The
aim of this document is to gather and analyze and give an in-depth insight of the complete Lost Item
Tracking System by defining the problem statement in detail.

1.1 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come up to define
the system, its requirements with respect to consumers. Also, we shall predict and sort out how we
hope this product will be used in order to gain a better understanding of the project, outline concepts
that may be developed later, and document ideas that are being considered, but may be discarded as
the product develops.

Moreover, the purpose of this SRS document is to provide a detailed overview of our software
product, its parameters and goals. This document describes the project’s target audience and its user
interface, hardware and software requirements. It defines how our client, team and audience see the
product and its functionality. Nonetheless, it helps any designer and developer to assist in software
development lifecycle (SDLC) processes.

1.2 Project Scope and Product Features

Lost Item Tracking System is a mobile phone application which will support to UNITEN
undergraduate student and admin. Students need to enter their personal details into the system.
When an item is lost, students can scan the QR code sticker which stick on it, and code shall be
send to the system. Then, the system shall send the lost thing owner detail to the person that scan it.
The system shall also send a notification to the owner of the lost thing. In other side, administrator
may get student details from the system. Administrator may change and send the student account
status back to the system. Figure 1 below show context diagram of our system.

Figure 1: Lost Item Tracking System Context Diagram

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 2

1.3 Definitions, Acronyms, and Abbreviations

Acronyms and Definitions

Abbreviations

QR-CTS Quick Response - Code Tracking System.

UNITEN College of Computing and Informatic.

User Person that interacts with the system (UNITEN

undergraduatestudent).

Admin/Administrator System administrator who is given specific permission for

managing and controlling the system.

SDLC Software Development Life Cycle.

NA No applicable

PF Product Function

C Design and Implementation Constraints

AD Assumptions and Dependencies

SRS Software Requirement Specification

PR Performance Requirements

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 3

PK Primary Key

FK Foreign Key

REL Reliability

AVL Availability

SEC Security

MAI Maintainability

POR Portability

Uniten University Tenaga Nasional

1.4 References
1- "Two-Dimensional Bar-code Decoding with Camera-Equipped Mobile Phones".
Retrieve from https://ieeexplore.ieee.org › document

2- “Barcode Readers using the camera device in Mobile Phone”. Retrieve from
https://ieeexplore.ieee.org › document

3- Share and Discover Knowledge on LinkedIn SlideShare. Retrieve from

https://www.slideshare.net

1.5 Overview

This document contains four sections:

Section 1 contains the purpose, scope, definitions, acronyms and references made to other
documents
Section 2 contains the overall description of the application, including constraints and assumptions.
Section 3 contains specific requirements of the system to be implemented. Section 4 contains other
non-functional requirements for the application.

2. Overall Description
This section will give an overview of the whole Lost Item Tracking System. The system
background will be providing, and system functional requirement will be describing in hare. This
section will consist of “Product Perspective”, “Vision Statement of the Solution”, “Product
Function”, “User classes and characteristics”, “Design and Implementation Constraints”, “User
Documentation” and “Assumptions and Dependencies
Copyright © [2021] by [Harveen Velan]. All Rights Reserved.
Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 4

2.1 Product Perspective

This subsection explains about the application’s interaction with other system. This subsection also
describes about how the application would operate inside various constraints. These constraints
include:

a) System interfaces
b) User interfaces
c) Hardware interfaces
d) Software interfaces
e) Communications interfaces
f) Memory
g) Operations
h) Site adaptation requirements

2.1.1 System interfaces

This system consists of thirteen main features:

PF1- User can login with their id and password.

PF2- User can generate their own QR code, when they have filled up their personal details.

PF3- User can key in and save their personal details.

PF4- Provide quick response method to get lost thing owner details. PF5- Allow user to view lost
thing owner details.

PF6- User can view their history about the name of owner they scanned, and the people who have
scanned their QR code.

PF7- User is given choose to use Profile Setting, Choose Language, Help, and Contact Admin.

PF8- User can view and change their personal details.

PF9- User can change system language between English and Malay. PF10- User can view system
guide line to get help.

PF11- User can report problem facing to admin.

PF12- Admin can create account, frozen account, unfrozen account, ban account and delete account.

PF13- Allow logged in user to log out

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 5

2.1.2 User interfaces

The user interface for this application shall be compatible with any android and ios smartphones.
The user interface shall be implemented with any tool or software package. Details for the user
interface will be included in System Design.



2.1.3 Hardware interfaces

The application can only be accessed on android and iOS mobile phones. All hardware for the
application requires a connection to the internet. All devices require camera functionality to access
or detect the QR code.

2.1.4 Software interfaces

Following are the software used for the mobile application.

Software Used Description

MySQL Database To save details register by the user.

Xamarin A framework that helps in mobile application development.

2.1.5 Communications interfaces

Lost Item Tracking System application shall use HTTP protocol for communication over the
Internet.

2.1.6 Memory constraints 


Not Applicable.

2.1.7 Operations 


Refer to User Interface.

2.1.8 Site adaptation requirements

Not Applicable.

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 6

2.2 Product Functions

2.3 User Classes and Characteristics

There will be two types of user to our system, which is UNITEN student, and administrator. These
two types of user are playing different role respectively to our Lost Item Tracking System.

UNITEN This type of user is allowed to use most of the system features. They
Student are able to use the system to generate their own personal QR code,
and scan other people’s QR code. For an example, if user found any
lost thing, they can scan the QR code sticker which stick
on lost thing in order to get owner detail, and return the thing. This is
same of their QR code to other people.

Administrator Administrator is only allowed to view and manage system’s database.

They are allowed to make changes to our system and database. For
example, they can modify account status and delete
student account which was expired.

2.4 Constraints
CT-1: This web application requires a maximum of 4 months for thedevelopment,

with 1 month for the testing and reworks.

CT-2: For final year project purpose, the application is built by only one person.
Copyright © [2021] by [Harveen Velan]. All Rights Reserved.
Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 7

2.5 Assumptions and Dependencies

AD1- System should only allow UNITEN student to access application.

AD2- User should have a valid internet to login and use the application.

AD3- The QR Code Sticker should be in good condition.

AD4- System should only allow to be use at smart phone with version more than 4 for Android and
version more than 7 for IOS.

AD5- Project scope will not require to be change when stakeholder sign off the scope statement.

AD6- Project model will not change throughout the execution of system.

AD7- UNITEN provide permission for UNITEN student to use the application.

AD8- UNITEN provide a server for this system to be run in internet

2.6 Apportioning of Requirements

Not Applicable

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 8

3. System Features
Login
Description and Priorities

This function allow system to check either the login user is the account owner or not, by
request their ID and password.

Priorities : High

Functional requirements :

1.The system shall allow user to enter id and password to login.

2.The system shall allow user login if both inputs are correct.
3.The system shall allow logged in user to use all the features which provided in
their account.
4.The system shall notify user if either one of the input was wrong.
Name Login
Source(s) System - Lost Item Tracking System
Associated Goal(s) The system shall enable account owner to access their
account to the application.
Primary actor(s) UNITEN Undergraduate Student, Admin
Other actor(s) NA
Pre-condition 1. The user is UNITEN student or admin.
Post condition NA
Result(s) - The user success to login into their account.
Main Scenario 4. User need to click “login” button in order to access
login page.
5. User need to enter their name and id, and click
“Submit” button.( Figure 4 and 5)
6. The system checks both input in database to read
their level and display correlation menu page.( Figure
6 and 7)
Alternative Scenario NA
Exception Scenario 2.1 If one of the inputs (ID and password) was invalid
value or empty, the system will perform action of step 2
again.
3.1 If one of the inputs or both inputs was not found in
database, the system will also perform action of step 2 again.
Related Use case(s) NA

Generate QR code
Description and Priorities
This function allow user to generate their QR code which will connect to their
personal details page.
Priorities : High
Functional requirements :

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 9

1.The system shall allow user to generate their QR code if their personal detail
have been filled up.
Name Generate QR Code
Source(s) System – UNITEN Lost Item Tracking System
Associated Goal(s) The system shall enable user to generate and get their QR
code.
Primary actor(s) UNITEN Undergraduate Student
Other actor(s) NA
Pre-condition 1.The user is authenticated to login into the system.
Post condition NA
Result(s) - The user QR code have been generated.
Main Scenario 1.The user clicks on “Generate QR Code” button in the
main page to access “Generate QR Code” page.

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 10

2.The system will generate a QR code for user if they

have already filled up their personal detail. (Figure 8)
Alternative Scenario NA
Exception Scenario 2.3 If user did not fill up those constraint of personal
details, then the system will not create QR code.
2.4 The system will automatically access to “Enter User
Detail” page.
Related Use case(s) NA

Enter User Details

Description and Priorities

This function allow user to enter their personal details and to be save in database.
Priorities : High
Functional requirements :
1.The system shall allow user to enter all their personal details.
2.The system shall allow user to save their key in details.
Name Enter User Detail
Source(s) System – UNITEN Lost Item Tracking System
Associated Goal(s) The system shall enable user to save user detail in database.
Primary actor(s) UNITEN Undergraduate Student

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 11

Other actor(s) NA
Pre-condition 1.The user is authenticated to login into the system.
Post condition NA
Result(s) - The user QR code have been saved in database.
Main Scenario 1.The user clicks on “Enter User Detail” button in the
“Generate QR Code” page.
2.User need to fill up specific personal details and clicks
“save” button. (Figure 9)
3.Those user detail will be store in database and under
user account.
Alternative Scenario NA
Exception Scenario 2.1 If user did not fill up those constraint of personal
details, then the system will not allow the “save” button to
be clicks.
Related Use case(s) NA

Scan QR Code

Description and Priorities

This function allow user to scan the QR code which is stick on lost thing.
Priorities: High
Functional requirements:

1,The system shall able to scan the QR code which is stick on lost thing

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 12

2.The system shall ask user permission of send their personal detail to lostthings
owner, in purpose to get lost thing’s owner detail.

Name Scan QR Code

Source(s) System – UNITEN Lost Item Tracking System
Associated Goal(s) The system shall enable user to scan and read the QR code
which is stick on lost thing.
Primary actor(s) UNITEN Undergraduate Student
Other actor(s) NA
Pre-condition 1. The user is authenticated to login into the system.
Post condition NA
Result(s) - User success to scan QR code and get to view owner
detail.
Main Scenario 6. User clicks on “Scan QR Code” button in the main
page.
7. User need to scan the QR Code which stick on the lost
thing. (Figure 10)
8. System find the user detail of the scanned QR code in
database.
9. System require user permission of send their personal
detail to lost thing owner’s. (Figure 11)
10. System display lost thing owner’s details.
Alternative Scenario NA
Exception Scenario 2.1 If the QR code was broken, system will not able to
response and move to next step.
4.1 If the user not allow their details to be send to lost
thing owner, then the system will not show lost thing owner’s
details.
Related Use case(s) NA

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 13

4. Other Nonfunctional Requirements

4.1 Performance requirements

The requirements in this section provide a detailed information regarding to the system
performance.

PR1- The system should login and logout the user account within 2 second.

PR2- After scanning the QR code, receive time of owner details will not more than 4 second.

PR3- The system speed should not be affected, when login user not more than 1000 people.

PR4- If the system down suddenly, it will automatically start up within 3 minutes.

4.2 Logical database requirements

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.

Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 14

4.3 Design constraints

C-1. Input modes / data types, including numeric, alphanumeric, binary/byte and
kanji/kana.

C-2. The amount of data storage capacity (40-L)

C-3. Standards for QR Code documented with JIS or ISO.

C-4. Size of generated QR code should be at least 1 x 1 inch. Or 2.5 x 2.5 cm (in
width and height)

C-5. QR Code should have appropriate margin width.

C-6. QR Codes need a high error correction level to remain scannable.

C-7. Overall development budget is RM 40,000.

C-8, Overall development period is less than 6 months.

4.3.1 Standards compliance

4.4 Software system attributes

This section will state quality properties for the entire QR-CTS. Below show five
quality properties which relate to this system.

4.4.1 Reliability

REL1- No more than 3 bugs will occur to QR-CTS in a year.

REL2- A bug will be solved no more than two days.

4.4.2 Availability

AVL1- QR-CTS should work 24hours during whole week.

AVL2- QR-CTS should be down at last day of each month, for service purpose.

4.4.3 Security

SEC1- QR-CTS should lock the user’s account after five time getting wrong password
and send a massage with an additional password for unlock the account to the user.

SEC2- The user should available to change new password when they have enter current
password correctly.

4.4.4 Maintainability

MAI1- QR-CTS should no need more than one week for programmer to add a new
Copyright © [2021] by [Harveen Velan]. All Rights Reserved.
Software Requirements Specification for [QR CODE TRACKING SYSTEM] Page 15

system feature.

MAI2- QR-CTS should test in every perspective more than 30 times when bug happen.

4.4.5 Portability

POR1- The application of QR-CTS should work on every phone’s Operating System.

Appendix A: Title of Appendix

Content of appendix. An appendix shall begin in a new fresh page.

Copyright © [2021] by [Harveen Velan]. All Rights Reserved.