Scribd
Upload
34 views5 pages

Chap 3

The document describes the software development life cycle used for a proposed registrar's office system. It includes 6 phases: 1) Planning, 2) Analysis, 3) Design, 4) Coding, 5) Deployment, and 6) Acceptance. For each phase except planning, key activities are described, such as analyzing information, designing system components, writing source code, testing, and delivering the final system. The system flow diagram shows the interactions between the ticketing, server, and window applications to manage user accounts and serve queue numbers.

Uploaded by

Doreen alvy Puerto
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
34 views5 pages

Chap 3

The document describes the software development life cycle used for a proposed registrar's office system. It includes 6 phases: 1) Planning, 2) Analysis, 3) Design, 4) Coding, 5) Deployment, and 6) Acceptance. For each phase except planning, key activities are described, such as analyzing information, designing system components, writing source code, testing, and delivering the final system. The system flow diagram shows the interactions between the ticketing, server, and window applications to manage user accounts and serve queue numbers.

Uploaded by

Doreen alvy Puerto
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Chapter III

METHODOLOGY

In this chapter the Software Development Life Cycle Model

will be illustrated and explained its phases based on the study.

Also, technical background and specification of the system

revealed.

Figure 2. Illustration of Software Development Life Cycle Model


Phase 1. Planning
This is the first phase where the most critical part in

completing the proposed system. The researcher observed and

gathered data in order to identify the needs of registrar’s

office. The researcher also coordinates to identify the problems,

the scope and objectives of the study by conducting interviews

from the Registrar’s Office.

Phase 2. Analysis
All information was analyzed by the researchers. This phase

also helped the researchers to have an idea on how to build and

help conceptualize on how the proposed system would be

beneficial. The leader assigned their roles and responsibilities

to do their tasks. The gathered information where combine to make

basis for creating the Chapter 1 for the objectives of the system

and Chapter 2 for the related basis of the said system.

Phase 3. Design

In this phase, the proponents gathered information allows to

design the system. The team manager assigned to each member to

create the Chapter 3 that includes Methodology, System

Development Life Cycle, Data Flow Diagram, Entity

Relationship Diagram and Power Point Presentation for Pre-Oral

defense.

Phase 4. Coding
This stage includes design, development, and testing based

on the information gathered and analyzed. Development Phase, the

researcher installed the needed application to create the propose

system, The researcher uses Visual Basic (VB.Net)as a programming


language, Visual Studio 2019 as a code editor and Xampp as a web

server. The researchers began working on the proposed system. It

comprises the design of how the system will seem based on user

requirements and research. The Software design is translated into

source code. All the components of the software are implemented

in this phase.

Phase 5. Deployment

Deployment starts once the coding is complete and the

modules are released for testing. In this phase, the developed

software is tested thoroughly and any defects found are assigned

to developers to get them fixed.

This is the feedback process of the proposed system after

it was implemented and undergone testing by its intended

users. It informs the developers if they have any suggestion and

flaws of the system functionality.

Phase 6. Acceptance
Once the software testing phase is over and no bugs or

errors left in the system, then the final deployment process

starts. The system is ready to deliver to client, and customers

start using the developed system.


System Flow Diagram

In this section the researcher will show and explain the

system flow diagram of the study concisely.

Figure 2: System Flowchart of NVC Registrar Queueing System

System Flow Diagram

In this section the researcher will show and explain the

system flow diagram of the study concisely.

First there would be 3 applications need to be open to in

order for the system to function, the ticketing, server and the

window application. The ticketing and server application doesn’t

need an account to be able to access the system, while in the

window application, the user needs an account to be able to


access the system. First if the user is already registered, all

they have to do is to login to their user account, if not they

have to register as new user.

After account creation and login, there are different tabs

of function the user to choose from like updating its user

password or monitor and call number from queue to serve. The

admin account is responsible in managing user account from

adding, updating and deleting inactive accounts. The admin also

can monitor which window is active as of the moment. After the

user is done with its process, they have to logout to their

account.

You might also like