Western Mindanao State University

Institute of Computer Studies

Department of Computer Science
Zamboanga City

In Partial Fulfillment
of the Requirements for the CSIT 142
On – The – Job Training

Zamboanga City Library Local Access Catalog System

Submitted by:

Maque, Ricah Mae G.

Albar, Admunir C.
Pusalan, Alkhan J.

Submitted to:

Mr. Salimar B. Tahil

Instructor

February 2019
 Table of Contents

Topics Page

I. The Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Client Background/Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Organizational Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

II. System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4. Definitions, Acronyms, and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Overall Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1. Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2. Product Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3. User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4. Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5. General Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6. Assumptions and Dependencies

3. Specific Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1. External Interface Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

3.3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4. Non – Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5. Design Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

III. System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. System Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1. HIPO with Module Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 1.2. Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Database Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1. ERD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2. Database Design / Schema / Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IV. System Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Bug Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3. Test Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V. Project Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

VI. Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transcribed interview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Letter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User Testing Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Training Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Acceptance Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I. THE CLIENT

1. Client Background/Profile

The Zamboanga City Library is a public library that gives free admission of their facilities
for anyone who wants to visit their library including borrowing of books, free WiFi access and etc. but
some of their facilities are not for free (e.g. Charging of phones and laptops, Using the Desktop Computers,
Printing and Photo Copying). They have Library Cards for anyone who wants to avail. They are located at
R.T Lim Boulevard, Zamboanga City under the Division of Sangguniang Panlungsod.

About our client Dr. Madelyn F. Candido, Librarian IV, she’s the current Head of the City
Library. She finished BSE Major in Library Science at Universidad de Zamboanga at 1998. She also has a
Master’s Degree taken at Universidad de Zamboanga with the course of Master in Library Science Major
in Library and Information Management Science at 2008. She has also finished Doctoral Degree also at
Universidad de Zamboanga at 2013 with the course of Doctor of Philosophy in Education Major in
Curriculum and Supervision. Before she appointed as the Head of the City Library at 2018, she was a Chief
Librarian at Universidad de Zamboanga. Her specialties are Library Science, Information Management,
Library Supervision, and Curriculum and Instructions.

2. Organizational Structure

Dr. Madelyn F. Candido

Librarian IV

Carmelita T. Agustin Rechelda E. Patrimonio Anna Melinda B. Decir

Librarian III Librarian I Librarian I

Eliza A. Zapanta Ma. Socorro Deborah Mary Gail E. Aizon Ma. Regene U. Rubio
Duremdez
Utility Worker II Clerk I J.O.
Admin. Aide VI
II. SYSTEM REQUIREMENTS

1. Introduction

1.1. Overview

The Zamboanga City Library Local Access Catalog System is a desktop / laptop application
that helps manage the books more easily. Lately, they are profiling the books manually, and then later on
they will type it with their written profiled book into the desktop using Microsoft Excel.

With the system we creating, we ease their job by minimizing the paper works instead
they write first in the paper, they will immediate input it in the system and save it and then later on, it can
be imported into Excel format if they want to.

1.2. Purpose

The purpose of this document is to ensure that the software requirements for the
Zamboanga City Library Book Inventory System are clearly defined and that all the requirements will be
the basis for the implementation and testing of the said system.

1.3. Scope

The content for this document will cover all the requirements for the duration of the
On – The – Job Training project implementation for the school year 2018 – 2019. Only the requirements
specified in this document will be included in the final system design.

1.4. Definitions, Acronyms, and Abbreviations

1.4.1. Definitions

Client – The person or the company who needs the software system.

vb.NET 2015 – Or the Visual Basic.NET 2015 is a version of visual basic

computer programming language.

MySQL – A database management system that serves as a storage of

data.

Administrator – A person who has the authority to access all the features
of the system.

Cataloger – A person who is in – Charge in cataloging is the one who will

profiling all books and inventory.

Clerk – A person who is in – Charge of searching books in the shelf if it is

available to borrow or not.
2. Overall Description

2.1. Product Perspective

Figure 1. Zamboanga City Library Book Inventory System Conceptual Design

 Figure 2. Zamboanga City Library Book Inventory System Network Architecture

2.2. Product Functions

The Administrator should be running so as to track the account details of each of the user. The database
will only respond to those system where the client is running.
 2.3. User Classes and Characteristics

2.3.1. The Library Staff

The majority of the Library Staff is to update the books and its inventory
daily. It concerns them how many books were profiled and stored properly. The
technical experience of these users should not matter as the system will be
straightforward and easy to use.

2.3.2. The IT Staff

IT Staff will be the primary maintainers of the application and may be to

perform some administrative functions to its database. The IT Staff will have a
technical background.

2.4. Operating Environment

Particulars Client System

Operating System Windows 7
Processor Pentium 4, 1.8 GHz
Hard Disk 100GB
RAM 4GB

2.5. General Constraints

Synchronization: uses a service like XAMPP to be able to connect to the database,

connects only to Windows 7 or better.

Memory: Device must have 2GB internal Hard Drive. And also, the RAM (Random
Access Memory) must be 1GB or better. Device must also have a USB
port, and the software must be able to read and write to that port.

Screen Orientation: The Screen Monitor size must be 1366 x 768 or better.

2.6. Assumptions and Dependencies

 It is assumed that the hardware designed will work correctly with the
operating system (windows 10) and the developed system.

 The system is running correctly using Microsoft Visual Studio Enterprise 2015
as the Software and Microsoft Windows 10 as the Operating System.
III. Specific Requirements

3.1. External Interface Requirements

3.1.1. User Interfaces

3.1.1.1. All interactions with the Zamboanga City Library Book Inventory
System will occur through an Information System (Offline
System).

3.1.1.2. The Zamboanga City Library Book Inventory System will be

accessed through a secure user interface requiring the use of a
predetermined login name and password.

3.1.1.3. Any unexpected system operation will be announced to the user

with an error message stating the cause of the error. In the event that a
cause cannot be readily determined a generic error message will be
presented.

3.1.1.4. The layout of an Information System will conform to a standard

screen resolution 1366 x 768 or better.

3.1.2. Hardware Interfaces

No. Hardware Interface Data / Component Needed Purpose

1 Local Area Network Ethernet, Ethernet Port, To be able to connect to the other
RJ45 Workstations.
2 Workstations Desktop or Laptop To be able the Client to use the system.

3.1.3. Software Interfaces

No. Software Interface Data / Component Needed Purpose

1 Operating System Microsoft Windows 7 or To be able to run the system
better sufficiently.
2 Information System Microsoft Visual Studio To be able to open the development of
Enterprise 2015 the system.

3.1.4. Communication Interfaces

No. Communication Data / Component Needed Purpose

Interface
1 Database XAMPP To be able to open the server of the
database.
 3.2. Functional Requirements

3.2.1. Login Module

Requirements Requirements Requirements Definition Priority

ID
FR 1.1.0 Log In The system must allow the user to log in the system. 1
(highest)
FR 1.2.0 Connection The system must allow the user to change the 1
Settings connection of the database. (highest)
FR 1.3.0 Forgot The system must allow the user to retrieve the password 1
Password by answering the security question. (highest)

3.2.2 Home Module

Requirements Requirements Requirements Definition Priority

ID
FR 2.1.1 Search Book The system must allow the user to view all books. 1
(highest)
FR 2.1.2 Descriptive The system must allow the user to create new book. 1
Cataloging (highest)
FR 2.1.3 Accessioning The system must allow the user to create new Accession 1
number and Property number in a new created book. (highest)
FR 2.1.4 Manage User The system must allow the user(admin) to create new 1
account but different user type. (highest)
FR 2.1.5 Book The system must allow the user to edit the Source, 1
Maintenance Subject, Author, Section, Includes, Place of Publication, (highest)
and Publisher that has already been saved in Descriptive
Cataloging Module.
FR 2.1.6 Reports The system must allow the user to generate report to 1
print out the necessary forms. (highest)
FR 2.1.7 Statistics The system must allow the user to view the statistics of 1
newly arrive books and the quantity of the books. (highest)
FR 2.1.8 Database The system must allow the user to export the entire 1
database as backup. (highest)
FR 2.1.9 Profile The system must allow the user to view who is currently 1
using the system. (highest)
FR 2.1.10 Logout The system must allow the user to logout in the system. 1
(highest)
 3.2.3. Search Book Module

Requirements Requirements Requirements Definition Priority

ID
FR 3.1.1 Search Title The system must allow the user to view the specific 1
books. (It can also be search by Section, Source, (highest)
Publisher, and Place of Publication).

3.2.4. Descriptive Cataloging Module

Requirements Requirements Requirements Definition Priority

ID
FR 4.1.1 Search Title The system must allow the user to view the specific 1
books. (It can also be search by Section, Source, (highest)
Publisher, and Place of Publication).
FR 4.1.2 Reset Filter The system must allow the user to reset all the search 1
forms. (highest)
FR 4.1.3 Edit The system must allow the user to edit created books. 1
(highest)
FR 4.1.5 View Summary The system must allow the user to view the summary of 1
the book. (highest)
FR 4.1.6 New Book The system must allow the user to fill the necessary 1
forms to be able to create new book. (highest)
FR 4.1.7 Add Author The system must allow the user to create new Author. 1
(highest)
FR 4.1.8 Add Subject The system must allow the user to create new Subject. 1
(highest)
FR 4.1.9 Add Section The system must allow the user to create new Section. 1
(highest)
FR 4.1.10 Add Source The system must allow the user to create new Source. 1
(highest)
FR 4.1.11 Add Place of The system must allow the user to create new Place of 1
Publication Publication. (highest)
FR 4.1.12 Add Includes The system must allow the user to create new Includes. 1
(highest)
FR 4.1.13 Add Publisher The system must allow the user to create new Publisher. 1
(highest)
FR 4.1.14 Save The system must allow the user to save the newly 1
created book. (highest)
FR 4.1.15 Cancel The system must allow the user to cancel the newly 1
formed book. (highest)
 3.2.5. Accessioning Module

Requirements Requirements Requirements Definition Priority

ID
FR 5.1.1 Search Title The system must allow the user to view the specific tool. 1
(highest)
FR 5.1.2 Add Tool The system must allow the user to add supplier, price 1
and copies of the specified tool. (highest)
FR 5.1.3 Tools with no The system must allow the user to view all tools with no 1
Accession and Accession and Property number. (highest)
Property
Number
FR 5.1.5 Tools with The system must allow the user to view all tool with 1
Accession and Accession and Property Number. (highest)
Property
Number
FR 5.1.6 View Batch The system must allow the user to view all books with 1
batches. (highest)

3.2.6. Manage User Module

Requirements Requirements Requirements Definition Priority

ID
FR 6.1.1 Search Name The system must allow the admin to search the names 1
of the users. (highest)
FR 6.1.2 Add Account The system must allow the admin to add a new account. 1
(highest)
FR 6.1.3 Edit Account The system must allow the admin to edit an account. 1
(highest)
FR 6.1.4 Delete Account The system must allow the admin to delete an account. 1
(highest)

3.2.7. Maintenance Module

Requirements Requirements Requirements Definition Priority

ID
FR 7.1.1 Manage Source The system must allow the user to edit source. 1
(highest)
FR 7.1.2 Search Source The system must allow the user to search all source. 1
(highest)
FR 7.1.3 Manage The system must allow the user to edit subject. 1
Subject (highest)
FR 7.1.5 Search Subject The system must allow the user to search all subjects. 1
(highest)
FR 7.1.6 Manage Author The system must allow the user to edit author. 1
(highest)
 FR 7.1.7 Search Author The system must allow the user to search all authors. 1
(highest)
FR 7.1.8 Manage The system must allow the user to edit section. 1
Section (highest)
FR 7.1.9 Search Section The system must allow the user to search all sections. 1
(highest)
FR 7.1.10 Manage The system must allow the user to edit includes. 1
Includes (highest)
FR 7.1.11 Search Includes The system must allow the user to search all includes. 1
(highest)
FR 7.1.12 Manage Place The system must allow the user to edit place of 1
of Publication publication. (highest)
FR 7.1.13 Search Place of The system must allow the user to search all place of 1
Publication publications. (highest)
FR 7.1.14 Manage The system must allow the user to edit publisher. 1
Publisher (highest)
FR 7.1.15 Search The system must allow the user to search all Publishers. 1
Publisher (highest)

3.2.8. Reports Module

Requirements Requirements Requirements Definition Priority

ID
FR 8.1.1 Print Report The system must allow the user to print the list of all 1
books. (highest)

3.2.9. Statistics Module

Requirements Requirements Requirements Definition Priority

ID
FR 9.1.1 View The system must allow the user to view the quantities of 1
the book in specific date. (highest)

3.2.10. Database Module

Requirements Requirements Requirements Definition Priority

ID
FR 10.1.1 Export The system must allow the user to export all database 1
Database into xml format. (highest)
 3.4. Non – Functional Requirements

3.4.1. Usability Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 1.1.0 Ease of Use The system shall be easy to use to the Client and easy to 1
Requirement comprehend information whenever the Client commits (highest)
a mistake.
NR 1.2.0 Learning The system shall not be requiring a huge amount of time 1
Requirements for the Client to learn the system. (highest)
NR 1.3.0 Understanding The system shall use words and symbols that are 1
and Politeness naturally understandable by the Client. (highest)
Requirements

3.4.2. Performance Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 2.1.0 Speed and The system shall be responding for every click of a 1
Latency button, document and upload and download. The data (highest)
Requirements update will be depending on the network speed of the
Client’s Workstation.
NR 2.2.0 Reliability and The system shall be day and night available but the 1
Availability maintenance from the technicians might cause the (highest)
Requirements system will down for a certain amount of time.
NR 2.3.0 Precision or The system shall be use only to the certified Zamboanga 1
Accuracy City Library employees and the admin should verify a (highest)
Requirements user’s account by supplying them with a password for
them to access their account.
NR 2.4.0 Robustness or The system shall have the option of undoing the action 1
Fault – by exiting the module or by restoring deleted users. (highest)
Tolerance
Requirements
NR 2.5.0 Capacity The system shall be able to manage all incoming 1
Requirements information for the database. (highest)
NR 2.6.0 Scalability or The system shall handle a large amount of database that 1
Extensibility comes from multiple accounts. (highest)
Requirements
NR 2.7.0 Longevity The system shall be expected to operate in a long term. 1
Requirements (highest)
 3.4.3. Operational and Environmental Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 3.1.0 Expected The system shall be taking place at the assigned 1
Physical department in the Zamboanga City Library of who will (highest)
Environment be using the system.
NR 3.2.0 Requirements The system shall be integrated by the IT services. 1
for Interfacing (highest)
with Adjacent
Systems
NR 3.3.0 Productization The system shall be run at the minimum specification of 1
Requirements 1GB RAM and 2GB of Hard Drive. (highest)

3.4.4. Maintainability and Support Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 4.1.0 Maintenance The system shall have the maintenance every year to 1
Requirements ensure the functionality of the system. (highest)
NR 4.2.0 Supportability The systems interface shall be easily comprehensible 1
Requirements and user – friendly even to non – technical users. (highest)
NR 4.3.0 Adaptability The system shall be run on Windows 7 or better 1
Requirements Operating Systems. (highest)

3.4.5. Security Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 5.1.0 Access The system shall not be gain access to the non – 1
Requirements registered users unless the Admin will supply them user (highest)
and password for them to access the system.
NR 5.2.0 Integrity The system shall have the limiting of access the 1
Requirements database. Only the admin can access the database. And (highest)
it has a back – up functionalities.
NR 5.3.0 Privacy The system shall have the restrictions or limits of all the 1
Requirements registered user accounts except by the Admin. (highest)
NR 5.4.0 Audit The system shall have the user and its transactions in the 1
Requirements database. (highest)
NR 5.5.0 Immunity The system shall have a minimum possibility of 1
Requirements corruption from the system itself or to the users. (highest)
 3.4.6. Cultural and Political Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 6.1.0 Cultural There is no Cultural Requirements in the system.
Requirements
NR 6.2.0 Political There is no Political Requirements in the system.
Requirements

3.4.7. Legal Requirements

Requirements Requirements Requirements Definition Priority

ID
NR 7.1.0 Compliance The system shall protect the department, the 1
Requirements documents, as well as the employee’s information (highest)
under the Data Protection Act.
NR 7.2.0 Standards The system shall be developed using the process of 1
Requirements Incremental Development as a standard requirement. (highest)

3.4.8. New Problems

Requirements Requirements Requirements Definition Priority

ID
NR 8.1.0 Effects on the The technical problems can lead to write a record on a 1
Current logbook while waiting for the system to be fixed. This (highest)
Environment will affect the organization of the records. And
sometimes, this will lead to inaccurate or loss records.
NR 8.2.0 Effects on the Currently there are no installed systems like our system 1
Installed will cause no effect to any existing system. (highest)
Systems
NR 8.3.0 Potential User There are different user types in the system; the Admin, 1
Problems the Cataloger and the Clerk. The Cataloger and the Clerk (highest)
cannot access the database only the Admin can.
NR 8.4.0 Limitations in The system may only be running on a Windows 1
the Anticipated Operating System. It may not work properly on other (highest)
Implementation Operating Systems.
Environment
that may inhibit
the new project
NR 8.5.0 Follow – up The Zamboanga City Library might change their 1
problem standards regarding the cataloging. It is imperative that (highest)
the team must apply the changes to the system in order
to adapt to the establishment changes.
 3.4.9. Mitigation to the new problem

Requirements Requirements Requirements Definition Priority

ID
NR 9.1.0 Requirement The Zamboanga City Library will have to verify the 1
for Mitigation operations and protocols that are being followed and (highest)
to the New used on the system to detect any unforeseen issue that
Product might come up.
NR 9.2.0 Data that has The data that is to be used by the system must be 1
to be Modified encoded to the new system. (highest)
or Translated
for the New
System

3.4.10. Risks

Requirements Requirements Requirements Definition Priority

ID
NR 10.1.0 Risk The risk might be occurred while developing the system 1
especially for the Client needs. We revise and apply the (highest)
recommendation of the Client of what they want for the
system.

3.4.11. User Documentation and Training

Requirements Requirements Requirements Definition Priority

ID
NR 11.1.0 User The team shall create technical specifications to 1
Documentation accompany the system developed, to allow the Client (highest)
Requirements effectively grasp the system’s works and functionalities.
NR 11.2.0 Training The training shall be provided by the team, they shall 1
Requirements introduce the system and its functionalities to the Client (highest)
of the system.

3.5. Design Constraints

3.5.1. Database Structure Constraints

The following constraints we used in SQL are:

NOT NULL - Ensures that a column cannot have a NULL value.

UNIQUE - Ensures that all values in a column are different.

PRIMARY KEY - A combination of a NOT NULL and UNIQUE.

Uniquely identifies each row in a table.
 FOREIGN KEY - Uniquely identifies a row/record in another
table.

CHECK - Ensures that all values in a column satisfies a specific

condition.

DEFAULT - Sets a default value for a column when no value is

specified.

INDEX - Used to create and retrieve data from the database

very quickly.

3.5.2. Development Tools Constraints

Microsoft Visual Studio Enterprise 2015 – for system

development.

XAMPP – server of the database

ZAP Crystal Report

3.5.3. Hardware Component Constraints

*Mouse

*Keyboard

*Monitor

*CPU

*Printer
V. Project Schedules
VI. Training
Appendices

Transcribed Interview

The interview conducted last November 19, 2018

The Team: Ma’am good morning. We would like to interview you ma’am for
the system we creating.

The Client: OK sure. Go ahead.

The Team: Ano po yung gusto nyong system ma’am? ano yung outline na gusto
nyo po ma’am?

The Client: Gusto ko lang yung simpleng system lang for us na mapadali lang ang
profiling ng books and mahanap ko siya agad if ever na gusto ko syang
hanapin.

The Team: So, include pa po namin ang borrowing and returning ma’am?

The Client: No. kasi hindi namin pinapalabas ang books outside of the Library.
They just get books from the shelf, read it and return it to the shelf.
Ganun lang yung borrowing of books namin. If they want to avail Library
Card, they can have it avail. Pero, we just only want you to focus on
profiling (cataloging) of books. Kasi dyan kami nahihirapan eh. We are
manually profiling (cataloging) the books. Ang haba haba na ng mga
paper na pinoprofile palang. Tapos ieencode pa yan sa computer isa isa
ulit. Tapos saka pa iprint.

The Team: So, ma’am, profiling of books lng po ung system na gagawin po namin
ma’am?

The Client: Kung pwede din sana yun din mga non-printable materials, yung
magazines, tska yung newspapers din include nyo yan dyan sa system
nyo. Para ma monitor namin kung ilang materials na ang meron kami
mga ganun ba. Pagkatapos namin yun iprofile sa system, pwede na
namin siya agad maprint. Para less na ba. Hindi na sulat dito, type doon.

The Team: Ok po ma’am. Ung UI ng profiling(cataloging) ng books ma’am same

lang po yung format niya sa profiling sheet nyo po maam?

The Client: Yes. Para madali ko lang sya ma familiarize. Kaya nyo lang sa same
lang ang format nyan sa system nyo?

The Team: Yes ma’am. Kaya lang ma’am.

The Client: I copy nyo lang ang format ng profiling sheet namin sa system nyo
hah? Gusto ko yung pagkatapos ng profiling, parang maging na syang
 masterlist mga ganun. Gusto ko Makita lahat ng mga nakaprofiled na ng
books.

The Team: Yes ma’am. Sige po ma’am. May iba pa po ba kayong suggestions
ma’am?

The Client: Wala naman for now. Concern lang namin is yung masterlist lang ng
books. Just concentrate lang dun talaga sa section na yun kasi
yun talaga ang kailangan namin. Mapadali lang ang profiling tska print
na agad. Yung UI din yung ano lang yung hindi sya masakit sa mata hah?
Kasi alam mo naman dito kami. Haha.

The Team: Ok po ma’am. Noted po. May iba pa po kayong suggestions?

The Client: Wala na wala na. Just concentrate lang sa cataloging section lang
hah?

The Team: Ok po ma’am. Salamat po ma’am. Balik lang po kami dito if may
questions pa kami ma’am.

The Client: Ah ok din. Salamat din sa inyo.

Letter
TOR
User Testing Forms
Training Certificate
Acceptance Certificate