1

ADAMA SCIENCE AND TECHNOLOGY UNIVERSITY

School of Electrical Engineering and Computing
Department of Computer Science and Engineering

Software requirement engineering (SSng 3201)

Software Requirement Specification for laptop anti-theft system

Team members:
Name ID

1. Abdulwahid Hussen …………………………….……….…. ugr/25287/14

2. Abenezer Sleshi…………………………………….…..…… ugr/25491/14
3. Amanuel Asefa…………………………………….…….……ugr/25354/14
4. Ananiya Fekede ………………………………………..……..ugr/25832/14
5. Debela Berako………………………………………….……..ugr/25581/14
6. Dejene Samuel………………………………………….……..ugr/25459/14
7. Gelila Mihirke…………………………………………..…….ugr/25683/14
8. Ifnan Feysal……………………………………………….…..ugr/26050/14
9. Mihret Habtamu…………………………………………….…ugr/25499/14
10. Mihret Lealem………………………………………….……..ugr/25335/14

Submission Date: 12/02/2024

submitted to:
2

Table of Contents
Chapter one............................................................................................................................................4
1.1. Introduction................................................................................................................................4
1.2. Background of Project...............................................................................................................5
1.3. Statement of the Problem..........................................................................................................5
1.4. Purpose of Project......................................................................................................................5
1.5. Objectives of the Project...........................................................................................................5
1.6. Feasibility Study.........................................................................................................................5
1.6.1. Technical Feasibility..........................................................................................................6
1.6.2. Operational Feasibility......................................................................................................6
1.6.3. Economic Feasibility..........................................................................................................7
1.7. Project Scope and Limitation...................................................................................................8
1.8. Significance of the project.........................................................................................................9
1.9. Methodology.............................................................................................................................10
1.9.1. Data Collection Methodology.........................................................................................10
1.9.2. Software Development Methodology.............................................................................11
1.9.3. Development tools............................................................................................................12
1.10. Testing plan...........................................................................................................................13
1.10.1. Unit testing........................................................................................................................13
1.11. Overview of the project phase................................................................................................15
1.12. Schedule................................................................................................................................17
1.13. Team composition................................................................................................................17
Chapter two..........................................................................................................................................20
2. Description of major system.......................................................................................................20
2.1. Description of the existing system......................................................................................20
2.2. Users of current system.......................................................................................................20
2.3. The problem of the current system....................................................................................20
2.4. Business rule of the current system....................................................................................21
Chapter 3..............................................................................................................................................22
3. Proposed System..........................................................................................................................22
3.1 Overview.......................................................................................................................................23

3.2. Functional Requirements........................................................................................................23

3.3. Non-functional Requirements.................................................................................................24
3.4. System Model...........................................................................................................................24
3.5. Constraints and Assumptions.................................................................................................26
3.6. USE CASE MODEL................................................................................................................27
3

3.6.1. Main Actor of the system.................................................................................................27

3.6.2. Use case diagram..............................................................................................................34
3.7. Object model............................................................................................................................34
3.8. sequence diagram.....................................................................................................................36
3.9. activity diagram.......................................................................................................................38
3.10. state diagram........................................................................................................................40
Chapter four.........................................................................................................................................42
4. system design................................................................................................................................42
4.1. overview....................................................................................................................................42
4.1.1. purpose of the system......................................................................................................42
4.1.2. design goal........................................................................................................................42
4.2. proposed system architecture.................................................................................................42
4.2.1. hardware/software mapping...........................................................................................43
4.2.2. The RFID work flow........................................................................................................44
4.2.3. deployment diagram........................................................................................................45
Reference..............................................................................................................................................47
4

Chapter One
1.1. Introduction

The central library at ASTU serves as a critical resource for students to access reference
materials, study spaces, and technology required for their academic success. However, the
rise in laptop thefts from the library has become a pressing issue, resulting in financial losses,
inconvenience, and disruption of studies for students.
To address this problem, ASTU aims to implement a laptop anti-theft system specifically for
the central library. This system will deter theft attempts and enable tracking of laptops
through technical solutions like RFID tagging and scanning.
This document provides a comprehensive system analysis for the proposed laptop anti-theft
system. It will examine the context, requirements, and design considerations for developing
an effective solution tailored to ASTU's needs.
The analysis begins by reviewing the major functions, users, and limitations of the current
central library system. This provides a basis for contrasting the benefits and new capabilities
of the anti-theft system.
Key areas covered include:
 User roles and major stakeholder groups
 Functional and non-functional requirements
 Business rules governing system operation
 Process flows for registration, tagging, and scanning
 Integrations with student databases and library systems
 Reporting needs and metrics to quantify impact
By thoroughly analyzing the gaps in the current environment, this system analysis aims to
build a strong foundation for the new anti-theft system. The requirements and context
established will inform the development of a robust, user-centric solution that addresses
ASTU's specific security challenges.
The completed analysis will provide clarity on the path forward to design, build, and deploy
an effective laptop anti-theft system for the central library. This will significantly improve
protection for students' devices and serve as a model for enhancing security across ASTU.

1.2. Background of Project

The laptop theft incidents in the central library at ASTU (Adama Science and Technology
University) have been a recurring problem. Numerous laptops have been reported stolen,
causing significant inconvenience and financial loss to the university and its students. The
need for an effective solution to mitigate this issue and ensure the safety of personal
belongings within the library has become imperative.
5

1.3. Statement of the Problem

The prevalence of laptop theft in the ASTU central library poses a serious security concern.
Some students with malicious intent take advantage of the library environment to steal
valuable personal computers. This not only affects the affected students but also disrupts the
academic and research activities of the university. It is crucial to develop a robust and reliable
system that can effectively control and prevent laptop theft incidents.

1.4. Purpose of Project

The purpose of this project is to design and implement a laptop anti-theft system for the
central library at ASTU. This system will enable students to register their laptops and
establish a secure connection between their devices and their profiles. Every time a student
leaves the library, they will be required to scan their laptop, ensuring that it aligns with their
registered profile. By implementing this system, we aim to enhance the security measures in
place and reduce the occurrence of laptop thefts within the central library.

1.5. Objectives of the Project

1.5.1. General Objective of the Project

The general objective of this project is to develop a comprehensive laptop anti-theft system
that effectively prevents and controls laptop theft incidents in the central library at ASTU.

1.5.2. Specific Objective of the Project

The specific objectives of the project include:

 Enabling students to register their laptops securely.

 Implementing a verification process to ensure that laptops leaving the library align
with their registered profiles.

1.6. Feasibility Study

Before proceeding with the project, a feasibility study is conducted assess the technical,
operational, and economic viability of the laptop anti-theft system.

It is essential to conduct a feasibility study to assess the technical, operational, and

economic viability of the laptop anti-theft and tracking system within the ASTU campus.
6

The feasibility study will provide valuable insights and help in making an informed
decision regarding the project's implementation

1.6.1. Technical Feasibility

The technical feasibility study will determine whether the required technology and
infrastructure are available to develop and implement the anti-theft and tracking software.

It will consider factors such as compatibility with existing systems, the availability of
necessary hardware and software components, and the expertise required for development.

 Assessing the compatibility of the software with the existing IT infrastructure,

including operating systems, network protocols, and security system.
 Seamless integration with ASTU database for real-time information updates
 The proposed anti-theft system is easily compatible with existing IT
infrastructure ,like OS,network protocols and security camera.
 Availability of hardware such as Laptops,Desktops and Severs as well as software
tools and frameworks for development .
Technical and development experts :
 Project manager ,
 Back-developer team,
 System architect and feasibility analyst team,
 Database design team and
 Testing and maintenance team.

1.6.2. Operational Feasibility

The operational feasibility study will focus on evaluating the practicality and effectiveness of
implementing the laptop anti-theft and tracking system within the ASTU campus.It will
consider factors such as the willingness of users to adopt the system, the impact on existing
workflows and processes, and the level of support and training required for successful
implementation.

 Assessing the willingness of laptop users(students ) and the library staff to adopt the
system and comply with the necessary security measures.
7

 Evaluating the impact of the system on existing workflows and processes within
ASTU.

 Identifying any modifications or adjustments required to integrate the system

seamlessly.

 Supporting and Training the library staff, including librarians and technicians to adopt
and use the anti-theft system software .

The proposed system should have robust security features to prevent unauthorized
access ,protect sensitive data,and ensure integrity of the system

1.6.3. Economic Feasibility

The economic feasibility study will analyze the financial viability of the laptop anti-theft and
tracking system

Cost Analysis: Estimating the costs associated with system development, hardware
acquisition, software licensing, infrastructure setup, and ongoing maintenance. The main
costs associated with the system are described in the table below:

Tasks and resources Costs

Requirements gathering $20/day

RFID Reader $3500

RFID Tag $10/Laptop

Real-time Database and cloud storage $50/month

Hosting $25/GB

Human Resources 50%/day

Return on Investment (ROI): Assessing the potential benefits of implementing the system,
such as reduced laptop theft incidents, cost savings from recovered laptops, and enhanced
security. Evaluating whether the benefits justify the investment and estimating the potential
ROI.
8

Cost-Benefit Analysis: Comparing the projected costs and benefits to determine the overall
economic feasibility of the project. The analysis will help in making informed decisions
regarding resource allocation and investment.

1.7. Project Scope and Limitation

Scope

 Student Registration: Students will register their personal information, including

name, student ID, and contact details. This information will be securely stored in the
system's database.

 Laptop Registration: Students will register their laptops by providing details such as
the laptop's serial number, make, model, and a clear photo for visual identification.
Each laptop will be assigned an RFID tag, which will be linked to the student's
profile in the database.

 Prevention: The system will implement security measures, such as visible signage,
surveillance cameras, physical barriers, and increased security personnel presence, to
deter potential laptop theft.

 Detection: RFID technology will be used to detect unauthorized removal of laptops

from the library. RFID readers at entrance and exit points will scan the RFID tags on
registered laptops, triggering alerts if unauthorized removal is detected.

 Alerting: When a potential theft is detected, immediate alerts will be generated to

library staff or security personnel. These alerts will provide specific information
about the laptop involved, including its unique identifier, student profile, and the
associated clear photo for visual identification.

Limitations

 False Alarms: The use of RFID tags may lead to false alarms due to technical glitches
or accidental triggering, causing unnecessary disruptions and inconvenience to library
users.
9

 Limited Coverage: The anti-laptop theft system may only cover specific areas within
the library, such as designated laptop zones or study areas, and may not extend to all
parts of the library. This limitation increases the risk of theft in uncovered areas.
 Cost: Implementing a comprehensive anti-laptop theft system with RFID technology
can be expensive. The costs involve the installation of security cameras, sensors,
tracking devices, and software solutions. Budget constraints may limit the scope and
capabilities of the system, potentially compromising its effectiveness.
 Privacy Concerns: The implementation of an anti-laptop theft system that utilizes
RFID tags and surveillance equipment may raise privacy concerns among library
users. Monitoring activities and tracking locations could be perceived as intrusive.
Clear communication and obtaining consent from users are essential to address
privacy concerns.
 Human Error: The system's effectiveness relies on the vigilance and response time of
library staff or security personnel. Human error, such as delayed responses or failure
to act promptly on alerts, can impact the system's ability to prevent or address theft
incidents effectively.
 Legal Considerations: The implementation of an anti-laptop theft system should
comply with relevant laws and regulations, including data protection and privacy
laws. Legal constraints may restrict certain functionalities or require specific
measures to protect user privacy.
 Evolving Theft Techniques: Thieves may develop new methods or techniques to
bypass or circumvent the anti-theft system, necessitating continuous updates and
improvements to maintain its effectiveness. Regular monitoring and adaptation to
emerging threats are crucial to stay ahead of potential theft techniques.

1.8. Significance of the project

The significance of implementing an anti-laptop theft system in a university library can be

viewed from several perspectives:

1. Security Enhancement: The primary significance of the project is to enhance the security
of laptops in the university library. Laptops are valuable assets for students and researchers,
containing important data and personal information. Implementing an anti-theft system
demonstrates the institution's commitment to protecting these assets and creating a safer
environment for users.
10

2. Theft Prevention: The system acts as a deterrent to potential thieves, reducing the
likelihood of laptop thefts occurring within the library premises. By implementing security
measures such as surveillance cameras, sensors, and alarms, the project aims to discourage
theft attempts and protect the property of library users.
3. Peace of Mind for Users: The presence of an anti-laptop theft system provides peace of
mind to library users, knowing that their laptops are being monitored and protected. This
sense of security can enhance the overall user experience and promote a productive learning
environment.
4. Minimizing Disruptions: Laptop theft incidents can disrupt academic activities and cause
inconvenience to students and researchers. By implementing an effective anti-theft system,
the project aims to minimize such disruptions and ensure the smooth functioning of the
library.
5. Institutional Reputation: Implementing an anti-laptop theft system showcases the
university's commitment to the safety and security of its students, faculty, and staff. It
enhances the institution's reputation as a responsible and secure learning environment,
attracting potential students and establishing trust among stakeholders.
6. Compliance and Risk Management: In many cases, universities are legally obligated to
safeguard personal data and protect against theft or unauthorized access. Implementing an
anti-theft system helps the institution comply with data protection regulations, mitigate risks,
and avoid potential legal consequences.
7. Technological Advancement: The project demonstrates the university's adoption of
advanced technologies and innovative solutions to address security challenges. It showcases
the institution's commitment to staying up-to-date with the latest developments and
leveraging technology to enhance user experiences.

1.9 Methodology

1.9.1 Data Collection Methodology

To gather the necessary information and requirements for the laptop anti-theft system, we
employed a fact-finding methodology, which included the following approaches:
11

1. Observation: We extensively surveyed various websites and platforms that have similar
systems in place to understand their functionalities and features. Additionally, we observed
library activities and the behavior of students within the library.

2. Survey: We conducted interviews with library staff to gain insights into the current
security measures implemented within the library. The questions asked during the interviews
were designed to uncover important details, such as:

 Existing security measures in place to prevent theft within the library.

 The number of reported laptop theft incidents within a specific time period.
 Presence and location of surveillance cameras within the library.
 Access control mechanisms, such as ID card swiping or security guards.
 Layout and design of the library, including areas where theft incidents are more
frequent.
 Existing policies or procedures related to laptop usage and storage in the library.
 Current methods for tracking and identifying laptops used by library staff and users.
 Incident reporting mechanisms for theft incidents and how they are handled.
 Any restrictions or limitations on laptop use or storage within the library.
 Specific requirements or preferences for the proposed solution, such as integration
with existing library systems or technology preferences.
During our interactions with the library staff, it was discovered that there have been laptop
theft incidents, particularly where students would leave their laptops unattended, and
individuals would enter the library pretending to own those laptops and subsequently stealing
them.

In addition to the methodology outlined above, we sought guidance and insights from our
instructor, who holds the highest responsibility or position in the system to be developed. Our
instructor provided valuable input regarding the general objectives, constraints, and
technological environment relevant to the project. This interaction further enriched our
understanding of the project scope and requirements, allowing us to consider additional
factors during the design and implementation of the proposed laptop anti-theft system.

1.9.2 Software Development Methodology

Agile methodology will be used as a software development methodology. Agile is well-suited

for software that need flexibility with limited time analysis and design to adapt dynamic
12

requirement. It also involves iterative development, frequent collaboration with stakeholders,

and the ability to respond to feedback quickly .

1.9.3 Development tools

1. Frontend Tools:

 React: JavaScript library for building user interfaces.

 Bootstrap: CSS framework for responsive web design.
2. Backend Tools:

 Frameworks: Django (Python) for building backend applications.

 DRF RESTful API: Used to enable communication between the frontend and
backend systems.
 Database Management Systems: PostgreSQL for data storage and retrieval.
3. Hardware Tools:

 RFID Technology: Hardware devices and sensors for tracking and scanning laptops.
4. Server Tools:

 Web Servers: Such as Apache HTTP Server, Nginx, or Microsoft IIS for hosting the
web application.
 Database Servers: PostgreSQL Server for managing the database.
5. Version Control Tools:

 Git: Distributed version control system for tracking changes in the source code.
 GitHub, GitLab, or Bitbucket: Web-based platforms for hosting and collaborating
on Git repositories.
6. Integrated Development Environments (IDEs):

 Visual Studio Code, PyCharm, Eclipse, or IntelliJ IDEA: IDEs for writing and
debugging code.
7. Testing Tools:

 pytest: Testing frameworks for unit testing.

 Selenium or Cypress: Tools for automated browser testing.
 Postman: Tools for testing and debugging APIs.
13

8. Project Management Tools:

 Microsoft Teams: Communication and collaboration platforms for the project team.

1.10 Testing plan

1. Requirements-based testing: We derived test cases, conditions, and data directly from the
system requirements. This included extensive functional testing to validate that requirements
were met. Non-functional attributes like performance, reliability, and usability were also
tested.

2. Unit testing: We tested individual software components in isolation to verify they

implemented the detailed design correctly. Syntax, semantics, and edge cases were evaluated
at the class level.

3. Security testing: The system's authentication, authorization, and access control

mechanisms were tested by attempting to breach the system with invalid credentials or gain
unauthorized access. Different user roles and privileges were validated.

4. Performance testing: To evaluate performance under different conditions, we configured

and tested the system on diverse operating systems, network environments, and hardware.
Factors like speed, stability, and scalability were examined.

5. Integration testing: After individual components were built, they were integrated and
tested as a group. Integration testing validated how well the components interacted with each
other and with the operating system and external components.

6. System testing: We performed end-to-end testing on the fully integrated system to verify it
matched the requirements. System testing used components that already passed integration
testing. We also conducted user acceptance testing by having non-developers test the system
and provide feedback.

1.10.1 Unit testing

Unit testing is a critical phase in software testing where we meticulously examined individual
software components in isolation to ensure that they adhered to the prescribed detailed
design. At the class level, we scrutinized the code for syntax and semantic errors, leaving no
room for oversight. Additionally, we subjected the components to various edge cases and
14

exceptional scenarios to validate their robustness and reliability. By conducting thorough unit
testing, we aimed to identify and rectify any discrepancies early on in the development
process, thereby bolstering the overall quality and integrity of the software system.

unit testing could be performed for the laptop anti-theft system:

1. Student Laptop Registration Module

 Test registration with valid student credentials

 Test registration with invalid credentials

 Check that laptop is added to system after registration

 Try to register laptop with duplicate serial number

 Verify registration data is stored in database

2. Laptop Checkout Module

 Check laptop availability logic

 Test successful checkout transaction

 Test error handling for invalid student id

 Check laptop status is updated after checkout

3. Laptop Check-in Module

 Test successful check-in transaction

 Check error handling for invalid laptop id

 Verify laptop status updated after check-in

 Confirm late fees assessed for overdue returns

4. Late Fee Calculation Module

 Check fee calculation for early, on-time, and late returns

 Test partial day calculations

 Verify late fees match expected amounts

15

 Test leap year edge case

5. Alarm Module

 Trigger alarm by simulating unauthorized laptop removal

 Verify alarm notification is sent

 Test alarm deactivation after laptop is returned

 Check error handling for faulty sensor input

6. Reporting Module

 Generate each report and verify format and contents

 Test report filters and parameters

 Validate totals match data in database

 Check performance for large data sets

7. Authentication Module

 Test login with valid credentials

 Check login fails with invalid credentials

 Verify appropriate access levels for each user role

 Check session timeouts and access revocation

1.11 Overview of the project phase

Project Overview

Goals:

 Reduce laptop theft incidents at the central library

 Improve security of student-owned devices

 Automate tracking and verification of laptops

 Deter theft attempts through alarms and monitoring

Users:
16

 Primary users are ASTU students who will register and tag their laptops

 Library staff will oversee system operation and scanning

 Admins will manage the system and analyze reports

Requirements Gathering:

 Conducted surveys, interviews, and observation studies with stakeholders

 Documented functional and non-functional requirements

 Created use cases for major system interactions

Analysis and Design:

 Performed gap analysis between current and proposed systems

 Finalized context and process flows for new system

 Developed system architecture, hardware and software specifications

Development Process:

 Implement registration, tagging, and matching modules

 Build alarm triggers and theft detection logic

 Create admin portal for statistics and system management

 Conduct incremental testing and fixes throughout development

Implementation:

 Pilot system rollout in central library

 Train library staff on system operation procedures

 Onboard students to register and tag their laptops

 Iterate based on user feedback from pilot

Measurement and Maintenance:

 Track usage metrics like registrations and scans

 Monitor system uptime, performance, and issues

17

 Manage tags and equipment upkeep

 Release updates and enhancements regularly

1.12 Schedule

Software project scheduling and planning is the timeline of distributing estimated effort
and time across the planned project duration by allocating the effort to specific software
engineering tasks. It is the document that describes how the project will be executed,
monitored, and controlled. The schedule evolves over time. During the early stages of
project planning, a macroscopic schedule is developed.

Time
Phase
First Second Third Fourt Fifth Sixth Week
week Week Week h Week
Week

Requirements gathering
and analysis phase

User design phase

Construction phase

Testing

Maintenance

1.13 Team composition

Team Composition

Title E- Learning

Name E-mail Roll

a) Coordinating and leading

the group
abdulwahidhussen750@g b) General designing
18

Title E- Learning

Abdulwah mail.com c) Implementing and

d) Working documentation
id Hussen e) Editing the document

Gelila gelilamihiirke@gmail.co a) Requirement analyzing.

m b) Specific designing
Mihirke , c) Implementation of the
Team mihrethabtamu1902@gm system and
Composit
Mihret d) Working on the
ail.com
ion Habtamu documentation
e) Editing the document

ananiyafekede@gmail.co a) Requirement analyzing.

m b) Designing the architecture,
c) implementation of the
system and
Amanuel d) Working on the
Asefa, documentation
e) Editing the document
Ananiya
Fekede

a) Requirement analyzing.
b) Designing the architecture,
ifnanfeysal9@gmail.com c) implementation of the
system and
ebenezerseleshi@gmail.c
Ifnan
om
Feysal,
Abenezer d) Working on the
Sleshi documentation
e) Editing the document
19

Title E- Learning

mihretlealem839@gmail. a) Requirement analyzing.

com b) Designing the architecture,
Dereje c) implementation of the
dejenesamuel90@gmail.c system and
Samuel, d) Working on the
om
Debela documentation
Wako, debelaberako9@gmail.co e) Editing the document
m
Mihret
Lealem
20

Chapter two

2. Description of major system

2.1. Description of the existing system

The main purpose of studying the existing system is to develop a new system which
efficiently performs activities than the current one and understands existing problems. The
existing laptop theft prevention system at ASTU's central library functions with very few
security safeguards. People using laptops are allowed to enter and exit the library using this
technology without having to go through rigorous verification processes. The primary means
of identifying the owner of a laptop is through the use of a PC ID card that is provided by
campus security, but its display is not always enforced. Because there are no specific
safeguards in place to confirm ownership or keep an eye on laptop movements within the
library, this careless approach to security makes laptops susceptible to theft. Because of this,
the system is not strong enough to prevent theft and protect personal property, putting
students and staff at danger of cash loss and data breach.

2.2. Users of current system

The users of the current system are primarily students and staff members of ASTU who
utilize the central library for studying, research, and accessing resources. These users are
mainly undergraduate students.

2.3. The problem of the current system

The drawbacks of the current system include:

1. Lack of security measures: The existing system does not have specific security measures to
prevent laptop theft incidents, making it easier for individuals with malicious intent to steal
laptops.

2. Financial loss: Laptop thefts in the central library have resulted in significant financial loss
for both the university and the affected students, who have to bear the cost of replacing their
stolen laptops.

3. Disruption of academic activities: Laptop thefts disrupt the academic and research
activities of the university, as students may lose important data and materials stored on their
21

stolen devices. This can hinder their progress and impact their ability to complete
assignments and projects.

4. Inconvenience for students: Students who have experienced laptop theft face
inconvenience and potential setbacks in their studies, as they have to spend time and effort to
replace their stolen devices and recover lost data

2.4. Business rule of the current system

A crucial component of the present ASTU central library system is identification. It is

anticipated that faculty, staff, and students will have a PC ID card that is provided by campus
security in order to identify their laptops. Nevertheless, there are times when security staff
fails to demand or enforce the display of the PC ID card, demonstrating the inconsistent
application of this identifying measure. As a result, the uneven implementation of identity
protocols leads to vulnerabilities in laptop security, which may enable theft occurrences to
occur on library property. To enhance security measures and reduce the likelihood of laptop
theft, it is crucial to standardize and reinforce the implementation of identity protocols.

 Identification Requirement: According to the implicit business regulation, people

must be able to identify their computers with a PC ID card that was granted by
campus security. Although there is such a rule, it is not consistently enforced,
suggesting a lack of compliance with security procedures.
 Absence of Verification Processes: There isn't a clear method in place to make sure
that people taking computers out of the library are indeed the owners. The lack of
protocols for authentication makes it easier for laptops to be taken from libraries
 Minimal Oversight: It is unable to efficiently trace laptop movement within the
22

Chapter 3
3. The Proposed System

The proposed laptop anti-theft system will operate based on the following business rules:

 Laptop Registration: All students using the central library must register their laptops
to the system. This registration process will involve providing the laptop's unique
identification (Serial number) details, and the student's profile information.
 RFID Tag Attachment: An RFID tag will be securely attached to each registered
laptop to ensure proper identification and tracking. This RFID tag will serve as a
means of verification and detection.
 Laptop Scanning: Before leaving the library, students will be required to place their
laptops near the RFID reader for scanning at a designated checkpoint and scan their
student ID. This scanning process will be overseen by a designated staff member
responsible for monitoring the system.
 Verification and Alarm: The system will compare the scanned RFID tag with the
registered information to ensure the owner ow tha laptop matches with the student
scanning the laptop. If a mismatch occurs or if an unauthorized attempt to remove or
tamper with the RFID tag is detected, an alarm will be triggered, indicating a potential
theft.
 Staff Monitoring: A designated staff member will oversee the laptop scanning
process. They will ensure that each student properly scans their laptop before leaving
the library and address any potential issues or concerns that may arise during the
scanning process.
 System Maintenance: Regular maintenance and updates of the system will be
performed to ensure its optimal functionality and adaptability to new security
challenges. This includes periodic checks and maintenance of the RFID tags to ensure
their integrity and effectiveness in the anti-theft system.
23

3.1. Overview

3.2. Functional Requirements

1. User Registration: The system should provide a user-friendly interface for students to
register themselves by entering their personal information, such as their name,
student ID, and contact details.

2. Laptop Registration: The system should allow students to register their laptops by
entering the laptop's unique identification details (serial number) and associating it
with their student profile.

3. RFID Tag Attachment: The system should facilitate the secure attachment of RFID
tags to registered laptops, ensuring proper identification and tracking.

4. Laptop Scanning: The system should have RFID readers at designated checkpoints in
the library. Students should be able to scan their laptops and student IDs using the
RFID readers, and the system should capture and verify the scanned information.

5. Verification and Alarm: The system should compare the scanned RFID tag and
student ID with the registered information to ensure accuracy and ownership. In case
of a mismatch or unauthorized attempt to remove or tamper with the RFID tag, the
system should trigger an alarm to indicate a potential theft.

6. Staff Monitoring: The system should provide a monitoring interface for designated
staff members to oversee the laptop scanning process, ensuring that each student
properly scans their laptop before leaving the library.

7. Reporting and Logging: The system should have the capability to generate reports
and maintain logs of scanned laptops, including the date, time, and student
information, to assist in theft investigation and monitoring activities.

8. System Administration: The system should include an administrative interface for

authorized personnel to manage user and laptop registrations, perform system
maintenance tasks, and configure system settings.
24

3.3. Non-functional Requirements

a. Integration: The system should be able to integrate with existing library management
systems to synchronize user and laptop information, ensuring data consistency and
streamlined operations.
b. Compliance: The system should comply with relevant data protection and privacy
regulations, such as GDPR or local privacy laws, to protect user information and
maintain legal compliance.
c. Usability: The system should have a user-friendly interface and clear instructions to
ensure ease of use for both students and staff, minimizing the need for extensive
training.
d. Data Backup and Recovery: The system should regularly back up data to prevent data
loss and have mechanisms in place for data recovery in case of system failures or
disruptions.
e. Scalability: The system should be designed to handle a growing number of registered
users and laptops, ensuring optimal performance even as the system expands.

Domain Requirement: The system should be designed to operate within the domain of a
library environment, specifically for the purpose of preventing laptop theft and ensuring the
security of laptops within the ASTU central Library.

Inverse Requirement: The system should not hinder or impede the normal operations of the
library, such as the ability of students to access library resources, study areas, or other library
services. It should seamlessly integrate with the existing library infrastructure and processes
without causing disruption.

3.4. System Model

The system model for the laptop anti-theft system in the central library at ASTU consists of
several components that work together to ensure the security and prevention of laptop theft
incidents. The following components make up the system model:

1. User Interface:

 The user interface allows library staffs and administrators interact with the system. It
provides a user-friendly interface for laptop registration, profile management, and
system configuration.
25

 Students can input their personal information, such as name, student ID, and
contact details, during the registration process.
 The user interface also enables students to register their laptops by providing details
such as the laptop's serial number, make, model, and a clear photo for visual
identification.
2. Database:

 The database stores and manages the registered user profiles and laptop information.
 It securely stores the personal information of students and associates each laptop
with its respective owner's profile.
 The database is accessed by the system for verification and matching purposes
during the laptop scan process.
3. Laptop Registration:

 The laptop registration component allows students to register their laptops securely.
 Students provide the necessary details of their laptops, including serial number,
make, model, and a clear photo, which are stored in the database.
 Each laptop is assigned an RFID tag, which is linked to the student's profile. This
tag will be used for identification and tracking purposes.
4. Verification Process:

 The verification process ensures that laptops leaving the library align with their
registered profiles.
 RFID readers are installed at entrance and exit points of the library. These
readers scan the RFID tags on registered laptops.
 -If an unauthorized removal is detected, an alert is triggered, indicating a
potential theft.

5. Alerting System:

 When a potential theft is detected, immediate alerts are generated to library staff or
security personnel.
 The alert provides specific information about the laptop involved, including its
unique identifier, student profile, and the associated clear photo for visual
identification.
26

 The alerting system aims to facilitate quick response and intervention to prevent
the theft from occurring or mitigate its impact.
6. Security Measures:

 The system implements various security measures to deter potential thefts and
enhance overall security within the library.
 Visible signage indicating the presence of the anti-theft system serves as a
deterrent.
 Surveillance cameras are installed at strategic locations to monitor activities and
provide additional evidence in case of theft.
 Physical barriers, such as restricted access areas or locked cabinets, can be
employed to prevent unauthorized access to laptops.
 Increased security personnel presence helps deter theft attempts and ensure the
safety of library users and their belongings.
3.5. Constraints and Assumptions

Constraints:

Resource Limitations: Limited budget and resources may constrain the implementation of
certain security measures or the deployment of advanced technologies within the anti-laptop
theft system.

Technological Limitations: The effectiveness of the system may be constrained by

technological limitations such as hardware compatibility, network connectivity issues, or
software integration challenges.

Regulatory Compliance: Compliance with legal and regulatory requirements, such as data
protection laws (e.g., GDPR), may impose constraints on data collection, storage, and
processing practices within the system.

User Adoption: Resistance to change or reluctance among users (students, staff,

administrators) to adopt new security protocols or technologies may hinder the successful
implementation and effectiveness of the anti-laptop theft system.

Operational Constraints: Operational constraints such as limited staffing or administrative

resources may affect the system's ability to monitor, manage, and respond to theft incidents
effectively.
27

Assumptions:

User Cooperation: The system assumes that users (students, staff) will cooperate with
security measures, including registering their laptops, carrying PC ID cards, and complying
with scanning procedures during entry and exit from the library.

Security Awareness: It is assumed that users are aware of the importance of laptop security
and the potential risks associated with theft, motivating them to actively participate in and
support anti-laptop theft initiatives.

System Reliability: The system assumes that the underlying technologies, including RFID
readers, databases, and alerting mechanisms, are reliable and resilient to ensure continuous
operation and accurate detection of theft incidents.

Compliance with Policies: Users are assumed to comply with library policies and
regulations related to laptop usage, security protocols, and code of conduct, reinforcing the
effectiveness of anti-laptop theft measures.

Collaboration with Security Personnel: The system assumes collaboration and coordination
between users and security personnel (library staff, campus security) to promptly respond to
theft incidents, investigate suspicious activities, and enforce security protocols.

Continuous Improvement: It is assumed that the anti-laptop theft system will undergo
continuous improvement and adaptation based on feedback, user experiences, and emerging
security threats to maintain its effectiveness over time.

3.6. Use Case Model

3.6.1. Main Actors of the system

 Student: The student is a primary actor who wants to register their laptop in the anti-
theft system and scan it when leaving the library.

 Library Staff: The library staff member is responsible for assisting students with
laptop registration. They verify the PC registration ID, record the laptop details, issue
an RFID tag, and register the laptop in the system and follows up the system on every
verification activities.

 System: The system is an automated computerized system that manages the laptop
anti-theft process. It includes components such as registration interfaces, RFID
28

readers, ID card scanners, and a backend database for storing and processing
information. (here the system is considered as an actor because the system is
responsible for carrying out specific actions or providing automated responses based
on inputs or events)

 Administrator: The administrator is a privileged user who has administrative access

to the laptop anti-theft system. They perform tasks such as managing user accounts,
generating reports, and configuring system settings.

Use Case scenarios

Use case 1: Library staff Registering into the system

 Use case name: staff Registration

 main actors: Library staff
 Participating Actors: system, Library staff
 Initial Condition: The library staff needs to access the laptop management system
 flow of events
1. The library staff opens the laptop management system registration page.
2. The system presents the registration form.
3. The library staff enters their information.
4. The system verifies the credentials.
5. The registration request is send to the administrators dashboard for aproval
 What Can Go Wrong:
The library staff enters incorrect or incomplete information:

 The system may prompt the staff to re-enter their information or provide missing
details.
 The system encounters errors while verifying the credentials:
 The system may display an error message asking the staff to retry or contact technical
support for assistance.
The registration request fails to send to the administrator's dashboard:

 There might be a technical issue preventing the request from being processed, which
may require system troubleshooting or contacting technical support.
29

Use Case 2: Administrator Approving Staff Registration

 Main Actor: Administrator

 Participating Actors: System, Library Staff
 Initial Condition: A registration request from a library staff member is pending
approval.
Flow of Events:

 Administrator accesses the system dashboard.

 Notices pending staff registration request.
 Reviews the details provided by the library staff.
 Validates the information and assesses the need for system access.
 Approves the registration request.
 System grants access to the library staff member.
Issues:

 Incomplete or unclear information provided in the registration request.

 Uncertainty regarding the necessity of system access for the staff member.
 System errors preventing the review or approval process.
Alternatives:

 Administrator seeks clarification from the library staff member regarding any
ambiguous or missing information.
 In case of system errors, administrator troubleshoots or contacts technical support for
assistance.

Use Case 3: Student and Laptop Registration

 Use Case Name: Student Laptop Registration

 Main Actor: Library Staff
 Participating Actors: Student, System
 Initial Condition: The student wants to register their laptop in the anti-theft system.
 Flow of Events:
1. The student brings their student Id, laptop and the PC registration ID issued by the
entrance gate of the university to the central library.
30

2. The library staff member responsible for laptop registration assists the student.
3. The library staff member verifies the student's PC registration ID.
4. The library staff member records the laptop's serial number, takes clear photos of the
laptop from the front and back, and issues a unique RFID tag for the laptop.
5. The library staff member registers the laptop in the anti-theft system, associating it
with the student's profile.
6. The system validates the entered information and completes the laptop registration
process.
7. The system issues a unique RFID tag for the laptop and the library staff seals it to
the laptop.

 What Can Go Wrong:

-The student provides an invalid or expired PC registration ID.

- The laptop's serial number is recorded incorrectly.

- The system encounters an error while registering the laptop or associating it with
the student's profile.

Use Case 4: Laptop Scanning

 Use Case Name: Laptop Scanning

 Main Actor: Student
 Participating Actors: System
 Initial Condition: The student wants to leave the library with their registered laptop,
and the laptop needs to be scanned for verification.
 Flow of Events:
1. The student approaches the exit gate of the library with their laptop.
2. The RFID reader at the exit gate detects the RFID tag on the laptop.
3. The system verifies the scanned RFID tag and senda the associated RFID tag to the
server.
4. The student scans their student ID card at the designated scanner.
5. The system checks if the scanned student ID matches with the owner of the laptop
as identified from the Tag.
6. If there is a match, the system allows the student to leave. Otherwise, an alarm is
triggered to indicate a potential theft.
31

 What Can Go Wrong:

-The RFID reader fails to detect the laptop's RFID tag.

-The system encounters an error while verifying the scanned information.

-The alarm is triggered incorrectly, causing inconvenience to the student.

 Alternative Flow:
If the system encounters an error while verifying the scanned information:

 The student may be asked to present their student ID and laptop details manually to
the library staff for verification.
If the alarm is triggered incorrectly:

 The library staff member investigates the cause of the false alarm and ensures that the
student's departure is not disrupted.

Use Case 5: Admin System Management and Statistics

 Use Case Name: System Management and Statistics

 Main Actor: Administrator
 Participating Actors: System
 Initial Condition: The administrator wants to manage the laptop anti-theft system and
view statistics.
 Flow of Events:
1. The administrator accesses the hard coded administrative interface of the laptop anti-theft
system.

2. The system validates the administrator's credentials and grants them administrative
privileges.

3. The administrator can perform various management tasks, such as:

- Generating reports on laptop registrations, policy violations, and system usage.

- Viewing statistics and analytics on registered laptops, usage patterns, and popular laptop
models.

- Managing user accounts, including creating new accounts, updating information, and
deactivating accounts.
32

- Monitoring system health and performance, including checking for errors or anomalies
and taking appropriate actions.

4. The system provides the administrator with real-time information and options to manage
and analyze the system.

 What Can Go Wrong:

- The administrator encounters errors while generating reports or viewing statistics.

- The system fails to provide accurate or up-to-date information for management

tasks.

- The administrator incorrectly configures system settings, leading to unintended

consequences or system malfunctions.

Use Case 6: Library Staff Login

 Use Case Name: Library Staff Login

 Main Actor: Library Staff
 Participating Actors: System
 Initial Condition: The library staff needs to access the laptop management system.
 Flow of Events:
1. The library staff opens the laptop management system login page.
2. The system presents the login form.
3. The library staff enters their username and password.
4. The system verifies the credentials.
5. If the credentials are valid, the system grants access to the library staff.
6. The library staff is now logged into the laptop management system.
 What Can Go Wrong:
The library staff enters incorrect credentials, and the system denies access.

The system experiences technical issues, preventing the library staff from logging in.

Use Case 7: Theft Reporting

- Use Case Name: Theft Reporting

33

- Main Actor: System

- Participating Actors: Administrator, Security Personnel(library staff)

- Initial Condition: The system detects a potential theft based on the anti-theft measures in
place.

- Flow of Events:

1. The system detects un-matching laptop id pair or unauthorized removal of a registered

laptop.

2. The system triggers an alarm and alerts the security personnel via email and the
dashboard page.

3. The security personnel respond to the alarm and further investigate the situation.

4. If a theft is confirmed, the security personnel immediately notify the administrator.

5. The administrator receives the theft report and takes appropriate actions, which may
include:

- Informing law enforcement authorities about the theft.

- Notifying the student who owns the stolen laptop.

- Updating the status of the stolen laptop in the system to reflect its stolen status.

- Collaborating with security personnel to provide any necessary evidence or information

to aid in the investigation.

- Implementing additional security measures or reviewing existing security protocols to

prevent future thefts.

- Assisting law enforcement authorities in recovering the stolen laptop, if possible.

6. The system logs the theft incident and any actions taken by the administrator and security
personnel for future reference.

 What Can Go Wrong:

- The system triggers a false alarm, leading to unnecessary panic or disruption.

- The security personnel fail to respond promptly or effectively to the alarm.

- The administrator fails to notify law enforcement authorities or the student promptly.
34

- The stolen laptop is not properly marked as stolen in the system, leading to potential
complications in recovery efforts.

3.6.2. Use case diagram

Fig 1 use case diagram

3.7. Object Model

here we define chosen objects/classes, along with their attributes and relationships, form the
object model that defines the structure and behavior of the laptop anti-theft system

Class: Student - Represents a student who uses the library and owns laptops.

- Attributes:

 first_name: the name of the student

 middle_name
35

 last_name
 photo
 studentID: Id number issued from registral
 contactDetails: the contact information of the student

Class: Laptop - Represents a laptop that can be registered and tracked in the anti-theft system.

- Attributes:

 serialNumber: the unique serial number of the laptop

 make: the manufacturer or brand of the laptop
 model: the specific model of the laptop
 front_photo: back side image of the laptop for visual identification
 back_photo: front side image of the laptop for visual identification
 RFIDTag: the RFID tag associated with the laptop
 owner: a student owning the laptop
 library: the library in which the laptop was registered(in this case it is central library
it is added for the sake of scalability)
Class: Library - in this case Represents the central library where the anti-theft system is
implemented (we are adding this class for evolving prepouse)

- Attributes:

- name: the name of the library

- location: the location of the library

- system_administrator: who administers the system in the library

Class: Theft_report - Represents a report of a laptop theft incident within the library.

Attributes:

 reportID: A unique identifier for the theft report.

 student: The student from who the report was made.
 laptop: The stolen laptop.
 Library:
36

 date: The date and time when the theft was reported.
 description: A description or details about the theft incident.
 status: The status of the theft report (e.g., pending, under investigation, closed).
 investigator: The person assigned to investigate the theft report.

Class Diagram

Fig 2 class diagram

3.8. Sequence Diagram

37

A sequence diagram depicts the flow of messages between various components for a specific
use case. In this project, sequence diagrams have been designed for selected use cases.

Sequence diagram for laptop scanning process

Fig 3 sequence diagram for laptop scanning process

38

Theft reporting sequence diagram

Fig 4 Theft reporting sequence diagram

3.9. Activity diagram

The graphical depiction of sequential activities and actions with provision for choice,
iteration, and concurrency is called an activity diagram. diagram represents the flow from one
activity to another and is simply a more complex form of a flowchart.
 39

This graphic helps describe behavior that involves a lot of parallel processing and illustrates
the links between workflows. It is possible to select the sequence in which tasks are
completed when utilizing an activity diagram. The following table illustrates Notation and
Definition used in Activity diagram.

Notation Definition

1. State In an activity diagram the states are activities representing the performance
1 Transition of operations. The transitions are triggered by the completion of the
operations.

2 Initial State A pseudo state to establish the start of the event into an actual state.

3 Final State Signifies when a state transition ends

4 Decisions As in a flowchart, a conditional flow of control is modeled using the

decision element. A decision is shown by labeling each output transition of a
decision with a different guard condition

Activity Diagram for the following uses:

Describes activities and flows of data or decisions between activities

Provides a very broad view of business processes
Can be used to break out the activities that occur within a use case
Commonly shows many different activities that will be handled by lots of
different symbols
Good for showing parallel threads
40

Fig 5 Activity diagram

3.10. state diagram

One type of UML diagram used to represent a system's dynamic nature is the state chart
diagram.

The transfer of power between states is depicted in a state chart graphic. A state is an object's
existing condition that modifies in response to an external event. The State Chart diagram's
primary goal is to simulate an object's lifecycle from creation to termination.

The following describes a few of our system's status chart diagrams.

41

Fig 5 state diagram for pc registration

42

Chapter 4
4. System Overview

4.1 Overview

The process of converting the analytical model into a system design model includes the
system design component.a few years prior, we were in an area of concern. In software
development, system design is the first component to enter the solution domain. The main
goal of this chapter is to convert the analysis model into the design model, which considers
the limitations and non-functional requirements mentioned in the previous sections on
requirement analysis and issue definition.

This document explains the system's overall design concerns, including persistent data
management, hardware/software mapping, subsystem breakdown, and design goal. It offers a
thorough architectural synopsis of the suggested system. It aims to convey and capture the
important architectural choices that have been made for the system.

4.1.1 purpose of the system

The system's overall design issues are covered in this document. It offers a thorough
architectural synopsis of the suggested system. It aims to convey and capture the important
architectural choices that have been made for the system.

4.1.2 design goal

The design objectives aim to create a system model of high quality, with design goals derived
from non-functional requirements. These requirements describe the characteristics and
attributes of the system, as well as any constraints that may limit its scope.

Performance criteria are crucial for the Anti-laptop theft application to provide a satisfactory
user experience. This includes ensuring a short response time, depending on the strength of
the available network, and equipping the processor with more than 1GB of RAM for efficient
operation.

4.2 proposed system architecture

The proposed system architecture for the laptop anti-theft system is designed to provide a
robust and comprehensive solution for preventing and controlling laptop theft incidents in the
43

central library at ASTU. It leverages RFID (Radio Frequency Identification) technology for
laptop tracking and identification.

 The system architecture consists of the following components:

1. Student and Laptop Registration Module: This module allows students to securely
register their laptops. Upon registration, each laptop is assigned a unique RFID tag. The
registration process involves collecting and storing information such as the student's name,
student ID, contact details, laptop's serial number, make, model, and a clear photo for visual
identification. This information is securely stored in the system's backend server.

2. Detection and Verification Module: The detection verification module ensures that
laptops leaving the library align with their registered profiles. RFID readers exit points of the
library. Each laptop's RFID tag is scanned by the RFID reader at the exit gate. The RFID
reader communicates with the backend server to verify the presence of the registered RFID
tag associated with the specific laptop. This process ensures that the laptop being taken out of
the library belongs to the registered student.

4. Alerting Mechanism: When a potential theft is detected, immediate alerts are generated
and sent to library staff or security personnel. The alerts provide specific information about
the laptop involved, including its unique identifier and student profile. This enablesprompt
action to be taken to prevent further theft and recover the stolen laptop. The alerting
mechanism are implemented through email notification and dedicated monitoring dashboard
accessible to authorized personnel.

5. Database Management System: The system architecture includes a robust and secure
database management system to store and manage the data related to student and laptop
registration, verification records, alerts, and other system information.

4.3 hardware/software mapping

The description of the Hardware Software mapping shows the different hardware devices
and equipment employed in the system and its interaction with the software components.

Essentially, there are three hardware parts in this system design. the database, server, and
client sides. Each user will have the required software loaded when they apply the system.
44

side by side with the hardware elements. It is necessary to install networks between each side.
Next, the mapped hardware will be assigned and configured to each subsystem software.

4.4 The RFID work flow

The RFID technology works by using electromagnetic fields to automatically identify and
track tags attached to objects, in this case, laptops. The RFID tags consist of a microchip that
stores unique identification data and an antenna for communication. When a laptop with an
RFID tag enters the range of an RFID reader, the reader emits an electromagnetic field. The
RFID tag on the laptop absorbs energy from the field and uses it to power up and transmit its
unique identifier back to the reader. The reader captures this information and sends it to the
backend server for processing and verification.

The basic installation of the system is shown in the figure below

Image 1 the RFID workflow

In addition, The backend server acts as the central control unit of the system, managing the
communication between various components. It hosts the database management system,
which stores and manages the registration data, verification records, and alert information. It
provides the necessary APIs (Application Programming Interfaces) for the RFID readers to
communicate with the server, enabling real-time data exchange. The backend server also
handles the generation and distribution of alerts to authorized personnel.
45

Here is how the device configurations will look like:

Image
2

Overall, the proposed system architecture utilizes RFID technology, integrated with a
backend server and a database management system, to provide a comprehensive laptop anti-
theft solution. It ensures secure laptop registration, efficient verification, theft detection, and
timely alerting mechanisms, thereby enhancing the security measures within the central
library at ASTU.

4.5 Deployment Diagram

In the runtime environment, the Library Staff PC and Admin PC are located inside the ASTU Central
Library. The ID Scanner and RFID Scanner are also placed within the library premises.

The Backend Server is responsible for handling the logic and business operations of the anti-theft
system. It communicates with the Frontend (Library staff Pc and Admin PC) through a REST API for
user interaction and data exchange.

The Database Server stores and manages the system's data, including student and laptop information.

The communication between the components is as follows:

 Library Staff PC and Admin PC communicate with the Backend Server through the REST
API.
46

 The ID Scanner and RFID Scanner interact with the Backend Server using MQTT, a
lightweight messaging protocol.
The Backend Server communicates with the Database Server to store and retrieve data as
needed

Fig 7 deployment diagram

47

Reference

 "Computer Security: Principles and Practice(3rd Edition)" by William Stallings and

Lawrie Brown:

Chapter 1: [PART 3: (Chapter 14: IT Security management and risk assessment) page
483]

 “RFID: Technology and Applications” by Sridhar Iyer:

 "Principles of Information Security" by Michael E. Whitman and Herbert J. Mattord:

 "Security Engineering: A Guide to Building Dependable Distributed Systems" by Ross J.

Anderson:

 "Network Security: Private Communication in a Public World" by Charlie Kaufman, Radia

Perlman, and Mike Speciner: