Ba Dormitory Management System: Institute of Computer Studies Western Mindanao State University

BA DORMITORY MANAGEMENT SYSTEM
BY: CODE X
INSTITUTE OF COMPUTER STUDIES
WESTERN MINDANAO STATE UNIVERSITY
Table of Contents
Chapter I................................................................................................................................................................... 8
Description of the System ....................................................................................................................................... 8
Overview of the System ...................................................................................................................................... 9
The Project Site.................................................................................................................................................... 9
Background of the Client..................................................................................................................................... 9
Hierarchical Input Process Output (HIPO) ........................................................................................................ 10
Description of the Main Module and Sub Module........................................................................................... 11
Chapter II................................................................................................................................................................ 14
The Company ......................................................................................................................................................... 14
Company Description ........................................................................................................................................ 15
Company Name ................................................................................................................................................. 15
Vision ................................................................................................................................................................. 15
Mission............................................................................................................................................................... 15
Company Logo ................................................................................................................................................... 16
Objective ............................................................................................................................................................ 16
Organization Structure ...................................................................................................................................... 16
System Analyst and Design Team ..................................................................................................................... 17
Programming Team ........................................................................................................................................... 17
Testing Team ..................................................................................................................................................... 17
Archivist Team ................................................................................................................................................... 18
Training Team .................................................................................................................................................... 18
Roles and Responsibilities ................................................................................................................................. 19
Work Personality Type and Evaluation of Work Styles ................................................................................... 21
Personal Assessment......................................................................................................................................... 21
Individual Assessment....................................................................................................................................... 22
Group Policies .................................................................................................................................................... 23
Meeting Policies: ........................................................................................................................................... 23
1
BY: CODE X
Financial Policies: .......................................................................................................................................... 24

Penalty Policies:............................................................................................................................................. 24
Agreement Contract ...................................................................................................................................... 25
Chapter III............................................................................................................................................................... 26
Project Planning ..................................................................................................................................................... 26
3.a Work Breakdown Structure ........................................................................................................................ 27
Phase 1: The Company .................................................................................................................................. 27
Phase 2: The Client ........................................................................................................................................ 27
Phase 3: Interview ......................................................................................................................................... 27
Phase 4: Project Planning .............................................................................................................................. 27
Phase 5: Project Costing ................................................................................................................................ 28
Phase 6: Requirement Analysis..................................................................................................................... 28
Phase 7: System design ................................................................................................................................. 29
Phase 8: System Development ..................................................................................................................... 29
Phase 9: Testing Plan ..................................................................................................................................... 29
Phase 10: Training Plan ................................................................................................................................. 30
Phase 11: Finalization of Internal and External Documentation ................................................................. 31
Chapter IV .............................................................................................................................................................. 32
Project Schedule .................................................................................................................................................... 32
Work Breakdown with Time Estimate .............................................................................................................. 33
Activity Graph with Description........................................................................................................................ 43
Activity Graph with Milestone .......................................................................................................................... 71
Activity Graph with Slack Time ......................................................................................................................... 77
Gantt Chart ........................................................................................................................................................ 83
Chapter V ............................................................................................................................................................... 93
Project Costing ....................................................................................................................................................... 93
5.2 Project Estimation ....................................................................................................................................... 94
Effort Cost ...................................................................................................................................................... 94
Hardware Cost ............................................................................................................................................... 94
Documentation Cost...................................................................................................................................... 95
2
BY: CODE X
Overall Cost ................................................................................................................................................... 95

5.3 Basic Constructive Cost Model (COCOMO) ................................................................................................ 96
COCOMO Semi-detached Project Type ........................................................................................................ 97
Chapter VI .............................................................................................................................................................. 99
Requirement Engineering ...................................................................................................................................... 99
6.1 Purpose of the Project .............................................................................................................................. 100
6.1.a Background of the Project ................................................................................................................. 100
6.1.a.1 Goals of the Project ......................................................................................................................... 101
6.2 The Stakeholders ....................................................................................................................................... 101
6.2.a Client ................................................................................................................................................... 101
6.2.b Customer ............................................................................................................................................ 101
6.2.c Stakeholders ....................................................................................................................................... 102
6.2.d The Hands-on User of the Product .................................................................................................... 103
6.2.e Priorities Assigned to the Users ......................................................................................................... 104
6.2.f The User Participation ........................................................................................................................ 104
6.3 Mandated Constraints .............................................................................................................................. 104
6.3.a Solution Constraints ........................................................................................................................... 104
6.3.b Implementation Environment ........................................................................................................... 105
6.3.c Partner Application ............................................................................................................................ 105
6.3.d Commercial Off-Shelf Product ........................................................................................................... 105
6.3.e Anticipated Work Place Environment ............................................................................................... 105
6.3.f Schedule Constraints .......................................................................................................................... 105
6.4 Naming Conventions and Terminology .................................................................................................... 105
6.5 Relevant Facts and Assumption ................................................................................................................ 106
6.5.a Relevant Facts .................................................................................................................................... 106
6.5.b Assumption......................................................................................................................................... 106
6.6 The Scope of the Work .............................................................................................................................. 107
6.6.a The Current Situation ......................................................................................................................... 107
6.6.c Work Partitioning ............................................................................................................................... 108
6.7 Business Data and Data Model ................................................................................................................. 110
3
BY: CODE X
6.7.a Entity Relationship Diagram (ERD) .................................................................................................... 110

6.8 Scope of the Work ..................................................................................................................................... 111
6.8.a Product Boundary .............................................................................................................................. 111
6.9 Functional and Data Requirement............................................................................................................ 118
6.9.a Requirement Shell .............................................................................................................................. 118
6.9.c Non-Functional Requirement ............................................................................................................. 123
6.10 Look and Feel Requirement .................................................................................................................... 123
6.10.a Interface............................................................................................................................................ 123
6.11 Usability and Humanity Requirement .................................................................................................... 124
6.11.a Ease of Use Requirement ................................................................................................................. 124
6.11.b Learning Requirements .................................................................................................................... 124
6.11.c Understandability and Politeness Requirements ............................................................................ 124
6.12 Performance Requirements .................................................................................................................... 124
6.12.a Speed and Latency Requirements ................................................................................................... 124
6.12.b Precision or Accuracy Requirements ............................................................................................... 124
6.12.c Reliability and Availability Requirements ....................................................................................... 125
6.12.d Robustness of Fault-Tolerance Requirements ................................................................................ 125
6.12.e Capacity Requirements .................................................................................................................... 125
6.12.f Longevity Requirements ................................................................................................................... 125
6.13 Operational and Environmental Requirements ..................................................................................... 125
6.13.a Expected Physical Environment ....................................................................................................... 125
6.13.b Requirements for Interfacing with Adjacent .................................................................................. 126
6.14 Maintainability and Support Requirement ............................................................................................ 126
6.14.a Maintenance Requirements ............................................................................................................ 126
6.14.b Supportability Requirements .......................................................................................................... 126
6.14.c Adaptability Requirements .............................................................................................................. 126
6.15 Security Requirements ............................................................................................................................ 126
6.15.a Access Requirements ....................................................................................................................... 126
6.15.b Privacy Requirements ...................................................................................................................... 126
6.16 Cultural Requirements ............................................................................................................................ 127
6.16.a Cultural Requirements ..................................................................................................................... 127
4
BY: CODE X
6.17 Legal Requirements ................................................................................................................................. 127

6.17.a Compliance Requirements ............................................................................................................... 127
6.18 Open Issues.............................................................................................................................................. 127
6.19 New Problem ........................................................................................................................................... 127
6.20 Tasks ........................................................................................................................................................ 128
6.20.a Project Planning ................................................................................................................................... 128
6.20.b Planning of the Development Phases ................................................................................................. 128
6.21 Risks ......................................................................................................................................................... 129
6.21.a Costs .................................................................................................................................................. 129
6.22 User Documentation and Training Requirements ................................................................................. 129
Chapter VII ........................................................................................................................................................... 130
System Design ..................................................................................................................................................... 130
7.0 Hierarchical Input Process Output (HIPO) .................................................................................................... 131
7.1 Context Flow Diagram ................................................................................................................................... 134
7.2 Data Flow Diagram ........................................................................................................................................ 135
7.2.a. Level 0 .................................................................................................................................................... 135
7.2.b Level 1 ..................................................................................................................................................... 136
7.3 Hierarchical Input Process Output (HIPO) .................................................................................................... 137
7.4 User Interface with Description .................................................................................................................... 138
7. 4. 1. Log- In Screen.................................................................................................................................. 138
7. 4. 2. Dashboard........................................................................................................................................ 138
7. 4. 3. Rental Record .................................................................................................................................. 139
7. 4. 4. New rental ....................................................................................................................................... 139
7. 4. 5. New border ...................................................................................................................................... 140
7. 4. 6. Search for borders ........................................................................................................................... 140
7. 4. 7. Browse room ................................................................................................................................... 141
7. 4. 8. Add on.............................................................................................................................................. 141
7. 4. 9. Border record .................................................................................................................................. 142
7. 4. 10. Billing record .................................................................................................................................. 142
7. 4. 11. Payment and Collection ................................................................................................................ 143
5
BY: CODE X
7. 4. 12. New payment and Collection ........................................................................................................ 143

7. 4. 13. Search for Rental ........................................................................................................................... 144
7. 4. 14. Settings .......................................................................................................................................... 144
7. 4. 15. Account .......................................................................................................................................... 145
7. 4. 16. Rooms ............................................................................................................................................ 145
7. 4. 17. Add Rooms..................................................................................................................................... 146
Chapter VIII .......................................................................................................................................................... 147
Testing Plan ......................................................................................................................................................... 147
8.1 Introduction ................................................................................................................................................... 148
8.1.a Objectives ........................................................................................................................................... 148
8.1.b Scope of the Test ................................................................................................................................ 148
8.1.c Target Test Items ................................................................................................................................ 148
8.2 Testing Methodology .................................................................................................................................... 149
8.3 Testing Process .............................................................................................................................................. 151
8.3.a Test Schedules .................................................................................................................................... 151
8.4 Resource and Responsibilities ...................................................................................................................... 152
8.4.a Testing Team ...................................................................................................................................... 152
8.4.b Test Environment ............................................................................................................................... 152
8.5 Deliverables ................................................................................................................................................... 153
8.6 Risk Issues ...................................................................................................................................................... 153
8.7 Dependencies ................................................................................................................................................ 154
8.8.1 Alpha Test Result .................................................................................................................................... 155
TEST DATA ....................................................................................................................................................... 155
8.8.2 Developer’s Test Cases ........................................................................................................................... 157
8.8.3 Beta Test Results .................................................................................................................................... 178
Chapter IX............................................................................................................................................................. 180
Training Phase ...................................................................................................................................................... 180
9.1 Description .................................................................................................................................................... 181
9.2 Training Objectives ........................................................................................................................................ 181
9.3 Scope of the Training .................................................................................................................................... 181
6
BY: CODE X
9.4 Target Trainees .............................................................................................................................................. 181

9.5 Training Team ................................................................................................................................................ 182
9.6 Training Policies............................................................................................................................................. 182
9.7 Training Reference ........................................................................................................................................ 182
9.8 Training Approach ......................................................................................................................................... 182
9.8.1 Identification of the Training Needs .................................................................................................. 182
9.8.2 Training Requirements ....................................................................................................................... 183
9.8.3 Training Venue ................................................................................................................................... 183
9.8.4 Training Schedule ............................................................................................................................... 183
9.8.5 Steps in Conducting Training ............................................................................................................. 183
9.9 Roles and Responsibilities............................................................................................................................. 183
9.10 Training Curriculum ..................................................................................................................................... 184
9.11 Evaluation .................................................................................................................................................... 185
9.11.1 Module of Evaluation ....................................................................................................................... 185
9.11.2 Evaluation Summary ........................................................................................................................ 186
Appendices........................................................................................................................................................... 187
Appendix A – Training Evaluation Forms ....................................................................................................... 188
Appendix B- Certificates .................................................................................................................................. 190
Appendix C- Test Cases Results ....................................................................................................................... 192
7
BY: CODE X
Chapter I
Description of the System
8
BY: CODE X
Overview of the System
The BA Dormitory has been a one stop dormitory for the student and other people who are
looking for rooms. It has become well-known for their friendly services which made the dormitory
currently serving the student and other people around 3 years.
Even though the dormitory has always been a one stop dormitory, the officer in charge or the
landlady serves their borders manually and keeps the records of their border through excel. To ease
the burden of possibly loosing tracks of the records, the Code X has chosen to develop BA Dormitory
Management System that would effectively manage and monitor the transaction.
The Project Site
The BA Dormitory Management System was developed to a desktop application for BA

Dormitory that offers a better and safe monitoring of its records as well as the information of its
borders, rooms and fees.
The main objective of the BA Dormitory Management System is to help organize the transaction
services that the dormitory offers. It will help the officer-in-charge to keep everything in place ad to
avoid losing file reports. A safe system for storing files and a better computer environment.
Background of the Client

The client of Code X for this project is the BA Dormitory ad the representative for this project is:
Ms. Melanie L. Ledesma
 The Officer-In-Charge / Landlady of the BA Dormitory

 A graduate of Practical Nursing I the year of 2013
9
BY: CODE X
Hierarchical Input Process Output (HIPO)
10
BY: CODE X
Description of the Main Module and Sub Module
Login The system allows the user to input the username and password,
If the username and password match with the user stored in database
Username then the user now can access the system.
Password
Boarder
This module, it is all about the boarders.
New Border In the sub-module view, it shows all the boarder’s information.
View
Guardian
Rent
In the rent module, this where the main transaction of the system.
New Rental In the sub module new transaction, the system asks for the boarders
infomation when it’s their first time renting.
New Border
Browse
Room
Add Ons
Save
11
BY: CODE X
Cancel
Billings This module allows the user to show and

print the bills of the boarders.
View Billings
Print Billings
Collection Where the collection of payments can

be viewed and new payments can be
done. Only the admin and cashier can
New access this module.
Payment
Settings . This module contains the settings of the

system (e.g. penalties and rental
settings)
Save
Cancel
Account
This module is where the admin add another
user to the system. And only the admin has
New the access to this. module.
Account
12
BY: CODE X
.
Profile User account settings.
Save
Cancel
Logout
The user exits the system.
13
BY: CODE X
Chapter II
The Company
14
BY: CODE X
Company Description
Code X is a software development company designed to offer good system related services that
suit its client’s needs. It is a new company working by a group of Computer Science people from
Western Mindanao State University.
Company Name
Code X is derived from two words “Code” and “X”. They were combined together to create a
company name that reflect the unity of the members to create a system that meets the need of our
clients. “X” was derived from the word of “Xaern” meaning to enjoy something so much you begin to
hate how much you like it. The “Code” is the word that symbolizes what our group aims and does for
the people. We shall be able to create a high-standard and user-friendly system software and provide
a good service to our clients.
Vision
The Code X Inc. shall be the number one choice for creating software system for the people. We
shall be able to create a high-standard and user-friendly system software and provide a good service to
our clients.
Mission
Code X Inc. aim to be one of the good companies that provide the best services that can satisfy
the needs of the client.
 Enhance individual’s knowledge and capabilities in the field of software development.

 Strive for operational and service excellence through a relentless focus on clients.
15
BY: CODE X
Company Logo
Objective
 To build a good organization or unification of all the member in the group

 To improve self-performance in doing the task that given to each member
Organization Structure
16
BY: CODE X
System Analyst and Design Team
Programming Team
Testing Team
17
BY: CODE X
Archivist Team
Training Team
18
BY: CODE X
Roles and Responsibilities
Chief Programmer: Mangking, Daisa A.
 The programmer should always test his/her code before going to the tester.
 Responsibility of logging errors, message on errors etc.
 Responsibility of sometimes recommending the right solution for the client to solve a problem.
 Responsibility to protect the privacy of the client’s data.
 Responsibility to update his/her skill via self-learning most times.

 Update the management about the data, status and problems if any that arises.
 Not but least programming and making your code maintainable.
System Analyst: Sali, Myrhana S.
 Defines application problem by conferring with clients; evaluating procedures and

processes.
 Develops solution by preparing and evaluating alternative workflow solutions.
 Controls solution by establishing specifications; coordinating production with programmers.
 Validates results by testing programs.
 Ensures operation by training client personnel; providing support.
 Provides reference by writing documentation.
 Updates job knowledge by participating in educational opportunities; reading professional
publications; maintaining personal networks; participating in professional organizations.
 Accomplishes information systems and organization mission by completing related results
as needed.
Testing Head: Salvador, Richa Rose
 They often set up the test environments or assist system administration and network
management staff in doing so.
 As test execution begins, the number of testers often increases, starting with the work
required to implement tests in the test environment.
 Testers execute and log the tests, evaluate the results and document problems found.
19
BY: CODE X
 They monitor the testing and the test environment, often using tools for this task, and often
gather performance metrics.
 Throughout the software testing life cycle, they review each other’s work, including test
specifications, defect reports and test results.
Project Manager: Jala, Norrama J.
 The person who has the overall responsibility for the successful initiation, planning, design,
execution, monitoring, controlling and closure of a project.
 Must have a combination of skills including an ability to ask penetrating question, detect
unstated assumption and resolve conflicts, as well as more general management skills.
 Can lessen risk significantly, often by adhering a policy of open communication, ensuring
every significant participant has an opportunity to express opinions and concerns.
 Is one who responsible for making decisions both large and small, in such a way that risk is
controlled uncertainly minimized. Every decision taken by the project manager should be
taken in such way that it directly benefits the project.
Archivist: Eyas, Jefford D.
 Promote access to records to the fullest extent consistent with the public interest but should
observe any legal or prudent restrictions on the use of records.
 Respond promptly and courteously to research request – not discussing the work of one
researcher with another except where a clear duplication of effort is apparent.
 Must not profit from any commercial exploitation of the records in custody, nor without
from others any information gained as a result of official duties.
Training Head: Hamsiri, Al-jadeed S.
 Monitor instructor performance to verify training is conducted as outlined in approved

training materials and in a manner that motivates personnel to learn.
 Develop training program and trainee status reports for line managers, and assist the line
manager in identifying and resolving human performance issues.
20
BY: CODE X
 Develop training policies that establish guidelines for all training functions.
 Verify that the training staff has obtained and is maintaining their technical and instructional
knowledge and skills.

Work Personality Type and Evaluation of Work Styles
The team defined a work style to be able describe each member’s character and Approaches to the activity.
 Intuitive introvert – is a character trait inquires other people’s opinions or ideas; he still considers
his own feelings.
 Intuitive extrovert – is a character trait that articulates tasks to other people and also shares his idea
as well as acknowledge feelings.
 Rational introvert – is a character trait that expresses thoughts regarding their ideas unto other
people.
 Rational extrovert – is a character trait that expresses their ideas and opinions to the team.
Personal Assessment
Name Position Individual assessment Group’s assessment
Norrama J. Jala Project Manager Rational extrovert Rational extrovert
Myrhana N. Sali System Analyst Rational extrovert Rational extrovert
Daisa A. Mangking Chief Programmer Rational extrovert Rational extrovert
21
BY: CODE X
Richa Rose Salvador Head Testing Engineer Rational extrovert Rational extrovert
Jefford D. Eyas Head Archivist Intuitive introvert Intuitive introvert
Al-jadeed S. Hamsiri Head Training Rational extrovert Rational extrovert

facilitator
Individual Assessment
Name Position Individual Assessment
I assessed myself as a rational

Norrama J. Jala Project Manager extrovert because I like to
express my ideas to the team
and also I can easily
communicate to my team.
I assessed myself as rational

Myrhana N. Sali System Analyst extrovert because I like to
express my ideas and opinions
to my team.
22
BY: CODE X

Daisa A. Mangking Chief Programmer extrovert because I do not hold
back when I want to voice out
my opinion and ideas to the
team.

Richa Rose Salvador Head testing engineer extrovert because I like to
express my ideas and thoughts
to the team that I think that
maybe able to help and
contribute to team’s welfare.
Chief archivist I assessed myself as intuitive

Jefford D. Eyas introvert because I prefer to
inquire other. Feelings and
opinions so that I’ll know what
to consider also my ideas.
Head training facilitator I assessed myself as a rational

Al-jadeed S. Hamsiri extrovert I prepare sharing my
thoughts and ideas to my team.
Group Policies
Meeting Policies:
 Everyone is required to attend every regular meeting especially during Software

Engineering class.
 No using cellphone during meetings except for emergency purposes only.
 No excuses on submitting any requirements during deadlines.
 Everyone should contribute amount of money is said so.
 Attendance is must
 Personal issues and problems must be put aside. All attention should focus on work
system.
 If there is a conflict between members it must be settled as soon as possible to avoid
any delay to the work progress.
23
BY: CODE X
 No to social media if there is a meeting

 Respect your members.
 Every member must give out their opinions.
 Avoid interruptions while a member is talking, they should listen.
 Avoid unnecessary topic
Financial Policies:
 Collection of payments is used for the expenses of the group for the project (outgoing
activities, documents and sleepovers).
 Assigned treasurer of the group must collect P15.00 once a week.
 A member who cannot pay on every meeting is being listed and expected to pay as soon
as possible.
 Assigned treasurer must remind members about the payments for the fund.
Penalty Policies:
 A late member will have a fine of P30.00.
 One absent will have a fine of P50.00.
 Late submission of tasks will receive a P20.00 fine per task.
 Not following the rules can be also caused of expulsion from the group.
 5 consecutive absent will expulsions of the team.
24
BY: CODE X
Agreement Contract
We the members of this group have read and hereby agreed to the said policies of the team.
Signed this 27th day of November, 2017.
Jefford D. Eyas Daisa A. Mangking Al-jadeed S. Hamsiri

Chief Archivist Chief Programmer Head Training Facilitator
Norrama J. Jala Myrhana N. Sali Richa rose Salvador

Project Manager Chief System Analyst Head Testing Engineer
Witnessed by:
Engr. Marvic Lines

Instructor
25
BY: CODE X
Chapter III
Project Planning
26
BY: CODE X
3.a Work Breakdown Structure

Phase 1: The Company
1.1 Stablish company
1.2 Create Company name
1.3 Create Company Description
1.4 Assign Roles and responsibility
1.5 Create Company logo
1.6 Create Mission and Vision
1.7 Set Goals and Objective
1.8 Set Policies and Penalties
1.9 Create Company Organizational Chart
1.10 Work style and schedule
Phase 2: The Client

2.1 Background of the Client
2.2 System Background
2.3 Hierarchy chart
Phase 3: Interview
3.1 Make an Interview letter
3.2 Prepare list of Questionnaire
3.3 Appointment for Interview
3.4 Actual Interview
3.5 Follow up Interview
3.6 Transcribe Interview
3.7 Finalize Documentation of Interview
Phase 4: Project Planning

4.1 Create Project Plan
4.2 Create Activity Graph
4.3 Lists of Activities with Duration
4.4 Create Gantt Chart
4.4.1 Activity Graph with Duration
4.4.2 Activity Graph with Activities
27
BY: CODE X
Phase 5: Project Costing

5.1 Effort Costing
5.2 Document Costing
5.3 Hardware Costing
5.4 Software Costing
5.5 Compute Estimated Economic Feasibility
5.6 Compute Actual Economic Feasibility
5.7 Final Documentation
Phase 6: Requirement Analysis

6.1 Conduct Requirement Analysis
6.2 Finalize Requirement Analysis
6.3 Functional Requirement
6.4 Non-Functional Requirement
6.4.1 Look and Feel Requirement
6.4.2 Usability Requirement
6.4.3 Performance Requirement
6.4.4 Operational Requirement
6.4.5 Maintainability and Portability Requirements
6.4.6 Security Requirement
6.4.7 Cultural and Political Requirement
6.4.8 Legal requirement
6.5 Volere requirements
6.5.1 Purpose of the Project
6.5.2 Goals of the Project
6.5.3 Client, Customer and Stakeholder
6.5.4 User of the Project
6.5.5 Mandated Constraints
6.5.6 Naming Convention and Definitions
6.5.7 Relevant Facts and Assumption
6.5.8 Scope of the work
6.5.9 Scope of the Project
6.6 Project Issues

6.6.1 Open Issues
28
BY: CODE X
6.6.2 Off the shelf Solutions

6.6.3 Task
6.6.4 Cut over
6.6.5 Risk and cost
6.6.6 User Documentation and training
6.6.7 Ideas and Solution
6.6.8 Finalize Requirement Specifications
Phase 7: System design

7.1 Make an Entity Relationship Diagram (ERD)
7.2 Construct Data Flow Diagram (DFD)
7.3 HIPO Diagram
7.4 Create and Design System Module
7.5 Finalize System Module
Phase 8: System Development

8.1 Develop Source Code for System Module
8.1.1 Implement coding for Home Module
8.1.2 Implement coding for Log in Module
8.1.3 Implement coding for User Accounts
8.1.4 Implement coding for Border Profile Accounts
8.1.5 Implement coding for Rooms Profile
8.1.6 Implement coding for Records Profile
8.1.7 Implement coding for Collection Profile
8.1.8 Implement coding for Admin
8.1.9 Implement coding for About Us
8.2 Initial Documentation of Source Code
Phase 9: Testing Plan
9.1 Develop Test Plan

9.1.1 Develop Unit test
9.1.2 Develop Integration Test Plan
9.1.3 Develop System Test Plan
9.1.4 Develop Performance Test Plan
29
BY: CODE X
9.1.5 Develop User Acceptance Test Plan

9.2 Perform Unit Testing
9.2.1 Perform Unit Testing for User Account
9.2.2 Perform Unit Testing for Border Profile
9.2.3 Perform Unit Testing for Rooms Profile
9.2.4 Perform Unit Testing for Records Profile
9.2.5 Perform Unit Testing for Collection Profile
9.2.6 Perform Identifying System Errors
9.3 Perform Integration Test Plan

9.3.1 Perform Entire Integration Testing
9.3.2 Debug Errors
9.3.3 Document Integration Testing
9.4 Perform System Test Plan
9.4.1 Perform Functional Test
9.4.2 Conduct Performance and Portability test
9.4.3 Perform Retest of the Final System
9.4.4 Document System Testing
9.5 Perform User Acceptance Test Plan
9.5.1 Perform Alpha Test
9.5.2 Debug Errors
9.5.3 Perform Retest of Final System
9.5.4 Perform the Beta Test
9.5.5 Debug errors
9.5.6 Perform Retest of the Final System
9.5.7 Document User Acceptance Test Plan
9.6 Finalize over-all Testing Document
Phase 10: Training Plan

10.1 Create Training Plan
10.2 Create User’s Manual
10.3 Implement User’s Training
10.3.1 Conduct User’s Training
10.3.2 Evaluate User’s Training
10.3.3 Document User’s Training
30
BY: CODE X
10.4 Introduce the System and User’s Manual
Phase 11: Finalization of Internal and External Documentation

11.1 Finalize Source Code Document
11.2 Finalize Over-all System Document
11.3 Final Defense
31
BY: CODE X
Chapter IV
Project Schedule
32
BY: CODE X
Work Breakdown with Time Estimate
Estimated
Activity Person-in-charge Duration Start Finish
1.1 Stablish company Codex 1 hour Sat 11/25/17 Sat 11/25/17
1.2 Create Company Codex 1 hour Sat 11/25/17 Sat 11/25/17

name

Description
1.4 Assign Roles and Codex 1 hour Sat 11/25/17 Sat 11/25/17
responsibility

logo
1.6 Create Mission and Codex 1 hour Sat 11/25/17 Sat 11/25/17
Vision
1.7 Set Goals and Codex 1 hour Sat 11/25/17 Sat 11/25/17
Objective
1.8 Set Policies and Codex 1 hour Sat 11/25/17 Sat 11/25/17
Penalties
1.9 Create Company Salvador 1 hour Sat 11/25/17 Sat 11/25/17

Organizational Chart
1.10 Work style and Jala 1 hour Sat 11/25/17 Sat 11/25/17
schedule
Phase 2: The Client
2.1 Background of the Hamsiri 1 hour Mon 11/27/17 Mon

Client 11/27/17
33
BY: CODE X
2.2 System Background Codex 2 hours Mon 11/27/17 Mon

11/27/17
2.3 Hierarchy chart Sali 1 days Thu 11/30/17 Fri 12/01/17
Phase 3: Interview
3.1 Make an Interview Jala 1 hour Mon 11/27/17 Mon

letter 11/27/17
3.2 Prepare list of Jala 1 hour Mon 11/27/17 Mon

Questionnaire 11/27/17
3.3 Appointment for Mangking 1 hour Mon 11/27/17 Mon

Interview 11/27/17
3.4 Actual Interview Mangking 2 hours Tue 11/28/17 Tue

11/28/17
3.5 Follow up Interview Mangking 1 hour Mon 12/04/17 Mon

12/04/17
3.6 Transcribe Interview Hamsiri 1 hour Mon 12/04/17 Mon

12/04/17
3.7 Finalize Hamsiri 2 hours Mon 12/04/17 Mon

Documentation of 12/04/17
Interview
4.1 Create Project Plan Codex 2 hours Mon 12/04/17 Mon

12/04/17
4.2 Create Activity Jala 1 day Tue 12/05/17 Wed

Graph 12/06/17
4.3 Lists of Activities Jala 1 day Tue 12/05/17 Wed

with Duration 12/06/17
4.4 Create Gantt Chart Jala 2 days Tue 12/05/17 Thu

12/07/17
34
BY: CODE X
4.4.1 Activity Graph Jala 1 days Tue 12/05/17 Wed

with Duration 12/06/17
4.4.2 Activity Graph Jala 1 days Tue 12/05/17 Wed

with Activities 12/06/17
5.1 Effort Costing Eyas 2 days Fri 12/08/17 Sun

12/10/17
5.2 Document Costing Eyas 2 days Fri 12/08/17 Sun

12/10/17
5.3 Hardware Costing Eyas 2 days Fri 12/08/17 Sun

12/10/17
5.4 Software Costing Eyas 2 days Fri 12/08/17 Sun

12/10/17
5.5 Compute Estimated Eyas 2 days Fri 12/08/17 Sun

Economic Feasibility 12/10/17
5.6 Compute Actual Eyas 2 days Fri 12/08/17 Sun

Economic Feasibility 12/10/17
5.7 Final Eyas 2 days Fri 12/08/17 Sun

Documentation 12/10/17
Phase 6: Requirement Analysis
6.1 Conduct Sali 3 days Sat 12/16/17 Tue

Requirement Analysis 12/19/17
6.2 Finalize Sali 3 days Sat 12/16/17 Tue

Requirement Analysis 12/19/17
6.3 Functional Sali 3 days Sat 12/16/17 Tue

Requirement 12/19/17
6.4 Non-Functional Sali 3 days Sat 12/16/17 Tue

35
BY: CODE X
6.4.1 Look and Feel Sali 3 days Sat 12/16/17 Tue

6.4.2 Usability Sali 3 days Sat 12/16/17 Tue

6.4.3 Performance Sali 3 days Sat 12/16/17 Tue

6.4.4 Operational Sali 3 days Sat 12/16/17 Tue

6.4.5 Maintainability Sali 3 days Sat 12/16/17 Tue

and Portability 12/19/17
Requirements
6.4.6 Security Sali 3 days Sat 12/16/17 Tue

6.4.7 Cultural and Sali 3 days Sat 12/16/17 Tue

Political Requirement 12/19/17
6.4.8 Legal requirement Sali 3 days Sat 12/16/17 Tue

12/19/17
6.5 Volere requirements Sali 5 days Tue 12/19/17 Sun

12/24/17
6.5.1 Purpose of the Hamsiri 1 hour Tue 12/19/17 Tue

Project 12/19/17
6.5.2 Goals of the Hamsiri 1 hour Tue 12/19/17 Tue

Project 12/19/17
6.5.3 Client, Customer Jala 1 hour Tue 12/19/17 Tue

and Stakeholder 12/19/17
6.5.4 User of the Project 1 hour Tue 12/19/17 Tue

12/19/17
6.5.5 Mandated Salvador 1 hour Tue 12/19/17 Tue

Constraints 12/19/17
36
BY: CODE X
6.5.6 Naming Jala 1 hour Wed 12/20/17 Wed

Convention and 12/20/17
Definitions
6.5.7 Relevant Facts and Jala 1 hour Wed 12/20/17 Wed

Assumption 12/20/17
6.5.8 Scope of the work Sali 2 days Wed 12/20/17 Fri 12/22/17
6.5.9 Scope of the Sali 2 days Wed 12/20/17 Fri 12/22/17

Project
6.6 Project Issues Sali 1 day Wed 12/20/17 Thu

12/21/17
6.6.1 Open Issues Sali 1 day Wed 12/20/17 Thu

12/21/17
6.6.2 Off the shelf Sali 1 day Wed 12/20/17 Thu

Solutions 12/21/17
6.6.3 Task Hamsiri 2 days Wed 12/20/17 Fri 12/22/17
6.6.4 Cut over Sali 2 days Wed 12/20/17 Fri 12/22/17
6.6.5 Risk and cost Sali 1 day Wed 12/20/17 Fri 12/21/17
6.6.6 User Hamsiri 5 days Fri 12/22/17 Wed

Documentation and 12/27/17
training
6.6.7 Ideas and Solution Hamsiri 2 days Wed 12/20/17 Fri 12/22/17
6.6.8 Finalize Sali 5 days Fri 12/22/17 Wed

Specifications
7.1 Make an Entity Sali 6 days Fri 12/22/17 Thu

Relationship Diagram 12/28/17
(ERD)
37
BY: CODE X
7.2 Construct Data Flow Sali 6 days Fri 12/22/17 Thu

Diagram (DFD) 12/28/17
7.3 HIPO Diagram Sali 2 days Fri 12/22/17 Sun

12/24/17
7.4 Create and Design Mangking, Sali 1 days Sun 12/24/17 Mon
System Module 12/25/17
7.5 Finalize System Sali 1 days Sun 12/24/17 Mon

Module 12/25/17
Phase 8: System Development
8.1 Develop Source Mangking 60 days Sat 01/20/18 Mon

Code for System 03/12/18
Module
8.1.1 Implement coding Mangking 2 days Sat 01/20/18 Mon

for Home Module 01/22/18
8.1.2 Implement coding Mangking 4 days Sat 01/20/18 Wed

for Log in Module 01/24/18
8.1.3 Implement coding Mangking 4 days Wed 01/24/18 Sun

for User Accounts 01/28/18
8.1.4 Implement coding Mangking 4 days Wed 01/24/18 Sun

for Border Profile 01/28/18
Accounts
8.1.5 Implement coding Mangking 3 days Wed 01/24/18 Sat 01/27/18

for Rooms Profile
8.1.6 Implement coding Mangking 5 days Wed 01/24/18 Mon

for Records Profile 01/29/18
8.1.7 Implement coding Mangking 4 days Mon 01/29/18 Fri 02/03/18

for Collection Profile
8.1.8 Implement coding Mangking 4 days Fri 02/03/18 Wed

for Admin 02/07/18
38
BY: CODE X
8.1.9 Implement coding Codex 1 days Fri 02/03/18 Sat 02/04/18

for About Us
8.2 Initial Eyas 3 days Fri 02/03/18 Sat 02/04/18

Documentation of
Source Code
9.1 Develop Test Plan Salvador 3 hours Mon 02/07/18 Mon

02/07/18
9.1.1 Develop Unit test Salvador 3 hours Mon 02/07/18 Mon

02/07/18
9.1.2 Develop Salvador 1 days Wed 02/09/18 Thu

Integration Test Plan 02/10/18
9.1.3 Develop System Salvador 1 days Thu 02/10/18 Fri 02/11/18

Test Plan
9.1.4 Develop Salvador 1 days Fri 02/11/18 Sat 02/12/18

Performance Test Plan
9.1.5 Develop User Salvador 1 days Mon 02/13/18 Tue

Acceptance Test Plan 02/14/18
9.2 Perform Unit Testing Salvador 3 hours Tue 02/14/18 Tue

02/14/18
9.2.1 Perform Unit Salvador 3 hours Tue 02/14/18 Tue

Testing for User 02/14/18
Account
9.2.2 Perform Unit Salvador 3 hours Tue 02/14/18 Tue

Testing for Border 02/14/18
Profile
9.2.3 Perform Unit Salvador 3 hours Wed 02/15/18 Wed

Testing for Rooms 02/15/18
Profile
39
BY: CODE X

Testing for Records 02/15/18
Profile

Testing for Collection 02/15/18
Profile
9.2.6 Perform Salvador 3 hours Wed 02/15/18 Wed

Identifying System 02/15/18
Errors
9.3 Perform Integration Salvador 2 days Fri 02/17/18 Sun

Test Plan 02/19/18
9.3.1 Perform Entire Salvador 2 days Mon 02/20/18 Wed

Integration Testing 02/22/18
9.3.2 Debug Errors Salvador 3 days Wed 02/21/18 Sat 02/24/18
9.3.3 Document Salvador 2 days Wed 02/21/18 Fri 02/23/18

Integration Testing
9.4 Perform System Test Salvador 2 days Wed 02/21/18 Fri 02/23/18
Plan
9.4.1 Perform Salvador 1 days Wed 02/21/18 Thu

Functional Test 02/22/18
9.4.2 Salvador 2 days Thu 02/22/18 Fri 02/23/18

Conduct Performance
and Portability test
9.4.3 Perform Retest of Salvador 2 days Sat 02/24/18 Mon

the Final System 02/26/18
9.4.4 Document System Salvador 2 days Sat 02/24/18 Mon

Testing 02/26/18
9.5 Perform User Salvador 2 days Sat 02/24/18 Mon

40
BY: CODE X
9.5.1 Perform Alpha Salvador 1 days Mon 02/26/18 Tue

Test 02/27/18
9.5.2 Debug Errors Salvador 3 days Mon 02/26/18 Thu

03/01/18
9.5.3 Perform Retest of Salvador 2 days Mon 02/26/18 Wed

Final System 02/28/18
9.5.4 Perform the Beta Salvador 3 days Mon 02/26/18 Thu

Test 03/01/18
9.5.5 Debug errors Mangking 5 days Mon 02/26/18 Sun

03/04/18
9.5.6 Perform Retest of Salvador 1 days Sun 03/04/18 Mon

the Final System 03/05/18
9.5.7 Document User Salvador 1 days Sun 03/04/18 Mon

9.6 Finalize over-all Salvador 3 days Sun 03/04/18 Wed

Testing Document 03/07/18
10.1 Create Training Hamsiri 1 days Sun 03/04/18 Mon

Plan 03/05/18
10.2 Create User’s Hamsiri 1 days Sun 03/04/18 Mon

Manual 03/05/18
10.3 Implement User’s Hamsiri 1 days Sun 03/04/18 Mon

Training 03/05/18
10.3.1 Conduct User’s Hamsiri 1 days Sun 03/04/18 Mon

Training 03/05/18
10.3.2 Evaluate User’s Hamsiri 1 days Sun 03/04/18 Mon

Training 03/05/18
10.3.3 Document User’s Hamsiri 1 days Sun 03/04/18 Mon

Training 03/05/18
41
BY: CODE X
10.4 Introduce the Hamsiri 1 days Sun 03/04/18 Mon

System and User’s 03/05/18
Manual
Phase 11: Finalization of Internal and External Documentation
11.1 Finalize Source Eyas 4 days Sun 03/04/18 Thu

Code Document 03/08/18
11.2 Finalize Over-all Eyas 4 days Sun 03/04/18 Thu

System Document 03/08/18
11.3 Final Defense Codex 5 days Mon 03/26/18 Sat 03/31/18
42
BY: CODE X
Activity Graph with Description
START
1.1
Create Company
Logo
Create Company Name
1.4 1.5
1.2 1.3
Create Company Assign Roles and

Description Responsibilities
1.6 1.7
Set Goals and Set Goals and 1.9

1.8 Objective Objective
Create Company
Set Policies and Organizational Chart
Penalties
43
BY: CODE X
A
Make an Interview
letter
1.10 2.1 2.2 2.3 3.1
Work style and Background of the System Background Hierarchy chart

schedule Client
3.6 3.5 3.4 3.2

3.3
Transcribe Follow up Actual Interview Appointment for Prepare list of

Interview Interview Interview Questionnaire
3.7 4.1 4.2 4.3 4.4
Finalize Create Gantt

Create Project Plan Create Activity Lists of Activities Chart
Documentation
Graph with Duration
of Interview
4.4.1
4.4.2
Activity Graph with
Duration
B Activity Graph with
Activities
44
BY: CODE X
B
Compute Estimated
Economic Feasibility
5.1 5.2 5.3 5.4 5.5
Effort Costing Document Costing Hardware Costing Software Costing
6.3 6.2 6.1 5.6

5.7
Functional Conduct Final Documentation Compute Actual

Finalize Requirement
Requirement Requirement Analysis Economic Feasibility
Analysis
6.4 6.4.1 6.4.2 6.4.3 6.4.4
Non-Functional Operational
Look and Feel Usability Performance
Requirement Requirement
Requirement Requirement Requirement
6.4.5
6.4.6
Maintainability and
Portability
C Security Requirements
Requirement
45
BY: CODE X
6.4.7 6.4.1 6.5 Purpose of the Goals of the

Project Project
Cultural and
Political Legal requirement Volere requirements 6.5.1 6.5.2
Requirement
6.5.4 6.5.3
6.5.5
User of the Client, Customer and
6.5.6 Project Stakeholder
Mandated
Naming Convention Constraints
6.5.7
and Definitions
Relevant Facts
and Assumption
6.5.8 6.5.9
Scope of the work Scope of the

Project D
46
BY: CODE X
6.6 6.6.1 6.6.2

Task
Project Issues Open Issues Off the shelf 6.6.3

Solutions
6.6.4
6.6.5
Cut over
6.6.6 Risk and cost
User
Documentation
and training
6.6.7 6.6.8
Ideas and Solution Finalize Requirement

Specifications E
47
BY: CODE X
7.1
Make an Entity HIPO Diagram

7.2
Relationship
Diagram (ERD)
Construct Data Flow 7.3
Diagram (DFD)
7.4
Create and Design

System Module
7.5
Finalize System
Module
F
48
BY: CODE X
8.1 8.1.1 8.1.2 Implement coding

for User Accounts
Develop Source
Implement coding Implement coding 8.1.3
Code for
for Home Module for Log in Module
System Module
8.1.4
8.1.5
Implement coding Implement coding for
for Border Profile About Us
8.1.6 Implement coding
for Rooms Profile Accounts
Implement
8.1.9
coding for
Records Profile
8.1.7 8.1.8
Implement coding Implement coding for 8.2

for Collection Profile Admin
Initial
Documentation of
G Source Code
49
BY: CODE X
9.1
Develop
Develop Test Plan 9.1.1 Integration Test
Plan
.1
9.1.2
Develop Unit test
9.1.3
Develop Develop System Test

Plan 9.1.4
9.1.5
H
Develop User
Acceptance Test Plan
50
BY: CODE X
9.2
Perform Unit Testing
for User Account
Perform Unit
Testing
9.2.1
9.2.2
Perform Identifying
System Errors
9.2.3 Perform Unit Testing
for Border Profile
Perform Unit
9.2.6
Testing for
Rooms Profile
9.2.4 9.2.5
Perform Unit Perform Unit

Testing for Testing for I
Records Profile Collection Profile
51
BY: CODE X
9.3 9.3.1
Perform Entire
Perform
Integration
Integration Test
Testing
Plan
9.3.2
Document
Debug Errors Integration Testing
9.3.3
52
BY: CODE X
9.4
Conduct
Perform System 9.4.1 Performance and
Test Plan Portability test
Perform Functional 9.4.2

Test
9.4.3
Perform Retest of the

Final System
9.4.4
Document System
Testing
K
53
BY: CODE X
9.5
Perform Alpha Test
Perform User
Acceptance
Test Plan
9.5.1
9.5.2

Debug Errors Final System
9.5.3
Document
Perform Retest of 9.5.6
User
Final System
Acceptance
Test Plan
9.5.4 9.5.5
9.5.7
Perform the Beta
Debug errors
Test
9.6
Finalize over-all
L Testing Document
54
BY: CODE X
10.1
Implement User’s
Create Training 10.2 Training
Plan
Create User’s 10.3

Manual Introduce the System
and User’s Manual
10.3.1 10.4
10.3.1
Conduct User’s
Training
10.3.1
Evaluate User’s
Training
Document User’s
Training M
55
BY: CODE X
11.1
Finalize Source Code

Document
11.2
Finalize Over-all
System Document
Final Defense
11.3
56
BY: CODE X
Activity Graph with Duration
START
1.1
Create Company
1 1
Logo
Create Company Name 1
1
1.4 1.5
1.2 1.3
Create Company Assign Roles and

1 1 Responsibilities
Description
1
1.6 1.7 1
Set Goals and Set Goals and 1.9

1.8 Objective Objective
Create Company
Set Policies and Organizational Chart
Penalties
57
BY: CODE X
A
Make an Interview
1
letter
1.10 2.1 2.2 2.3 3.1

1 2 1 1
Work style and Background of the System Background Hierarchy chart 1
schedule Client
3.6 3.5 3.4 3.2

3.3
1 2 1 1
Transcribe 1 Prepare list of
Follow up Actual Interview Appointment for
Interview Interview Interview Questionnaire
3.7 4.1 4.2 4.3 4.4
2 2 1 1
Finalize Create Gantt
Create Project Plan Create Activity Lists of Activities 2
Documentation Chart
Graph with Duration
of Interview
1
4.4.1
4.4.2
1 Activity Graph with
Duration
B Activity Graph with
Activities
58
BY: CODE X
B
2 Compute Estimated
5.1 5.2 5.3 5.4 5.5
2 2 2 2
Effort Costing Document Costing Hardware Costing Software Costing

2
6.3 6.2 6.1 5.6

5.7
3 2
3 3
Functional Conduct Final Documentation Compute Actual
Finalize Requirement
Requirement 3 Requirement Analysis Economic Feasibility
Analysis
6.4 6.4.1 6.4.2 6.4.3 6.4.4
3 3 3 3
Non-Functional Operational
Look and Feel Usability Performance 3
Requirement Requirement
Requirement Requirement Requirement
6.4.5
6.4.6
3
Maintainability and
Portability
C Security Requirements
Requirement
59
BY: CODE X
3
C
6.4.7 6.4.8 6.5 Purpose of the Goals of the

1
3 5 Project Project
Cultural and
Political Legal requirement Volere requirements 6.5.1 6.5.2
Requirement 1
1 6.5.4 6.5.3
1
1 6.5.5
User of the Client, Customer and
6.5.6 Project Stakeholder
1
Mandated
Naming Convention Constraints
6.5.7
and Definitions
Relevant Facts
and Assumption
2
6.5.8 6.5.9
Scope of the work Scope of the

Project D
60
BY: CODE X
1 D
6.6 6.6.1 6.6.2

2 Task
1 1
Project Issues Open Issues Off the shelf 6.6.3

Solutions
6.6.4
5 6.6.5
1
Cut over
6.6.6 Risk and cost
User
Documentation 2
and training
6.6.7 6.6.8
5
Ideas and Solution Finalize Requirement

Specifications E
61
BY: CODE X
7.1 6
Make an Entity 2 HIPO Diagram

7.2
Relationship
Diagram (ERD)
Construct Data Flow 7.3
Diagram (DFD)
1
7.4
Create and Design

System Module
7.5
Finalize System
Module
F
62
BY: CODE X
94 F
8.1 8.1.1 8.1.2

4 Implement coding
2 4 for User Accounts
Develop Source
Implement coding Implement coding
Code for 8.1.3
for Home Module for Log in Module
System Module
3 8.1.4
5 8.1.5
Implement coding Implement coding for
for Border Profile About Us
8.1.6 Implement coding
for Rooms Profile Accounts
Implement
8.1.9
coding for 4
Records Profile
8.1.7 8.1.8 1 1
4
Implement coding Implement coding for 8.2
for Collection Profile Admin
Initial
Documentation of
G Source Code
63
BY: CODE X
9.1
3
Develop
Develop Test Plan 9.1.1 Integration Test
1
n Plan
.1
n
n 9.1.2
Develop Unit test
n 1
n
n
n
n
9.1.3
n
n 1
n
Develop n Develop System Test
Performance Test n Plan
Plan 9.1.4n
n
1
n
n
n
n 9.1.5
n
n
H n
n Develop User
n Acceptance Test Plan
n
n
n
n 64
n
n
n
n
BY: CODE X
3 H
9.2
3 Perform Unit Testing

for User Account
Perform Unit
Testing
9.2.1
9.2.2
3
n
Perform Identifying
n
n System Errors
9.2.3 Perform Unit Testing
n
for Border Profile
n
Perform Unit n
n3 9.2.6
Testing for
n 3
Rooms Profile
n 3
n
9.2.4
n 9.2.5
n
n
Perform Unit Perform Unit
Testing for Testing for I
Records Profile Collection Profile
65
BY: CODE X
2
n
n
n 2
9.3 n n
9.3.1
n n
n n
Perform Entire
Perform n n
n n Integration
Integration Test
n n3 Testing
Plan
n nn
n nn
n nn
n nn
n n
9.3.2
n n
n n Document
n Integration Testing
Debug Errors n
n 3n
n n
n n
9.3.3
n n
n n
n n
n n
n n
n n
n J n
n
66
BY: CODE X
1
9.4
n
n
n Conduct
Perform System n 9.4.1 2 Performance and
Test Plan n Portability test
n
n 9.4.2
Perform Functional
n
Test
n
n
n 2
n
n 9.4.3
n
n
2
n
n
n Final System
9.4.4
Document System
Testing
K
67
BY: CODE X
2 K
n
n
n
9.5 n
n
n Perform Alpha Test
1
n
Perform User n
Acceptance n
Test Plan n
n 9.5.1
n
n
n
n 3
n n
9.5.2
n
2
n
n Perform Retest of the
n Debug Errors
Final System
9.5.3 n
n
n
Document
Perform Retest
nn of n 9.5.6
3 n User
Final System
1 Acceptance
n
n 5 Test Plan
n
9.5.4 9.5.5 1
n
n 9.5.7
n
Perform the Beta n 3
Debug errors
Test n n
n n
n n
n n
9.6
n Finalize
n over-all
nL Testing
n Document
68
n n
n n
n n
n n
n n
BY: CODE X
1
10.1
Implement User’s
Create Training 1
10.2 Training
Plan
Create User’s 10.3

Manual Introduce the System
1 and User’s Manual
10.3.1 1 10.4
1
10.3.1 1
Conduct User’s
Training
10.3.1
Evaluate User’s
Training
Document User’s
Training M
69
BY: CODE X
11.1
4
Finalize Source Code

Document
11.2
Finalize Over-all
System Document
Final Defense
11.3
70
BY: CODE X
Activity Graph with Milestone
Activity Milestone
1.1 Stablish company Build Company
1.2 Create Company name Company Name
1.3 Create Company Company Description
Description
1.4 Assign Roles and Roles and Responsibilities
responsibility
1.5 Create Company logo Build Company
1.6 Create Mission and Build Company
Vision
1.7 Set Goals and Build Company
Objective
1.8 Set Policies and Company Rules
Penalties
1.9 Create Company Build Company
1.10 Work style and Company Rules
schedule
Phase 2: The Client
2.1 Background of the Finding Client
Client
2.2 System Background System Background
2.3 Hierarchy chart System Background
Phase 3: Interview
3.1 Make an Interview Interview letter
letter
3.2 Prepare list of list of Questionnaire
Questionnaire
3.3 Appointment for Appointment for client
Interview
3.4 Actual Interview Interview for client
3.5 Follow up Interview Interview for client
3.6 Transcribe Interview Interview for client
71
BY: CODE X
3.7 Finalize Finalize Documentation

Documentation of
Interview
4.1 Create Project Plan Project Plan
4.2 Create Activity Graph Activity Graph
4.3 Lists of Activities with Activity Graph
Duration
4.4 Create Gantt Chart Activity Graph
4.4.1 Activity Graph with Activity Graph
Duration
4.4.2 Activity Graph with Activity Graph
Activities
5.1 Effort Costing Project Costing
5.2 Document Costing Project Costing
5.3 Hardware Costing Project Costing
5.4 Software Costing Project Costing
5.5 Compute Estimated Project Costing
5.6 Compute Actual Project Costing
5.7 Final Documentation Project Costing
Phase 6: Requirement
Analysis
6.1 Conduct Requirement Requirement Analysis
Analysis
6.2 Finalize Requirement Requirement Analysis
Analysis
6.3 Functional Requirement Analysis
Requirement
6.4 Non-Functional Requirement Analysis
Requirement
6.4.1 Look and Feel Requirement Analysis
Requirement
6.4.2 Usability Requirement Analysis
Requirement
72
BY: CODE X
6.4.3 Performance Requirement Analysis

Requirement
6.4.4 Operational Requirement Analysis
Requirement
6.4.5 Maintainability and Requirement Analysis
Portability Requirements
6.4.6 Security Requirement Analysis
Requirement
6.4.7 Cultural and Political Requirement Analysis
Requirement
6.4.8 Legal requirement Requirement Analysis
6.5 Volere requirements Requirement Analysis
6.5.1 Purpose of the Requirement Analysis
Project
6.5.2 Goals of the Project Requirement Analysis
6.5.3 Client, Customer and Requirement Analysis
Stakeholder
6.5.4 User of the Project Requirement Analysis
6.5.5 Mandated Requirement Analysis
Constraints
6.5.6 Naming Convention Requirement Analysis
and Definitions
6.5.7 Relevant Facts and Requirement Analysis
Assumption
6.5.8 Scope of the work Requirement Analysis
6.5.9 Scope of the Project Requirement Analysis
6.6 Project Issues Requirement Analysis
6.6.1 Open Issues Requirement Analysis
6.6.2 Off the shelf Requirement Analysis
Solutions
6.6.3 Task Requirement Analysis
6.6.4 Cut over Requirement Analysis
6.6.5 Risk and cost Requirement Analysis
6.6.6 User Documentation Requirement Analysis
and training
6.6.7 Ideas and Solution Requirement Analysis
6.6.8 Finalize Requirement Requirement Analysis
Specifications
73
BY: CODE X

7.1 Make an Entity Entity Relationship Diagram
Relationship Diagram
(ERD)
7.2 Construct Data Flow Data Flow Diagram
Diagram (DFD)
7.3 HIPO Diagram HIPO
7.4 Create and Design System Design
System Module
7.5 Finalize System Finalize System Module
Module
Phase 8: System
Development
8.1 Develop Source Code Implementation Coding
for System Module
8.1.1 Implement coding Implementation Coding
for Home Module
for Log in Module
for User Accounts
for Border Profile
Accounts
for Rooms Profile
for Records Profile
for Admin
for About Us
8.2 Initial Documentation Implementation Coding
of Source Code
9.1 Develop Test Plan Testing Plan
9.1.1 Develop Unit test Testing Plan
74
BY: CODE X
9.1.2 Develop Integration Testing Plan

Test Plan
9.1.3 Develop System Test Testing Plan
Plan
9.1.4 Develop Testing Plan
9.1.5 Develop User Testing Plan
9.2 Perform Unit Testing Testing Plan
9.2.1 Perform Unit Testing Testing Plan
for User Account
for Border Profile
for Rooms Profile
for Records Profile
9.2.6 Perform Identifying Testing Plan
System Errors
9.3 Perform Integration Testing Plan
Test Plan
9.3.1 Perform Entire Testing Plan
Integration Testing
9.3.2 Debug Errors Testing Plan
9.3.3 Document Testing Plan
Integration Testing
9.4 Perform System Test Testing Plan
Plan
9.4.1 Perform Functional Testing Plan
Test
9.4.2 Conduct Testing Plan
Performance and
Portability test
9.4.3 Perform Retest of the Testing Plan
Final System
9.4.4 Document System Testing Plan
Testing
75
BY: CODE X
9.5 Perform User Testing Plan

9.5.1 Perform Alpha Test Testing Plan
9.5.2 Debug Errors Testing Plan
9.5.3 Perform Retest of Testing Plan
Final System
9.5.4 Perform the Beta Testing Plan
Test
9.5.5 Debug errors Testing Plan
9.5.6 Perform Retest of the Testing Plan
Final System
9.5.7 Document User Testing Plan
9.6 Finalize over-all Testing Testing Plan
Document
10.1 Create Training Plan Users Training Plan
10.2 Create User’s Manual Users Training Plan
10.3 Implement User’s Users Training Plan
Training
10.3.1 Conduct User’s Users Training Plan
Training
10.3.2 Evaluate User’s Users Training Plan
Training
10.3.3 Document User’s Users Training Plan
Training
10.4 Introduce the System Users Training Plan
and User’s Manual
Phase 11: Finalization of
Internal and External
Documentation
11.1 Finalize Source code Finalization of Internal and External Documentation
Document
11.2 Finalize Over-all Finalization of Internal and External Documentation
System Document
11.3 Final Defense Finalization of Internal and External Documentation
76
BY: CODE X
Activity Graph with Slack Time
Activity Dependencies Duration ES EET LST LET Slack

T Time
1.1 Stablish company -- -- 1 1 1 1 0

1.2 Create Company name 1.1 1 2 2 2 2 0
1.3 Create Company 1.1 1 2 3 2 3 1
Description
1.4 Assign Roles and 1.1 1 2 3 3 3 0
responsibility
1.5 Create Company logo 1.1 1 2 4 4 4 0
1.6 Create Mission and Vision 1.1 1 5 5 5 5 0
1.7 Set Goals and Objective 1.1 1 6 6 6 6 0
1.8 Set Policies and Penalties 1.1 1 7 7 7 7 0
1.9 Create Company 1.1,1.5 1 8 8 8 8 0
1.10 Work style and schedule 1.1 1 9 9 9 9 0
2.1 Background of the Client 1.10 1 10 10 10 10 0

2.2 System Background 2.1 2 11 11 11 11 0
2.3 Hierarchy chart 2.2 1 12 12 12 12 0
3.1 Make an Interview letter 2.3 1 13 13 13 13 0

3.2 Prepare list of 3.1,2.3 1 14 14 14 14 0
Questionnaire
3.3 Appointment for Interview 3.2 1 15 15 15 15 0
3.4 Actual Interview 3.3 2 16 16 16 16 0
3.5 Follow up Interview 3.4 1 13 13 13 13 0
3.6 Transcribe Interview 3.5 1 9 9 9 9 0
3.7 Finalize Documentation of 3.6 2 17 17 17 17 0
Interview
4.1 Create Project Plan 3.7 2 18 19 18 19 0

4.2 Create Activity Graph 4.1 1 20 20 20 20 0
77
BY: CODE X
4.3 Lists of Activities with 4.2 1 21 22 21 22 0

Duration
4.4 Create Gantt Chart 4.3 2 23 24 23 24 0
4.4.1 Activity Graph with 4.4 1 25 26 25 26 0
Duration
4.4.2 Activity Graph with 4.4.1 1 27 28 27 28 0
Activities
5.1 Effort Costing 4.4.2 2 29 30 29 30 0

5.2 Document Costing 5.1 2 31 31 31 31 0
5.3 Hardware Costing 5.2 2 32 32 32 32 0
5.4 Software Costing 5.3 2 33 33 33 33 0
5.5 Compute Estimated 5.4 2 34 34 34 34 0
5.6 Compute Actual Economic 5.5 2 35 35 35 35 0
Feasibility
5.7 Final Documentation 5.6,5.5 2 36 36 36 36 0
6.1 Conduct Requirement 5.7 3 37 38 37 38 0

Analysis
6.2 Finalize Requirement 6.1 3 39 39 39 39 0
Analysis
6.3 Functional Requirement 6.2 3 40 59 40 59 0
6.4 Non-Functional 6.3 3 60 69 60 69 0
Requirement
6.4.1 Look and Feel 6.4,6.3 3 70 79 70 79 0
Requirement
6.4.2 Usability Requirement 6.4.1 3 80 83 80 83 0
6.4.3 Performance 6.4.2 3 84 87 84 87 0
Requirement
6.4.4 Operational 6.4.3 3 88 89 88 89 0
Requirement
6.4.5 Maintainability and 6.4.4 3 90 90 90 90 0
Portability Requirements
6.4.6 Security Requirement 6.4.5 3 91 91 91 91 0
6.4.7 Cultural and Political 6.4.6 3 92 92 92 92 0
Requirement
6.4.8 Legal requirement 6.4.7 3 93 93 93 93 0
78
BY: CODE X
6.5 Volere requirements 6.4.8 5 94 94 94 94 0

6.5.1 Purpose of the Project 6.5 1 95 95 95 95 0
6.5.2 Goals of the Project 6.5.1 1 96 96 96 96 0
6.5.3 Client, Customer and 6.5.2 1 97 97 97 97 0
Stakeholder
6.5.4 User of the Project 6.5.3, 6.5.1, 1 98 98 98 98 0
6.5.2
6.5.5 Mandated Constraints 6.5.4 1 99 99 99 99 0
6.5.6 Naming Convention and 6.5.5 1 10 100 100 100 0
Definitions 0
6.5.7 Relevant Facts and 6.5.6 1 10 101 101 101 0
Assumption 1
6.5.8 Scope of the work 6.5.7 1 10 102 102 102 0
2
6.5.9 Scope of the Project 6.5.8 1 10 103 103 103 0
3
6.6 Project Issues 6.5.9 1 10 104 104 104 0
4
6.6.1 Open Issues 6.6 1 10 105 105 105 0
5
6.6.2 Off the shelf Solutions 6.6.1 1 10 101 101 101 0
1
6.6.3 Task 6.6.2 1 10 102 102 102 0
2
6.6.4 Cut over 6.6.3 1 10 103 103 103 0
3
6.6.5 Risk and cost 6.6.4 2 10 104 104 104 0
4
6.6.6 User Documentation and 6.6.5 2 10 105 105 105 0
training 5
6.6.7 Ideas and Solution 6.6.6 10 106 106 106 0
6
6.6.8 Finalize Requirement 6.6.7 3 10 107 107 107 0
Specifications 7
7.1 Make an Entity 6.6.8 6 10 109 109 109 0

Relationship Diagram (ERD) 9
7.2 Construct Data Flow 7.1 6 11 110 110 110 0
Diagram (DFD) 0
7.3 HIPO Diagram 7.2 2 11 111 111 111 0
1
79
BY: CODE X
7.4 Create and Design System 7.3 1 11 112 112 112 0

Module 2
7.5 Finalize System Module 7.4 1 11 113 113 113 0
3
1
8.1 Develop Source Code for 7.5 2 11 114 114 114 0
System Module 4
8.1.1 Implement coding for 8.1 2 11 115 115 115 0
Home Module 5
8.1.2 Implement coding for 8.1.1 2 10 107 107 107 0
Log in Module 7
8.1.3 Implement coding for 8.1.2 4 0
User Accounts
Border Profile Accounts 9
Rooms Profile 0
Records Profile 1
Collection Profile 2
Admin 3
8.1.9 Implement coding for 8.1.8 4 0
About Us
8.2 Initial Documentation of 8.1.9 1 11 114 114 114 0
Source Code 4
115 115
9.1 Develop Test Plan 8.2 3 10 107 107 107 0
7
9.1.1 Develop Unit test 9.1 3 0
9.1.2 Develop Integration Test 9.1.1 3 10 109 109 109 0
Plan 9
9.1.3 Develop System Test 9.1.2 1 10 109 109 109 0
Plan 9
9.1.4 Develop Performance 9.1.3 1 11 110 110 110 0
Test Plan 0
9.1.5 Develop User 9.1.4 1 11 111 111 111 0
Acceptance Test Plan 1
80
BY: CODE X
9.2 Perform Unit Testing 9.1.5 3 11 112 112 112 0

2
9.2.1 Perform Unit Testing for 9.2 3 11 113 113 113 0
User Account 3
9.2.2 Perform Unit Testing for 9.2.1 3 0
Border Profile
9.2.3 Perform Unit Testing for 9.2.2 3 11 114 114 114 0
Rooms Profile 4
Records Profile 5
Collection Profile 6
9.2.6 Perform Identifying 9.2.5 3 11 117 117 117 0
System Errors 7
9.3 Perform Integration Test 9.2.6 2 11 118 118 118 0
Plan 8
9.3.1 Perform Entire 9.3 2 11 119 119 119 0
Integration Testing 9
9.3.2 Debug Errors 9.3.1 3 22 220 220 220 0
0
9.3.3 Document Integration 9.3.2 2 22 220 220 220 0
Testing 1
9.4 Perform System Test Plan 9.3.3 2 22 220 220 220 0
0
9.4.1 Perform Functional Test 9.4 1 22 220 220 220 0
0
9.4.2 Conduct Performance 9.4.1 2 22 220 220 220 0
and Portability test 0
9.4.3 Perform Retest of the 9.4.2 2 22 220 220 220 0
Final System 0
9.4.4 Document System 9.4.3 2 22 220 220 220 0
Testing 0
9.5 Perform User Acceptance 9.4.5 2 22 220 220 220 0
Test Plan 0
9.5.1 Perform Alpha Test 9.5 1 22 220 220 220 0
0
9.5.2 Debug Errors 9.5.1 3 22 220 220 220 0
0
9.5.3 Perform Retest of Final 9.5.2 2 22 220 220 220 0
System 0
81
BY: CODE X
9.5.4 Perform the Beta Test 9.5.3 3 11 118 118 118 0

8
9.5.5 Debug errors 9.5.4 5 11 119 119 119 0
9
9.5.6 Perform Retest of the 9.5.5 1 22 220 220 220 0
Final System 0
9.5.7 Document User 9.5.6 1 22 220 220 220 0
Acceptance Test Plan 1
9.6 Finalize over-all Testing 9.5.7 3 22 220 220 220 0
Document 0
220 220
10.1 Create Training Plan 9.6 1 22 220 220 220 0
0
10.2 Create User’s Manual 10.1 1 22 220 220 220 0
0
10.3 Implement User’s 10.2 1 11 118 118 118 0
Training 8
10.3.1 Conduct User’s Training 10.3 1 11 119 119 119 0
9
10.3.2 Evaluate User’s 10.3.1 1 22 220 220 220 0
Training 0
10.3.3 Document User’s 10.3.2 1 22 220 220 220 0
Training 1
10.4 Introduce the System and 10.3.3 1 11 114 114 114 0
User’s Manual 4
11.1 Finalize Source code 10.4 4 11 118 118 118 0

Document 8
11.2 Finalize Over-all System 11.1 4 11 119 119 119 0
Document 9
11.3 Final Defense 11.2 3 22 220 220 220 0
0
82
Gantt Chart
83
84
85
86
87
88
89
90
91
92
BY: CODE X
Chapter V
Project Costing
93
BY: CODE X
5.2 Project Estimation
Effort Cost
Name of The Member Number of working Number Rate per Total Cost
w/ (current position) hours per day working Day
days
Jala, Norrama 8 122 ₱ 400 ₱ 48,800.00
(Project Manager)
Sali, Myrhana (System Analyst) 8 122 ₱ 400 ₱ 48,800.00
Mangking, Daisa (Chief 8 122 ₱ 225 ₱ 27,450.00

Programmer)
Salvador, Richa Rose (Test 8 122 ₱ 225 ₱ 27,450.00
Engineer)
Eyyas, Jefford (Chief Archivist) 8 122 ₱ 175 ₱ 21,350.00
Hamsiri, Al jadeed (Head Trainer) 8 122 ₱ 175 ₱ 21,350.00
Total Effort Costs: P195,200.00
Hardware Cost
Hardware Unit/Quantity Cost Total Cost
Router 1 pc ₱ 1200.00/pc ₱ 1,000.00
Total Hardware Costs: P 1,000.00
94
BY: CODE X
Documentation Cost
Item Unit/Quantity Costs Total Cost
Photocopy 90 pages ₱ 1.00/page ₱ 90.00

Folder 2 pcs ₱ 5.00/pc ₱ 10.00
Flash disc 5 pcs ₱ 50.00/pc ₱ 250.00
BookBind(Spiral) 2 pcs ₱ 50.00/pc ₱ 100.00
BookBind(Hardbound) 1 pc ₱ 300.00/pc ₱ 300.00
User’s manual 2 pcs ₱ 160.00/pc ₱ 320.00
Printing 300 pages ₱ 1.00/page ₱ 300.00
Total Documentation Costs: P 1,840.00
Overall Cost
Expenses Costs
Effort Cost ₱195,200.00
Hardware Cost ₱1,000.00
Documentation Cost ₱ 1,840.00
Total Facility Costs P198,040.00
Description Complexity
Total Low Medium High Total

Number
Inputs 6 4x3 2x4 1x6 26
Outputs 7 1x4 4x5 2x7 38
Interfaces 1 1x5 1x7 1x10 22

Total Unadjusted Function Points (TUFP) 107
95
BY: CODE X
5.3 Basic Constructive Cost Model (COCOMO)
General System Characteristics Rating
Data Communication 2
Distributed Data Processing 1
Performance 2
Heavily used Configurations 1
Transaction Rate 2
On-Line Data Entry 0
End-User Efficiency 1
On-Line Update 0
Complex Processing 1
Reusability 3
Installation Ease 2
Operational Ease 2
Multiple Sites 1
Facilitate Chance 1
Total Processing Complexity 18
(0-5) 0 is the lowest; 5 is the greatest effect
96
BY: CODE X
COCOMO Semi-detached Project Type
NUMBER OF INPUTS NUMBER OF INTERFACE NUMBER OF OUTPUTS

Username and Password Username and Password
Router/Switch
Add boarders View boarders
Add rent View rental fee amount
Add rooms View reports

Accounts View Rooms
Settings
Accounts
About us
Table of Function Points
Adjusted Project Complexity (APC)
.65 + (0.01 X 18) = 0.83
Total Adjusted Function Points (TAFP)
.83 X 107= 88.81 (TAFP)
Source Lines of Codes (KLoC/SloC)
Visual Basic = 10
88.81(TAFP) X 30(VB) 8.881 KLoC
Compute for Effort₱ 48,800.00

(Semi-detached)
E= ab (KLoC)bb
E= 3.0(8.881)1.12
E= 3.0(11.54)
E= 34.626 Person Months
97
BY: CODE X
Project Duration
(Semi-detached)
D= cb(Effort-Applied)db
D= 2.5(34.626).35
D= 2.5(3.46)
D= 8.6 months
Therefore it needs 9 months and more days to complete the system project.
People Required
= Effort applied/Project Duration
= `34.626/8.6
= 4.026 person need or 4 persons needed for the project.
But if 5 persons will do the project. Duration will be:
D=Effort/No. Of person
D=34.626/5
D= 6.925 or 7 months
98
BY: CODE X
Chapter VI
Requirement Engineering
99
BY: CODE X
Requirement Engineering
The CODE X Company used the waterfall model in the development of the BA Dormitory
Management System. This type of methodology is chosen to guarantee that every functionality
that is required by the client, is in the developed system. During the analysis and design phase
series of prototypes were created to immediately identify the issues and easily resolve. The
developing team conducted series of interviews with the client to ensure that all requirements
were gathered and approved by the client.
The data gathered is used in the development process of the system, Volere
Requirements were created, required Modules were determined, diagrams such as Entity
Relationship Diagram, HIPO Chart, Data Flow Diagram and Context Diagram were structured by
the analysis team. The programming team and analysis team worked together to produce more
reliable system and meet the needs and concerns of the user.
6.1 Purpose of the Project
The purpose of creating BA Dormitory Management System is to organize the transaction

records that the BA Dormitory to keep tracks and put everything in place. It will minimize the
work of the landlady, and will provide a better way to keep tracks of the transaction services.
6.1.a Background of the Project
The BA DORMITORY is one of the dormitory here in Zamboanga, prior to the

development of the BA DORMITORY the Landlady and the Owner of the dormitory have
been serving the student and other people through manually and through Microsoft Excel
to keep track of the records.
When retrieving their records of transaction, it would take a lot of time and effort
because there would be numerous number of folders making it difficult to find for a
specific record.
To avoid nuisance of possibly loosing tracks of the record transaction, The CODE X
has chosen to develop BA DORMITORY SYSTEM that would effectively manage and
100
BY: CODE X
monitor the transaction, it would provide a better way to keep tracks of the record
transaction.
6.1.a.1 Goals of the Project
The goal of our project is to develop an information system for BA DORMITORY

that can help the Landlady to lessen the work from problem of having to do It manually.
The Landlady will instead be concerned elsewhere, working on the several different
issues.
 To provide securities that will secure the entire dormitory information.
 To enable the user to search and sort the data records.
 To provide an easy way on searching available rooms and to let the user knows the
availability of each rooms
6.2 The Stakeholders
6.2.a Client
Our client for this project is the “BA Dormitory”. Ms. Melanie Ledesma is the
representative for this project. She’s the OIC (Officer in Charge) of the BA Dormitory.
6.2.b Customer
The customer of this project is our client. With the use of our system the
Dormitory Management System, they can now experience a better service to other
customer which is the border of the dormitory.
101
BY: CODE X
6.2.c Stakeholders
These are the following stakeholders that affected by the product:
 Melanie Ledesma
She is the OIC (Officer in Charge) and also the land lady of the BA
Dormitory.
 Ara Chua
The owner of the BA Dormitory
 Software Engineering Instructor/adviser
o Engr. Marjorie Rojas

o Engr. Marvic Lines
They are the team consultant.
 Norrama Jala
The project manager of the team and she stood as a leader. She is
responsible for making decision, scheduling for meeting, task and
she will remind and follow up all the assigned task of her member.
 Myr-hana Sali
She is the systems analyst of the team. She is responsible for

analyzing and understanding the gathered data from interview
with the client.
 Daisa Mangking
She is the chief programmer of the team. She is responsible for

program design and implementation of the entire system. She will
do the actual code.
102
BY: CODE X
 Richa Rose Salvador
She is the testing head of the team. She is responsible for testing
the system to find out if there is a possible error or problem on the
system and corrected for the development of the system.
 Jefford Eyas
He is the chief archivist of the team. He is responsible in collecting
and monitoring the task that has been done and put it together for
the documentation.
 Al-jadeed Hamsiri
He is the head trainer of the team. He is responsible to train the

client and he will create a user manual that will guide the user on
the functionality of the project.
6.2.d The Hands-on User of the Product
User name User Role Subject Matter Technological

experience experience
Mrs. Ara Chua Admin Master Intermediate
Ms. Melanie Ledesma Clerk Master Intermediate
103
BY: CODE X
6.2.e Priorities Assigned to the Users

To identify the importance and precedence of the users.
User Principle Assigned
Admin Key User
Registered User Secondary User
6.2.f The User Participation
The participation of the user is very important so that the developers will be able
to determine the requirements of the project.
6.3 Mandated Constraints
There are many constraints on the system that we are currently working on. Most these
will probably be social and budgetary as opposed to technical constraints. Even though we
assume that these constraints will occur in the future, currently we have any direct knowledge
about it.
6.3.a Solution Constraints
Description: The system should be an Application Software.

Rationale: The client can access through the dorm’s and its border’s information.
Fit Criterion: The system is accessible without the internet, but can only be used
through a computer.
104
BY: CODE X
6.3.b Implementation Environment
The environment in which the system is going to take place is in the dorm,
itself. The environment will be filled with the dorm’s borders and the admin
accessing through the system.
6.3.c Partner Application
The applications that is working together in developing the system are the
MySQL and Visual Studio.
6.3.d Commercial Off-Shelf Product
The Programming languages that are known for creating desktop-based system
are SQL and Visual Basic .NET.
6.3.e Anticipated Work Place Environment
The users and the admin can access the Application anytime, anywhere as
long as they have their computers with them.
6.3.f Schedule Constraints
Refer to Chapter 4 for complete project schedule
6.4 Naming Conventions and Terminology

Naming Conventions
BA Dormitory – one of the dormitory here in Zamboanga city
Codex – The developers of the project
105
BY: CODE X
Admin – Manage and control the usage of the project or the primary user of the
system
Clerk – The secondary user of the system
Cashier – Also a secondary user of the system.
Stakeholders – Person who is responsible for the development of the whole
project
Gantt Chart – chart that correspond the schedule of developing the system
HIPO Chart – arrangement of the requirement needed by the developers
ERD – graphical representation of the entities being tracked in the system
DFD – dataflow diagram represents the entire process of the system.
6.5 Relevant Facts and Assumption

6.5.a Relevant Facts
 The Admin and borders will have an account.

 Borders can only access through their information.
 The Admin can edit, delete and add border’s data.
6.5.b Assumption
 We assume that the user of the system will be comfortable in using our
project
 We assume that the work of the user will be less hassle by using the project
 We assume that if power outage may happen the user will do manually
their activities.
 We assume that the functionality of the project will meet the requirements
given by the client.
 We assume that the project will be finish before the deadline.
 We assume that everything will go as planned.
106
BY: CODE X
6.6 The Scope of the Work
6.6.a The Current Situation
The current situation is the existing application is working but is on

maintenance. The only available services of the BA Dorm is through contacting the
assigned staff, the future borders still need to fill up the Registration form access
their information or any concerns in person through the staffs of the BA
Dormitory. The system is still on process.
107
BY: CODE X
6.6.b Context of the Work

6.6.c Work Partitioning
EVENT
EVENT NAME INPUT OUTPUT
#
Administrator, Clerk signs in to Username Initializes home screen
the system Password
1
Administrator, Clerk add a new Border’s details Updated BA DORMITORY Border’s list
2 border
Administrator, Clerk modifies a Border’s details Updated BA DORMITORY Border’s list

3 border
Administrator, Clerk deletes a Selected border Updated BA DORMITORY Border’s list

4 border
Administrator, Clerk add a new User’s details Updated BA DORMITORY User account list
5 user account
Administrator modifies a user Updated BA DORMITORY User account list

account User’s name
6
Clerk modifies a user account Username and Updated BA DORMITORY User account list
password
7
Administrator deletes a user Selected Updated BA DORMITORY User account list

account account
8
Administrator, Clerk adds new Rent payment Updated BA DORMITORY rent transactions
rent transaction details,
Border details,
9 Guardian
details
108
BY: CODE X
Administrator, Clerk modifies rent Rent payment Updated BA DORMITORY rent transactions
transaction details,
10 Border details,
Guardian
details
Administrator modifies rental fee Rental fee Updated BA DORMITORY rental fee amount
amount amount details
11
Administrator, adds room Room details Updated BA DORMITORY room

12
Administrator, Clerk modifies Room details Updated BA DORMITORY room

13 room
Administrator, Clerk prints rent Start date of Print rent transactions

transactions transaction
14 End date of
transaction
Administrator, Clerk modifies User details Updated BA DORMITORY user list
15 user position
Administrator, Clerk prints Start date of Prints monthly revenue

monthly revenue transaction
16
End date of
transaction
Administrator, Clerk prints annual Start date of Prints annual revenue
revenue transaction
17
End date of
transaction
109
BY: CODE X
6.7 Business Data and Data Model

6.7.a Entity Relationship Diagram (ERD)
110
BY: CODE X
6.8 Scope of the Work

6.8.a Product Boundary
111
BY: CODE X
Use case title: Login

Primary Actor: Admin
Level: Kite (summary)
Stakeholders: Admin/Clerk/Cashier
Precondition: User must have an account
Minimal Guarantee: Valid username or password
Success Guarantee: Admin/Clerk successfully logged in. Shows Dashboard
Trigger: Admin/clerk full access of the system
Main Success Scenarios:
1. The user enters username and password.
2. The system validates the entered username and password and grants
access into the system.
Extensions
1a. The username and password do not match to the database.
1a1. Enter the valid username and password.
Use case title: Add Boarder

Level : Kite (summary)
Stakeholders: Admin/Clerk
Precondition: User must have an account. You must login as admin/clerk.
The user must login as administrator or clerk.
The user enters the necessary data.
The user saves the boarder data.
Extensions:
a. The system save button does not work.
a1. Refresh system
112
BY: CODE X
Use case title: Edit Boarder

Precondition: User must have an account.
1. The user must login as administrator or clerk.
2. The user clicks the boarder module.
3. The user clicks the edit button on selected boarders.
4. The user enters the new information.
5. The user saves the changes made in the member boarder’s account.
Extensions:
Use case title: Edit Rental


2. The user clicks the settings module.
3. The user enters the necessary data.
4. The user saves the boarder data.
Extensions:
1a. The username and password does not match to the database.
113
BY: CODE X
Use case title: Add Rooms

Stakeholders: Admin
1. The user must login as administrator.
2. The user clicks the room module.
3. The user clicks the new room button.
4. The user enters the necessary data.
5. The user saves the information.
Extensions:
Use case title: Edit Rooms

Stakeholders: Admin
2. The user clicks the rooms module.
3. The user clicks the edit button on selected room.
4. The user enters the new information.
5. The user saves the changes made in the room module.
Extensions:
114
BY: CODE X
Use case title: Payment

Primary Actor: Cashier
Stakeholders: Admin/cashier
1. The user must login as administrator or cashier.
2. The user clicks the collection module.
3. The user generates a bill.
4. The user chooses a recipient.
5. The user clicks the unpaid bill then save it.
Extensions:
Use case title: Print bills

Primary Actor: Cashier
Stakeholders: Admin/Cashier
Trigger: Admin/cashier full access of the system
2. The user clicks the Billing module.
3. The user enters the months he/she wants to print.
4. The system shows the bills.
5. The user clicks the print button.
Extensions:
1a. The username and password does not match to the database.
115
BY: CODE X
Use case title: Add New User

Stakeholders: Admin
1. The user must log-in as an Administrator.
2. The user adds user account.
3. The user enters necessary data.
4. The user saves the newly created user account.
5. The system notifies the user that a new user account has been made.
Extensions:
Use case title: Edit User Account

Stakeholders: Admin
Extensions:
116
BY: CODE X
Use case title: Delete User Account

Stakeholders: Admin
1. The user must log-in as an Administrator.
2. The user chooses a user account to be deleted.
3. The system notifies that the selected user account has been successfully deleted.
Extensions:
117
BY: CODE X
6.9 Functional and Data Requirement

6.9.a Requirement Shell
Requirement #: 01 Requirement Type: 9 Use Case #: 01

Description: Allow the administrator and clerk to log in to the system.
Rationale: The Administrator, Clerk and Cashier must be able to log-in to the system and be able to access the system’s
functionalities depending on user’s level.
Source: Ms. Melanie L. Ledesma
Fit Criterion: The administrator and clerk must have a valid username and password to be able to login successfully.
Customer Satisfaction: 5 Customer Dissatisfaction: 5
Dependencies: User Account

History: January 2018

Description: Allow the Administrator and clerk to add boarder.
Rationale: The Administrator and Clerk must be able to log-in to the system and be able to add boarder this includes
information that should be able to update in the system’s database.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to add boarder.
Customer Satisfaction:5 Customer Dissatisfaction: 5

118
BY: CODE X

Description: Allow the Administrator and clerk to edit boarder’s information.
Rationale: The Administrator and Clerk must be able to log-in to the system to access the boarder module and be able to
update boarder’s information in the system’s database.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to edit boarder.


Description: Allow the Administrator and clerk to edit rental.
Rationale: The Administrator and Clerk must be able to log-in to the system and be able to edit rental payment this
includes information that should be able to update in the system’s database.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to edit rental.

119
BY: CODE X

Description: Allow the Administrator and clerk to add rooms.
Rationale: The Administrator and Clerk must be able to log-in to the system and be able to add rooms this includes
information that should be able to update in the system’s database.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to add rooms.


Description: Allow the Administrator and clerk to edit rooms.
Rationale: The Administrator and Clerk must log-in to the system to be able edit room’s information that should be able to
update in the system’s database.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to edit rooms.

120
BY: CODE X

Description: Allow the Administrator and cashier to add payment.
Rationale: The Administrator and Cashier must log-in to the system to be able to add payment this includes information
that should be able to update in the system’s database.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to add payment.


Description: Allow the Administrator and clerk to print bills.
Rationale: The Administrator and Clerk must be able to log-in to the system and be able to access the billing module and
be able to print bills.
Fit Criterion: The Administrator and Clerk must successfully login to the system to be able to edit print bills.

121
BY: CODE X

Description: Allow the Administrator to add new user account.
Rationale: The Administrator must be able to add new user account and should be able to update changes in the system’s
database
Fit Criterion: The Administrator must successfully login to the system to be able to add new user account.


Description: Allow the Administrator, Clerk and Cashier to edit user account.
Rationale: The Administrator, Clerk and Cashier must login to the system to be able to edit their user account and should
be able to update the changes in the system’s database.
Fit Criterion: The Administrator, Clerk and Cashier must successfully login to the system to be able to edit user account.

122
BY: CODE X

Description: Allow the Administrator to delete user account.
Rationale: The Administrator must login to the system to be able to delete user account and should be able to update
changes in the system’s database.
Fit Criterion: The Administrator must successfully login to the system to be able to delete user account.

6.9.c Non-Functional Requirement
 The buttons and text must be visible and clear to the users.
 The BA Dormitory Management System security includes the
authentication of the user through username and password.
6.10 Look and Feel Requirement

6.10.a Interface
The BA Dormitory Management System that wish to develop have a

combination of black, red and blue color. The design should pass the requirements
of a standard software application, it should be user-friendly.
123
BY: CODE X
6.11 Usability and Humanity Requirement

6.11.a Ease of Use Requirement
The system’s interface is a user-friendly type. Its forms are likely the same
with manually processed registration form of the dorm, but it remodeled into a
computerized one. The buttons, labels and other fields are properly arranged so
the users will not have difficulty in accessing the system.
6.11.b Learning Requirements
The developers provided a user-manual for the user’s tutorial, so the users
will be guided and will not struggle in the future in using the system.
6.11.c Understandability and Politeness Requirements
All the terms used in the system are specified in the User Manual. The
system will not use terms that are not familiar to the users.
6.12 Performance Requirements

6.12.a Speed and Latency Requirements
The system requires a fair amount speed when used, but the outcome is
not directly influenced by it. It still depends on the how fast the computer
operates.
6.12.b Precision or Accuracy Requirements
Amounts shall be in peso type. It should be in whole or integer type

numbers.
124
BY: CODE X
6.12.c Reliability and Availability Requirements
The system is accessible 24/7 by the users
6.12.d Robustness of Fault-Tolerance Requirements
 The system should help the client’s works to be easier.

 The system must give precise results.
 The system should store its data.
6.12.e Capacity Requirements
The system should be able to manage data coming from the database and the
website.
6.12.f Longevity Requirements
The system is expected to operate maximum maintenance for one year.
6.13 Operational and Environmental Requirements

6.13.a Expected Physical Environment
 The product will be installed inside the Dormitory’s office.

 It can be used in both laptop and Desktop computers.
 It will be used by the admins and the users.
125
BY: CODE X
6.13.b Requirements for Interfacing with Adjacent
The interface of the system should fit in any monitor’s screen size resolution
without interface or designs being destroyed.
6.14 Maintainability and Support Requirement

6.14.a Maintenance Requirements
To ensure the functionality with the system, it should be updated for every
month.
6.14.b Supportability Requirements

The BA-dormitory Management System is expected to run smoothly with at least
Windows XP operating system with at least dual core processor.
6.14.c Adaptability Requirements
 The system can be run on Windows OS 7, 8 and 10.

 The system is exclusively for the BA Dormitory.
6.15 Security Requirements

6.15.a Access Requirements
Each user has a different. All can access through their information but only
the admin can edit, delete, add some of the system’s module.
6.15.b Privacy Requirements
 The system shall only access the user accounts with the manager’s command.
 The system has a restriction for all kinds of users.
 The system should notify if the transaction is already done.
126
BY: CODE X
6.16 Cultural Requirements

6.16.a Cultural Requirements
There should be no cultural or ethnic involvement in the system’s design.
6.17 Legal Requirements

6.17.a Compliance Requirements
 Anything regarding the money is out of the boundary of the system.
6.18 Open Issues

 The dormitory doesn’t have any computer.
 The manager might change the dormitory’s function.
6.18.a Products that can be Copied
6.19 New Problem

6.19.a Effects on the Current Environment
Instead of the manual process in handling the border’s data, the system has now
the record of the borders.
6.19.b Potential User Problem

The Hard-copied User-Manual helps the users who are not yet used to in using the
system.
6.19.c Limitations in the Anticipated Implementation
The computer should at least have Microsoft Visual Basic 2010 or above so the
system could successfully run.
127
BY: CODE X
6.20 Tasks
Methodology
The Waterfall Model illustrates the software development process in a linear sequential
flow; hence it is also referred to as a linear-sequential life cycle model. This means that any phase in the
development process begins only if the previous phase is complete.
The Team decided to use a the Waterfall method because the concept of this model is simple,
easy to manage due to the rigidly of the model – each phase has specific deliverables and review process,
phases do not overlap from each other also, one of the best reason why we chose the this kind of model
over the other is because Waterfall Model is best to use if and only if the requirements are clear, very
well-known and fixed.
6.20.a Project Planning

Refer to Chapter 3: Project Plan
6.20.b Planning of the Development Phases

128
BY: CODE X
6.21 Risks
In making the system one of the risk that the team is facing is the time frame in developing the
system, given only by a short period of time, the team must be able to have an output every day to be
able to complete the task. Due to the reason that the project that the team is developing is a
Management system this requires a narrow understanding with regards with Accounting, in the
curriculum that we have, we don’t have any accounting subject that would help us understand the
Client’s wants and demand, hence we need to cope up with this and self-tutorial is needed and this
leads to more time consuming. Also assuming that the product is already been delivered to the client,
it is also a risk about the technical know-how of each user, we need to adjust on the capability on the
user’s side now that there will a lot of changes and some modification on the business transaction.
6.21.a Costs
6.22 User Documentation and Training Requirements

6.22.a User Documentation Requirements
The User and Team should have knowledge of the system and it is by
providing a manual, so that we can further understand the system’s work and
functionalities.
6.22.b Training Requirements

The training is necessary for the user to know how to use the system
properly. The codex is responsible for teaching the user to operate the system.
They will introduce the functionalities and the system.
129
BY: CODE X
Chapter VII
System Design
130
BY: CODE X
7.0 Hierarchical Input Process Output (HIPO)
131
BY: CODE X
Description of the Main Module and Sub Module
Login
The system allows the user to input the username and password,
If the username and password match with the user stored in database
Username then the user now can access the system.
Password
Boarder
This module, it is all about the boarders.
New Border In the sub-module view, it shows all the boarder’s information.
View
Guardian
Rent
In the rent module, this where the main transaction of the system.
New Rental In the sub module new transaction, the system asks for the boarders
infomation and this is where the process of payment.
New Border
Browse
Room
Add Ons
Save
Cancel
132
BY: CODE X
Billings
This module allows the user to show and print the bills of the boarders.
View Billings
Print Billings
Collection
Where the collection of payments can be viewed and
new payments can be done. Only the admin and
New cashier can access this module.
Payment
Settings
This
. module contains the settings of the
system (e.g. penalties and rental settings)
Save
Cancel
Account
This module is where the admin add another user
to the system. And only the admin has the access
New to this module.
Account
133
BY: CODE X
.
Profile
User account settings.
Save
Cancel
Logout The user exits the system.
7.1 Context Flow Diagram
134
7.2 Data Flow Diagram
7.2.a. Level 0
135
7.2.b Level 1
136
BY: CODE X
7.3 Hierarchical Input Process Output (HIPO)
137
BY: CODE X
7.4 User Interface with Description

7. 4. 1. Log- In Screen
This is the log-in form. All the system users can see this log-in form every time the application
is being started. This is where the system users fill in their corresponding username and
password to be able to access the system.
7. 4. 2. Dashboard
Dashboard menu depends on the user access in the system, below is the menu for each user
in the system. The dashboard of the clerk has the forms as the admin. But some of the
modules cannot access by the clerk. Because it is disable only the admin can access them all.
138
BY: CODE X
7. 4. 3. Rental Record
The screen shows when the button “rent” is clicked. If you click the “new rental” another
form will show.
7. 4. 4. New rental
After clicking the new rental this form will pop up. The upper right side are the buttons for
extra options.
139
BY: CODE X
7. 4. 5. New border
If you click the “new border” this form will pop up. Fill-up the form and click “proceed to
rent”.
7. 4. 6. Search for borders
This form show the list of borders who have completed their transactions before.
140
BY: CODE X
7. 4. 7. Browse room
This form will show the list of all rooms.
7. 4. 8. Add on
This for form shows adding appliances for free or with Charge.
141
BY: CODE X
7. 4. 9. Border record
This form shows the list of all the borders.
7. 4. 10. Billing record
This form will show the unpaid bills, due date, due amount, amount after due, and the status.
142
BY: CODE X
7. 4. 11. Payment and Collection
This form shows the list of payment the admin and the cashier only can access the this payment
module.
7. 4. 12. New payment and Collection
After clicking the “new rental” this form will pop up for the new payment and collection.
143
BY: CODE X
7. 4. 13. Search for Rental
This form shows the list of rental records. Just click the “select” on the right side of the record.
7. 4. 14. Settings
This form shows the system settings where you can change the above shown. Only the admin can
access this module.
144
BY: CODE X
7. 4. 15. Account
This form shows the account of the admin, the clerk, and the cashier. Only the admin can add user.
7. 4. 16. Rooms
This form shows the list of rooms and its description. Only the admin can delete rooms.
145
BY: CODE X
7. 4. 17. Add Rooms
The new room form is shown when you click “new room” under the “manage rooms”. The admin
and the clerk can add a room. The user needs to input the necessary details for the room to be able
to add it.
7. 4. 18. Profile
This form shows the account of the user where he can change his username and password.
146
BY: CODE X
Chapter VIII
Testing Plan
147
BY: CODE X
8.1 Introduction
Testing is being held by the system’s Testers. The Company aims in developing and
delivering a Software that meets the client’s expectations in executing the system, this will be
done by the company’s testing plans by testing the system’s functionalities and features in
each and every module of the system.
8.1.a Objectives
 Inform every results and errors to the programmer for the system’s revisions
and improvements.
 To ensure that the system is error-free and accurate before the testing phase
ends.
 To present the Testing phase documentation.
8.1.b Scope of the Test

The Testing phase will be handling from Unit, Integration testing to System
testing. This includes Functional, Performance, Usability, Compatibility, Security,
Acceptance, Alpha and Beta testing.
8.1.c Target Test Items

The BA Dormitory Management system has different modules that will be
tested to ensure reliability of the system.
The following are the modules to be tested individually:
SECURITY MODULE
This module keeps the system secure by allowing users to log in and
log out by using their respective accounts in the system.
 Log-in - allows the users to access by entering their Username and
Password.
 Log-out – allows the users to end their access in the system
BOARDER MODULE
This module is where all the boarders’ information is, in the system.
 View - it shows all the boarder’s information
RENT MODULE
In this module, is where the main transaction takes place.
148
BY: CODE X
 New Transaction – In this sub module, the system asks for the
Boarder’s information and where the process of payment is made.
 Records – where the records of payments are
 Print – this allows the user to print the transaction made by the boarder
 Revenue - This sub module the user is allowed to edit certain payment
amount.
SETTINGS MODULE
This module will let the user which is the admin, to change the fee
and manage rooms.
 Rental Fee – allows the admin to change the rental payment
 Rooms – allows the admin to add and manage rooms
CREATE USER ACCOUNT MODULE

This module allows user to fill up forms required for creating an
account.
MY ACCOUNT MODULE
This module allows the user to manage their account and log out from
the system.
 Account Settings- lets the user to manage their respective accounts
 Log out- terminates the user from the system
8.2 Testing Methodology

a. Unit Testing
In this phase, the team will be testing the system unit by unit by its module. It
will be a lot easier to identify errors or any unwanted behaviors in the system.
b. Integration Testing
In this part, modules of the system are tested and combined as a group to
ensure the system’s efficiency.
This test has two types, the Incremental test which includes:
o Bottom-up Approach
- where the lowest level components are tested first, then the
highest level components. The process is repeated until the
component at the top of the hierarchy is done testing.
149
BY: CODE X
o Top-down approach
the top integrated modules are tested and the sub-modules of
the module are tested step by step until the end of the related module
o Sandwich Testing
A combination of top-down testing and bottom up testing
A non-incremental test:
o Big Bang Testing
the developed modules are being combined together to form a
complete software system or major part of the system and used for
testing.
c. System Testing
Testing is made to evaluate the system’s compliance in its specified
requirements, its process is made on its scope and should require no
knowledge in the code and the logic of the system.
This includes the following:

o Compatibility Testing
Testing the application to ensure its compatibility with the
different computing environment
o Acceptance Testing
The system application is tested for its acceptability. Its
purpose is to evaluate the system’s compliance with business
requirements and deliberation.
o Alpha Testing
A type of acceptance testing; performed to identify all possible
issues/bugs before releasing the product to the user or the public.
o Beta Testing
A type of test performed by "real users" of the software

application in a "real environment".
150
BY: CODE X
8.3 Testing Process

8.3.a Test Schedules
ACTIVITY ESTIMATED TEST TIME PERSON IN-CHARGE
Duration Date Started Date Finished

Unit Test 1 day 2/26/18 2/26/18 Norrama Jala
Myr-hana Sali
Integration Test 1 day 2/27/18 2/27/18 Norrama Jala

Myr-hana Sali
Richa Rose Salvador
System Test 1 day 2/28/18 2/28/18 Myr-hana Sali
Richa Rose Salvador
Database Test 1 day 3/2/18 3/2/18 Richa Rose Salvador
Performance Test 1 day 3/4/18 3/4/18 Myr-hana Sali
Compatibility Test 1 day 3/6/18 3/6/18 Myr-hana Sali

Richa Rose Salvador
Usability Test 1 day 3/7/18 3/7/18 Norrama Jala
Alpha Test 1 day 3/7/18 3/7/18 Myr-hana Sali

Richa Rose Salvador
Beta Test 1 day 3/6/18 3/6/18 Myr-hana Sali
151
BY: CODE X
8.4 Resource and Responsibilities

8.4.a Testing Team
Richa Rose Salvador

Testing Engineer
Myr-hana Sali
Test Assistant
Roles:
 Designs test cases.
 Record, track, and analyze test results for Testing documentation.
 Provides test case’s results.
8.4.b Test Environment

Hardware Resources
 Laptops
 Flash Drive
 LAN for Networking
Software Resources
 OS (Windows 7,10)
 Paint, Photoshop
 Visual Studio
 Xampp
 Microsoft Word & Excel
 Web Browser (Mozilla Firefox, Chrome, Opera, Internet Explorer,
Microsoft Edge) for Database
 Visual Paradigm
152
BY: CODE X
Human Resources
RESOURCE TYPE DESIGNATION COMPOSITION PERSON IN CHARGE TASK
Programming Head 1 Daisa Mangking Corrects the

Team Programmer System errors
detected during
tests.
Testing Team Head Tester 2 Richa Rose Salvador Run tests and
Myr—hana Sali documents test
results.
Project Manager Project 1 Norrama Jala Supervises the
Manager testing phase and
revision status.
8.5 Deliverables
DOCUMENTS DESRIPTIONS PERSON IN CHARGE

Test plan Testing plan is for basis of Head tester
the team conducting
different types of tests.
Test cases The test cases are used for Testing team
basis in executing tests.
Test case result Test result are done after Testing team
conducting tests. It includes
the test cases and results
that will use by the
Programmers to debug and
fix errors.
Bug report Indicates the total passed Testing Team
and failed test cases.
8.6 Risk Issues
a. Schedule:
The team must be informed and aware by the said schedule given.
153
BY: CODE X
b. Requirements:
Changes in the system may affect the testing phase.
c. Management:
Effectiveness in the management must be made in the process of developing
the system.
8.7 Dependencies
 Staff Dependencies
The team should perform their best with accuracy and focus.
 Hardware Dependencies
The equipment that will be use must be ready, available and is in its
best condition.
 Software Dependencies
Software must be well conditioned.
154
BY: CODE X
8.8.1 Alpha Test Result

TEST DATA
Steps 1: Add New User Account - Clerk (Admin)

*Select “Accounts” Tile.
*Select the “New Account” Button.
*Input the First Name (Lauren) (No duplicate username) and Last name (Jauregui).
*Select an “Account Role” from the Combo box. Select (Clerk).
*Then Click “Save”. Note the username and password will be system generated.
 Scenario 1 Modify incorrect user info.
Steps 2: Settings (Admin)

*Select “Settings” Tile. The system will automatically load the “Settings” form.
*Select “Save” Button to edit the Settings.
*Input the ff. Miscellaneous “Advance (Months)” (1), “Deposit (Months)” (1).
*Input the ff. Add-ons Charge “Appliance/s” (100).
*Select penalties type Percentile (%)/In Amount (PHP100).
*Number of the days before the penalty applies on the amount due. Then Click “Save”
Button.
 Scenario 1 Empty fields for different settings.
Steps 3: Add New Room/s (Admin)

*Select “Rooms” Tile. The system will automatically load the “Rooms” form.
*Select “New Room” Button. Input necessary room details.
*Click “Save”.
Steps 4: Log In with the New Added User. (Case 1)

*Input the username and password.
 Scenario 1 Correct username and correct password
 Scenario 2 Incorrect username or incorrect password
 Scenario 3 Correct username and correct password but capitalized.
 Scenario 5 Correct username and correct password but user already login other
device.
Main Transaction
Steps 5: Add New Rent (Clerk or Admin)

*Select “Rent” Tile and Select “New Rental” Button.
*Select “New Border” for first time boarders and input necessary and optional fields.
*Select “Browse Border” for those who have rented and completed their contract before.
*Browse for room choice.
*Input Miscellaneous “Advance” (1) and “Deposit” (1), Rental Span (1).
*Input add-ons and select if “Free” or “With Charge”.
 Scenario 1: Modify incorrect input data.
 Scenario 2: Empty fields (System will not allow).
 Scenario 3: Paid amount is lesser than the amount due (System will not allow).
155
BY: CODE X
Steps 6: Add New User Account – Cashier (Admin)

*Select “Accounts” Tile.
*Select the “New Account” Button.
*Input the First Name (Camila) (No duplicate username) and Last name (Cabello).
*Select an “Account Role” from the Combo box. Select (Cashier).
*Then Click “Save”.
 Scenario 1 Modify incorrect user info.
Steps 7: Payment (Cashier and Admin)

*Select “Collection” Tile, click “New Payment” then Search for a member (Camila Cabello or
Lauren Jauregui).
*Click the “Select” and input the amount intended to pay. (2000)
*Select “Save” or “Save and Print”.
 Scenario 1. Modify payment details(allow cashier)
Steps 8: Billings (Cashier and Admin)

*Select “Billings” Tile then click “Print” button.
Steps 9: Collections and Payments (Cashier)

*Select “Collection” Tile, click “New Payment” then Search for a member (Camila Cabello or
Lauren Jauregui).
*Click the “Select” and input the amount intended to pay. (2000)
*Select “Save” or “Save and Print”.
 Scenario 1. Modify payment details(allow cashier)
Steps 10: Extend Rental (Clerk and Admin)

*Select “Rent” Tile and Search for the boarder (Barrack Obama).
*Click “Select” button and click “Extend” button.
*Input number of extended month/s.
*Click “Save”.
Steps 11: End Rental (Clerk and Admin)

*Select “Rent” Tile and Search for the boarder (Barrack Obama).
*Click “Select” button and click “End” button.
*Click “Save”.
Steps 12: New Boarder (Clerk and Admin)

*Select “Boarder” Tile and click “New Border”.
*Input boarder necessary and optional information then click “Proceed to Rent
156
8.8.2 Developer’s Test Cases
User - Admin
Use Case Number: UC 01 Date:
BA Dormitory Management System Test Case No: STATUS
Project Name:
Log in App Version No:
This Test is conducted for the current user to ensure that Build No: % Passed
Test Description:
they can Log in and manipulate the system. Total Duration: Test
A. The tester must read all the documents needed for Total No. of passed test case: Cases
conducting the Testing phase. Total No. of failed test case:
B. The tester must conduct the testing phase with at Total no. of tested test
% Tested
Setup for Test: least 3 computers – networked together. cases:
Test
C. The tester must have an account for each type of user.
Cases
D. The tester must report everything to the Programming Total no. of test cases:
Team after the execution of the system.
STEP ACTION EXPECTED RESULTS ACTUAL RESULTS PASS/FAIL
A Log in Module
*The user can log in to the system.
*Splash screen will display to load the components of
Input the correct username and
A1 the system.
password on the log in form.
*A main form will display based on the user’s access
level.
Input the incorrect username and *The user can’t log in to the system.
A2
password on the log in form. *(Please enter a valid username and password.)
Input incorrect username and incorrect *The user can’t log in to the system.
A3
password in the log in form. *(Please enter a valid username and password.)
Input the correct username and *The user can’t log in to the system.
A4
incorrect password in the log in form. *(Please enter a valid username and password.)
Note: Mark P (passed) & F (failed) for every item tested for the current build
Status
P Pass Prepared By: Verified By:
F Fail
Richa Rose R. Salvador Norrama Jala
Test Engineer Project Manager
157
Project Name:
Border Module App Version No:
Build No:
Test Description: This Test is conducted on adding, editing a border.
Total Duration: % Passed
A. The tester must read all the documents needed Total No. of passed test Test Cases
for conducting the Testing phase. case:
B. The tester must conduct the testing phase with at Total No. of failed test case:
least 3 computers – networked together. Total no. of tested test
Setup for Test: C. The tester must have an account for each type of cases:
% Tested
user.
Test Cases
D. The tester must report everything to the
Total no. of test cases:
Programming Team after the execution of the
system.
PASS/
STEP ACTION EXPECTED RESULTS ACTUAL RESULTS
FAIL
A Border Module – New Border
A1 Click Border icon. “Border Record” form will be displayed.
A2 Select “New Border” Tile. The “New Border” form will be displayed.
*The Inputted information will be displayed
Input the information needed. (required * If required information not inputted, message will appear -
A3
or not required) “Border first name, Last name and contact information are
required.”.
The “New Rental” form will be displayed along with the
A4 Select “Proceed to Rental” Button.
inputted border information.
A5 Select “Browse Room”. “Browse Room” form will be displayed.
A6 Select desired room. Back to “New Rental” form.
*The Inputted information will be displayed.
Input the information needed. (required
A7 * If required information not inputted, message will appear -
or not required)
“Room information is required.”.
158
A new data will be added and a Message box will appear -
A8 Select “Save” Button
“New rent and border successfully saved.”
Select “Edit” on the Border you desire to The information of the selected border will be displayed on
A9
edit. the “Edit Border” form.
Input the information you want to edit. * If required information not inputted, message will appear -
A10
(required or not required) “Border first name, Last name and contact information are
required.”.
A new data will be added and a Message box will appear –
“Border successfully saved.”
B Border Module - View Guardian
B1 Click Border icon. “Border Record” form will be displayed.
B2 Select “View Guardian” Tile. The “Guardian record” form will be displayed.
Select “Edit” on desired Guardian
B3 The “Edit Border” form will be displayed.
information.
B4 Input the information needed. *The Inputted information will be displayed.
B5 Select save button.
Status
F Fail
159
Project Name:
Rent Module App Version No:
Build No:
Test Description: This Test is conducted on editing, adding, ending a rental. % Passed
Total Duration:
Test
A. The tester must read all the documents needed for Total No. of passed test
Cases
conducting the Testing phase. case:
Setup for Test: least 3 computers – networked together. Total no. of tested test % Tested
C. The tester must have an account for each type of user. cases: Test
D. The tester must report everything to the Programming Cases
PASS/
FAIL
A Rent Module – Adding a New Rental Information
A1 Select “Rent” Tile. The “Rental Record” form will be displayed.

A2 Select “New Rental” Tile. The “New Rental” form will be displayed.
A3 Select “New Border” Tile. The “New Border” form will be displayed.
A4
required.”.
The “Search Border” form will be displayed, only available
A5 Select “Browse Border” Tile. borders will be displayed – borders with current Rental record
will not be displayed.
Browse Room Tile will only valid if a Border has been selected.
A6 Select “Browse Room” Tile.
“Browse Room” form will be displayed.
A7 Select a preferred room. Room details will be displayed on New Rental form.
160
A8 Select Add-ons Tile. Displays Add-ons form.
A9 Select “Save” button.
“New Rent and border successfully saved.”
Rent Module - Editing an existing Rental
B
Information
B1
B2
required.”.
Displays Update Border form along with the selected border
B3 Select Update Border button.
information.
B4 Select Update Room button. Displays Browse Room form with the room information.
B5 Select “Save” button.
“Rental Information successfully saved.”
Status
F Fail
161
Project Name:
Rooms Module (Admin) App Version No:
This Test is conducted on editing, adding, ending a Room Build No:
Test Description: % Passed
information. Total Duration:
Test Cases
A. The tester must read all the documents needed for Total No. of passed test case:
conducting the Testing phase.
Total No. of failed test case:
B. The tester must conduct the testing phase with at
Setup for Test: least 3 computers – networked together. Total no. of tested test cases:
% Tested
C. The tester must have an account for each type of user. Test Cases
D. The tester must report everything to the Programming Total no. of test cases:
PASS/
FAIL
A Rooms Module – Adding a new Room
A1 Select “Rooms” Tile. The “Manage Room” form will be displayed.
A2 Select “New Room” Button. “New Room” form will be displayed.

A3 * If required information not inputted, message will appear -
or not required)
“ Room Name/Code/No is required .”
The new Room information will be saved and a Message box
A4 Select “Save” Button.
will appear -“New Room successfully saved.” .
B Rooms Module - Editing an existing Room information

Select “Edit” button on the selected “Edit Room” form and the selected room information will be
B1
Room information you wish to edit. displayed.
162
B2 * If required information not inputted, message will appear -
or not required)
“Room Name/Code/No is required.”
The new account information will be saved and a Message
B3 Select “Save” Button.
box will appear - “Room successfully updated.”
Status
F Fail
163
Project Name:
Collection Module App Version No:
This Test is conducted on editing, adding a Collection Build No:
Test Description:
information. Total Duration: % Passed
A. The tester must read all the documents needed Test Cases
Total No. of passed test case:
for conducting the Testing phase.
% Tested
user.
Test Cases
system.
PASS/
FAIL
Collection Module – Adding a New
A
Collection
A1 Select “Collection” Tile. The “Payment and Collection” form will be displayed.
A2 Select “New Collection” Button *The “New Payment and Collection” form will be displayed
A3 Select “Search Rent”. The “Search Rental” form will be displayed.

The selected Rental information will be load on “New
A4 Select desired Rental information.
Payment and Collection” form.
A5 Input the information needed. *The Inputted information will be displayed.
Press “Ok” button to confirm inputted An amount will be displayed corresponding to the inputted
A6
information. information.
A7 Input the desired amount. Save only button will be enabled.
A8 Select “Save Only” button. Message box will appear – “Payment Successfully saved.”
164
B Collection Module – Editing a Collection
Select “Edit” button on Collection
B1 “Edit Payment and Collection” form will be displayed.
information you wish to edit.
Input the information needed. (checked
B2 Payment Information will be displayed.
or unchecked)
B3 Select “Save Only” button. Message box will appear – “Payment successfully saved.”
Message box will appear – “Payment successfully saved.”
B4 Select “Save and Print”.
Printable Collection information will be displayed.
Status Prepared By: Verified By:

P Pass
F Fail Richa Rose R. Salvador Norrama Jala
165
Project Name:
Settings Module App Version No:
This Test is conducted on editing the Settings Build No:
Module. Total Duration:
Test Cases
A. The tester must read all the documents needed Total No. of passed test case:
for conducting the Testing phase. Total No. of failed test case:
least 3 computers – networked together. cases:
Setup for Test: C. The tester must have an account for each type of % Tested
user. Test Cases
D. The tester must report everything to the Total no. of test cases:
system.
PASS/
FAIL
A Settings Module
A1 Select “Settings” Tile. The “Update Settings” form will be displayed.
Input the information needed. (valid or *The Inputted information will be displayed.
A2
null) * If inputted null value, message will appear
box will appear - “New Settings successfully saved.”

P Pass
166
Project Name:
Billings Module App Version No:
Build No:
Test Description: This Test is conducted on deleting a Billing data. % Passed
Total Duration:
Test
Cases
Setup for Test: % Tested
C. The tester must have an account for each type of cases:
Test
user.
Cases
Programming Team after the execution of the system.
PASS/
FAIL
A Billings Module
A1 Select “Billings” Tile. The “Billing Record” form will be displayed.
Filter keyword/s in the search column
A2 Displays sets of Billing Records searched with correct details.
provided.
Input keyword/s in the search box provided. Displays sets of products searched with correct details.
A3
(valid or not related) * Displays on form "No Billings yet".
Select “Delete” Button of the selected Billing Message box will appear – “Are you sure you want to delete this
A4
record. billing?”
Selected billing will be deleted.
A5 If clicked “Yes”, “No”.
Back to current search in Billing record form.
A6 Select “Print Bill”. Printable Billing information will be displayed.

P Pass
167
Project Name:
Account Module App Version No:
This Test is conducted on editing, adding and deleting Build No:
an Account information. Total Duration:
Test
Cases
Test
user.
Cases
PASS/
FAIL
A Account Module – Adding a New Account
A1 Select “Account” Tile. The “New Rental” form will be displayed.
A2 Select “New Account” Button *The “New Border” form will be displayed.
Input the information needed. (required * Upon clicking “Save” - If required information not inputted,
A3
or not required) message will appear (First Name, Last Name, Username and
Password are required.)
Input Username. (more than 6 characters
A4 * Upon clicking “Save” - message will appear (Username must be
or less than)
at least 6 characters long.)
Input Password. (more than 6 characters
A5 * Upon clicking “Save” - message will appear (Password must be at
or less than)
least 6 characters long.)
Input Password. (Retyping the Wrong * Upon clicking “Save” - message will appear (Password did not
A6
Password) match.)
A New Account will be successfully saved and a Message box will
appear “New Account Successfully saved”.
B Account Module – Editing an Account
Select “Edit” button on the selected “Edit Account” form and the selected room information will be
B1
Account information you wish to edit. displayed.
168
B2
The new account information will be saved and a Message box will
B3 Select “Save” Button.
appear - “Account successfully updated.”
C Account Module – Deleting an Account
Select “Delete” button on the selected A message box will appear – “Are you sure you want to delete ___
C1
Account information you wish to delete. Account?”
The Account will be deleted.
C2 Select “Yes”.
Manage Account will be displayed.

P Pass
169
Project Name:
Profile Module App Version No:
Build No:
Test Description: This Test is conducted on editing My Account. % Passed
Total Duration:
Test
Cases
Test
user.
Cases
PASS/
FAIL
Profile Module – Editing My Account
A
Profile
The “My Account” form will be displayed.
A1 Select “Profile” Tile
Current User Account Information will be displayed.
A2 * Upon clicking “Save” - If required information not inputted,
or not required)
message will appear (Username and Password are required.)
A3 * Upon clicking “Save” - message will appear (Username must
or less than)
be at least 6 characters long.)
A4 * Upon clicking “Save” - message will appear (Password must
or less than)
Input Password. (Retyping the Wrong * Upon clicking “Save” - message will appear (Password did
A5
Password) not match.)
The New Account changes will be successfully saved and a
Message box will appear “Account Successfully updated”.
170

P Pass

Project Name:
Log out App Version No:
Build No:
Test Description: This Test is conducted on Logging out. % Passed
Total Duration:
Test
Cases
Test
user.
Cases
PASS/
FAIL
A Logging out
Message box will appear – “Are you sure you want to log
A1 Select “Log out” button.
out?”
Logs out from the current user.
A2 Select “Yes”
Log in Form will be displayed.
171

P Pass
User – Clerk

Project Name:
Adding New Boarder’s and Clerk module. App Version No:
To determine the functionality and discrepancies of Build No:
the module. Total Duration:
Test
Cases
least 3 computers – networked together.
C. The tester must have an account for each type of
Total No. of failed test case: Test
user.
Cases
172
PASS/
STEP ACTION EXPECTED RESULT ACTUAL RESULT
FAIL
A Login
The system shall determine if the username and

The admin/user inputs valid
A1 password combination is correct and shall their
username and password
respective interface.
Click “Login” button then the
The registered user will be redirected to the features of
A2 system checks the admin/user is a
the system.
valid user.
B Rent
Rental record will show.
B1 The user clicks the “Rent” button
“Search” bar and “New rental”, “edit” button will show.
B2 The user clicks the “ Search “ button List of names will show.
New form will show.

The user can “update border”, “Update Room”, “add-
B3 The user clicks the “Edit” button
ons”, “Extend Rental” or “End Rental”; “Save” and
“Cancel” button will show.
New form will show and can add new border.
The user clicks the “New Rental” New buttons will show such as “New border”, “browse
B4
button border”, “Browse Room”, “add-ons”, “Save” and
“Cancel”.
The user clicks the “Update border” The user can update the borders information and their
B3.1
button. guardian information and save.
The user clicks the “Update Room” The user can update/change their room they want and
B3.2
button. save.
The user clicks the “Add-ons”
B3.3 The user can add a new items/appliances and save.
button.
The user clicks the “Extend Rental”
B3.4 The user can extend the rental of the borders.
button.
The user clicks the “End Rental”
B3.5  The user can end/void the rental of the borders.
button.
B3.6 The user clicks the “Save” button.  All the information will updated.
B3.7 The user clicks the “Cancel” button.  The form will close.
173
The user clicks the “New border”  The user can add a new border and will proceed to
B4.1
button. rental.
The user clicks the “Browse border”  The user can browse an old border that finished the
B4.2
button contract.
The user clicks the “Browse Room”

B4.3  List of rooms will show.
button
The user clicks the “Add-ons”  The user can add a new items/appliances to the border
B4.4
button. with charge or free.
B4.5 The user clicks the “Save” button.  The system will save all information.
B4.6 The user clicks the “Cancel” button.  The form will be close and it will not be saved.
C Border
 Borders Record will show.
C1 The user clicks the “Border” button.  New buttons will show such as “New Border”, “View
Guardian”, “Edit” and “Search” bar.
C2
button. rental.
 The borders guardians’ record will show.
The user clicks the “View Guardian”
C3  The system allowed the user to edit the borders
button.
guardian information.
 The system should allowed the user to edit the borders
C4 The user clicks the “Edit” button
information and guardian information.
D Billings
The user clicks the “Billings”  The system will show to user of the Billing records of
D1
buttons. each border.
The user clicks the “Print bill”
D2  The system will print the borders bill.
buttons.
E Profile
174
E1 The user clicks the “Profile” button.  The user can change their username and password only.
F Log-out
The user clicks the “Log-out”
F1  The system will close.
button.

P Pass
175
User – Cashier

Project Name:
New Payment and Collection Module App Version No:
To determine the functionality and discrepancies of Build No:
the module. Total Duration:
Test
Cases
Total No. of failed test case: Test
user.
Cases
PASS/
STEP ACTION EXPECTED RESULT ACTUAL RESULTS
FAIL
A Login
. The system shall determine if the username and password
A1 combination is correct and shall show the users their respective
username and password.
interface.
A2 system checks the The registered user will be redirected to the features of the system.
admin/user is a valid user.
Collection Module – Adding a
A
New Collection
B1 Select “Collection” Tile. The “Payment and Collection” form will be displayed.
Select “New Collection”
B2 *The “New Payment and Collection” form will be displayed
Button
B3 Select “Search Rent”. The “Search Rental” form will be displayed.
176
Select desired Rental The selected Rental information will be load on “New Payment and
B4
information. Collection” form.
Input the information
B5 *The Inputted information will be displayed.
needed.
Press “Ok” button to confirm An amount will be displayed corresponding to the inputted
B6
inputted information. information.
B7 Input the desired amount. Save only button will be enabled.
B8 Select “Save Only” button. Message box will appear – “Payment Successfully saved.”
C Search rent
The user clicks the “search
C1 List of names will show.
rent” button.
The user will clicks the name
C2 The advance payment button will show.
in the list
D Advance payment
The user clicks “advance
D1 Advance payment form will show.
payment” button
D2 The user clicks “save” button The system will save all the information.
The user clicks “save and
D3 The system will save the information and print.
print” button
E Logout
The user clicks “Log out”
E1 The user will be logged-out from the system.
button.

P Pass
177
BY: CODE X
8.8.3 Beta Test Results

TEST DATA
1. Please list any glitches, spelling/formatting errors, or parts of this system that
were inaccessible.
- None. It was all good.
2. What didn’t work as expected?
- Nothing I think. They were all working.
3. What’s the most confusing part of the system?
- The main transaction at first. But I got through it anyways.
4. If you could change one thing about the system, what would it be to make it
user-friendly and useful?
- Nothing that I could think of as of the moment.
5. What do you like about this system?
- The color and the environment as a whole.
178
BY: CODE X
6. Please rate your experience while navigating through the system from 1 to 5.
- 4.
7. Are the links clearly labeled?
- Yes.
8. I can access information quickly on the system.
i. Agree Disagree
9. It’s easy to remember where to find things.
i. Agree Disagree
10.Forms have the right amount of information.
i. Agree Disagree
179
BY: CODE X
Formatted: Left: 1", Width: 8.5", Height: 11"
Chapter IX
Training Phase
180
BY: CODE X
9.1 Description
The user of the system will undergo a training, the team will be teaching the user on how
the system will work. The training phase will only be exclusive to the users of the system.
9.2 Training Objectives

This phase is a guide for the training team to educate the user on how to manipulate the
system and to effectively use the system to its outmost purpose.
The objective of the Training Plan is to meet the difference procedures to meet the
training requirements. The goals are:
 To be able to help the user to develop their skills and understanding about the
system.
 To be able to train and introduce the system to the client, teach and train the
functionalities and features of the system.
 To be able to meet the requirements that is expected by the client.
9.3 Scope of the Training

Training will focus on the different features of the system, which will include the
following:
 Guiding the user on how the system works.

 Understand the system with ease.
 To guide the user’s functionalities of the system.
9.4 Target Trainees

Trainees involved in BA Dormitory Management System are the following:
 Owner of the BA Dormitory

 Officer in Charge/Landlord
181
BY: CODE X
9.5 Training Team
Training Team
Richa Rose R.
Daisa A. Mangking Jefford Eyas
Salvador Assistant Trainer
Training Engineer Assistant Trainer
9.6 Training Policies

The following policies and guidelines should fulfill by the trainees and trainers during the
training process that will be held at the BA Dormitory are:
 The developers of the System should explain each modules/functionalities of the

system to the user.
 The training will be conducted on the said date that has been agreed by the
training team and the client.
9.7 Training Reference

The team is to deploy the BA Dormitory Management System training reference.
9.8 Training Approach

9.8.1 Identification of the Training Needs
The developers of the system should have the knowledge of all the functions of
the system and should be prepared to conduct the training to the user of the system. Each
member of the team must do their assigned task in order to succeed.
182
BY: CODE X
9.8.2 Training Requirements

These are the following requirements, needed in order to train the user and
should be prepared before the training begin.
 2 or 3 Laptops
 User Manual
 Developed System
9.8.3 Training Venue

The training will be held at BA Dormitory.
9.8.4 Training Schedule

The training should be scheduled and planned by the client and the team.
9.8.5 Steps in Conducting Training

 Provide brief Introduction of the System
 Step-by-step procedure of the flow of the system
 Functionalities of the system will be explained
9.9 Roles and Responsibilities
Trainer Position Responsibilities
Daisa A. Mangking Chief Trainer She is responsible for guiding

and explaining to the users of
the system on the
functionalities and flow.
183
BY: CODE X
Richa Rose R. Salvador Assistant Trainer He is responsible for assisting

the Chief Trainer and
providing brief introduction
of the system.
Jefford Eyas Assistant Trainer He is responsible for assisting
the Chief Trainer and
providing brief introduction
of the system.
9.10 Training Curriculum
Topic Duration Trainer

Part I. Overview 30mins Daisa A. Mangking
Part II. System Summary 25mins Richa Rose R. Salvador
Log in 25mins Daisa A. Mangking

 Connection Setting
Profile 20mins Jefford D. Eyas

 Account Setting
 Log Out
Boarder 30mins Jefford D. Eyas
 Add Boarder
 Edit Boarder Details
 View List
Collection 35mins Richa Rose Salvador
 New Payment
 Edit Payment Details
 View List
184
BY: CODE X
v Room 35mins Richa Rose Salvador

 Add room
 Edit Room Details
 View List
Users 30mins Jefford D. Eyas

 Add User
 Edit User Details
 View List
Settings 30mins Jefford D. Eyas
 Rental Fees
 Rooms
Rent 45mins Daisa A. Mangking

 Add Rental
 Edit Rental Details
 View Rental Transactions
9.11 Evaluation
9.11.1 Module of Evaluation
After the training, there is an evaluation form will be given that determines the
performance of each trainee as they demonstrate and explain the system.
Training Results
The training team will be giving evaluation form to the trainees at the end of the training
session. That will determine whether the system has met the requirements.
Rate:
1- Poor (Needs Improvement) 4 - Very Satisfactory
2- Fair 5 - Excellent
3- Satisfactory
185
BY: CODE X
9.11.2 Evaluation Summary

The user of the system has understood the functionalities and features of the
system. The training is so effective and has met all the objective of the system which also helped
the users learn on how to use the system. After training, the users will be able to use the system
effectively.
186
BY: CODE X
Appendices
187
BY: CODE X
Appendix A – Training Evaluation Forms
Training Evaluation Form

For the participants in WMSU-MPC (Multi-purpose Cooperative)
Date: _____________
Title and location of training: _______________________________
Trainer: _____________________________
Instructions: Please indicate your level of agreement with the statements listed below in #1‐11.
Strongly Agree Neutral Disagree Strongly

Agree Disagree
1. The objectives of the training

Were clearly defined.
2. Participation and interaction

Were encouraged.
3. The topics covered were relevant

To me.
4. The content was organized and

easy to follow.
5. The materials distributed were

helpful.
6. This training experience will be

useful in my work.
7. The trainer was knowledgeable

About the training topics.
188
BY: CODE X
8. The trainer was well prepared.
9. The training objectives were met.
10. The time allotted for the training

was sufficient
11. The meeting room and facilities
12. What did you like most about this training?
13. What aspects of the training could be improved?
14. How do you hope to change your practice as a result of this training?
15. What additional adult ESL trainings would you like to have in the future?
16. Please share other comments or expand on previous responses here.
Thank you for your feedback!
189
BY: CODE X
Appendix B- Certificates
190
BY: CODE X
Formatted: Left, Space After: 8 pt, Line spacing:

Multiple 1.08 li, Widow/Orphan control, Adjust space
between Latin and Asian text, Adjust space between
Asian text and numbers
191
Appendix C- Test Cases Results
Use Case Number: UC 01 Date: 11/3/18

BA Dormitory Management System Test Case No: 01 STATUS
Project Name:
Log in App Version No: 01
Build No: 01
This Test is conducted for all the users to ensure that they
% Passed
Test Description: can Log in and manipulate the system. 93%
Total Duration: 00:02:30 Test Cases
A. The tester must read all the documents needed for Total No. of passed test case: 32
conducting the Testing phase. Total No. of failed test case: 12
B. The tester must conduct the testing phase with at least Total no. of tested test cases: 32
Setup for Test: 3 computers – networked together. % Tested
100%
Total no. of test cases: 32
D. The tester must report everything to the Programming
PASS/
FAIL
A Log in (All User)
Input the correct username and *Splash screen will display to load the components of the
A1 Same as expected P
password on the log in form. system.
*A main form will display based on the user’s access level.
Input the correct username and incorrect *The user can’t log in to the system.
Status
P Pass
F Fail Prepared By: Verified By:

Test Engineer Project Manager 192
Project Name:
Add New User Account App Version No: 01
This Test is conducted on adding a new Account user Build No: 01
Test Description:
like Administrator, Cashier and Clerk. Total Duration: 00:04:30 % Passed
93%
32
B. The tester must conduct the testing phase with at Total No. of failed test case: 12
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
Add New User Account
A
(Administrator/Cashier/Clerk)
A1 Select “Accounts” Tile. The “Manage Account” form will be displayed. Same as expected P
A2 Select “New Account” Button. The “New Account” form will be unlock. Same as expected P
or not required) “First name, Last name, Username and Password are
required.”.
A new account will be added and a Message box will appear -
A4 Select “Save” Button Same as expected P
“New Account successfully saved.” .

P Pass
193
Project Name:
Edit User Account (Current User) App Version No: 01
This Test is conducted on editing an Account user like Build No: 01
Administrator, Cashier and Clerk. Total Duration: 00:02:30
Test 93%
32 Cases
32
C. The tester must have an account for each type of user. cases: Test 100%
PASS/
FAIL
Edit User Account
A
A1 Select “Profile” Tile. The “My Account” form will be displayed. Same as expected P
A2 * If required information not inputted, message will appear - Same as expected P
or not required)
“Username and Password are required.”.
A3 Select “Save” Button. Same as expected P
box will appear -“Account successfully updated.” .

P Pass
194
Project Name:
Edit User Account (Admin’s Side) App Version No: 01
This Test is conducted on editing an Account user like Build No: 01
Administrator, Cashier and Clerk. Total Duration: 00:02:00 93%
Test Cases
Total No. of failed test case: 12
Setup for Test: least 3 computers – networked together. Total no. of tested test cases: 32
% Tested
C. The tester must have an account for each type of user. 100%
Test Cases
D. The tester must report everything to the Programming Total no. of test cases: 32
PASS/
FAIL
Edit User Account
A
A1 Select “Accounts” Tile. The “Manage Account” form will be displayed. Same as expected P
*The Search form will be displayed
*The user can filter its search by name or employee number
A2 Select “Search” Button Same as expected P
*The user can input the search keyword of the Member
*The Search result will be displayed
Select “Edit” Button for the selected The Registration Form of the selected Member will be
Member. displayed with its information.
or not required) “First name, Last name, Username and Password are
required.”.
box will appear -“Account successfully updated.” .
Prepared By: Verified By:
Status
P Pass
F Fail
195
Project Name:
Terminate Active User Account App Version No: 01
This Test is conducted on deleting an Account user Build No: 01
Test Description:
like Administrator, Cashier and Clerk. Total Duration: 00:01:00 % Passed
93%
Total No. of passed test case: 32
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
Terminate Active Account User
A
(Administrator)
A1 Select “Accounts” Tile. The “Management Account” form will be displayed. Same as expected P
A2 Select “Search” Button *The user can filter its search by username. Same as expected P
A confirmation Message will appear “Are you sure you want
Select “Delete” Button for the selected
A3 to delete “ ” Account? (Yes/No)” if yes. The account has Same as expected P
Member.
successfully deleted.

P Pass
196
Project Name:
Add New Boarder App Version No: 01
Build No: 01
Test Description: This Test is conducted on adding a new Boarder. % Passed
Total Duration: 00:01:30 93%
Test Cases
A. The tester must read all the documents needed Total No. of passed test case: 32
for conducting the Testing phase. Total No. of failed test case: 12
32
100%
user. Test Cases
D. The tester must report everything to the Total no. of test cases: 32
system.
PASS/
FAIL
Add New Boarder
A
(Administrator/General Manager/Clerk)
A1 Select “Boarder” Tile. The “Boarder Record” form will be displayed. Same as expected P
A2 Select “New Boarder” Button. The Boarder Registration form will be displayed. Same as expected P
Input the information needed. (required * If required information not inputted, message will appear
or not required) (Boarder First Name, Last Name and Contact information are
required)
The “New Rental” form will be displayed.
A4 Select “Proceed to Rent” Button Same as expected P
*Boarder will only be saved if a rental record has been added.

P Pass
197
Project Name:
Edit Boarder Information App Version No: 01
This Test is conducted on editing a Boarder’s Build No: 01
Information. Total Duration: 00:03:30
Test 93%
32 Cases
Setup for Test: 32 % Tested
Test 100%
user.
Cases
PASS/
FAIL
Edit Boarder
A
information (Administrator/Cashier/Clerk)
A1 Select “Boarder” Tile. The “Edit Boarder” form will be displayed. Same as expected P
A2 Select “Search” Button *The user can filter its search by name Same as expected P
Select “Edit” Button for the selected The Registration Form of the selected Member will be displayed with
Boarder. its information.
Input the information needed. (required or
A4 * If required information not inputted, message will appear - “First Same as expected P
not required)
name, Last name, Username and Password are required.”.
A boarder will be successfully modified and a Message box will appear
(Boarder Successfully saved).

P Pass
198
Project Name:
Adding a New Rental Record App Version No: 01
Build No: 01
Test Description: This Test is conducted on adding a new Rental Record. % Passed
Total Duration: 00:01:30
Test 93%
32 Cases
Test 100%
user.
Cases
PASS/
FAIL
Adding a New Rental Record – New Border
A
(Administrator/Clerk)
A1 Select “Rent” Tile. The “New Rental” form will be displayed. Same as expected P
A2 Select “New Border” Button *The “New Border” form will be displayed. Same as expected P
Input the information needed. (required * If required information not inputted, message will appear
or not required) (Boarder First Name, Last Name and Contact information are
required)
The “New Rental” form will be displayed.
A4 Select “Proceed to Rent” Button Same as expected P
*Boarder will only be saved if a rental record has been added.
A5 * If required information not inputted, message will appear Same as expected P
or not required)
“Room information is required”.
A boarder and a rental record will be successfully modified and a
A6 Select “Save” Button Message box will appear “New Rent and Border Successfully Same as expected P
saved”.

P Pass
199
Project Name:
Edit Rental Record App Version No: 01
This Test is conducted on editing an existing Rental Build No: 01
Record. Total Duration: 00:01:30
Test 93%
32 Cases
Test 100%
user.
Cases
PASS/
FAIL
Edit Rental Record
A
(Administrator /Clerk)
A1 Select “Rent” Tile. The “Rental Record” form will be displayed. Same as expected P
Select “Edit” Button for the selected The Edit Rental Form of the selected Record will be displayed
Boarder. with its information.
You can either choose “Update Border”,
A4 “Update Room”, “Add-ons”, “Extend The corresponding form will be displayed. Same as expected P
Rental” or “End Rental”.
A5 *The Inputted information will be displayed Same as expected P
or not required)
A boarder will be successfully modified and a Message box
will appear - “Rental Information Successfully saved”.

P Pass
F Fail Richa Rose R. Salvador Norrama Jala 200
Project Name:
Terminating an Existing Rental Record App Version No: 01
This Test is conducted on terminating an existing Build No: 01
Test Description:
Rental Record. Total Duration: 00:02:30 % Passed
93%
32
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
Terminating an Existing Rental Record
A
*The record can be filtered by room no., status, name of the
A2 Select “Search” Button Same as expected P
occupant or date in/out
Select “Edit” Button for the selected The selected Rental record will be displayed with its
record. information.
*A message box will appear – “The rent will be marked as
closed or void. Would still like to continue?”
A4 Select “End Rental” button Same as expected P
*If clicked “Yes” - The “Rent status” will be changed to
“Closed/Void”

P Pass
201
Project Name:
Editing a Guardian’s Record App Version No: 01
This Test is conducted on editing an existing Build No: 01
Test Description:
Guardian’s Record. Total Duration: 00:02:30 % Passed
93%
32
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
Editing a Guardian’s Record
A
(Administrator /Clerk)
A1 Select “Border” Tile. The “Border Record” form will be displayed. Same as expected P
Select “View Guardian” Button The “Guardian Record” form will be displayed.
Select “Edit” Button for the selected The selected Guardian record will be displayed with its
Guardian. information.
A4 Input the information needed. *The Inputted information will be displayed Same as expected P
A boarder will be successfully modified and a Message box

will appear - “Border Successfully saved”.

P Pass
Project Name:
Adding a New Payment App Version No: 01
This Test is conducted on adding a new Rental Build No: 01
Test Description:
Payment. Total Duration: 00:01:30 % Passed
93%
32
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
Adding a New Payment
A
(Administrator /Cashier)
A1 Select “Collection” Tile. The “Payment and Collection” form will be displayed. Same as expected P
A2 Select “New Payment” Button The “New Payment and Collection” form will be displayed. Same as expected P
A3 Select “Search Rental” Button. The List of Rental record will be displayed. Same as expected P
Select/Search an item of Rental record in The Registration Form of the selected record will be displayed
the list view. with its information.
A5 Select “Advance Payment” Button The “Advance Payment” form will be displayed. Same as expected P
A6 Input the information needed. Same as expected P
*”Advance Payment” form will be load
Input the information needed -- The
A7 system will require you to pay at least 1 *Save button will be enabled. Same as expected P
month rental fee.
A Rental Payment will be successfully created and a Message
A8 Select “Save” button. Same as expected P
box will appear - “Payment Successfully saved”.
203
Project Name:
Adding a New Room App Version No: 01
This Test is conducted on adding a new Room Build No: 01
information. Total Duration: 00:01:30 93%
Test Cases
32
100%
user. Test Cases
system.
PASS/
FAIL
Adding a New Room
A
A1 Select “Rooms” Tile. The “Manage Room” form will be displayed. Same as expected P
A2 Select “ New Room” button The “New Room” form will be displayed. Same as expected P
A3 *If required information not inputted, message will appear Same as expected P
or not required)
“Room Name/Code/No is required”.
A new Room will be successfully created and a Message box
will appear - “New Room Successfully saved”.

P Pass
204
Project Name:
Editing a Room App Version No: 01
This Test is conducted on editing a Room Build No: 01
Test Cases
32
100%
user. Test Cases
system.
PASS/
FAIL
A Editing a Room (Administrator/ Clerk)

A2 Select “Search” Button *The user can filter its search by Room number Same as expected P
Select “Edit” Button for the selected Room The selected Room record will be displayed with its
A4 *If required information not inputted, message will appear Same as expected P
or not required)
“Room Name/Code/No is required”.
A5 Select “Save” Button. will appear - “Room Successfully saved”. Same as expected P

P Pass
Project Name:
Changing an availability of a Room App Version No: 01
This Test is conducted on changing an availability of Build No: 01
a Room. Total Duration: 00:01:30 93%
Test Cases
32
100%
user. Test Cases
system.
PASS/
FAIL
Changing an availability of a Room
A
A2 Select “Search” Button *The user can filter its search by Room number Same as expected P
Select “Edit” Button for the selected The selected Room record will be displayed with its
Room information. information.
A4 Check the checkbox for Not Available. *The checkbox will be checked. Same as expected P
will appear - “Room Successfully saved”.

P Pass
206
Project Name:
Search Module App Version No: 01
Build No: 01
Test Description: This Test is conducted on Search boxes/filters. % Passed
Total Duration: 00:01:30 93%
Test Cases
Total No. of failed test case: 12 100%
user. Test Cases
system.
PASS/
FAIL
Search Module
A (Administrator/Clerk/Cashier)
Input keyword/s in the search box
A1 Displays sets of products searched with correct details. Same as expected P
provided.
Input keyword/s in the search box
A2 provided but is not related to any of the Displays on form "No Results Found". Same as expected P
products present.

P Pass
207
User - Admin
Project Name:
Log in App Version No: 01
This Test is conducted for the current user to ensure that Build No: 01
they can Log in and manipulate the system. Total Duration: 00:01:20 93%
Test Cases
conducting the Testing phase. Total No. of failed test case: 12
B. The tester must conduct the testing phase with at least Total no. of tested test cases: 32
Setup for Test: 3 computers – networked together. % Tested
100%
D. The tester must report everything to the Programming
STEP ACTION EXPECTED RESULTS ACTUAL RESULTS PASS/FAIL
A Log in Module
*Splash screen will display to load the components of
Input the correct username and
A1 the system. Same as expected P
password on the log in form.
*A main form will display based on the user’s access
level.
Input the correct username and *The user can’t log in to the system.
incorrect password in the log in form. *(Please enter a valid username and password.)
Status
F Fail
Richa Rose R. Salvador Norrama Jala Melanie L. Ledesma
Test Engineer Project Manager BA Dormitory Landlady
208
Project Name:
Border Module App Version No: 01
Build No: 01
Test Description: This Test is conducted on adding, editing a border.
Total Duration: 00:04:50 % Passed
93%
32
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
A Border Module – New Border
A1 Click Border icon. “Border Record” form will be displayed. Same as expected P
A2 Select “New Border” Tile. The “New Border” form will be displayed. Same as expected P
required.”.
The “New Rental” form will be displayed along with the
A4 Select “Proceed to Rental” Button. Same as expected P
inputted border information.
A5 Select “Browse Room”. “Browse Room” form will be displayed. Same as expected P
A6 Select desired room. Back to “New Rental” form. Same as expected P
or not required)
“Room information is required.”.
“New rent and border successfully saved.”
209
required.”.
A new data will be added and a Message box will appear –
B Border Module - View Guardian
B1 Click Border icon. “Border Record” form will be displayed. Same as expected P
B2 Select “View Guardian” Tile. The “Guardian record” form will be displayed. Same as expected P
Select “Edit” on desired Guardian
B3 The “Edit Border” form will be displayed. Same as expected P
information.
B4 Input the information needed. *The Inputted information will be displayed. Same as expected P
B5 Select save button. Same as expected P

P Pass
F Fail Richa Rose R. Salvador Norrama Jala Melanie L. Ledesma
210
Project Name:
Rent Module App Version No: 01
Build No: 01
Test Description: This Test is conducted on editing, adding, ending a rental. % Passed
Test 93%
32 Cases
32
C. The tester must have an account for each type of user. cases: Test 100%
PASS/
FAIL
A Rent Module – Adding a New Rental Information
A2 Select “New Rental” Tile. The “New Rental” form will be displayed. Same as expected P
A3 Select “New Border” Tile. The “New Border” form will be displayed. Same as expected P
required.”.
The “Search Border” form will be displayed, only available
A5 Select “Browse Border” Tile. borders will be displayed – borders with current Rental record Same as expected P
will not be displayed.
Browse Room Tile will only valid if a Border has been selected.
A6 Select “Browse Room” Tile. Same as expected P
“Browse Room” form will be displayed.
A7 Select a preferred room. Room details will be displayed on New Rental form. Same as expected P
211
A8 Select Add-ons Tile. Displays Add-ons form. Same as expected P
A9 Select “Save” button. Same as expected P
“New Rent and border successfully saved.”
Rent Module - Editing an existing Rental
B
Information
B1 Same as expected P
required.”.
Displays Update Border form along with the selected border
B3 Select Update Border button. Same as expected P
information.
B4 Select Update Room button. Displays Browse Room form with the room information. Same as expected P
B5 Select “Save” button. Same as expected P
“Rental Information successfully saved.”
Status
F Fail
212
Project Name:
Rooms Module (Admin) App Version No: 01
This Test is conducted on editing, adding, ending a Room Build No: 01
Test Cases
Total No. of failed test case: 12
Setup for Test: least 3 computers – networked together. Total no. of tested test cases: 32
% Tested
C. The tester must have an account for each type of user. 100%
Test Cases
D. The tester must report everything to the Programming Total no. of test cases: 32
PASS/
FAIL
A Rooms Module – Adding a new Room
A2 Select “New Room” Button. “New Room” form will be displayed. Same as expected P

or not required)
“ Room Name/Code/No is required .”
The new Room information will be saved and a Message box
will appear -“New Room successfully saved.” .
B Rooms Module - Editing an existing Room information
213
Select “Edit” button on the selected “Edit Room” form and the selected room information will be
Room information you wish to edit. displayed.
B2 * If required information not inputted, message will appear - Same as expected P
or not required)
“Room Name/Code/No is required.”
B3 Select “Save” Button. Same as expected P
box will appear - “Room successfully updated.”
Status
F Fail
214
Project Name:
Collection Module App Version No: 01
This Test is conducted on editing, adding a Collection Build No: 01
Test Description:
information. Total Duration: 00:04:20 % Passed
93%
Total No. of passed test case: 32
32
% Tested
user. 100%
Test Cases
system.
PASS/
FAIL
Collection Module – Adding a New
A
Collection
A1 Select “Collection” Tile. The “Payment and Collection” form will be displayed. Same as expected P
A2 Select “New Collection” Button *The “New Payment and Collection” form will be displayed Same as expected P
A3 Select “Search Rent”. The “Search Rental” form will be displayed. Same as expected P
The selected Rental information will be load on “New
A4 Select desired Rental information. Same as expected P
Payment and Collection” form.
A5 Input the information needed. *The Inputted information will be displayed. Same as expected P
Press “Ok” button to confirm inputted An amount will be displayed corresponding to the inputted
A7 Input the desired amount. Save only button will be enabled. Same as expected P
215
A8 Select “Save Only” button. Message box will appear – “Payment Successfully saved.” Same as expected P
B Collection Module – Editing a Collection
Select “Edit” button on Collection
B1 “Edit Payment and Collection” form will be displayed. Same as expected P
information you wish to edit.
Input the information needed. (checked
B2 Payment Information will be displayed. Same as expected P
or unchecked)
B3 Select “Save Only” button. Message box will appear – “Payment successfully saved.” Same as expected P
Message box will appear – “Payment successfully saved.”
B4 Select “Save and Print”. Same as expected P
Printable Collection information will be displayed.

P Pass
216
Project Name:
Settings Module App Version No: 01
This Test is conducted on editing the Settings Build No: 01
Module. Total Duration: 00:01:30 93%
Test Cases
32
100%
user. Test Cases
system.
PASS/
FAIL
A Settings Module
A1 Select “Settings” Tile. The “Update Settings” form will be displayed. Same as expected P
Input the information needed. (valid or *The Inputted information will be displayed.
null) * If inputted null value, message will appear
box will appear - “New Settings successfully saved.”

P Pass
217
Project Name:
Billings Module App Version No: 01
Build No: 01
Test Description: This Test is conducted on deleting a Billing data. % Passed
Test 93%
32 Cases
Test 100%
user.
Cases
PASS/
FAIL
A Billings Module
A1 Select “Billings” Tile. The “Billing Record” form will be displayed. Same as expected P
Filter keyword/s in the search column
A2 Displays sets of Billing Records searched with correct details. Same as expected P
provided.
Input keyword/s in the search box provided. Displays sets of products searched with correct details.
(valid or not related) * Displays on form "No Billings yet".
Select “Delete” Button of the selected Billing Message box will appear – “Are you sure you want to delete this
record. billing?”
Selected billing will be deleted.
A5 If clicked “Yes”, “No”. Same as expected P
Back to current search in Billing record form.
A6 Select “Print Bill”. Printable Billing information will be displayed. Same as expected P

P Pass
218
Project Name:
Account Module App Version No: 01
This Test is conducted on editing, adding and deleting Build No: 01
an Account information. Total Duration: 00:01:30
Test 93%
32 Cases
Test 100%
user.
Cases
PASS/
FAIL
A Account Module – Adding a New Account
A1 Select “Account” Tile. The “New Rental” form will be displayed. Same as expected P
A2 Select “New Account” Button *The “New Border” form will be displayed. Same as expected P
A4 * Upon clicking “Save” - message will appear (Username must be Same as expected P
or less than)
at least 6 characters long.)
A5 * Upon clicking “Save” - message will appear (Password must be at Same as expected P
or less than)
least 6 characters long.)
Input Password. (Retyping the Wrong * Upon clicking “Save” - message will appear (Password did not
Password) match.)
A New Account will be successfully saved and a Message box will
appear “New Account Successfully saved”.
B Account Module – Editing an Account
219
Select “Edit” button on the selected “Edit Account” form and the selected room information will be
Account information you wish to edit. displayed.
The new account information will be saved and a Message box will
B3 Select “Save” Button. Same as expected P
appear - “Account successfully updated.”
C Account Module – Deleting an Account
Select “Delete” button on the selected A message box will appear – “Are you sure you want to delete ___
C1 Same as expected P
Account information you wish to delete. Account?”
The Account will be deleted.
C2 Select “Yes”. Same as expected P
Manage Account will be displayed.

P Pass
220
Project Name:
Profile Module App Version No: 01
Build No: 01
Test Description: This Test is conducted on editing My Account. % Passed
Test 93%
32 Cases
Test 100%
user.
Cases
PASS/
FAIL
Profile Module – Editing My Account
A
Profile
The “My Account” form will be displayed.
A1 Select “Profile” Tile Same as expected P
Current User Account Information will be displayed.
A2 * Upon clicking “Save” - If required information not inputted, Same as expected P
or not required)
message will appear (Username and Password are required.)
A3 * Upon clicking “Save” - message will appear (Username must Same as expected P
or less than)
A4 * Upon clicking “Save” - message will appear (Password must Same as expected P
or less than)
Input Password. (Retyping the Wrong * Upon clicking “Save” - message will appear (Password did
Password) not match.)
The New Account changes will be successfully saved and a
Message box will appear “Account Successfully updated”.
221

P Pass

Project Name:
Log out App Version No: 01
Build No: 01
Test Description: This Test is conducted on Logging out. % Passed
Test 93%
32 Cases
Test 100%
user.
Cases
PASS/
FAIL
A Logging out
Message box will appear – “Are you sure you want to log
A1 Select “Log out” button. Same as expected P
out?”
Logs out from the current user.
A2 Select “Yes” Same as expected P
Log in Form will be displayed.
222

P Pass
User – Clerk

Project Name:
Adding New Boarder’s and Clerk module. App Version No: 01
To determine the functionality and discrepancies of Build No: 01
the module. Total Duration: 00:01:30
Test 93%
27 Cases
Total No. of failed test case: 0 Test 100%
user.
Cases
223
PASS/
STEP ACTION EXPECTED RESULT ACTUAL RESULT
FAIL
A Login
The system shall determine if the username and

A1 password combination is correct and shall their Same as expected P
username and password
respective interface.
The registered user will be redirected to the features of
A2 system checks the admin/user is a Same as expected P
the system.
valid user.
B Rent
Rental record will show.
B1 The user clicks the “Rent” button Same as expected P
“Search” bar and “New rental”, “edit” button will show.
B2 The user clicks the “ Search “ button List of names will show. Same as expected P
New form will show.

The user can “update border”, “Update Room”, “add-
B3 The user clicks the “Edit” button Same as expected P
ons”, “Extend Rental” or “End Rental”; “Save” and
“Cancel” button will show.
New form will show and can add new border.
The user clicks the “New Rental” New buttons will show such as “New border”, “browse
button border”, “Browse Room”, “add-ons”, “Save” and
“Cancel”.
The user clicks the “Update border” The user can update the borders information and their
B3.1 Same as expected P
button. guardian information and save.
The user clicks the “Update Room” The user can update/change their room they want and
button. save.
The user clicks the “Add-ons”
B3.3 The user can add a new items/appliances and save. Same as expected P
button.
The user clicks the “Extend Rental”
B3.4 The user can extend the rental of the borders. Same as expected P
button.
The user clicks the “End Rental”
B3.5  The user can end/void the rental of the borders. Same as expected P
button.
B3.6 The user clicks the “Save” button.  All the information will updated. Same as expected P
B3.7 The user clicks the “Cancel” button.  The form will close. Same as expected P
224
button. rental.
The user clicks the “Browse border”  The user can browse an old border that finished the
button contract.
The user clicks the “Browse Room”

B4.3  List of rooms will show. Same as expected P
button
The user clicks the “Add-ons”  The user can add a new items/appliances to the border
button. with charge or free.
B4.5 The user clicks the “Save” button.  The system will save all information. Same as expected P
B4.6 The user clicks the “Cancel” button.  The form will be close and it will not be saved. Same as expected P
C Border
 Borders Record will show.
C1 The user clicks the “Border” button.  New buttons will show such as “New Border”, “View Same as expected P
Guardian”, “Edit” and “Search” bar.
C2 Same as expected P
button. rental.
 The borders guardians’ record will show.
The user clicks the “View Guardian”
C3  The system allowed the user to edit the borders Same as expected P
button.
guardian information.
 The system should allowed the user to edit the borders
C4 The user clicks the “Edit” button Same as expected P
information and guardian information.
D Billings
The user clicks the “Billings”  The system will show to user of the Billing records of
D1 Same as expected P
buttons. each border.
The user clicks the “Print bill”
D2  The system will print the borders bill. Same as expected P
buttons.
225
E Profile
E1 The user clicks the “Profile” button.  The user can change their username and password only. Same as expected P
F Log-out
The user clicks the “Log-out”
F1  The system will close. Same as expected P
button.

P Pass
226
User – Cashier

Project Name:
New Payment and Collection Module App Version No: 01
To determine the functionality and discrepancies of Build No: 01
the module. Total Duration: 00:01:30
Test 93%
A. The tester must read all the documents needed Total No. of passed test
8 Cases
B. The tester must conduct the testing phase with
at least 3 computers – networked together.
user. Total No. of failed test case: 0 Test 100%
D. The tester must report everything to the Cases
system.
PASS/
STEP ACTION EXPECTED RESULT ACTUAL RESULTS
FAIL
A Login
. The system shall determine if the username and password
A1 combination is correct and shall show the users their respective Same as expected P
username and password.
interface.
A2 system checks the The registered user will be redirected to the features of the system. Same as expected P
admin/user is a valid user.
Collection Module – Adding a
A
New Collection
B1 Select “Collection” Tile. The “Payment and Collection” form will be displayed. Same as expected P
Select “New Collection”
B2 *The “New Payment and Collection” form will be displayed Same as expected P
Button
B3 Select “Search Rent”. The “Search Rental” form will be displayed. Same as expected P
Select desired Rental The selected Rental information will be load on “New Payment and
information. Collection” form.
227
Input the information
B5 *The Inputted information will be displayed. Same as expected P
needed.
Press “Ok” button to confirm An amount will be displayed corresponding to the inputted
inputted information. information.
B7 Input the desired amount. Save only button will be enabled. Same as expected P
B8 Select “Save Only” button. Message box will appear – “Payment Successfully saved.” Same as expected P
C Search rent
The user clicks the “search
C1 List of names will show. Same as expected P
rent” button.
The user will clicks the name
C2 The advance payment button will show. Same as expected P
in the list
D Advance payment
The user clicks “advance
D1 Advance payment form will show. Same as expected P
payment” button
D2 The user clicks “save” button The system will save all the information. Same as expected P
The user clicks “save and
D3 The system will save the information and print. Same as expected P
print” button
E Logout
The user clicks “Log out”
E1 The user will be logged-out from the system. Same as expected P
button.

P Pass
228

Ba Dormitory Management System: Institute of Computer Studies Western Mindanao State University

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ba Dormitory Management System: Institute of Computer Studies Western Mindanao State University

Uploaded by

Copyright:

Available Formats

BA DORMITORY MANAGEMENT SYSTEM

Financial Policies: .......................................................................................................................................... 24

Overall Cost ................................................................................................................................................... 95

6.7.a Entity Relationship Diagram (ERD) .................................................................................................... 110

6.17 Legal Requirements ................................................................................................................................. 127

7. 4. 12. New payment and Collection ........................................................................................................ 143

9.4 Target Trainees .............................................................................................................................................. 181

Overview of the System

The Project Site

The BA Dormitory Management System was developed to a desktop application for BA

Background of the Client

Ms. Melanie L. Ledesma

 The Officer-In-Charge / Landlady of the BA Dormitory

Hierarchical Input Process Output (HIPO)

Description of the Main Module and Sub Module

Billings This module allows the user to show and

Collection Where the collection of payments can

Settings . This module contains the settings of the

 Enhance individual’s knowledge and capabilities in the field of software development.

 To build a good organization or unification of all the member in the group

System Analyst and Design Team

Roles and Responsibilities

Chief Programmer: Mangking, Daisa A.

 Responsibility to update his/her skill via self-learning most times.

System Analyst: Sali, Myrhana S.

 Defines application problem by conferring with clients; evaluating procedures and

Testing Head: Salvador, Richa Rose

Project Manager: Jala, Norrama J.

Archivist: Eyas, Jefford D.

Training Head: Hamsiri, Al-jadeed S.

 Monitor instructor performance to verify training is conducted as outlined in approved

Name Position Individual assessment Group’s assessment

Norrama J. Jala Project Manager Rational extrovert Rational extrovert

Myrhana N. Sali System Analyst Rational extrovert Rational extrovert

Daisa A. Mangking Chief Programmer Rational extrovert Rational extrovert

Jefford D. Eyas Head Archivist Intuitive introvert Intuitive introvert

Al-jadeed S. Hamsiri Head Training Rational extrovert Rational extrovert

Name Position Individual Assessment

I assessed myself as a rational

I assessed myself as rational

I assessed myself as a rational

I assessed myself as a rational

Chief archivist I assessed myself as intuitive

Head training facilitator I assessed myself as a rational

 Everyone is required to attend every regular meeting especially during Software

 No to social media if there is a meeting

activities, documents and sleepovers).

 Assigned treasurer of the group must collect P15.00 once a week.

 A late member will have a fine of P30.00.

 One absent will have a fine of P50.00.

 Late submission of tasks will receive a P20.00 fine per task.

 5 consecutive absent will expulsions of the team.

Signed this 27th day of November, 2017.

Jefford D. Eyas Daisa A. Mangking Al-jadeed S. Hamsiri

Norrama J. Jala Myrhana N. Sali Richa rose Salvador

Engr. Marvic Lines

3.a Work Breakdown Structure

Phase 2: The Client

Phase 4: Project Planning

Phase 5: Project Costing

Phase 6: Requirement Analysis

6.6 Project Issues

6.6.2 Off the shelf Solutions