Professional Documents
Culture Documents
Reference Document
Reference Document
This section provides the software development plan for the ACLC EZ Borrow Library
System.
3.1. Requirements and Development
The proponent determined that the librarian and the students would require the
following functional requirements in order to use the system:
Librarian Functional Requirements
Req. ID Description Priority Complexity
LFR. 01 Upon going to the website, the librarian High Medium
shall fill out the login credentials needed
by the system.
LFR. 02 The registered librarian can access the High High
functionality of the system by providing
the correct login information.
After logging in, the librarian will be
automatically redirected to the system’s
landing page.
However, if the librarian's login
credentials are incorrect, a login error
message will be displayed.
LFR. 03 New assigned librarian can also register in High Medium
the website by clicking on the “Sign Up”
button.
LFR. 04 Librarian can add students who borrowed Medium Medium
books personally.
Table 2. Librarian Functional Requirements
Student Functional Requirements
Req. ID Description Priority Complexity
SFR. 01 The system can only be accessed by High High
students with the login credentials from
the student portal.
SFR. 02 After logging in, the students will be Medium Medium
redirected to the system’s landing page
where they can search for available books
and newly updated books in the library.
Table 3. Student Functional Requirements
The system's rudimentary user interface (UI) design was also created by the
proponent, although it may be upgraded and improved in the near future after more data
has been gathered for analysis.
3.2. Project Documentation
This section defines the tool(s) used to produce the project documentation and how
document configuration will be controlled.
Microsoft Word – the proponent entered all the data and supporting materials into this
software program during the project's active phase.
Canva – this website was used by the proponent to create a logo for the library
system.
Google Meet/Messenger Video Call – from the convenience of one's own home, this
program was utilized to undertake project analysis and brainstorming.
Face-to-face Meet up – when project analysis cannot be adequately conveyed through
online calls, a meetup was held during the project review and in-person classes.
3.3. System Life Cycle
This section describes the lifecycle model used across ACLC EZ Borrow Library System
projects. The model encompasses the entire development process from requirements analysis
through deployment.
Structure analysis uses a concept called the systems development life cycle (SDLC) to
plan and manage the system development process. The SDLC model contains the following
steps:
1. System Planning.
2. System Analysis.
3. System Design.
4. System Implementation.
5. System Operation, Support, and Security.
Figure 1. System Development Life Cycle Model
3.4. Schedules and Resources
The project's comprehensive schedule can be found in this table. In addition to
showing the essential path and any crucial dependencies, the schedule also shows the
assigned individuals.
Requirements Gathering
Analysis
Design
Coding
Testing
Acceptance
Maintenance
Jan | Feb | Mar | April | May Sept | Oct | Nov | Dec | Jan Future
rd
3 Year Second Semester 4th Year First Semester