Chapter 4

Chapter 4 PERFORMANCE ANALYSIS
4.1 Introduction
In this chapter, the developers will discuss the system functionality, efficiency, and main
ability of the system. To know it is suitable on the expected outcome of objectives. The
developers will provide test and conduct of the system and to for seeing how to be
developed system will help them in their current and future operations.
4.2 Experimental
The developers conducted a review to the users, by analyzing the performance of the
proposed system, checking the possible errors and functions in each module. The used
parameters are given by the developers listed below.
4.2.1 Test Plan
A test plan is a document describing the testing scope and activities. It is the basis
for formally testing any software in a project. It includes the objective and scope of
the tests to be run. A test plan also has test cases and it serves as a framework and
a guide to ensure your testing project is successful and helps you to control risks. It
is a record of the test planning process. The plan typically contains a detailed
understanding of the eventual work flow. [BART2018]
Computerized Library System for Banca Banca Integrated National High School 4-1
4.2.2.1 Test Plan Activities (part one)
Test Test Plan Description
Cases
No.
1.0 Login To verify the valid accounts and
it has three (3) attempts.
2.0 Main form This is where the user can find
all the modules.
3.0 Account Management To determine if the form shows
all the created user accounts.
3.1 Update user account To determine if the module
could validate and update user
account.
3.2 Add user account To determine if the module
could add a account.
4.0 Audit trail To determine if the system can
track the transaction of the
librarian.
4.2.2.2 Test Plan Activities (part two)
5.0 Backup and restore To determine if the system can
back up the database and system.
Then restore.
6.0 Book information This module can save, update, a
module copy of the book. And can
generate call number.
6.1 Generate call number To determine if the system can
generate a call number in the
module of book information.
6.2 Save book information To determine if the created book
information will be accepted by
the system. And allow to add a
book information.
6.3 View list of book To determine if the system can
information view the list of book that been
created.
6.4 Update book To determine if the system
information allows updating the book
information.
4.2.2.3 Test Plan Activities (part three)
7.0 Archive To determine if the system
can archive some book
from the list of book
information.
8.0 Student information This module allows to add,
module save, clear, view the list of
student information and
update the information in
the form.
8.1 Add student information To determine if the system
allows adding the student
information.
8.2 Save student information To determine if the form
can save the student
information in the database.
8.3 Import student To determine if the system
information can import the student
information from database.
4.2.2.4 Test Plan Activities (Part Four)
8.4 View list student To determine if the system can
information show the list of student
information from a database.
8.5 Update student To determine if the form can
information update the student information
from the database.
8.6 Search student To determine if the system can
information search the student information
from the database.
9.0 Teacher Information This module can add, save, clear,
and view list of teacher
information
9.1 Add teacher To determine if the system
information allows adding the teacher
information.
4.2.2.5 Test Plan Activities (Part five)
9.2 Save teacher To determine if the created
information teacher information will be
accepted in the system after
adding the information of teacher
in form.
9.3 Update Teacher To determine if the system is can
Information able to update the teacher
information.
10.0 Borrowed This module allows receiving
Management request transaction, save,
remove, view transaction.
10.1 Student Request To determine if the requested
book of borrowers will be
accepted by the system.
10.2 Save Borrowed To determine if the borrowers
Management request will add and save to issue
the books from librarian.
4.2.2.6 Test Plan Activities (Part six)
10.3 Finish borrowed To determine if the system can
books issue books for the borrowers.
11.0 Book out This module allows receiving
Monitoring the return book of borrowers.
11.1 Return book To determine if can see the list
of return books.
11.2 Print Slip To determine if can print the
Acknowledgement penalty of the borrowers.
12.0 Maintenance To determine if the system
allows seeing the record of
each module that needs
maintenance for the
information.
12.1 Calendar of holidays This module allows not to
count the holidays in penalty.
12.2 Author This module allows maintain
the call number.
4.2.2.7 Test Plan Activities (Part seven)
12.3 Category This module allows maintain the
call number.
13.0 Reports This module will print all reports
from every module.
14.0 Kiosk This verify the valid account to
log in the request of the book.
Table 4-1 (Test Case)
4.2.2 Test Cases
The Computerized Library System for Banca Banca Integrated National High School
Advising System developers conducted software evaluation that will test its functions and
if the system runs effectively during or after the testing.
These are the following tests:
❖ TEST CASES
❖ User Authentication
Test Case No. 1.0
Objective: To determine if the system will match
the user information to the database to
` access the system.
Expected Result: The system must display an error
message if the user gets an invalid
username and password. However, if
the admin will use the correct
username and password, it will go in
the main form of the system.
Actual Result: The figures Show the test case 1
(user Authentication) display a
message in the login attempts if the
username and password get invalid.
Each user must register to account
and input their own valid username
and password.
Figure 4-1 Test Case 1.0 (User Authentication Log in Validation)
Figure 4-2 Test Case 1.0 (User Authentication Log in Successfully)
Figure 4-3 Test Case 1.0 (User Authentication Log in Attempt Failed)
❖ Main form
Test Case No. 2: To determine if the system will
display the main form after a
successful login in the system.
Expected Result: The system will display the main
form where the admin can access all
the modules. After the admin
successful login in the system.
Actual Result: The test case 2 (Main form) will show
after. If the admin is successful login
into their valid username and
password.
Figure 4-4 Test Case 2.0 (Main form)
❖ User Management
Test Case No. 3.0
Objective: To determine if the module will show the
created user account.
Expected Result: The form will show all the created user
account for admin.
Actual Result: The figure shows the test case (Account
Management) where the modules display the
user account of admin.
Figure 4-5 Test Case 3.0 (Account Management)
❖ Update User Account
Test Case No. 3.1
Objectives: To determine if the system could update the
username and password of an existing user
account.
Expected Result: The form will show a successful update
message. Before the successfully update
message, it shows a confirmation message
before you update the user accounts.
Actual Result: The figures show the confirm updated user
message. And the successfully updated user
account.
Figure 4-6 Test Case 3.1 Update Account Management)
❖ Add User Account
Test Case No. 3.2
Objectives: To determine if the system add another
account in the system
Expected Result: The form will show a successful add of
another account. Before the successfully add
message, it shows a confirmation message
before you add the user accounts.
Actual Result: The figures show the confirm add user
message. And the successfully add user
account.
Figure 4-7 Test Case 3.2 Add Account Management confirmation)
❖ Audit Trail
Test Case No. 4.0
Objectives: To determine if the user admin can access the
audit trail module and view the logs of the
user.
Expected Result: The system should display user audit trail
module
Actual Result: The system displays the audit trail module.
Figure 4-8 Test Case 4.0 (Audit Trail)
❖ Backup and Restore
Test Case No 5.0
Objectives: To determine if the system can back up the
database and record and restore the system.
Expected Result: The form will show the backup and restore
process.
Actual Result: The figure ill shows the successfully backup
and restore.
Figure 4-9 Test Case 5.0 (Backup and Restore)
Figure 4-10 Test Case 5.0 (Backup)
Figure 4-11 Test Case 5.0 (Successfully Backup)
Figure 4-12 Test Case 5.0 (Restore)
Figure 4-13 Test Case 5.0 (Successfully Restore)
❖ Book information Module
Test Case No. 6.0
Objective: To determine if the system will display the
Book information module.
Expected Results: The form will show the existing book
information in the system that valid by the
admin. Then the generation of the call
number
Actual Results: This figure shows the test case where the
module display all the existing book
information. Then generate the call number.
Figure 4-14 Test Case 6.0(Book Information)
❖ Generate Call Number
Test Case No. 6.1
Objective: To determine if the system will generate a
call number.
Expected Results: The form will show the generated call
number in .
Actual Results: This figure shows the test case where the
module display a generated call number in
form.
Figure 4-15 Test Case 6.1 (Generation of call number)
Figure 4-16 Test Case 6.1 (Successful Generation of call number)
❖ Save Book Information
Test Case No. 6.2
Objective: To determine if the system could save and
the book information. has confirmed message
and notification if its successfully save.
Expected Result: The form will show successfully save the
book information, a confirmation message
before the save process.
Actual Result: The figure will show the added and save
Book information in the system.
Figure 4-17 Test Case 6.2(Save Book Information)
Figure 4-18 Test Case 6.2(Confirmation Save Book Information)
Figure 4-19 Test Case 6.2(Successful Save Book Information)
❖ View list book information
Test Case No. 6.3
Objectives: To determine if the system can view the book
information after saving new information.
Expected Result: The form will show the list of book
information in the table.
Actual Result: The figure will show the successful input of
book information in the list of tables.
Figure 4-20 Test Case 6.3 (View list of book information)
Figure 4-21 Test Case 6.3 (Table list of book information)
❖ Update Book Information
Test Case No. 6.4
Objective: To determine if the system could update the
book information has confirmed message and
notification if it is successfully updated.
Expected Result: The form will show successfully update the
book information, a confirmation message
before the update process and display a
notification message.
Actual Result: The figure will show the updated book
information on the table, and it is
successfully updated.
Figure 4-22 Test Case 6.4 (Update Book Information)
❖ Archive
Test Case No. 7.0
Objective: To determine if the system can archive the
books. by choosing obsolete and damage
book.
Expected Result: The form will show successfully the archive
book.
Actual Result: The figure will show the archive book and it
will go to the list of archives in table.
Figure 4-23 Test Case 7.0 (Archive)
Figure 4-24 Test Case 7.0 (Move to archive)
Figure 4-25 Test Case 7.0 (Successfully Move to archive)
Figure 4-26 Test Case 7.0 (Successfully clear Move to archive)
❖ Student Information
Test Case No. 8.0
Objectives: To determine if the system will display the
student information. The admin can input the
student information that will register in the
table of the system.
Expected Result: The student information will successfully
register in the system.
Actual Result: The Form will show the successfully added
of student information in the system.
Figure 4-27 Test Case 8 .0 (Student Information)
❖ Add Student Information
Test Case No. 8.1
Objectives: To determine if the system could validate the
student information in the system.
Expected Result: The student information will disable. And
can be input some student information in the
fields
Actual Result: The form and fields can be input by librarian
after clicking the add button.
Figure 4-28 Test Case 8 .1 (Add Student Information)
❖ Save Student Information
Test Case No.8.2
Objectives: To determine if the system can save the new
student information in the database.
Expected Result: The student information will save to system
and show a confirmation message after you
save the student information and it will send
you a notification if the student information
exists in the system.
Actual Result: The figure will successfully save in the
system and it can be shown in the view list of
students after adding the information to the
student.
Figure 4-29 Test Case 8.2 (Confirmation Save Student Information)
Figure 4-30 Test Case 8.2 (Successfully Save Student Information)
❖ Import Student Information
Test Case No. 8.3
Objectives: To determine if the system will display the
imported student information. To the system
Expected Result: The student information will successfully
register in the system.by importing.
Actual Result: The Form will show the successfully import
student information.
Figure 4-31 Test Case 8.3 (Import Student Information)
Figure 4-32 Test Case 8.3 (Browse Student Information)
Figure 4-33Test Case 8.3(Successfully Import Student Information)
❖ View list Student Information
Test Case No.8.4
Objectives: To determine if the system can view the
student information after saving and add a
new information.
Expected Result: The form will show, that admin input in the
student information module in the system.
Actual Result: The figure will show the successful input of
student information by admin in adding and
saving on the system.
Figure 4-34 Test Case 8.4 (View Student Information)
❖ Update Student Information
Test Case No. 8.5
Objectives: To determine if the student information can
be updated in the system.
Expected Result: The form of student information will
successfully update in the system and show
some confirmation message before you
successfully update the student information.
Actual result: This record of the student will be successfully
updated the information in the system and
database.
Figure 4-35 Test Case 8.5 (Update Student Information)
Figure 4-36 Test Case 8.5 (Successfully Update Student Information)
❖ Search Student Information
Test Case No. 8.6
Objectives: To determine if the system could search the
student information.
Expected Result: The form will show the name of student
information on the table search by the admin.
Actual Result: The figure will show the search for student
information
Figure 4-37 Test Case 8.6 (Search Student Information)
❖ Teacher Information
Test Case No. 9.0
Objectives: To determine if the system can show the
fields in the module, that admin can input the
information of the teacher.
Expected Result: The form will show the existing input of
teacher information that valid by the admin.
Actual Result: This figure shows the test case where the
module displays all the existing teacher
information
Figure 4-38 Test Case 9.0 (Teacher Information Module)
❖ Add Teacher information
Test Case No. 9.1
Objectives: To determine if the system is able to add
teacher information.by clicking the add
button it will disable the fields
Expected Result: The form will show the other buttons and the
admin can add teacher information
Actual Result: The figure show can add and save the
teacher information.
Figure 4-39 Test Case 9.1 (Add Teacher Information Module)
❖ Save Teacher information
Test Case No. 9.2
Objectives: To determine if the system can able to save
teacher information
Expected Result: The teacher information will save in the
system.
Actual Result: The teacher information that was validated
by Librarian is successfully saved into the
system.
Figure 4-40 Test Case 9.2 (Confirmation Save Teacher Information Module)
Figure 4-41 Test Case 9.2 (Successfully Save Teacher Information Module)
Figure 4-42 Test Case 9.2 (Save Teacher Information Module)
❖ Update Teacher Information
Test Case No. 9.3
Objectives: To determine if the teacher information can
be updated in the system. Click some teacher
information in the fields to update.
Expected Result: The form of Teacher information will
successfully update in the system and show
some confirmation message before you
successfully update the student information.
Actual Result: This record of the student will be successfully
updated the information in the system and
database.
Figure 4-43 Test Case 9.3 (Update Teacher Information)
Figure 4-44 Test Case 9.4 (Successfully Teacher Information)
❖ Borrowed Management
Test Case No. 10.0
Objectives: To determine if the module will show the
borrowing transaction on the table and if can
issue book to the borrower.
Expected Result: The form will be able to issue book. And shoe
the borrowing transactions.
Actual Result: The figure shows the test case (Borrowing
Module) where the module shows the
borrowing Transaction of the system
Figure 4-45 Test Case 10.0 (Borrowed Management)
❖ Borrow Request
Test Case No. 10.1
Objectives: To determine if the system could view the
student request.
Expected Result: The form will show the student who request
book in the system.
Actual Result: The figure will show all who are the student
that request for the book.
Figure 4-46 Test Case 10.1 (Borrowed Management)
Figure 4-47 Test Case 10.1 (Double Click Borrow Request)
Figure 4-48 Test Case 10.1 (Call number not much Borrowed Management)
❖ Save Borrowed Management
Test Case No. 10.2
Objectives: To determine if the system could add and
save the borrowed book to process.
book in the system.
Figure 4-49 Test Case 10.2 (Call number not much Borrowed Management)
Figure 4-50 Test Case 10.2 (Successful Save Borrowed Management)
❖ Finish Borrowed Management
Test Case No. 10.3
Objectives: To determine if the system could issue the
books that borrowers request.
book in the system.
Figure 4-51 Test Case 10.3 (Finish Borrowed Management)
Figure 4-52 Test Case 10.3 (Successful Finish Borrowed Management)
Figure 4-53 Test Case 10.3 (Print the Borrowers Request)
❖ Book out Monitoring
Test Case No. 11.0
Objectives: To determine show the returned book list, in
table.
Expected Result: The form will show the list of borrowers who
need to return book issued.
Actual Result: The figure will show the list of return book
borrowers.
Figure 4-54 Test Case 11.1 (Print the Borrowers Request)
❖ Return book
Test Case No. 11.1
Objectives: To determine if the system will show the list
of return.
Expected Result: The form will show the list of return
transaction.
Actual Result: The figure will show the list of return book
borrowers.
Figure 4-55 Test Case 11.1 (Book out Monitoring Management)
Figure 4-56 Test Case 11.1 (Confirmation Return book)
Figure 4-57 Test Case 11.1 (Successful Returned Books)
❖ Print Slip Acknowledgement
Test Case No. 11.2
Objectives: To determine if the system could print the slip
acknowledgement of penalty.
Expected Result: The form will show the printed penalty slip.
Actual Result: The figure will show the actual printed of
penalty slip.
Figure 4-58 Test Case 11.2(Print slip Acknowledgement)
Figure 4-59 Test Case 11.2(Confirmation Print Slip Acknowledgement)
Figure 4-60 Test Case 11.2 (Print Slip for Acknowledgement)
❖ Maintenance
Test Case No. 12.0
Objectives: To determine show all the records of the
maintenance.
Expected Result: The form will show the list of maintenance
that be needed in system
Actual Result: The figure will show the list of maintenance
Figure 4-61 Test Case 12.0 (Maintenance)
❖ Holiday Maintenance
Test Case No. 12.1
Objectives: To determine if the system allow to save new
record of holidays,
Expected Result: The form will all the record of the Holidays
of calendar.
Actual Result: The figure will show the form of Holidays of
calendar
Figure 4-62 Test Case 12.1 (Holiday Maintenance)
❖ Author
Test Case No. 12.2
Objectives: To determine if the system allow to save and
update the record of author.
Expected Result: The form will show all the record author and
maintain the call number
Actual Result: The figure will show the form saving and
update the author to maintain the call
number.
Figure 4-63 Test Case 12.2(Author Maintenance)
❖ Category Maintenance
Test Case No. 12.3
Objectives: To determine if the system allow to view and
update the category maintenance.
Expected Result: The form will show the list of category
maintenance.
Actual Result: The figure will successfully update the
category maintenance
Figure 4-64Test Case 12.3 (Category Maintenance)
❖ Report
Test Case No. 13.0
Objectives: To determine if the system allow to print all
the reports.
Expected Result: The form will show the process of print in
reports.
Actual Result: The figure will successfully print the reports.
Figure 4-65 Test Case 13.0 (Reports)
Figure 4-66 Test Case 13.0 (Overdue Reports)
Figure 4-67 Test Case 13.0 (Print Overdue Reports)
Figure 4-68 Test Case 13.0 ( List of Borrowers Reports)
Figure 4-69 Test Case 13.0 (Print List of Borrowers Reports)
Figure 4-70 Test Case 13.0 (List of Returned Books)
Figure 4-71Test Case 13.0 (Print List of Returned Books)
❖ Kiosk
Test Case No. 14,0
Objectives: To determine if the system allow to request a
book by borrowers by log in in the kiosk.
Expected Result: The form will show fields that need to input
to process the request.
Actual Result: The figure will successfully show the fields
that needed to input to request.
Figure 4-72 Test Case 14.0 (Login Kiosk)
Figure 4-73 Test Case 14.0 (Add to cart Kiosk)
Figure 4-74 Test Case 14.0(Confirmation Add to cart Kiosk)
Figure 4-75 Test Case 14.0 (Successfully Add to cart Kiosk)
Figure 4-76 Test Case 14.0 (Confirmation Save Add to cart Kiosk)
Figure 4-77 Test Case 14.0 (Successful Add to cart Kiosk)
4.2.2 3 Test Log
Test Test Plan Description
Cases
No.
1.0 Login Success
2.0 Main form Success
3.0 Account Success
Management
3.1 Update user Success
account
3.2 Add user account Success
4.0 Audit trail Success
5.0 Backup and Success
restore
6.0 Book information Success
module
6.1 Generate call Success
number
6.2 Save book Success
information
6.3 View list of book Success
information
6.4 Update book Success
information
7.0 Archive Success
8.0 Student Success
information
module
8.1 Add student Success
information
8.2 Save student Success
information
8.3 Import student Success
information
8.4 View list student Success
information
8.5 Update student Success
information
8.6 Search student Success
information
9.0 Teacher Success
Information
9.1 Add teacher Success
information
9.2 Save teacher Success
information
9.3 Update Teacher Success
Information
10.0 Borrowed Success
Management
10.1 Student Request Success
10.2 Save Borrowed Success
Management
10.3 Finish borrowed Success
books
11.0 Book out Success
Monitoring
11.1 Return book Success
11.2 Print Slip Success
Acknowledgement
12.0 Maintenance Success
12.1 Calendar of Success
holidays
12.2 Author Success
12.3 Category Success
13.0 Reports Success
14.0 Kiosk Success
Table 4-2 (Test log)
4.3 Result and Analysis
After the system has been completed, the developers organized system testing and
evaluation to determine the accomplishment of the system. The evaluators were given
a survey questionnaire wherein they need to rate the system according to different
categories: Functionality, Reliability, Usability, Efficiency, Maintainability, and
portability. The developers conduct a dry run to perform the system testing, to
determine if the system function meet the expected result.
4.3.1 Population, Sample Size, and Sampling Technique
Slovin’s formula is used to calculate the sample size (n) given the population
Size (N) and a margin of error (e). It is a random sampling technique formula
to estimate sampling size. It is computed as n = N / (1+Ne2)
Whereas: n = no. of samples
N = Total population
e = error margin / margin of error
Slovin’s Formula
n=N/(1 + N e2)
Where: n=600/(1+600* (0.005) (0.005))
n=600/(1+600* (0.0025)
n=600/(1+1.5)
n=(600/2.5)
n=240
4.3.2 Data Gathering Instrument
Data gathering instrument is the used of different tools in gathering information
to other individuals. The developers used a survey questionnaire and were given
to 259 students to evaluate and for further development and analysis. The table
below shows the ISO 9216 Characteristics and Sub-Characteristics
Characteristics Sub- Characteristic Explanation
Suitability The system performed
the tasks required.
Functionality
Accurateness The system can search
data accurately
The system is capable of
Reliability Consistency handling errors.
The system can be
Learnability learned easily
The user learns use the
Usability User Friendly system easily.
The software can be

used/operated without
Operability
much effort.
The software responded
Time behavior to the user.
Efficiency
Resource Utilization The system can perform

consistent.
Maintainability Testability The system tested

easily.
The system can be

Portability Install ability installed easily.
Table 4-3 (ISO 9126 Characteristic and Sub-Characteristic)
The purpose of this evaluation plan was to provide systematic and reliable data to
the users. The gathered data were tallied, analyzed and subjected to statistical
approach. Based on the results of the evaluation, the computerized system was
improved and enhanced to meet the satisfaction of the users. Responses were based
in the Likert scale with the following ratings. 5 - Strongly Agree, 4 – Agree, 3 -
Fairly Agree, 2 – Disagree, 1 - Strongly Disagree. Student’s responses were
illustrated in table 4-3.
4.3.2.1 Likert Scale
Numerical Range Scale Level Interpretation
Description of
Agree
5 4.20 – 5.00 Strongly Agree Excellent
4 3.41 – 4.20 Agree Average
3 2.61 – 3.40 Fairly Agree Below average
2 1.81 – 2.60 Disagree Poor
1 1.00 – 1.80 Strongly disagree Very poor
Table 4-4 (Likert Scale Numerical Response Ratings)
Table 4 – 4 Shows the Likert Scale Numerical Response Ratings which served as a
guide to interpret the system performance and overall result of the system testing
in terms of the software quality assurance of ISO 9126 that conducted by the
developers.
4.3.3 Statistical Formula
Weighted Average Mean:
The researchers also used weighted arithmetic mean that was similar to an average mean.
The weighted arithmetic mean of a set of values was represented by x1, x2, x3… xn that
could be expressed as the sum of the values multiplied by their corresponding weights.
Where:
fi = represents the weight or frequency of each item
xi = represents each of item values
In simplified form, the formula is:
4.3.4 Survey Results
After collecting all the survey forms, the developers summarized all the data for statistical
analysis. The developers showed the summarized system testing evaluation result and the
graphical representation based on its Functionality, Reliability, Usability, Efficiency,
Maintainability and portability features of the system.
1. Functionality: The system performed the tasks required.
Table 4.5 Suitability
1150
x= = 4.96
240
The results of the survey in table 4-5 has a weighted mean of 4.96, it implies
that most of the students of Banca Banca Integrated National High School
that Computerized library system could be performed the tasks required,
because they already saw how the system works.
Figure 4-78 Suitability
2. Functionality: The system can search data accurately
Table 4.6 Accurateness
1060
x= = 4.41
240
The results of the survey in table 4-6 has a weighted mean of 4.41 , it implies
that most of the students of Banca Banca Integrated National High School
agreed that Computerized Library System could be presented the results as
expected, because they already saw how the system can search data accurately.
Figure 4-79Accurateness
3. Reliability: The system is capable of handling errors.
Table 4.7 Consistency
1085
x= = 4.52
240
The results of the survey in table 4-10 has a weighted mean of 4.52, it implies that
most of the students of Banca Banca Integrated National High School agreed that
Computerized Library System could eliminate the system, because they already
saw how the system is capable of handling errors.
Figure 4-80 Consistency
4. Usability: The system can be learned easily
Table 4.8 Learnability
1100
x= = 4.58
240
Computerized Library System could be easily learned, because they already saw
how the system works.
Figure 4-81 Learnability
5. Usability: The user learns use the system easily.
Table 4.9 User Friendly
899
x= = 4.78
110
Computerized Library System could be easily learned by the user, because they
already saw how the system works
Figure 4-82 User Friendly
6. Usability: The software can be used/operated without much effort.
Table 4.10 Operability
1135
x= = 4.72
240
Computerized Library System could be operated and use without much effort.
Figure 4-83 Operability
7. Efficiency: The software responded to the user.
Table 4.11 Time Behavior
1085
x= = 4.52
240
Computerized Library System could be responded to the user correctly.
Figure 4-83 Time behavior
8. Efficiency: The system can perform consistent.
Table 4.12 Resource Utilization
1138
x= = 4.74
240
The results of the survey in table 4-12 has a weighted mean of 4.74 it implies that
Computerized Library System can perform consistently.
Figure 4-84 Resource Utilization
9. Maintainability: The system tested easily.
Table 4.13 Testability
1185
x= = 4.93
240
Computerized Library System is tested easily.
Figure 4-85 Testability
10. Portability: The system can be installed easily.
Table 4.14 Install ability
1145
x= = 4.77
240
Computerized Library System is easily installed.
Figure 4-86 Installability
4.4 SUMMARY
The developers used test plan activities to determine the description of every module and
its process. Also conduct an experiment to support the hypothesis of the developers. It will
show the objective, expected result and actual result of the system created. An actual result
shows the outcome and conclusion of every experiment the developers has conducted.
These test cases are cover by observation from a user which may lead to better performance
to the system. The developers also conduct integration testing and system testing to validate
that all software module dependencies are functionally correct. Data gathering also helps
the developers to improve the developed system by using Likert scale to measure the
accurateness of the system.

Chapter 4

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Chapter 4

Hochgeladen von

Copyright:

Verfügbare Formate

Chapter 4 PERFORMANCE ANALYSIS

parameters are given by the developers listed below.

4.2.1 Test Plan

understanding of the eventual work flow. [BART2018]

Test Test Plan Description

1.0 Login To verify the valid accounts and

it has three (3) attempts.

2.0 Main form This is where the user can find

all the modules.

3.0 Account Management To determine if the form shows

all the created user accounts.

3.1 Update user account To determine if the module

could validate and update user

3.2 Add user account To determine if the module

could add a account.

4.0 Audit trail To determine if the system can

track the transaction of the

5.0 Backup and restore To determine if the system can

back up the database and system.

6.0 Book information This module can save, update, a

module copy of the book. And can

generate call number.

6.1 Generate call number To determine if the system can

generate a call number in the

module of book information.

6.2 Save book information To determine if the created book

information will be accepted by

the system. And allow to add a

6.3 View list of book To determine if the system can

information view the list of book that been

6.4 Update book To determine if the system

information allows updating the book

7.0 Archive To determine if the system

can archive some book

from the list of book

8.0 Student information This module allows to add,

module save, clear, view the list of

student information and

update the information in

8.1 Add student information To determine if the system

allows adding the student

8.2 Save student information To determine if the form

can save the student

information in the database.

8.3 Import student To determine if the system

information can import the student

information from database.

8.4 View list student To determine if the system can

information show the list of student

information from a database.

8.5 Update student To determine if the form can

information update the student information

from the database.

8.6 Search student To determine if the system can

information search the student information

from the database.

9.0 Teacher Information This module can add, save, clear,

and view list of teacher

9.1 Add teacher To determine if the system

information allows adding the teacher

9.2 Save teacher To determine if the created

information teacher information will be

accepted in the system after

adding the information of teacher