Chapter 3

Descriptive Research
The descriptive research involves representation, recording,
analysis and interpretation of the current nature, construction or
procedures of phenomena which centers around current conditions, or
how an individual, group or thing behaves or functions. It frequently
involves some sort of correlation or difference. In other words,
descriptive research may be defined as a purposive process of
investigating, arranging and organizing data about prevailing cycles,
pattern, rehearses, convictions and cause impact connections and
making sufficient and exact understanding about such information
regardless of the guidance of measurable strategies. It describes the
subject of the research without concentrating on why a particular
phenomenon happens.

Experimental Research
Experimental research is a research that stringently sticks to a
scientific research design. It incorporates a theory, a variable that can
be controlled by the researcher, and factors that can be estimated,
determined and analyzed. Above all, experimental research is finished
in a controlled environment. The researchers gather information and
results will either support or reject the theory. This method for research
is connected to at theory testing or an insightful exploration strategy or
method. The research should establish a remarkable cause and effect.

Developmental Research
Developmental research was defined as a foundational
investigation of planning, creating and assessing informative projects,
cycles, and products that should meet the measures of inward
consistency and adequacy. Developmental research characterized
formative examination as an intuitive, cyclic course of advancement
and exploration wherein hypothetical thoughts of the designer feed the
improvement of products that are gathered as samplings and analyzed.
Which the final product has been evaluated.

Software Process
Agile method was utilized to come up with the cycle process for
this research as characterized continuous recurrence of development
and testing throughout the software developmental life cycle of this
project. It will help the product team to accurately capture the elements
and features that will matter most to the end users to prioritize the
delivery of those features and also to deliver useful software that
addresses the end users’ needs with quality provided through
technology.

Agile Development

Figure 1. Agile Development Cycle

Shows the agile model that served as the basis for developing PTC
Faculty Scheduling and Loading System

Requirements / Analysis
This is the first phase of agile development where the gathering
of requirements and analysis by the researchers were done through
interviews with the program chair and faculty members about their
manual and existing process. The researchers specified the needed
software and hardware requirements for the system.
Design
The creation of the entire architecture of the proposed system
happened here in the second phase of the agile development.
Implementation
This is the third phase in agile development. All parts of the
designed system are implemented and source code is created.
Testing
Testing includes the checking of any failures and errors
encountered in coding and how to fix it. Everything is completely
tested and re-tested if necessary until all issues are settled.
Deployment
After the system has been tested and all needed iterations are
made, it goes to deployment phase. The developed system is then
delivered to the end user.
Maintenance
Maintenance go along with the system along its entire life cycle.
Changing, modifying and updating the system software must keep up
with customer needs and must be monitored. Any issues encountered
by the users must be corrected and fixed.

Planning and Data Gathering

SWOT Analysis

A Faculty Scheduling and Loading System can be characterized to be

a system which allows academic department chairs an assignment of
schedules and load appropriate subjects to faculty. The software is
simple and user friendly but still it able to serve it purpose. There is
always a room for improvement and future developments that can
make the software to run more effectively.

Strengths

 User-friendly
 plotting of schedules can be made easily
 easy viewing and printing of schedules
  customizable and adjustable (add subject specially for summer
classes, add classroom, applicable for per cycle and regular
programs)

Weaknesses

 the system is only for making schedules, loading and facilitation

of available classrooms
 only the admin is authorized to add faculty’s time schedule and
loading
 instructors/faculty can only view their schedules and subject
loads by using their accounts

Opportunities

 Visualization of data about available rooms, subjects and

teachers’ load
 Reporting system lets users load reports and schedules
 Provide additional features in the future

Threats

 Such system will have additional costs for the Institution

 Funding for training of Information and Instructional Technology
Support Staff

Feasibility Study
Feasibility study is the basis or testing of a proposed system by
its usefulness, how it satisfies the requirements by the utilizations of its
resources. Is it worth it to resolve a problem?
Operational, technical and economic factors are the kinds of feasibility
study. This is to know whether a project has a good chance to
succeed.

Technical Feasibility
Studying on the accessibility of resources that can influence the
capacity to accomplish the proposed system. This is to determine the
technology needed if the proposed project is achievable or not.
  Is the current equipment accessible and compatible to existing
programming innovation or software technology?
 Is the developed system can be upgraded?
 On the off chance that new innovation is required, what can be
developed?
The following factors are included in our study.

 Easy to install
 Compatible in operating system
 Efficient in data handling
 Providing inherent features for security
 Flexibility
 Good condition
 Maintains and debugs easily
The most frequently difficult area encountered is technical feasibility.
That is why analyzing and defining the processes should be conducted
parallel with the technical feasibility assessment. It evolves on
hardware, software, etc.) and into what extent the proposed system
can be supported.

Costing
Development Cost

This table shows the developmental cost of the system. This includes the
researcher’s expenses to development a system.

Development cost Duration Monthly Cost Total

Amount
Researcher’s allowance 5 months 1500 7500
Ink 5 months 80 240
Paper 5 months 230/rim 460
Internet fees 5 months 1299 7794
Total Cost 15,994
Milestone Scheduling (with analysis)

activity Jan Ma r April July Aug

10- 1- 1– 1- 1-
Feb March June July Aug
28 30 30 30 30
2022 2022 2022 2022 2022

Gathering of
information
and writing of
proposal
Specifications
of software
requirements,

System Design

System
Validation
System
Presentation

CODING

Programming Language: Hypertext Pre-Processor (PHP), Java Script, Hypertext

Markup Language (HTML), Structured Query Language (SQL)

TESTING

● We will be using Web browser and XAMPP server, Web browser and MySQL
DBMS as a testing tool.
● This is to ensure that the system is in good condition and error free.

IMPLEMENTATION

● The objective for this system is to carry out the system effectively.
 ● The main activity involved in this implementation part is coding from scratch
and the most important things is it meets the user requirement
● Remove critical errors found in the program to make sure the program runs
successfully.

OPERATION AND MAINTENANCE

● In the organization stage, it includes finalizing client documentation

● finalizing the system
● set-up and conducting training for the user to get familiarize with the new
system
● Equipment and development tools (eg. IDE/Microsoft Project) HTML, PHP,
Java, MySQL and Notepad++
● Operating system server (eg. OS/Web server App Server)
● Database system (eg. Oracle/MS SQL Server MySQL) MySQL
● Hardware requirement: Intel Core i5 and above, 16GB of RAM 64 bit O.S

● System Design & Development ( done by Paolo)

● -Flow Chart per module
● -Data Flow Diagram Level 0 and 1
● -UMS unified model lang (Use Case Diagram Only)
● -Normalization of database
● -Entity Relationship of Database ERD Diagram
 FUNCTIONAL SUITABILITY 1 2 3 4 5
1 Functional Completeness

The Degree to which the set of functions covers all the specified tasks and user
objectives.
2 Functional Correctness

The degree to which FSALS provides the correct results with the needed degree
of precision.
3 Functional Appropriateness

The degree to which the functions facilitate the accomplishment of specified

tasks and objectives.
PERFORMANCE EFFICIENCY 1 2 3 4 5
1 Time Behavior

The degree to which the response and processing times and throughout of
FSALS, when performing its functions, meet requirements.
2 Resource Utilization

The degree to which the amounts and types of resources used by FSALS, when
performing its functions , meet requirements.
3 Capacity

The degree to which the maximum limits of FSALS parameters meet

requirements.
USABILITY 1 2 3 4 5
1 Appropriateness Recognizability

The degree to which users can recognize whether a product or a system is

appropriate for their needs.
2 Operability
The degree to which an FSALS has an attributes that make it easy to operate
and control.
3 User Error Protection

The degree to which the FSALS protects users against making errors.
4 User Interface Aesthetics

The degree to which the users enable pleasing and satisfying interaction for
user.
5 Accessibility

The degree to which a FSALS can be used by people with the broadest range of
characteristics and capabilities to achieve a specified goal in a specified context
of use.
RELIABILITY 1 2 3 4 5
1 Maturity

The degree to which the FSALS meets needs for reliability under regular
operation.
2 Availability

The degree to which the FSALS is operational and accruable then required for
use.
3 Fault tolerance

The degree to which the FSALS operates as intended despite the presence of
hardware or software faults.
4 Recoverability
 The degree to which in the event of an Interruption or a failure. The FSALS can
recover the data directly affected and re-establish the desired state of the
system.
SECURITY 1 2 3 4 5
1 Confidentiality

The degree to which FSALS ensures that are accessible only to those authorized
to have access.
2 Integrity

The degree to which FSALS ensures that data are accessible only to those
authorized to have access.
3 Non-repudiation

The degree to which the actions of an entity can be traced uniquely to the
entity.

4 Accountability

The degree to which the actions of an entity can be trace uniquely to the entity.
5 Authenticity

The degree to which the identity of a subject or resource can be prove to be one
claimed.

Questions:

Can be the system be improved?

Yes

If No

If YES,

What are recommendations that you can suggest?

_____________________________________________