CHAPTER III

METHODOLOGY

Project Design

In designing the Record Management System for Barangay Nutrition

Committee of Mag-asawang Ilat, Tagaytay City the following system

development methodology was used; context diagram, data flow diagram,

iterative methodology.
 33

Figure 3. Context Diagram of Record Management System for Barangay

Nutrition Committee of Mag-asawang Ilat, Tagaytay City

Figure 3 illustrates the context diagram of the system showing the three

entities that utilize the system. The Barangay Secretary, Barangay Nutrition

Scholar, Barangay Health Worker and Chairman on nutrition.

Figure 4. Data Flow Diagram of Barangay Secretary Entity

Figure 4 illustrates the Barangay Secretary would log in to the system

(1.0). The system designers have provided a default administrative account in

order to enable the Barangay Secretary to access exclusive privilege such as

adding user and update their information. During the process of user registration,

all users must give a unique username and password. (2.0).

 34

The Barangay Secretary has the right privilege to view records,

search and can generate reports through a printable file (3.0).

 35

Figure 5. Data Flow Diagram of Barangay Health Worker/Barangay Nutrition

Scholar Entity

Figure 5 illustrates the Barangay Nutrition Scholar and Health Worker, as

the user of the system starts the process by logging into the system by means of

a valid username and password (1.0). The user has the ability to input

information about the managing of child record (2.0), it includes computation of

body mass index for the child (2.1) and immunization for the infant (2.2). And for

the managing of mother information (3.0), it includes prenatal checkup (3.1) and

postnatal checkup (3.2) which is the data entry forms. It includes the data view,

adds and update. The user of the system can generate reports through a

printable file (4.0)

 36

Figure 6. Data Flow Diagram of Chairman on Nutrition Entity

Figure 6 illustrates the Chairman on Nutrition, as the user of the system

start the process by logging into the system by means of a valid username and

password (1.0). The user has the ability to view and request all the reports (2.0)

Project Methodology

An iterative life cycle model does not start with a full specification of

requirements. In this model, the development begins by specifying and

implementing just part of the software, which is then reviewed in order to identify

further requirements. Moreover, in iterative model, the iterative process starts

with a simple implementation of a small set of the software requirements, which

iteratively enhances the evolving versions until the complete system is

implemented and ready to be deployed. Each release of Iterative Model is

developed in a specific and fixed time period, which is called iteration. An

Iterative model iterates Requirements, Design, Build and test phases again and

again for each requirement and builds up a system iteratively till it is completely

built. Moreover, an iterative model can accommodate changes in requirements,

which

are very
 37

common in most of the projects. It also provides an opportunity to identify and

build any major requirement or design flaws throughout the process because of

its iterative nature.

Figure 7. Iterative Methodology (Morse,2016)

Figure 7 illustrates the iterative methodology, it consists of six phases

specifically; planning phase, analysis phase, design phase, testing phase,

evaluation phase and deployment phase.

Planning and Requirement Phase

As the first stage of the iterative model, the researchers conducted proper

planning, to help them in mapping out the specification of a document, establish

software or hardware requirements and generally prepare them for the upcoming

stages of the cycle.

The researchers conducted information gathering, gone to Barangay of Mag-

asawang Ilat and conducted an interview to the Barangay Health Scholar and the

Barangay Health Worker concerning their problem and difficulties in their line of work in
 38

the Barangay, get the necessary documents for gathering data and for constructing

processes.

Analysis and Design Phase

Once the planning and the gathering of requirements were done, the

researchers designed the flow of the system by designing the data flow diagram,

the first draft of user’s interface was also created and the modules were

designed.

Implementation Phase

The phase where the device is ready to serve and to be used during the

performance of the task. Once the system is successfully developed it could

already be available for the client to be tested.

Testing Phase

When the system is done the researchers will do testing on the

system it involved the process of compatibility with the hardware, operating

system, data integrity in the database and user authorization access rights. The

researchers will do several tests using unit testing, user acceptance testing and

integration testing.
 39

System Operation and Testing Procedure

This procedure shows how the system works and task that the users

should perform.

1. Install the application. Make sure that all the hardware and software

requirements will take into consideration.

2. The system can be accessed by logging – into the web browser. The

user must use a username and password given by the administrator to be

able to log in.

3. The user now can have access to the system.

Unit Testing

Unit testing is a software development process in which the smallest

testable parts of an application, called units, are individually and independently

scrutinized for proper operation. Unit testing can be done manually but is often

automated.

User Acceptance Testing

User acceptance testing, otherwise known as Beta, Application, or End –

User Testing, is often considered the last phase in the web development

process, the one before final installation of the software on the client site, or final

distribution of it. User acceptance testing is the usage of the software by people

from the intended audience and recording and correcting of any defects which
 40

are discovered. It’s the closest thing a “real world” test available. It gives users

the chance to interact with the software and find out if everything works as it

should if features have been overlooked, miscommunicated, not communicated;

and so on.

Integration Testing

Integration testing, also known as integration and testing, is a software

development process which program units are combined and tested as groups in

multiple ways. In this context, a unit is defined as the smallest testable part of the

application. Integration testing can expose problems with the interfaces among

program components before trouble occurs in real-world program execution.

Integration testing is a component of Extreme Programming, a pragmatic method

of software development that takes a meticulous approach to build a product by

means of continual testing revision.

Deployment Phase

After the system is fully tested and free from any error, the client now

may use and enjoy the benefits of the developed system.

Evaluation Procedure

Evaluation is a process that critically examines a program. It involves

collecting and analyzing information about a program’s activities, characteristics,

 41

and outcomes. Its purpose is to make judgments about a program, to improve its

effectiveness, and/or to inform programming decisions (Patton, 1987).

The researchers used the slovin's formula (n=N/ (1+Ne^2)) where n =

Number of samples, N = Total population and e = Margin of Error, to get the

approximate figure of respondents needed. With the margin of error of 5%, level

of confidence of 85%, response distribution of 50%, and the student’s population

of 2,163 enrolled in the first semester of the school year 2018-2019 in City

College of Tagaytay, which equivalent to 190 students sample size. The total

population of the Barangay Nutrition Committee of Mag-asawang Ilat of 4 sample

size. The total population of SCS faculty of 18, which equivalent to 17 sample

size.

Table 1 shows the numerical rating and its equivalent interpretation to

scale the report of project evaluation.

Table 1.System Evaluation Sheet Numerical and Interpretation Scale

 42

Gathered data is computed by using Mean Range Formula to conclude if

the proposed system meets the Software Factors Standard for Acceptance.