Method Used

The researchers used a hybrid approach in developing the system. They used a
combination of Scrum, Kanban and Rapid Application Development. Selecting only 1
specific methodology will make it complicated for the researchers to finish the system. A
hybrid approach will also help meet with the deadlines and needs of the client. Hybrid
approach are what companies are using nowadays, helping the researchers be up to
date. The researchers will use the Kanban method to look and maintain with the tight
schedules. The scrum will also help with the development and/or coding part of the
system. And the Rapid Application development method will help with the faster
releases of the system. The disadvantage of the Rapid Application Development
approach is that documentation is often overlooked, but with the help of Kanban
method, this will ease it up a bit.

(Insert flow/diagram of Scrumban + RAD approach)

3.1.1 Scrum Method (definition and process (link it with the current system))

3.1.2 Kanban Method (definition and process (link it with the current system))

3.1.3 Rapid Application Development (definition and process (link it with the current
system))

3.2 Instrument Used

Statistical Data Treatment

 The statistical instrument is use in any process that aim at describing some

phenomena by using instrument or device, however the results may be used as a

control too. Some of the example used by the proponent that the questionnaire and

surveys.

o (Frequency Distribution) Equation

o (Weighed Mean) Equation

Formula:
~x=Efx
o Wherein:
n
~
o x = Weighted Mean
o Efx = Sum of the product of f and x
o f = Frequency
o x = Weight
o n = Total number

3.3 Measurement and Prototype Evaluation

Here we discuss the development of an approach for software design quality

improvement. This approach will utilize software developer’s subjective opinions on

software design. The solution should bring forward the software developer’s tacit

knowledge of good or poor software design.

3.3.1 System Testing

Based on the book of Software Engineering a Practitioner’s Approach Seventh

Edition by Roger S. Pressman, PH, D, System testing is a series of different gathered

test whose primary purpose to fully exercise the computer-based system. But each test

has a different purpose, all work together to verify that the system elements have been

properly integrated and performing allocated functions.

 Criteria
 o Object Functionality

Object Functionality refers to the construct allowing an object to be invoked or

called as if it were an ordinary function, usually with the same syntax.

o Arithmetic Computation

Arithmetic Computation is used to provide the company with objective

information about future apprentices to ensure they will be successful on the job and

apprentice training.

o Object Report Parameter

Report Parameter is used to specify the data to be used on the report. Connect

related reports together and vary report presentation.

o Data Relationship Integrity

Relationship Integrity is a term used to describe data that is intact. More

specifically, it may be accessed, modified, or copied by those who are authorized to do

so.

o IPO Transaction

IPO is a pattern commonly used for describing an information-processing

program or other process.

o Network Connection Client/Server

A Computer network is the interconnection of computing devices in order to

share data and is built with a combination of computer hardware and software.

 Likert Scale
 The system performance is based on the scale of three that is No Revision,

Minor Revision and Major Revision.

2.1 – 3.0 = 3 No Revision

1.1 – 2.0 = 2 Minor Revision
0.1 – 1.0 = 1 Major Revision

 Tester (3 IT Professional)

The proponents are required to approach at least 3 College Professor and 2

Outsider who has the knowledge about the system. It is important to know if there are

some objects, modules or anything, which is present in the system that needs

improvement

3.3.2 Software Evaluation

There are 5 evaluators to assess the system, it was composed of three (3) IT

Instructors from Infotech Development System Colleges and two (2) IT Professionals

from outside the school.

 Criteria

o Functionality

Functionality refers to quality or state of being functional. It is the design that is

admired for both its beauty and functionality. Data management functionalities such as

data integrity, security, recoverability and manageability.

o Graphical User Interface

Graphical User Interface is the common method of interacting with a computer

that allows any graphics image to be displayed on screen.

o Reliability
 Reliability is very important upon testing the software. It must be consistent to

ensure that the system is reliable to use.

o Data Security

Data Security is an umbrella term for the protection of electronic data.

o Network Architecture

Network Architecture refers to the design of a communication system, which

includes the backbones, routers, switches, wireless access points, access methods and

protocols used.

o Portability

Portability is the ability of the system to work on different kinds of hardware,

software and other environments without changing upon execution.

 Likert Scale

The system performance is based on the scale of 3, which is No Revision

(Satisfactory), 2, which is Minor Revision (Poor), and 1 which is Major Revision (Needs

Improvement).

2.1 – 3.0 = 3 No Revision (Satisfactory)

1.1 – 2.0 = 2 Minor Revision (Poor)
1.1 – 1.0 = 1 Major Revision (Needs Improvement)

 Evaluator

Evaluator is the one who evaluated the software. He used and tested the system

to know if it is accurately working.

3.3.3 User Acceptance

User Acceptance is the final testing stages by users of a new or changed

information system. If successful it signals the approval to implement the system live.
Cosmetic and other small changes may also be required because of the test, but the

system is considered stable and processing data according to requirements.

 Criteria

o Ease of Use/Customer Fit

The system must be fit to the customer’s requirement. The system product would

imply the modification of some of its characteristics according to the customer

requirements.

o Performance Efficiency

The system must be efficient to ensure that the system is effective.

Incompetence of system may lead to disorganization.

o Performance Effectiveness

Effectiveness refers to the readiness of the system for service or action.

 Likert Scale

The system performance is based on the scale of 5-Excellent, 4 – VG that is

Very Good, 3 – S that is Satisfactory, 2 – A which is Average and 1 – NI that it Needs

Improvement.

5 – E – Excellent
4 – VG – Very Good
3 – S – Satisfactory
2 – A – Average
1– NI – Needs Improvement

 User Evaluator (5 User Company Evaluator)

There are 5 evaluators to assess the system, it was composed of three (3) IT

Instructors from Infotech Development System Colleges and two (2) IT Professionals

from outside the school.

3.4. Analytical Aspect

(Statement)

3.4.1 Data and Processes

(Paragraph)

 Context Diagram

 Data Flow Diagram

  Sub-Level (0.1.1)
 Program Flowchart (0.1.1)

3.4.2 GUI Design

 Forms
 App Form
 Reports
3.4.3 Database Design

3.4.4 UML-UCASE

3.5 Software Cost

Cost Analysis

The Review and evaluation of the separate cost elements and profit in a

contractor’s proposal (including cost or pricing data or information other than cost or

pricing data), and the application of judgement to determine how well the proposed

costs represent what the cost of the contract should be assuming reasonable economy

and feasibility.

The total development cost of the proposed system is Php. xxx,xxx.00 (See

Appendix I: Budget Requirements)

Return of Investment (ROI)

A performance measurement used to evaluate the efficiency of an investment

or to compare the efficiency of a number of different investments. To calculate

ROI, the benefit (Return) of an investment is divided by the cost of the

investment; the result is expressed as a percentage or a ratio xx.xx%.

 Payback Period (PP)

The length of time required to receive the cost of an investment. The payback

period of a given investment or project is an important determinant of whether to

undertake the position or project, as longer payback periods are typically not

desirable for investment positions.

The Payback Period of the proposed system is x.x year. (See Appendix J:

Computational Breakdown of Economic Feasibility)