CHAPTER III

SOFTWARE EVIDENCES
3.1 Business Process Review
1. Introduction
The Internet Laboratory and Computer Laboratory Logger System in the
University of Southeastern Philippines makes the everyday services more
organized, and also it is vital and time efficient system that could perform
productive informational task within the organization. The primary goal of the
Logger system project is to help the user to easily access the Internet Laboratory
without giving COR or any other burden requirements. This is done so that
formality among students in accessing school computer laboratory and internet
laboratory is orderly done.

2. Stakeholders for the project

The stakeholders behind the project development includes:
Admin (Internet Laboratory)
 Nhor Hisham Deporkan
Admin (Computer Laboratory)
 Luchi dela Cruz

3. Purpose of the Project

The purpose of this system is to improvise the management of computer
and internet laboratories of the school. Proper actions and standard procedures
through log in system features of every students for user control aspects and to
set rules of all the computer and internet laboratories equipment of the university.
Daily monitoring of students tasks, to assure that they use the lab in educational
purposes. Furthermore, insuring secure and well manage school computer and
internet laboratories is at most priority of the project with its advance firewall and
advance proxy security features that will block incoming intruders and banned
websites for the students that is not an educational information.

4. Scope of the Project

The Internet and Computer Laboratory Logger system has a scope that
gives progress in organizing the everyday process through implanting log in
features before accessing the computers. This is to provide uniformity and easy to
monitor Computer and Internet laboratories. Each student was intended to register
and sign up to be able to have an access of the said laboratories. Other individuals
like university staffs are not included. Every student has a fix number of hours that
 they have to use within the semester range only and if they have fully used all of
the hours they cannot access the lab anymore.

5. Where to find initial Information need

Most of the information needed for the system will be provided by the
students of the University who will be using the system. Another user would be the
admin or the person whom the students might inquire for any vacant and also for
reservations and other concerns. IT specialist is also needed for troubleshoot
purposes.

6. Develop a basic plan for conducting the project

The project team have gathered all the information about the students and
other allowed individuals to access the computer and internet laboratories.
Afterwards we the team will begin to add up all the information into the database,
and start developing the system’s processes using the prescribed software for the
logger system.

7. Develop a schedule for the entire project

Task Date Started Date End

Project Meeting August 14, 2018 August 16, 2018
Design August 16, 2018 August 19, 2018
Create Database August 19, 2018 August 23, 2018
Structure
Design Implementation October 15, 2018 October 26, 2018
System Functionalities November 05, 2018 November 16, 2018
Installing of the System November 19, 2018 November 23, 2018
Review of Errors November 26, 2018 November 27, 2018
Project Final Presentation December 04, 2018 December 04, 2018
Table 7.1 Project Schedule
8. Develop a budget
The project was developed in the Internet Lab and Computer Lab where the
team was interned in, and therefore does not require huge budget. The University
has provided the resources needed for the project. Table 8.1 show the budget for
the project.

Task Labor Cost Material Cost Total

Project Design Php 20,000.00 Php 20,000.00
and Development
Basic Hardware Php 6,000.00 Php 6,000.00
Test Php 1,000.00 Php 1,000.00
Final Installation Php 1,500.00 Php 1,500.00
and Test
Total Php 22,500.00 Php 6,000.00 Php 28,500.00
Table 8.1 Project Budget

9. Develop communications plan

Audience: Students and Faculty

Strategy: The team is focusing to the assigned project which is the logger system
of both Computer and Internet Laboratory. The system must do the functions as
stated below:
 Able to monitor daily record of the Student that uses the Internet and
Computer Laboratory, provide security in every Internet access
 Blocking prohibited websites
 Provide accurate computerized timer for every computer sessions in
Internet Laboratory. Register clients or students through a barcode
scanner

Future formats: The developed system equip with the function that can be use
thoroughly. In addition, the system allows to make changes in the whole process
and is adaptable to any various change.
Projected effectiveness: If the needs and wants of the user meet, all of the
function is very consistent, and the client is satisfied with function given, the project
is certainly effective and reliable to use.
Closing: This document serves as a general guide to the developers or the project
team communications plan and may change depending on the business’s needs
and focus. Let us keep it basic, responsive, and functional.
10. Identify the project problems that will need to overcome
 Time constraint – since the system has allotted a fix amount of time for

students to use the lab it has a limitations in covering all the students’

works and other educational concerns.

 Bugs and errors – this are the things that the team might overlook

during the project testing/presentation and might occur when the project

is already implemented
3.2 Software Project Management Plan

1. Introduction
1.1 Background of the study
Internet is considered to be one of the most important and beneficial
invention of mankind. It makes our life easier in a lot of aspects.
Communication becomes easy, research for study purposes becomes
convenient, and this serve as a good source of income for businessman. One
example that makes use of Internet are the infamous Internet cafés or most
commonly known as Computer Shop. In our community, a lot of computer
shops are being put up and this increases the competition in this field. And one
concern of every Computer Shop owner is the improvement of their operations
and accounting systems for a fast and manageable transaction in their
business.
Computer Shop is a place where one can use a computer with
Internet access, most for a fee, usually per hour or minute; sometimes one can
have unmetered access with a pass for a day or month, etc. These are popular
all over the Philippines, either for business or for educational purposes.
Computer shops make use of a client/server relationship. It is a program
relationship in which one program or the client requests a service or resource
from another program or the server. In networking the client mostly establishes
connection to the local web server over a local area connection (LAN) or wide
area connection (WAN) such as the internet. Servers are powerful computer
or process dedicated to manage disk drives (file server), printer (print server),
and network (network server). Clients are PCs or workstation on which users
run application. Clients rely on or in the server for resources, such as file,
devices, and even processing power.
Related to this studies, the proponents are aiming to build a system
for our University Computer Laboratory and Internet Laboratory that improves
the data and security of the said laboratories through building a centralized
client/server management system that will produce an exceptional security and
the fastest transfer of data and information from a real time web that provides
a monitoring for the admin that can be viewed anytime he needs to.
1.2 Goals and Objectives
The aim of the system is to produce a system that improves the data
and security of the Computer and Internet Laboratory with an exceptional
security and the fastest transfer of data and information from a real time web
that provides a monitoring for the admin that can be viewed anytime he needs
to. Specifically, the project aims to:
 Have an accurate computerized timer for every computer sessions
in Internet Laboratory; while unlimited time for every students
computer session in Computer Laboratory
 Provide security from unauthorized use of computers in both
Computer and Internet Laboratory
 Provide a website limiter option to monitor and control the website
that the students can visit in both Computer and Internet Laboratory
 Remotely monitor and control all client computers from a server to
properly manage both Computer and Internet Laboratory
 Block websites that the students are not allowed to visit
 Register clients or students through a barcode scanner

1.3 Project Overview

This project titled “Internet Lab and Computer Lab Logger with Barcode
Scanner Student Monitoring”, will give benefit to the said university regarding
the monitoring, security and control over the client computers in the said
laboratories. This will be a client/server relationship program where client
computers are the computers where the students can access the Internet and
the server are the computers where only the admin can access.
In this system, the admin/server side can monitor the activity of the
students and the amount of time they consumed. Every students in the Internet
Laboratory that makes use of the Internet has an allocated time usage of four
hours per day, 2 hours in the morning and 2 hours in the afternoon. They are
limited to only 2 hours and will not allowed to extend time. While in Computer
Laboratory, students will be given unlimited time in accessing the computer.
Servers in both laboratories can block websites where students is prohibited
to visit.
The benefit of this computer – based system is to make the Internet and
Computer Laboratories monitoring system effortless, easier and faster.
1.4 Scope and Limitation
This system entitled “Internet Lab and Computer Lab Logger with
Barcode Scanner Student Monitoring” covers the management of each of the
laboratories and the monitoring of the entire system. The system offers a real-
time update of all information coming from the client computers that are being
used. The students in Internet Laboratory is limited to only 4 hours per day and
unlimited time for the students using the Computer Laboratory. Under the main
server are the administrator which handles entire units which he is managing.
The Admin should have control over the usage of the client system. And the
Client part which runs on all other systems which is being used.
The proposed system covers the major operations of the Internet
Laboratory and Computer Laboratory such as monitoring and time usage of
client computers. The system has nothing to do with the printing services,
salary of employees and strategies implied by the business on how to attract
more customers.
This study is intended for the student in the university and also does not
cover the security and maintenance of the internet connection.

1.5 Benefits
 The system has an accurately computerized timer for every
computer sessions in Internet Laboratory
 The system has security features from unauthorized use of
computers in both Computer and Internet Laboratory
 The system controls the website that the students can visit in both
Computer and Internet Laboratory
 Remotely monitor and control all client computers from a server to
properly manage both Computer and Internet Laboratory
 The system can easily register clients or students through the use of
barcode scanner
 Provides a user-friendly interface so that user can easily use the
software.
1.6 Project Deliverables
Deliverable Date
Mockup Screens June 21, 2018

Database Design June 21, 2018

Presentation of Project Proposal with June 21, 2018

Prototype

Rough Draft of Design June 28, 2018

Layout of System July 8, 2018

Table 1.6.1 Project Deliverables

1.6.1 Software Project Management Plan

The Software Project Management Plan is the art and science of

planning and leading software products in which software projects are
planned, implemented, monitored and controlled.

Work, Resources and Time Estimation: The Table 1.6.1.1 is the plan created for
the project.
Activity Time Resources to be Used
Estimation
Gathering information about what 12 Structure of the client
the system would be and server side, ballpen,
bondpaper
Creating proposal, flowchart and 20 Structure of the client
design of the project and server side, ballpen,
bondpaper
Creating Project 103 Laptops, Internet
Finalizing the project, Fixing bugs 2 Laptops, Internet and
and errors Computer Laboratories
computer, Internet
Presenting the Project 1 Laptop, Internet
Table 1.6.1.1 Work, Resources and Time Estimation
Scheduling:
Internet Laboratory
Task Name Duration Start
Identifying information that needed 3 August 14, 2018
Design 3 August 16, 2018
Database Structure 5 August 19, 2018
Add Student 3 August 23, 2018
Edit Student 3 August 26, 2018
Delete Student 2 August 29, 2018
Shutdown Client 7 August 31, 2018
Restart Client 5 September 07, 2018
Unlock Client 5 September 12, 2018
Block Website 7 September 17, 2018
Login Student 6 September 24, 2018
Student Time Checker 7 September 30, 2018
Student Login via Barcode 8 October 07, 2018
Generate Report (Student in/out) 6 October 15, 2018
Computer Laboratory
Shutdown Client 7 October 21, 2018
Restart Client 8 October 28, 2018
Unlock Client 7 November 04, 2018
Block website 7 November 11, 2018
Login Student 2 November 18, 2018
Generate Report (Student in/out) 6 November 19, 2018
Program Curriculums 1 November 25, 2018
Add College 1 November 25, 2018
Edit College 1 November 25, 2018
Delete College 1 November 25, 2018
View Program Curriculum 1 November 25, 2018
Add Curriculum Program 1 November 26, 2018
Add Courses 1 November 26, 2018
Edit Courses 1 November 26, 2018
Delete Courses 1 November 26, 2018
Testing 2 November 26, 2018
Table 1.6.1.2 Scheduling of the Internet Lab and Computer Lab Logger with
Barcode Scanner Student Monitoring
Finish
August 16, 2018
August 19, 2018
August 23, 2018
August 26, 2018
August 29, 2018
August 31, 2018
September 07, 2018
September 12, 2018
September 17, 2018
September 24, 2018
September 30, 2018
October 07, 2018
October 15, 2018
October 21, 2018
October 28, 2018
November 04, 2018
November 11, 2018
November 18, 2018
November 19, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 26, 2018
November 26, 2018
November 26, 2018
November 26, 2018
November 28, 2018
Figure 1.6.1.2 Gantt Chart of Internet Lab and Computer Lab Logger with Barcode
Scanner Student Monitoring

Risk Analysis: The following below are identified possible risks of the system. It
may involve business impact, development environment, project issues and
technical issue.
 Laboratory Revenue – The risk in creating the project which is the need of
the laboratory will never be a problem since the resources are provided and
available.
 Availability of the Resources – As stated above, all the resources needed
for the development are available. The only thing left is utilization of those
resources.
 Environment Issue – The place where the development of the system was
mostly done is at the university premises or house of classmate
 1.6.2 System Analysis Report
Overview: The system that was assigned to the project team is consist of
the team project members, clients and the project management.

Functional Requirements:
 Register student through barcode scanner
 Monitor time consumed by the clients using the client computer
 Block websites
 Add, Edit, Delete Students
 Login Student
 Add, Edit, Delete college
 Add, view program curriculum
 Add, Edit, Delete course
 Shutdown, restart, unlock client/server
 Generate Report (Student in and out)

Nonfunctional Requirements:
 Security: a login window form will ensure security for all stakeholders
 Reliability: ensuring that software & hardware will perform the required tasks
 Usability: the modified software project and the internal database system
designed to be user friendly and straightforward
 Extensibility: the client has stated that the organization will one day be
handed over therefore the system will be built in a way that future growth
can occur
 Documentation: user manuals to ensure that the system can be maintained
once the Industry experience project has commenced

1.6.3 System Design Report

HEADER
SIDEBAR
BODY

Figure 1.6.3.1 Internet Lab and Computer Lab Logger with Barcode Scanner
Student Monitoring Design Layout
Overview: The design of the software composed of the header where the
reservation statuses displays, and the functional requirements was located; sidebar
with fill-up forms in order to add/update a reservation; and the body that displays all
the reserved training rooms with their corresponding details.

Detailed Description:
LOGIN – composed of a form (username and password), login button and the
company name
Main Account – serves as the home of the system software; a tab page with two
options
Reservation – displays all the training rooms that has been reserved (with their
corresponding statuses of: ‘Reserved’ or ‘On-going’);
Add/Update/Cancel/Refresh/Sort reservations
Report – displays the report of the reservations with corresponding statuses of:
‘Reserved’ or ‘Cancelled’
Edit Profile – lets you change your details
Sign Up – lets you sign-up for an account; every sign up sends a verification code
into your email address

Use: The system is accessed by logging in client’s account. Only the IT Specialists
can have accessed privileges for the system.

1.6.4 Software Test Plan

This report defines the strategy and the approach in testing the project. The
test plan for the project aims to recommend and describe the testing strategies to
be employed and identify the required resources and provide estimate of the test
efforts.

The testing strategies are the following:

 Inspection – examine the program code for well-known errors properly
 Walkthrough – review each functionality to detect errors
 Desk checking – Sequentially execute the program code mentally
 Module Testing – test the modules of the system one-by-one in the system
 System Testing – Bring together all the programs that a system comprises
 Acceptance Testing
 Alpha Testing – Testing using the simulated data of the completed program
 Security Testing – Verify the protection mechanism built into the system
 Performance Testing – Determine how the system performs on the range of
possible environment
 Validation Testing – done at the end of the development process and takes
place after verifications are completed

1.6.5 User Manual

The User Manual of Awesome OS Training Room Reservation System is
shown in Software Test Plan Chapter.

2. Project Organization
2.1 Process Model
Scrum is a framework for project management that emphasizes teamwork,
accountability and iterative progress toward a well-defined goal. The framework
begins with a simple premise; Start with what can be seen or known. After that,
track the progress and tweak as necessary. The three pillars of Scrum are
transparency, inspection and adaptation.

2.2 Organizational Structure

The figure on the next page is the stakeholders of the project “Internet Lab and
Computer Lab Logger with Barcode Scanner Student Monitoring”. It is specified
there the people behind the performance of the current Internet and Computer
Laboratories.

2.3 Organizational Interfaces

The Leader/Scrum Master shall coordinate the team meetings and will report
to the adviser for progress and difficulties encountered.

2.4 Project Responsibilities

Scrum Master/Team Leader: Scrum Master is responsible for ensuring Scrum is
understood and enacted. Scrum Masters do this by helping the Scrum Team
adhere to Scrum theory, practices and rules.
 Dhaibert Jay Abiera
Scrum Development Team / Team Members: Scrum Development Team is a
group of people who do the work of delivering a potentially releasable increment
of “Done” product at the end of each Sprint. Only members of the Development
Team create the increment.
 Angelo A. Abregana
 Kyette M. Albaña
 Virgithe Angelique Alfaro
 April Jay S. Alviola
 Jezreel Autida
 Rica Bardinas
 Gilbert James Cabahug
 Hannah Faith Y. Carcallas
 Jenelyn Catamora
 Coleen Meg Ceballos
 Jhon Paul Jun Celocia
 Maria Kristine G. Digma
 Joshua Esguerra
 Michelle Anne D. Lig-onan
 Hannah Mae Lolong
 Kcrots Pette O. Lomigo
 Gracel Gray Mahusay
 Daisy Marie Magalso
 Cyrill A. Pacomios
 Almira Jean Palcat
 Joren E. Paglomotan
 Mary Grace Ponce
 Judy Ann Recustodio
 KC Jean V. Yana

Scrum Product Owner / Stakeholders: The Scrum Product Owner is responsible

for maximizing the value of the product and the work of the Development Team.
 Deporkan
 Luchi dela Cruz
3. Managerial Processes
3.1 Management Objectives and Priorities
The objective of the project is to develop a system for the Internet and
Computer Laboratory of the university that monitors and control the laboratories.
The reservation process, when will the project be done and implemented and the
specified quality. The project is prioritized due to its time-constrained nature and
benefit it will serve to the clients after completion.

3.2 Assumptions and Constraints

The project should be finish before the semester ends. The team should finish
the project 1-2 weeks before presentation so that integration can proceed, and the
team will be able to fix errors that was found during integration.

3.3 Risk Management

The team might encounter unexpected problems during the system
development. To prevent this risks that could become the reason for system failure,
the team has organized these mitigation strategies.

Risk Mitigation Strategy

System features not discussed Finalize user requirements during

during initial client meeting (Scope initial client meeting.
Creep) Schedule another client meeting if
critical features are not discussed.

Bugs and errors present in the Take time to find bugs and resolve
system them before they get worse. Make
sure that there are no other bugs
present.

Delay in task completion Always remind team members the

importance of time management.

Table 3.3.1 Risk and Mitigation Strategy

Preventing scope creep is one of the most important actions during

development, so in order to avoid this, the project team has the solutions to prevent
scope creep.
  Doing the task early to avoid overloading of tasks
 Finalize user requirements at the beginning of the development to avoid
additional requirements while developing the system
 Apply time management
In order to prevent problems arising during project integration, the teams have
agreed to integrate the subsystems into one at the beginning of development in
order to proceed with the project smoothly.

3.4 Staffing Plan

This section implies the role of every person behind the project system.

ROLE AUTHORITY RESPONSIBILITIES Name

Project Can make decisions in Take charge in the Dhaibert Jay
Manager every situation aside overall responsibilities Abiera
from managing financial in decision making.
support.
System Is the one who control Developed the overall Gilbert James
Engineer and developed the functionalities of the Cabahug
software technicalities of system.
Kcrots Pette O.
proposed system.
Lomigo
System Is a person who uses A person who analyze Hannah Mae
Analyst analysis and design the flow or sequence of Lolong
techniques to solve the proposed system.
Jhon Paul Jun
business problems
Celocia
using information
technology.
Database Has the authority to Are capable in April Jay S.
Administrator manage the database planning, installation, Alviola
attributes and the one con-figuration,
Kyette M. Albaña
who has an authority to database design,
give privilege in performance
accessing the database. monitoring, security,
troubleshooting as well
as backup and data
recovery.
System Are the one who is/are Responsible in Almira Jean
Designer assigned in managing managing the front-end Palcat
the user interface of the view of the system.
Virgithe
system.
Angelique Alfaro

4. Technical Processes

4.1 Methods, Tools and Techniques

Using the SCRUM Methodology, the project team adopts an empirical
approach to address challenges successfully. SCRUM accepts that problems
cannot be fully understood or defined, instead, focusing on maximizing the
team’s ability to respond in an agile manner to emerging challenges.
The Scrum Master, Dhaibert Jay Abiera, calls for a daily meeting discussing
about the progress of the said project.

4.2 Software Documentation

The researchers provided this documentation to help the developers have
their guidelines in making the system. The documentation includes different
reports to clearly explain the requirements of the system and the interaction of
the clients to the system. The following are the reports that will be discussed in
the documentation of the software:
 Software Project Management Plan
 Software Analysis Report
 Software Design Report
 Software Test Plan
The reports help developers to have better result and making the system
successful. Furthermore, the reports mentioned above will be expanded in the
next chapters.
 5. Work Elements and Budget
5.1 Work Packages

Internet and Computer

Laboratory Logger System

Conception Definition and Execution Performance Project Close

and Initiation Planning and Control

Meeting with Create Mock- Layout of the Find and Fix Launch
Ms. Cempron up Screens System Errors/Bugs Project
about what is
the system all
Add, Edit, Delete Student,
about Create
College and Courses
Database
Design Shutdown, Restart, Unlock
client
Gathering
information Creating Block Website
about the proposal and
system Add and View Curriculum
presentation program
of the project
Generate Report
(Student in/out)

Figure 5.1.1 Project Work Packages of the Internet Lab and Computer Lab Logger
with Barcode Scanner Student Monitoring

5.2 Resource Requirements

 people and their skills
 equipment – laptop and computer
 time – schedule
 budget – the project was developed in the company where the team
was interned in, and therefore does not require any budget.

5.3 Budget Allocation

Task Labor Cost Material Cost Total
Project Design Php 20,000.00 Php 20,000.00
and Development
Basic Hardware Php 35,000.00 Php 35,000.00
Test Php 1,000.00 Php 1,000.00
 Final Installation Php 1,500.00 Php 1,500.00
and Test
Total Php 22,500.00 Php 35,000.00 Php 57,500.00

5.4 Schedule

Internet Laboratory
Task Name Duration Start
Identifying information that needed 3 August 14, 2018
Design 3 August 16, 2018
Database Structure 5 August 19, 2018
Add Student 3 August 23, 2018
Edit Student 3 August 26, 2018
Delete Student 2 August 29, 2018
Shutdown Client 7 August 31, 2018
Restart Client 5 September 07, 2018
Unlock Client 5 September 12, 2018
Block Website 7 September 17, 2018
Login Student 6 September 24, 2018
Student Time Checker 7 September 30, 2018
Student Login via Barcode 8 October 07, 2018
Generate Report (Student in/out) 6 October 15, 2018
Computer Laboratory
Shutdown Client 7 October 21, 2018
Restart Client 8 October 28, 2018
Unlock Client 7 November 04, 2018
Block website 7 November 11, 2018
Login Student 2 November 18, 2018
Generate Report (Student in/out) 6 November 19, 2018
Program Curriculums 1 November 25, 2018
Add College 1 November 25, 2018
Edit College 1 November 25, 2018
Delete College 1 November 25, 2018
View Program Curriculum 1 November 25, 2018
Add Curriculum Program 1 November 26, 2018
Add Courses 1 November 26, 2018
Edit Courses 1 November 26, 2018
Delete Courses 1 November 26, 2018
Testing 2 November 26, 2018
Finish
August 16, 2018
August 19, 2018
August 23, 2018
August 26, 2018
August 29, 2018
August 31, 2018
September 07, 2018
September 12, 2018
September 17, 2018
September 24, 2018
September 30, 2018
October 07, 2018
October 15, 2018
October 21, 2018
October 28, 2018
November 04, 2018
November 11, 2018
November 18, 2018
November 19, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 25, 2018
November 26, 2018
November 26, 2018
November 26, 2018
November 26, 2018
November 28, 2018

Table 5.4.1 Detailed Project Schedule of the Internet Lab and Computer Lab
Logger with Barcode Scanner Student Monitoring
6. Scope Definition Phase
6.1 Scope
This system entitled “Internet Lab and Computer Lab Logger with Barcode
Scanner Student Monitoring” covers the management of each of the laboratories
and the monitoring of the entire system. The proposed system covers the major
operations of the Internet Laboratory and Computer Laboratory such as monitoring
and time usage of client computers. The system has nothing to do with the printing
services, salary of employees and strategies implied by the business on how to
attract more customers. This study is intended for the student in the university and
also does not cover the security and maintenance of the internet connection.

6.2 Project Description

The goal of the system is to build a system that all the requested
reservations of the training rooms inside the site building. There is only one
system user; Super Admin (SA). Their roles and privileges are as follows:

Super Admin (Administration)

 No restrictions
 Menu access
 Back-end configuration access

6.3 Proposed Solution

The proposed solution for the Internet and Computer administrators is the
usage of the “Internet Lab and Computer Lab Logger with Barcode Scanner
Student Monitoring” so that monitoring and controlling of client computers would
be easy.

6.4 System Requirements

Hardware
Hardware Minimum Specification

Processor SSE2 capable Intel Pentium 4 or later

Software
Software Minimum Specification

OS Windows 7 or later
 6.5 Development tools and technologies used

Development Tools Tools Used

Software  Microsoft Visual Basic 2012

Server  Xampp

Table 6.5.1 Development tools and technologies used

7. PROBLEM ANALYSIS PHASE

7.1. Summary of Problems
The only problem why the proposed system must be solved is:
 To replace and improve the old system of monitoring of the Internet
Laboratory and install this to Computer Laboratory

7.2 List of Interviews and Facilitated Group Meetings Conducted

Date Description
06/21/2018  Distribution of task in each team member
 Analyze Awesome OS Training Room Reservation System
flow chart and preparation of strategic plans
 Making of proposal

06/24/2018  Checking of the progress of the system

07/24/1018  Checking of the system

Table 7.2.1 List of Interviews and Facilitated Group Meetings Conducted

7.3 Models of the Current System

Unfortunately, there are no models of their current system since this is the very
first system that was made for Training Room reservation. They are currently doing
a manual way in reserving a training room. Because of this matter, the proponents
decided to develop a system to automate the said process.