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.

Non-Functional Requirements

16

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. Table 1. Books_info Field Name book_Id Data Type Int Size Required No Description Book Id

17

Book_Title Author Shelf_No Category TotalNo NoBorrowed

Varchar Varchar Varchar Varchar Int Int

40 30 3 10

Yes Yes Yes Yes Yes Yes

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 Table 3. Borrower_detail Field Name Data Type Size Required Description

18

request_no Borrower_ID book_Id

Int Varchar Integer 10

No No No

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 Use Case Description This implies the different interactions between the users of the system and the system itself to achieve a common goal function.

20

Figure 3.2 Use Case of Students Process Use Case Name: Search library materials Purpose: To search library materials Triggering Actor: Student Benefiting Actor: Student Pre-Condition: The student wants to search a book. Post-Condition: The student has successfully searched the book. User 1. Click search bubbleButton 2. Display search form 3. Input the name of the book 4. Display the name of the book System

21

Use Case Name: Borrow library materials Purpose: To borrow library materials Triggering Actor: Student Benefiting Actor: Student Pre-Condition: The student wants to borrow a book. Post-Condition: The student has successfully borrowed the book. Student 1. Click borrow bubbleButton 2. Display borrow form 3. Input borrowers ID 4. Display the name of the borrowers 4.1 else 4.1.1 display invalid borrowers ID 5. Click browse button 6. Display the list of books 7. Select the book you like 8. Display the book 8.1 if the remaining book is zero 8.1.1 display running out of a copies System

22

9. Click borrow button 10. a If is not empty 10.a.1 if status is borrowed 10.a.1.1 display your current status is borrowed 10.a.2 else 10.a.2.1 borrowed 10. b. Else 10.b.1 display fill-up everything 11. Display current status is borrowed or requesting 12. Click Ok button display request is

23

Figure 3.3 Use Case of Librarians Process Use Case Name: Login Purpose: To confirm admin to login Triggering Actor: Librarian Benefiting Actor: Librarian

24

Pre-Condition: The librarian wants to login. Post-Condition: The librarian has successfully login. Librarian 1. Click Login bubbleButton 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 System

Use Case Name: Search library materials Purpose: To search library materials Triggering Actor: Librarian Benefiting Actor: Librarian

25

Pre-Condition: The librarian wants to search a book. Post-Condition: The librarian has successfully search the book. Librarian 1. Click search bubbleButton 2. Display search form 3. Input the name of the book 4. Display all the books System

Use Case Name: View borrowers Purpose: To view borrowers Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to view the borrowers list. Post-Condition: The librarian has successfully viewed the borrowers list. Librarian 1. Click view button 2. Display view borrowers form System

Use Case Name: Register students information

26

Purpose: To register the information of the students Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to register the students. Post-Condition: The librarian has successfully registered the students. Librarian 1. Click add borrower bubbleButton 2. Display addBorrower form 3. Input information of the student 4. Verify the input 4.1 If the input is not duplicated 4.1.1 display added successfully 4.2 else 4.1.1 display duplicate of record 5. Click save button System

Use Case Name: Update students membership Purpose: To update the membership of the students Triggering Actor: Librarian Benefiting Actor: Librarian

27

Pre-Condition: The librarian wants to update the students membership. Post-Condition: The librarian has successfully updated the students membership. Librarian 1. Click view borrowers status System

bubbleButton 2. Display borrowers status form 3. Input borrower ID 4. Verify input 4.1 If the input is not empty 4.1.1 display addBorrowers form 4.2 else 4.1.1 display Borrowers ID is empty 5. Click update button 6. Display addBorrowers form 7. Update the status of the student 8. Verify input 8.1 if is not empty 8.1.1 display updated successfully 8.2 else 8.2.1 display fill-up everything 9. Click update button

28

Use Case Name: View returned library materials Purpose: To view returned library materials Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to view returned library materials. Post-Condition: The librarian has successfully viewed returned library materials. Librarian 1. Click view borrowers status System

bubbleButton 2. Display borrowers status form 3. Input borrower ID 4. Display dgvBooks

Use Case Name: Return library materials Purpose: To return library materials Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to return library materials. Post-Condition: The librarian has successfully returned library materials.

29

Librarian 1. Click view borrowers status

System

bubbleButton 2. Display borrowers status form 3. Input borrower ID 4. Display dgvBooks 5. Click the dgvBooks list 6. Verify input 6.1 if the status is borrowed 6.1.1 display book returned 6.2 else 6.1.1 display choose first a

unreturned book 7. Click return button

Use Case Name: Save library materials Purpose: To save library materials Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to save library materials. Post-Condition: The librarian has successfully saved library materials.

30

Librarian 1. Click add books bubbleButton

System

2. Display addBook form 3. Choose the new 4. Input information of the book 5. Verify the input 5.1 if the input is not empty 5.1.1 display successfully save 5.2 else 5.2.1 display some fields left empty 6. Click save button

Use Case Name: Update library materials Purpose: To update library materials Triggering Actor: Librarian Benefiting Actor: Librarian Pre-Condition: The librarian wants to update the library materials. Post-Condition: The librarian has successfully updated the library materials. Librarian 1. Click add books bubbleButton System

31

2. Display addBook form 3. Choose the old 4. Click browse button 5. Display the list of books 6. Double click the row header to choose a book 7. Display the information of the book in the addBooks form 8. Change the total books 9. Verify input 9.1 if the total books is greater than the updated total number 9.1.1 display successfully updated 9.2 else 9.2.1 display totalNo of book must not be less than to the previous totalNo 10. Click update button

Use Case Name: Approve students request Purpose: To approve the students request Triggering Actor: Librarian Benefiting Actor: Librarian

32

Pre-Condition: The librarian wants to approve the request of the students. Post-Condition: The librarian has successfully approved the request of the students. Librarian 1. Click borrowers request bubbleButton 2. Display request form 3. Click the row header of the request form 4. a. If the librarian select a request 4.a.1 if number of borrowed is equal to totalNo 4.a.1.1 display out of copies 4.a.2 else 4.a.2.1 borrowed 4. b. Else 4.b.1 display choose first a request 5. Click update button display successfully System

Use Case Name: Reject students request Purpose: To reject the students request Triggering Actor: Librarian

33

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 4.b.1 display choose first a request 5. Click update button System