Chapter 3 REQUIREMENTS ANALYSIS

This chapter exemplified the system requirements analysis in the development of Library System of Mactan National High School. System requirements analysis included functional, nonfunctional, and usability requirements.

Functional Requirements Functional requirements refer to what the software can do, the inputs it can accept and the processes to be done to come up with the desired output. Library system has the following functionalities: Processing The system performed the following processes: 1. Students membership; 2. Library materials registration; 3. Inquire (information on library materials); 4. Borrowing of library materials; 5. Returning of library materials; 6. Updates of library materials; 7. Updates of student membership; and

15

8. Approve / Reject the students request.

Inputs The system was capable of accepting information of the following inputs: 1. Login for the Librarian; 2. Registering students information; 3. Library materials; 4. Borrowing of library materials; 5. Returning of library materials; and 6. Search or locate library materials. Output The system should be able to display the: 1. Details of searched and located library materials; 2. List of library materials; 3. List of returned materials; and 4. Information of all library materials and students information.

16

Non-Functional Requirements Non-functional requirements are the different constraints and standards of the software. These refer to the modes of the system, how it would be developed and the tools required for its development. The following are the non-functional requirements of the system: 1. Deletion of records is not allowed; and 2. Members of library staff are the only ones allowed to operate the system.

Usability Requirements Usability requirements refer to the characteristics that the users of the system should possess. The system users should have all the qualifications indicated below: 1. Being a computer competent; 2. Having a concept of the library transactions; and 3. Being knowledgeable of the automated system.

Metadata Metadata refers to the overall description of data in the database. It expresses the context or relativity of data.

17

Table 1. Books_info Field Name book_Id Book_Title Author Shelf_No Category TotalNo NoBorrowed Data Type Int Varchar Varchar Varchar Varchar Int Int 40 30 3 10 Size Required No Yes Yes Yes Yes Yes Yes Description Book Id Book Title Book Author Book Shelf Number Book Category Book Total Number Number Borrowed Book

Primary Key: book_Id Table 2. Borrower_header Field Name Borrower_ID Borrower_Name Borrower_Section Picture Borrower_Address Borrower_CNo Borrower_EAdd Data Type Varchar Varchar Varchar Varchar Varchar Varchar Varchar Size 10 40 10 150 100 20 30 Required Yes Yes Yes No Yes Yes Yes Description Borrowers Id Borrowers Name Borrowers Section Borrowers Picture Borrowers Address Borrowers Cell Number Borrowers Email Address

Primary Key: borrower_id

18

Table 3. Borrower_detail Field Name request_no Borrower_ID book_Id Data Type Int Varchar Integer 10 Size Required No No No Description Borrowers Request Number Borrowers Id(Foreign key) Borrowers Book Id (Foreign key) DateBorrowed DateReturned Status Datetime Datetime Varchar 10 Yes Yes Yes Borrowers Date Borrowed Borrowers Date Returned Borrowers Status

Primary Key: request_no

Use Case Model This is a diagram that shows the relationship among actors and use cases within a system. It has some components to include, namely: Use case, describes a sequence of actions that provides something of measurable value to an actor and is drawn as a horizontal ellipse; Actor, which is an external system, person, organization, that plays a role in one or more interactions with your system. They are drawn as stick figures; Association lines between actors and use cases, which are indicated in use case diagrams by solid lines. They exist whenever an actor is involved with an interaction described by a use case; and

19

Rectangle around the use cases, which is called as the system boundary box and is used to indicate the scope of the system.

Figure 3.1 Use Case Model of Mactan National High School Library Monitoring System

20

Use Case Description This implies the different interactions between the users of the system and the system itself to achieve a common goal function.

Figure 3.2 Use Case of Process Login Use Case Name: Login Purpose: To confirm admin to login Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to login. Post-Condition: The librarian has successfully login.

21

Librarian 1. Click Login bubbleButton

System

2. Display login form 3. Input username and password 4. Click or Press Enter to login 5. Verify the input 5.1 If is not empty 5.1.1. if password is correct 5.1.1.1 display successfully login 5.1.2 else 5.1.2.1 display invalid account 5.2 else 5.2.1 display some fields left empty 6. Display the admin form

22

Figure 3.3 Use Case of Process Inquiry Use Case Name: Search library materials Purpose: To search library materials Triggering Actor: Librarian and Student Benefiting Actor: Librarian and Student Pre-Condition: The user (librarian/student) wants to search a book. Post-Condition: Records of book/s containing the search keyword will be viewed in the data grid view. Librarian and Student 1. Click search bubbleButton 2. Display search form 3. Input the name of the book 4. Display all the books System

23

Figure 3.4 Use Case of Process Record Use Case Name: Maintain Borrowers record Purpose: To maintain borrowers record Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to process borrowers record. Post-Condition: The system processes borrowers record. Librarian System 1. Display borrower status form 2. Input borrowers ID

24

3. Verify borrowers ID

Use Case Name: Verify Borrowers Record Purpose: To verify borrowers identification Triggering Actor: System Benefiting Actor: Librarian Pre-Condition: There is a need to verify borrowers identification. Post-Condition: The system verifies borrowers identification. Librarian System 1. Search 2. Update borrower

Use Case Name: Add Borrower Purpose: To add borrower detail Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The Librarian wants to add borrower.

25

Post-Condition: A borrower is officially registered. Librarian System 1. Display borrowers information 2. Enter new details 3. Update database

Use Case Name: Maintain Library Materials Purpose: To process library materials record Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to process library materials record. Post-Condition: The system processes library materials record. Librarian 1. Click the add book bubbleButton 2. Display the addBooks form 3. Choose action, System

Use Case Name: Verify Library Material Purpose: To verify library materials

26

Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: There is a need to verify library materials. Post-Condition: The system verifies library materials. Librarian System 1. Add/ update book 1.1 if add, 1.1.1 add books 1.2 else, 1.2.1 update book

Use Case Name: Add Library Material Purpose: To add library material Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to register a library material. Post-Condition: A library material is officially registered. Librarian 1. Choose option new System

27

2. Input library material details 3. Update database

Use Case Name: Update library material Purpose: To update library materials details Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to update library materials records. Post-Condition: Library materials record is successfully updated. Librarian 1. Choose option old 2. Input library material details 3. Update database System

Use Case Name: View Borrowers Request Purpose: To view borrowers request Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to process the request record.

28

Post-Condition: The system processes borrowers request record. Librarian 1. Click the borrowers request System

bubbleButton 2. Display RequestForm 3. Input borrower ID

Use Case Name: Verify Borrowers Request Purpose: To verify borrowers request Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: There is a need to verify borrowers requests identification Post-Condition: The system verifies borrowers requests identification. Librarian System 1. Select 1.1 approve request 1.2 reject request

Use Case Name: Approve Borrowers Request Purpose: To approve borrowers request

29

Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to approve the borrowers request. Post-Condition: The librarian has successfully approved the borrowers request. Librarian 1. Select the borrowers book request 2. Click approve button 3. Successfully approved System

Use Case Name: Reject Borrowers Request Purpose: To reject borrowers request Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to reject the borrowers request. Post-Condition: The librarian has successfully rejected the borrowers request. Librarian 1. Select the borrowers book request 2. Click reject button 3. Successfully rejected System

30

Use Case Name: Reject students request Purpose: To reject the students request Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to reject the request of the students. Post-Condition: The librarian has successfully rejected the request of the students. Librarian 1. Click borrowers request bubble Button 2. Display request form 3. Click the row header of the request form 4. a. If the librarian select a request 4.a.1 display request rejected 4. b. Else System

31

4.b.1 display choose first a request 5. Click update button