Chapter 4

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

CHAPTER 4

METODOLOGY

This chapter presented the methods and procedures on how the research project is to be done. It

includes discussion on research method and techniques, systems development methodology,

requirements analysis, requirement documentation, design of software, development and testing,

implementation plan and implementation results.

DEVELOPMENT AND TESTING

General Description of the Software

The Automated Class Scheduling Web System is composed of different functionalities, that only

the academic head and school registrar can manipulate. This functions are:

 Adding subjects and assigning the available time, day, room, and appropriate instructors

to handle the given subjects.

 The system is also capable of deleting and updating the class schedule.

DESCRIPTION

The figure that being shown is the specific task that is fulfill by the researcher and to what date

and time as the milestone to be perform are the following: Project Planning, Requirements,

Analysis and Design, System Development, System Testing, Project Deployment and System

Review. In the project Planning and requirement is the First milestone that the researchers

planning for proposed tittle, finding client, identifying the problems and its solutions which is

took too much month’s (date) before the researcher complete the first task and milestone. The

second milestone is the analysis and design which is the phase contains analyzing, before the
researcher completed the second task and, milestone. The third milestone is the system

development where in their phase is all about the coding and checking errors, of the program it

took months before the researcher accomplished the task and milestone. The fourth milestone is

the system testing in these phases is all about establishing, troubleshooting, coding, and

debugging test the system, it took monthsbefore the researcher accomplished the task and

milestone. The fifth milestone is the deployment in which the system is ready for deployment to

the client where it sets meaning and prepared the papers and final test of the system which is

took one months before the researcher deploys the system. The last milestone is the system

review, in after the deployment the process still going that the researcher review some parts of

the system and final testing before the system will turn over to the client together with the

documents, these also took months from before the researcher terminate the milestone.

TESTING PLAN

The proponent come up a test plan that will be utilized to as to fulfill the standard and to test it

accurately and effectively of the proposed system. The test plan is generated based to the

process, technique, and procedures that the proponents have in testing the system. This test plan

is Automated Class Scheduling System supports the following objective:

1. Identify the process of creating a schedule without any conflicts.

2. Identify who is the available instructor, room, and time to take that subject.

3. Determine the qualitative description of the proposed system


Table 1: Test Plan of Automated Class Scheduling System

Test Item Automated Class Scheduling System

Feature and Function to be tested Features:

Log in and Log out

Dashboard

Room

Calendar

Instructors

Feature and Function not to be tested N/A

Test Environment Software:

windows 11

Visual studio Code 2022

XAMPP

MySQL

Hardware:

Personal Computer

Laptop
Description of the Test Participants

The study potential respondent of the Automated Class Scheduling System for STI College

Dagupan. Include the academic head and school registrar and any knowledgeable organization

staff who may later operate the system.

Academic Head

The school academic head is responsible for manipulating the system and creating a schedule for

every student who enrolls especially the irregular students.

School Registrar

They are also responsible to assign the schedule, check the availability of time, room and

instructor.

Load, Stress and Beta Testing

To be completed by the system users. Its primary goals are to assets the system acceptance by

end-user. This testing determines the system’s its success or failure and consists of load, stress

and beta testing.

Loading testing

Once the program is about to finished. To determine if it can handle the actual demands for the

end user: the proponents will perform a load testing. It is to define a system performance under

an explicit expected load. For this, components are tested on how it will work going to execute

while handling large amount o data. This testing will demonstrate Automated Class Scheduling

System are able to function properly regardless of heavy loads has been generated. Therefore, it
can handle number of users this testing also indicates that the system has reached its performance

apex.

Stress testing

The proponent will also conduct stress testing. Before the system is distributed to the client, it is

tested to verify that it will not fail under critical situations. This stress testing can be conducted

through a load testing tools by defining a test case with a very high number of concurrent virtual

users. The project system is tested beyond normal working point and evaluates how the system

respond under these utmost conditions. This testing helps the proponent to recognized unseen

bugs and errors, for this, it will be able to fix early as the system will be deployed.

Beta testing

The final phase of testing in which the system is testing using actual data. The proponents will

conduct a beta testing under the end user, that the system ensure that it functions properly. This

is to certify the usability, compatibility, and reliability of the system. This test measuring how

well the project meets the client expectation and assesses the degree that schedule is ready to

give without conflicts. As the proponent perform beta testing to the client, the result determines

the Automated Class Scheduling System has already met the user satisfaction and are ready for

deployment.

Testing schedule

Table 2: Test schedule of Automated Class Scheduling System.

Evaluator Position Name Date Tested Assigned Person

Academic Head
School Registrar

Automated Class Scheduling System

Software Evaluation Sheet

Testing Criteria

Name: ________________________ Date: ________________________

Evaluator Position: ________________________________

Instruction: put a check (/) in the column that is corresponds to your answer.

Range QUANTITATIVE DWSCRIPTION DESCRIPTION

5 Strongly Agree

4 Agree

3 Neither Agree or Disagree

2 Disagree

1 Strongly Disagree

Table 3: Criteria of Usability

A. Usability 5 4 3 2 1

1. The system was easy to navigate.

2. The dashboard of the system well organized.


3. The system was responsive.

4. The schedule of the system is well function.

5. Overall, I am satisfied with how easy it uses.

Table 4: Criteria of Reliability

B. Reliability 5 4 3 2 1

1. The System is Performing consistently well

2. The System complete task faster without error.

3.

4.

5. Overall, the system is reliable

Table 5: Criteria of Performance

C. Performance 5 4 3 2 1

1. There no problem encountered of displaying of generating

the schedule.

2. The system is responsive in terms of loading error.

3. The system operates quickly and efficiently in terms of

monitoring the students schedule if there is a conflict.

4. The system was providing zero redundant data

5. I can effectively complete my work using this system


Table 6: Criteria of Supportability

D. Supportability 5 4 3 2 1

1. The proponents give best guidelines

2.

3.

4.

5. Overall, the proponents give

Table : Criteria of Implementation

E. Implementation 5 4 3 2 1

1. The develop project met the goals and objective

2. The develop project have relevant of displaying

information to be need of end user.

3. The project requirement was accurately met.

4. The role and responsibilities are clearly defined in the

developed project.

5. Over all, the system is work as intended.


Table : Criteria of Interface

F. Interface 5 4 3 2 1

1. The design, font, color, and size are clear and good to the

eye.

2. Responsiveness of user’s controls

3. Provides understandable on-screen instructions

4. Appropriateness organization of components (button,

icons, scroll, etc.) in the system

5. Appropriateness of label and text readability

Implementation Plan

The Automated Class Scheduling System will be soon implemented in STI College Dagupan.

Activity Date Person Assigned

Installation of Software Programmer and System

Component Designer

Testing Plan Project Manager and System

Analysis

Training Team
Maintenance Every Semester Programmer

Approval of the System Client

You might also like