EPOKA Library System

Requirements Specification

EPOKA Library System Requirements Specification

Version 1.0

April 6, 2023

Software Modelling and Design

Contributors:

Amara Çela

Anita Mjeshtri

Irisa Nazari

John Nase

Patrik Madhi

Sara Berberi

April 06, 2023 Page 1 of 18

 EPOKA Library System
Requirements Specification

Table of Contents

EPOKA LIBRARY SYSTEM REQUIREMENTS SPECIFICATION

VERSION 1.0

APRIL 19, 2021

1. EXECUTIVE SUMMARY

1.1 PROJECT OVERVIEW

1.2 PURPOSE AND SCOPE OF THIS SPECIFICATION

2. PRODUCT/SERVICE DESCRIPTION

2.1 PRODUCT CONTEXT

2.2 USER CHARACTERISTICS

2.3 ASSUMPTIONS

2.4 CONSTRAINTS

2.5 DEPENDENCIES

3. REQUIREMENTS

3.1 FUNCTIONAL REQUIREMENTS

3.2 NON FUNCTIONAL REQUIREMENTS

3.2.1 Product Requirements

3.2.1.1 User Interface Requirements

3.2.1.2 Usability

3.2.1.3 Efficiency

3.2.1.3.1 Performance Requirements

3.2.1.3.2 Space Requirements

3.2.1.4 Dependability

3.2.1.5 Security

3.2.2 Organizational Requirements

3.2.2.1 Environmental Requirements

3.2.2.2 Operational Requirements

3.2.2.3 Development Requirements

3.2.3 External Requirements

3.2.3.1 Regulatory Requirements

3.2.3.2 Ethical Requirements

3.2.3.3 Legislative Requirements

3.2.3.3.1 Accounting Requirements

3.2.3.3.2 Security Requirements

3.3 DOMAIN REQUIREMENTS

4. USER SCENARIOS/USE CASES

April 06, 2023 Page 2 of 18

 EPOKA Library System
Requirements Specification

1. Executive Summary

1.1 Project Overview

To facilitate and enhance a better access to the education system, an efficient solution is to digitalize the University’s Library in order to bring it
closer to all the students as well as to provide better management features to the librarians and administrators of the library. Our work consists of taking all
the necessary steps that will result in the creation and maintenance of the finished product: the library web application for Epoka University. As mentioned
above this system will be available to three levels of users: the university’s students, the librarians and the administrators.

The account of the administrator will be provided using the backend of the web application development, meaning that the moment this
application is deployed, the administrator will be able to access his/her account to which he/she can make modifications, such as changing the password.
The supply of the books and their entry in the system will be an available feature for the administrator. Therefore, he/she will be able to enter the
information about any new books, such as their title, authors, genres, description, cover page and the number of copies of that particular book that are in
stock. In addition to that, the administrator will also be able to update the information provided for each book, such as when errors in their registration are
made or when he/she changes the number of copies. This user category is also provided with a feature of deleting books. The administrator can find the
entered books in the main page of his/her account. He/she will be able to access statistics of the books that are borrowed and which ones are requested
the most in the library. The administrator account will be provided with a feature of receiving messages that come as feedback from students. An important
functionality of the administrator will the ability to register librarians, using the Epoka university email of the person they are registering.

Librarians will be able to approve the registration made by the administrator, by clicking approve or reject in the email automatically sent when
the administrator is attempting to make the registration. The home page of the librarian account will also contain all the available books. In addition to that
he/she will manage the orders made by students: approving orders which sets their status as ‘approved’, changing their status as ‘borrowed’ when the
book has been picked up by the student, changing their status as ‘returned’ when the book is returned, and contacting the student when the return date is
surpassed.

This web app will also provide useful features for all students, including but not limited to viewing the available books along with information and
descriptions for each of them, ordering them for pickup, personalizing their account by adding books to favorites, as well as giving feedback or requests. In
order to register, students are only required to create an account using their Epoka email.

The product of this ongoing process of communication, design and implementation will bring down barriers in the accessibility of education and
information, helping students find the needed books without having to check the entire physical library. Furthermore, it will also help administrators keep
track of the books, and librarians keep track of orders, making sure that the return deadline is respected.

1.2 Purpose and Scope of this Specification

The main purpose of our project is to create, develop, and implement a modern and comprehensive electronic library in our university that will
provide all the students, and every faculty member with seamless access to a wide range of books, where they will be able to have their own personal
account, mark their favorite books, order electronically hard copies of the books, and send feedback based on their personal experience. The project aims
to enhance the overall learning experience at the university and make the process of finding books and ordering them easier for both students and the
Epoka library staff.
The scope of the Epoka electronic library project includes the following:
- Development and implementation of the electronic system for the Epoka University library: The process of developing a software to adapt to specific
needs of the university community includes the selection of the appropriate software as well as the customization and integration of software with different
problem solutions to produce a user-friendly platform as efficiently as possible.

April 06, 2023 Page 3 of 18

 EPOKA Library System
Requirements Specification

- Access and authentication: The Epoka electronic library system will provide secure and authenticated access to a wide range of electronic resources and
will ensure that only authorized users can access the system.
- Books management and organization: The electronic library of our university will ensure that the books are easy to find electronically and can be ordered
to access them physically.
- Search tools: The electronic library system will provide advanced search to allow its users easy access to books.
- User account management: The system will allow the students to create and manage their own accounts.
- Accessibility: The Epoka electronic library system will be easily accessible to all users, including those with disabilities.
Our purpose as aspiring Software Engineers is to leave a mark on our university by providing a comprehensive and user-friendly platform for
them, supporting learning activities, and enhancing the overall quality of study and experience of the university community.

2. Product/Service Description
Our team is dedicated to improving access to education by digitalizing the Epoka University library. We have designed a web application that
brings the library closer to the students and provides efficient management features for its librarians and administrators. The system will allow
administrators to manage the books by adding, modifying or deleting information for each book. On the other hand, librarians will manage the orders and
feedback sent from the students. Students will be able to view the available books, order them for pickup, personalize their account by adding books to
favorites and provide feedback or requests. The system will provide a better communication between users, which will enhance the learning experience of
the students. The system will be available only for active undergraduate and graduate students of Epoka University.

2.1 Product Context

The Epoka University Library System will be a self-contained system and independent of other products. However, it will interface with other
related systems such as the university’s student information system and database. It will be integrated with the student information system to ensure that
only registered students can access the library system. It will also be integrated with the university’s authentication system to ensure secure access to the
system. Our system will be designed to work smoothly with these other systems, ensuring easy operation for the users. The application will be accessible
from any device with internet access.

2.2 User Characteristics

The application will be used by three types of users: students, librarians and administrators. The user profiles for each of them are: -University
Students: The primary users of the library web application are university students from different faculties like Architecture and Engineering, Economics and
Administrative Sciences, Law and Social Sciences and different academic levels, including both undergraduate and graduate students. They will use the
application to access information on available books, order for pickup, personalize their account and give feedback or requests. Students are expected to
have basic technical knowledge and experience in using web applications; however technical expertise is not a requirement to use the system. -Librarians:
The librarians who will use the library web application are part of the existing staff or the University. They will manage the orders of the students and the
feedback sent from them. They will also contact students who have not returned borrowed books according to the deadline. They will need approval from
the administrators to gain access to the system. They are expected to have advanced technical knowledge and experience in library management. -
Administrators: The administrators will be responsible for adding, modifying or deleting the information for each of the books. They will also register
librarians, so only authorized staff can take this position within the system. Administrators are expected to have advanced technical knowledge and
experience in database managements and library administration.

2.3 Assumptions

• It’s important to have a reliable internet connection available for both students and staff to access the system.
• The hardware equipment, such as computers, laptops or mobile devices, should be able to access the web application.
• The users, including librarians and administrators, have basic computer skills and are familiar with the internet.
• The users should also have access to the necessary login credentials, such as usernames and passwords, to access the web application.
• The system should be developed using programming languages and frameworks that are compatible with the university’s existing IT infrastructure.
• The web application should be designed with responsive design principles to ensure that is can be accessed on different devices with various screen
sizes and resolutions.
• The system must respect the data protection regulations and provide enough security measures to protect user data and prevent unauthorized access.

April 06, 2023 Page 4 of 18

 EPOKA Library System
Requirements Specification

•It is assumed that every active student of the university possesses an active Epoka account.
•It is assumed that the online library system will represent the actual physical books with high accuracy and real-time updates.

2.4 Constraints

There are several factors that will limit the design options for the digitalized library system for Epoka University.
Parallel Operation with an old system:
This will be Epoka University’s first library system so our system will not be operating with an old system. However, our system may need to operate in
parallel with other systems Epoka has. This may require our system to interface with the other systems.
Audit Functions:
Another constraint is the need to track user activity and maintain the integrity of the system. This will affect how data is collected, stored and analyzed.
Access, management and security:
The system will need to have access controls and security measures in place, to protect the data and ensure that only the authorized users can access the
system. Since our product will be a web application, each user needs to have access to the internet. These constrains will affect the design of the
authentication and authorization mechanisms, as well as the encryption and algorithms used to secure the data.
Criticality of the application:
The criticality of the web application will constrain the design options in terms of reliability, fault tolerance and disaster recovery. For example, the system is
somehow critical to the functioning of the university, and it may need to have redundant servers and backup systems in place to ensure continuity of
service.
System resource constraints:
Since the Epoka University library system will be a web application, disk space or other hardware resources may not be a significant constraint. However,
there may be other resource constraints that need to be considered, such as the amount of memory and processing power required to handle user
requests and to ensure that the system runs smoothly. The design of the system architecture and algorithms will need to take these constrains into account
to optimize the use of resources and ensure efficient performance.
Other design constraints:
There may be other design constrains imposed by the university, such as programming language or framework preferences. These constrains will affect
the choice of technologies and tools used to develop the system. We will be using HTML, CSS, JavaScript and PHP to develop the library web application.
In addition, to connect the PHP server with the database, which will be built using MySQL, we will also use JDBC. These choices of technologies and tools
are influenced by the university’s preferences.

2.5 Dependencies

• The system may require accurate and up-to-date data from the university’s existing library.
• The system may need to be integrated with other university’s systems, such as the student information system or learning management system, to
ensure seamless access to library resources and services.
• The development of the system may rely on specific technologies or tools, such as a particular programming language, database system or web
framework.
• Certain features or modules may need to be developed back-to-back and may depend on the completion of other project milestones or components, such
as the design of the user interface.

3. Requirements

3.1 Functional Requirements

April 06, 2023 Page 5 of 18

 EPOKA Library System
Requirements Specification

Date SME Reviewed /

Req# Requirement Comments Priority
Reviewed Approved

BR_01 The system shall allow the registration of The users if the Epoka Library System 1 06/04/23 Anita Mjeshtri
either Epoka University students, librarians will be either students, librarians or
and library administrator. administrators.

BR_02 The system shall provide different graphical Each type of user will be provided with 1 06/04/23 Anita Mjeshtri
user interfaces for each of these three different features, therefore it is
types of users. necessary to have a different GUI.

BR_03 The student user shall be able to register The email address will be checked if 1 06/04/23 Anita Mjeshtri
by providing a valid Epoka email address, valid, based on the specifications of
first name, last name, password and phone Epoka Email for students, consisting of
number. the first letter of the first name, the last
name and enrollment year.

BR_04 If the status of the student becomes When a student is transferred, or he/she 2 06/04/23 Anita Mjeshtri
passive from the university, his status in finished his/her studies the status is
the library system will also change to changed to passive.
passive.

BR_05 The student user shall be able to verify To ensure that the email entered for 1 06/04/23 Anita Mjeshtri
his/her registration by receiving a special registration actually belongs to the user,
code in their email. the code will be sent by email and
entered on the website by the student
registering.

BR_06 The student user shall be able to log in to To access his/her account the user 1 06/04/23 Anita Mjeshtri
his/her account by providing the correct should input a valid email address that
information: Epoka email and password. matches with the entered password for
that address.

BR_07 The system shall grant student users the The home page will contain all the 1 06/04/23 Anita Mjeshtri
information: including title, author, genre, available books along with the
picture of the cover and the number of information about each of them.
books in stock, for all the books offered by
the EPOKA University Library, in the home
page.

BR_08 The student user shall be able to click on The students can view the information 2 06/04/23 Anita Mjeshtri
the desired book, to get more information about all the books available in the
about the book, including the information library.
mentioned above as well as a short
description.

BR_09 The student user shall be able to order a Student users can order a book, whose 1 06/04/23 Anita Mjeshtri
book, that he will get to pick up within the status will be 'ordered' until the student
specified time frame. picks it up, in this case its status will
change to 'borrowed'.

April 06, 2023 Page 6 of 18

 EPOKA Library System
Requirements Specification

Date SME Reviewed /

Req# Requirement Comments Priority
Reviewed Approved

BR_10 When a book is ordered by a student, its Each time a book is ordered by a student 1 06/04/23 Anita Mjeshtri
stock number shall decrease. user its stock will decrease, until it
reaches 0. In this case the book can still
be viewed but not ordered.

BR_11 The student user should be able to save Students can save books as favorites 1 06/04/23 Anita Mjeshtri
books as favorites. that will be added to their personal
favorites page(even when the stock of
the book is 0) that is unique for each
student.

BR_12 The student user should be able to filter the Student users can choose to view only 2 06/04/23 Anita Mjeshtri
books by the desired genres and authors the books of a certain genre or of a
that are available. certain author.

BR_13 The student user shall be able to search for The student can search for the desired 2 06/04/23 Anita Mjeshtri
a specific book title. book by book title.

BR_14 The student user should be able to give Students can send suggestions or 3 06/04/23 Anita Mjeshtri
feedback or send a message about feedback about the books and the
suggestions or requests. service.

BR_15 The feedback sent by users should appear The messages sent by student users can 3 06/04/23 Anita Mjeshtri
on the account of the librarian and be read by both the librarian and the
administrator. manager.

BR_16 The student user can view his/her profile. Student users can view the information 2 06/04/23 Anita Mjeshtri
they have entered: email, password, first
name, last name and phone number.

BR_17 The student user can modify his/her name, Users can change their name, last name, 2 06/04/23 Anita Mjeshtri
last name, password, phone number and phone number, password and modify the
profile picture in the profile page. default profile picture.

BR_18 The main administrator shall be registered To ensure that the library is 1 06/04/23 Anita Mjeshtri
from the server side, when the web administrated by the competent person,
application is made available. his account will be the first one
registered.

BR_19 The library administrator shall be able to The administrator must enter the valid 1 06/04/23 Anita Mjeshtri
log in to his/her account by providing the Epoka email and password to access
correct information: Epoka email and his/her account.
password.

BR_20 The administrator shall be able to enter The administrator enters the information 1 06/04/23 Anita Mjeshtri
new books, along with the information about each new book he/she enters into
about each of them (title, author, genre, the system
description, cover page and stock).

April 06, 2023 Page 7 of 18

 EPOKA Library System
Requirements Specification

Date SME Reviewed /

Req# Requirement Comments Priority
Reviewed Approved

BR_21 A list of all the available books shall be The administrator can view all the books 1 06/04/23 Anita Mjeshtri
represented in the home page of the and their information.
account of the library administrator.

BR_22 The administrator shall register the The administrator can enter the 1 06/04/23 Anita Mjeshtri
librarians by inputting their information information about the librarian that will be
(Epoka email, password, first name, last entered in the system
name and phone number).

BR_23 The librarian can validate the information To verify the account creation the 1 06/04/23 Anita Mjeshtri
entered by the administrator, by receiving librarian can check and verify it from
an email with this information. his/her email account.

BR_24 A messages section shall be provided to Library administrators can review the 3 06/04/23 Anita Mjeshtri
the library administrator to which the messages sent by the student users.
incoming feedback from student users shall
be stored.

BR_25 The administrator of the library shall be The administrator can modify the title, 2 06/04/23 Anita Mjeshtri
able to update the information about a author, genre, stock, description and
book. cover page of the book.

BR_26 The administrator of the library shall be The administrator can delete books when 2 06/04/23 Amara Çela
able to delete books. they are removed from the library.

BR_27 Each student shall be able to see all the The student can choose any of the areas 3 06/04/23 Amara Çela
books in his/her area of study by selecting of study offered at Epoka University
his/her specific field of study. (Software Engineering, Law, Economics,
Business Informatics etc.) and search for
the list of books that they will study
through all the years at Epoka University.

BR_28 The student shall be notified one day A notification will be sent to the students 2 06/04/23 Amara Çela
before the deadline for returning the one day before he/she has to return the
borrowed book. book.

BR_29 The student shall be able to see or edit The students can see all the books in the 2 06/04/23 Amara Çela
his/her favorite book list. favorite section, but they also can
remove a specific book from their
favorites list by pressing a button.

BR_30 The student shall be able to see or edit The students can see all the books in the 1 06/04/23 Amara Çela
his/her ordered book list. order section, but they also can remove a
specific book from their ordered list by
pressing a button, when the book has not
yet been picked up by him/her.

April 06, 2023 Page 8 of 18

 EPOKA Library System
Requirements Specification

Date SME Reviewed /

Req# Requirement Comments Priority
Reviewed Approved

BR_31 When a book is returned, its stock number When a book is returned, its stock 1 06/04/23 Amara Çela
shall increase. number will be increased by the librarian.
If the stock of a book was zero and that
book was unavailable to order for other
students, that specific book will now be
available for anyone who wants to order
it.

BR_32 Each student shall manage his/her The student shall be able to manage if 3 06/04/23 Amara Çela
notification settings. he/she wants to receive notifications from
Epoka Library, such as the notification for
the book returning.

BR_33 Each student shall be able to deactivate Students may choose to temporarily 3 06/04/23 Amara Çela
his/her account for a specified period. deactivate their account for a week or a
month.

BR_34 Each student shall be able to delete his/her Students will be able to permanently 2 06/04/23 Amara Çela
account. delete their account and will be asked to
enter their account password and to
confirm the deletion of the account, while
being aware that all the history of their
account (favorite and ordered lists) will
be deleted as well.

BR_35 Each student shall be able to find support Students should be able to find the 2 06/04/23 Amara Çela
in the “Help and Support” section. frequently asked questions which may
answer the question they may have.
Otherwise, they can contact the librarian
through the contact information provided
for them.

BR_36 The administrator shall be able to view or The administrator can edit his/her name, 1 06/04/23 Amara Çela
edit his/her profile. surname, phone number, password.

BR_37 The administrator should receive a To change the password, the old 2 06/04/23 Amara Çela
confirmation email every time he/she tries password should be entered by the
to change his/her account password. administrator and then an email
confirmation about the password change
will be sent to the administrator.

BR_38 The administrator shall be able to view the The administrator can see the most 1 06/04/23 Amara Çela
statistics of the library. ordered books from the students.

BR_39 The administrator shall be able to The administrator can remove a librarian 2 06/04/23 Amara Çela
discharge a librarian. from the system by deleting his/her
account.

April 06, 2023 Page 9 of 18

 EPOKA Library System
Requirements Specification

Date SME Reviewed /

Req# Requirement Comments Priority
Reviewed Approved

BR_40 The librarian shall be able to view his/her The librarians can see their profile but 2 06/04/23 Amara Çela
profile. cannot edit their personal information
after they have confirmed it to the
administrator.

BR_41 The librarian shall be able to login into their The password is given to the librarian by 2 06/04/23 Amara Çela
account by entering their Epoka email and the administrator who is the person who
password. created his/her account.

BR_42 When the librarian is trying to delete his/her Since the account was initially created by 1 06/04/23 Amara Çela
account a permission request is sent to the the administrator and this post was
administrator. granted to him/her by the administrator,
they should first quit their post and then,
after their request is approved, they may
be granted permission to delete their
account or their account may be deleted
directly from the administrator.

BR_43 The librarian shall be able to see the list of The librarians can see all the books 1 06/04/23 Amara Çela
the books in the system. registered in the system with all their
detailed information.

BR_44 The librarians shall be able to confirm the After a book is returned by a specific 1 06/04/23 Amara Çela
returned book. student, it is confirmed by the librarian
and the stock number of that specific
book is increased. The book is removed
from the student’s ordered list.

BR_45 The librarian shall be able to search books Each librarian should be able to search 2 06/04/23 Amara Çela
by their title or by their author. for a specific book by the book name or
its author.

BR_46 The administrator shall be alerted when the An alert message should be displayed to 2 06/04/23 Amara Çela
stock number of a book falls below five. the administrator whenever there are
less than five copies of a book.

BR_47 The student shall be able to order only one Students cannot order two copies of the 1 06/04/23 Amara Çela
copy of the book at a time. same book.

BR_48 Administrators shall be able to modify the If the administrator considers a change in 2 06/04/23 Amara Çela
information of the librarian account. the librarian account as necessary,
he/she can do it with the librarian
consensus. If the librarian

would like to change something, they

should ask the administrator to do it.

April 06, 2023 Page 10 of 18

 EPOKA Library System
Requirements Specification

Date SME Reviewed /

Req# Requirement Comments Priority
Reviewed Approved

BR_49 The librarian shall be notified when a A notification will be shown to the 1 06/04/23 Amara Çela
student has not returned the borrowed librarian when a specific student has not
book within his/her deadline. returned the book within the deadline
and the librarian should contact the
student.

BR_50 Students with disabilities shall be able to Epoka Library System is being designed 1 06/04/23 Amara Çela
use the library as any other student, to be accessible to all Epoka students.
without any difficulties. Students with disabilities should be able
to use features

such as screen reader compatibility,

keyboard navigation or alternative text for
images.

BR_51 The Epoka electronic library shall be Students, administrators, librarians and 1 06/04/23 Amara Çela
optimized for any device, allowing Epoka’s anyone part of the Epoka University can
students to access electronic resources access Epoka’s library electronically from
from their devices. any device

3.2 Non-Functional Requirements

3.2.1 Product Requirements

3.2.1.1 User Interface Requirements

The user interface of this system is divided into five (5) main sections:

 Registration interface

 Home page interface (books)

 Student Interface

 Librarian interface

 Administrator interface

Registration Interface:

This section outlines the requirements for the registration interface of the Epoka University Library System.  The registration interface will consist of two
main processes, "Log In" and "Sign Up".  

The Sign-Up process can be completed only by students since the administrator must be registered when the system is deployed, and the librarians will be
added manually by the administrator. The account creation process for the students will be completed using the email address provided by Epoka
University.

The students must enter their first and last name, username, phone number, and password. Before clicking sign up the system prompts the students to
verify their passwords.

April 06, 2023 Page 11 of 18

 EPOKA Library System
Requirements Specification

The Log-In interface will consist of a user entering the email address provided by Epoka University, and then the password. The Log-In interface can be
applied to all user types.

A "forgot password" functionality will assist users who may forget their password or lose access to their accounts. Clicking on it will help users reset their
passwords and regain access to their accounts.

Home Page interface:

This interface will be accessed by every registered user. The purpose of this home page is to display all of the books registered in the Epoka university
library. The data will be filtered and organized to be easily navigable and user-friendly.

Initially, the user can search directly for the book they’re looking for, or the user can even specify their major by choosing a study degree and the list of
courses taken from the syllabus will show on the page. The user may select a course and every book from that course will appear. The “view as” button
can allow the user to show the books as a list, as small icon books, or as large icon books. The “order by” button will order the books by the number of
downloads, publication time, title, author name, etc. A book is shown by its cover and title. By clicking on it the user can get more information about the
book size, number of pages, name of the author, publication year, and edition. Additionally, student users have more complex and special functionalities on
the homepage, which will be furtherly mentioned in the “Student Interface” section.

Student Interface:

Except for basic functionalities like searching and viewing books, student users have other special functionalities, such that by hovering over the book, the
system can assist students to add the book to their favorites or order it by clicking on two separate buttons. Adding a book to favorites will make it appear
on the “Book collection”. Furthermore, ordering or reserving the book will facilitate the students with information like library availability (borrowed, available)
of the book, time, and date when the student can reserve the book. The reservation of the book by a student will cause them to get the approval if the book
is on stock, otherwise the button can appear disabled, or the book will not show up as available. After approval, the book will appear as reserved
automatically. Then the student must go to the library and get the book. If a student user does not show up, the librarian will wait for them for 12 hours, and
after that the librarian can either deny the request or notify the students by their phone number, however, it is not mandatory to do so. 

The “Book collection” functionality provides the students to see the books that are added to their favorites, and the ordered books. The students can also
make their “Book collection” private or public as they wish. One week before the students get daily notifications about their due date to submit the books.

Students can give feedback on the system or even report bugs and inconveniences. These messages can be read by the librarians and the administrator.
Student users can view their profiles and edit personal data.

A green dot in a student’s profile indicates an active user in terms of accessibility, while a grey dot implies that this user has no longer access to the library.

Librarian Interface:

To gain access to their interface, librarians first have to approve the registration of their profile by the administrator.

The librarian will have access to the default homepage without any specific features like the student users.

The “Borrowers” functionality consists of listing the borrowers of the books based on left days in ascending or descending order. If there are students that
don’t submit their books in time, their records will immediately turn red. Then, the librarian can choose to click on their profile and call them by the phone
number shown in their profile, or even ignore the late submission for a few days if the book has a low demand.

When a student submits a book in the library, the librarian must make a book “returned”, so the in-library availability of the book will become “available” for
students to view. On the other hand, when many students reserve a book, the system will automatically approve the request of the student who applied
first.  

Administrator Interface:

The Administrator Interface is a key component of the system, as it facilitates the manual registration of librarians and the management of book records.
Upon deployment, developers will manually register the administrator. The administrator is responsible for adding librarians to the system, which can be
accomplished by selecting the "Add Librarians" button located in the left pane of the interface. The librarian registration process mirrors that of student
registration.

April 06, 2023 Page 12 of 18

 EPOKA Library System
Requirements Specification

The administrator will also add books and edit them. On the bottom of the “Add Librarians”, There will be a “View Books” which when clicked will show all
the books as a table. The table will have columns like title, author name, quantity or stock, date of publication, date of import in the system, status
(borrowed, returned, available), number of pages, etc. The administrator can edit the information of the book, delete the book from the database as a
record, or even add a new book.
The administrator can read the messages that students may send, like reports about bugs, suggestions, or complaints in terms of the library service. The
bug reports will be communicated to the software developers by the administrator, while other notifications will be handled properly by the administrator
and even by the librarians if needed. 

3.2.1.2 Usability

Usability of the software refers to the extent to which the product can be used to efficiently achieve the goals of the intended audience. There are a couple

of points that make up the usability of a software:

- Learnability: the software must be easy to learn by the three different types of users. The application will be easy to understand for all stu-

dents, librarians, and the administrator of the library. There will be clear instructions to each command in the different views of the user interfaces.

- Accessibility: the software will have to be available remotely as each student may use it from their own devices. The application should be

available for both pc and mobile use.

- Responsiveness: the software must be highly responsive. It must be able to successfully respond to the user’s requests in real time,

therefore operating on and changing data in real time on both the student and librarian side.

- Flexibility: the program should be flexible enough to accommodate different user needs and preferences. It will allow customization on cer-

tain parts such as setting or changing passwords and adding available books to the database. The developers will also be able to maintain and update

the program when needed.

- Effectiveness: The app must be simple and easy to use for both students and the librarians running it therefore making it very practical and

effective. It will help digitize and modernize the process of borrowing books from the school library.

- Consistency: the application must use well known terminology, so users find it easy to understand and navigate through the system.

- Efficiency: the user should find it very easy to complete every task, with easy commands and instructions even if it is the first time the

user is in contact with the application or they haven't used it in a while.

- The application should be very simple to use for all students. It will approximately only take a few minutes for a student to get up to speed

with the app as it will be a very well-designed, intuitive application.

- As they are essentially administering the application, librarians and administrators may need a bit more time to become completely familiar

with all of its capabilities. Although it will take some time to become familiar with the app, it should be noted that a week of use should be sufficient for li-

brarians and administrators to become skilled in using it.

3.2.1.3 Efficiency

Efficiency of the software does not mean just making sure that the software completes all the tasks given to it. There are two main groups of requirements
that determine how efficient a system is, performance and space requirements.

3.2.1.3.1 Performance Requirements

- Response time: the system should be able to respond to the user requests in real-time with no lag or delay.

- Throughput: the system should be able to handle a relatively high flow of data at a time as multiple students may be using the application all at once.
The program should be able to respond to every single request as soon as the command is given without compromising its speed or performance.

- Compatibility: the application should be compatible with different hardware such as computers or mobiles as long as they have a connection to the
internet as most functions will require it. Regardless of the device the application is being used on, the performance and functionality should not be
affected.

April 06, 2023 Page 13 of 18

 EPOKA Library System
Requirements Specification

3.2.1.3.2 Space Requirements

Our software is a web application which means users will not have to download anything
to their device. This means that there is no required space needed for the application and
the storage of the user's device will not be affected. They will simply have to search for the
application online on a search engine to use it.

3.2.1.4 Dependability

 The data of the books in the Homepage depends on the BookList database. 

 Registering in the library using the Epoka Mail depends on the Epoka Account.

 When the student users search and click courses, the courses are depending on the syllabus provided by the department of the university. 

 The approval of a reservation request made by a student depends on the time the request was submitted. 

 The account will be considered active and passive based on the information from EIS platform of Epoka University.

Availability

 The application will be available only if the device has access to the internet. 

 The application will be available to users in any time, however in the weekends, holidays, or out of the university season reserving the books
will not be available. Other features like viewing the books or adding them to favorites will still work. 

 The application will be available at any geographic location by any device and phone number, however, only accounts with Epoka university
email addresses will be able to get registered.

Reliability
The software has to run correctly at all times, even at nights or weekends it should produce the expected outputs for the given inputs consistently. Since

this software is going to be used by a large number of students, it must be powerful enough to withhold all the students interacting with it at a time,

without crashing or slowing down. It is important that the list of books updates as the students place their requests in real time.

April 06, 2023 Page 14 of 18

 EPOKA Library System
Requirements Specification

To make sure the system is reliable, it will undergo a lot of testing before it is publicly used and it will be continuously monitored when published. To ensure
that the system meets the user expectations, it will also be updated and maintained regularly after publishing

Monitoring
After publishing the application, the developers will continue testing out the system along with students and librarians for the upcoming days to ensure

that it withholds all of the user's operating on it at a time while looking for any bugs along the way.

The developers will be in direct contact with the administrator of the system who will report any bug or fault found in the system by any user and

will act on it as soon as possible with as little downtime as possible.

The system will be able to run on its own without the need of the developers and will be easily operated by the administrator and librarians. Each student

can create their own account in the application and can then use the application to borrow books from the

library without the need of a librarian or developer.

Maintenance
Specify attributes of the system that relate to ease of maintenance. These requirements may relate to modularity, complexity, or interface design.
Requirements should not be placed here simply because they are thought to be good design practices.

Integrity & Security

The integrity of a software is critical for ensuring the reliability, security and trustworthiness of a software system. Therefore, the developers

must take steps to maintain the software throughout its life cycle.

- Users will only be able to access the given interfaces according to the group they belong to.

- Students and librarians will only be able to change their own accounts data and information.

- The administrator can grant a librarian access to use the system.

April 06, 2023 Page 15 of 19

 EPOKA Library System
Requirements Specification

- Students will not have direct access to the book database and will not be able to change any data on

it.

- Account passwords will have to follow certain rules to make them harder to guess.

- There is no sensitive personal data stored within a user's account.

- Several security measures will be implemented on the software and will be revised continuously.

- The code will be reviewed and examined for any errors or vulnerabilities that could compromise its integrity.

3.2.2 Organizational Requirements

3.2.2.1 Environmental Requirements

 Internet Access: The web app requires a reliable and stable internet connection to function properly.

 Web Browsers: The web app should be compatible with all the popular web browsers.

 Devices: The web app should be accessible on all devices like laptops, desktops, mobile phones and tablets.

 Security: The app should ensure that sensitive user data is very well protected.

 Technical Support: Any glitches or bugs that affect the app’s functionality should be dealt with quickly.

 User-friendly Interface: The app should have user-friendly features and be fairly easy to navigate and use to encourage student engagement.

3.2.2.2 Operational Requirements

 User Authentication: Students should be allowed to create an account and log in with the university’s email to access the app.

 Book List: The web app should provide the list of books the library has and the details for each book.

 Borrowing System: The web app should have the borrowing system that allows the users to borrow the books they need.

 Search and Filter: Students should be able to search and filter the book list easily by title, author, publication date, availability status and so forth.

 Notification System: The app should notify the students about the status of their borrowed books, or the availability of the books they want.

 User Feedback: the app should allow the users to provide feedback on the overall user experience.

3.2.2.3 Development Requirements

The app will be accessed through internet connection such as Wi-Fi or mobile data. Other network issues will be handled by the system.

3.2.3 External Requirements

3.2.3.1 Regulatory Requirements

Personal information such as names, surnames, and borrowing history should be gathered, processed, and kept in a safe and lawful manner. The app should also
follow some security standards, such as SSL and two-factor authentication, to prevent unauthorized access or security breaches.

3.2.3.2 Ethical Requirements

1. Request Permission Only When We Need It:

It is very easy to go overboard with sending access requests to the users. We might think it is easier to get those permissions out of the, but the user
does not feel the same way. They feel uncomfortable.

2. Stop Promoting the Quantity of Engagement:

There’s a reason some apps are so engaging and addictive, and we will promote the opposite of that. We will advise our users to use the app only when
needed.

April 06, 2021 Page 26 of 19

 EPOKA Library System
Requirements Specification

3. Never Use Dark Patterns:

Dark patterns are a type of design trick, and they may take many different shapes. For instance:

●  Asking ambiguous or perplexing questions in an effort to sway users' responses in favor.

●  Ads that look like ordinary content.

●  Automatically starting a subscription without reminding users the trial is about to expire.

3.2.3.3 Legislative Requirements

 Copyright Laws: The app should comply with copyright laws and policies, such as fair use guidelines and the Copyright Act.

 Protection of Personal Information Laws: The app should follow all the best practices regarding data protection and privacy. It should ensure the security

of the data and protect the confidentiality of the records.

 User Compliance: When the students use the app, they must confirm their acceptance of the terms of use and privacy policies. If they do not agree with one

or many of these terms, they are free to not use our application.

3.2.3.3.1 Accounting Requirements

Due to the nature of our web app, no accounting requirements will be implemented.

3.2.3.3.2 Security Requirements

 Authentication: The web app should require users to authenticate themselves before any access permission is given.

 Authorization: The web app should provide authorization on the users based on their roles and privileges. For example, students should only be allowed to

order books and view their history, while librarians have additional privileges.

 Encryption: All sensitive data transmitted between the users’ devices and the app should be encrypted following a protocol like HTTPS.

 Secure Passwords: Password should be hashed and salted according to the industry standards.

 Session Management: The users should be logged out after a period of inactivity.

 Regular Updates: The app should regularly be updated to fix bugs and patch security flaws.

3.3 Domain Requirements

We will use the top-level domain that educational institutions use, .edu domain. To be more specific the domain will be .epoka.edu.al. Because the library will be
part of Epoka University and will be used only by Epoka students, we are qualified to use that domain ending.

April 06, 2021 Page 26 of 18