Chapter III

Research Methodology

This chapter presents the requirements analysis, system design and construction of the
St. Peters College High School Electronic Logbook System.
Software Development activities
A.
B.
C.
D.

Requirement Analysis
System Design
Implementation
Testing

Requirements Analysis
The researcher investigates the problem statement and learns the problem domain to
discover and understand system requirements. In this step, following activities are being
conducted: Interview School personnel to identify the users desired input and output
requirements. It will be conducted to gather information about the actual system of High
School student Electronic Logbook. The rules and regulations are determined regarding
on the students logging in and out of the campus. In these phase upon the resources
such as internet articles, electronic materials, and interview conducted. The researcher
will then justified the project description integrating the idea from resources were
determined and researcher will then write the proposal.

System Design
After the gathering of requirements the conducted proper and thorough analysis, the
researcher now takes place in actual design of the whole system by applying methods
and tools that are mentioned in the requirements analysis. Graphical User Interface
(GUI) was utilized in this system in order for the clients to easily understand and
approach in a user friendly design.

The researcher also used the design diagrams in the analysis and design of the project
as follows:

Entity Relationship diagram An entity-relationship diagram (ERD) is crucial to a good

database design. It is used as a high-level logical data model, which is useful in
developing a conceptual design for databases. An entity is a real-world item or concept
that exists on its own. Entities are equivalent to database tables in a relational
database, with each row of the table representing an instance of that entity. An attribute
of an entity is a particular property that describes the entity.
Use case Diagram- A use case diagram is "a diagram that shows the relationships
among actors and use cases within a system. Within most use case models the use
case specifications tend to be the primary artifact with use case diagrams filling a
supporting role as the "glue" that keeps your requirements model together. Use case
models should be developed from the point of view of your project stakeholders and not
from the (often technical) point of view of developers.

Data Flow Diagram - A Data Flow Diagram (DFD) is a graphical representation of the
"flow" of data through an information system, modeling its process aspects. A DFD is
often used as a preliminary step to create an overview of the system, which can later be
elaborated. DFDs can also be used for the visualization of data processing (structured
design).A DFD shows what kind of information will be input to and output from the
system, where the data will come from and go to, and where the data will be stored. It
does not show information about the timing of process or information about whether
processes will operate in sequence or in parallel.

Context Diagram - isa diagram that defines the boundary between the system, or part
of a system, and its environment, showing the entities that interact with it. This diagram
is a high level view of a system . Context diagrams show a system, often software-

based, as a whole and its inputs and outputs from/to external factors.

Context

Diagrams represent all external entities that may interact with a system. Such a diagram
pictures the system at the center, with no details of its interior structure, surrounded by
all its interacting systems, environments and activities. The objective of the context
diagram is to focus attention on external factors and events that should be considered in
developing a complete set of systems requirements and constraint (Kossiakoff and
Sweet, 2011)

Implementation
In these phase the proposed system will add enhancement to students and ease work.
In order to apply the proposed system, it will require additional software and hardware
requirements in order to be utilized by the clients. Such that all user of the proposed
system will be using interfaces accordingly to their usage. Researcher will be using
barcode reader, and the student which is the user will bring with them their barcoded id.
High school student will be separated to other staff of St. Peters College; they will be
provided a separate interface with their personal logging in and out in the campus.
Through the advent of network technology, the proposed will be connected to a simple
Local area network (LAN) connection. The database server will be located near the
school guard house where all the data is stored. The involvement of school guard
whose primary role in the system is to maintain the security of data with the use of web
database management software php my Admin.

Testing
The actual construction of the system is done and procedures described in this study.
Testing will be applied wherein that system was tested whether it is running successfully
or it is to operate. In case there are errors, necessary change shall be made .It will be
checked if it works as expected which is then subjected further corrections for
improvements. The efficiency of the applications of the system will be evaluated
according to its functionalities and capabilities to handle errors.

Hardware and Software Requirements

The following are the hardware and software requirements to be used for the design
and development of the proposed system.
Hardware requirements:

Processor: Pentium 4, with 64 bit type

Memory: 128 MB
Hard disk: (SATA) 320GB
Mouse: PS/2 compatible mouse port with pad
Keyboard: 101/102 keys
Power Supply: 220 to 250 watts
Printer: EPSON LX-300
Barcode Reader
Modem
Monitor (LED)

Software Requirements

Heidi SQL 8.1

Operating System (O.S)Windows 7
PHP
VB.NET
Web browser
I.S.S Server
Database tools (Xampp)
Firewall configuration