Professional Documents
Culture Documents
CHAPTER III
Brief Introduction
Software Methodologies
Requirements Analysis
System Design
Testing
Implementation
Maintenance
In this phase, the researchers will start to develop the proposed system. It
includes the design; how the system would look like based on user requirements,
and the researchers/programmer would like to add personal design to make the
system more interactive and user friendly.
Testing
During this process, the system will be tested to see if it already meets the
requirements. If there is an issue with the framework, the developers can fix it
until it is fully functional. The benefits of using the modified waterfall approach
are that developers can go back to any step that needs to be fixed without having
to start from the beginning. The proponents will be having a seminar in the
Quezon City University (QCU) to teach the students on how to use the system
properly and they have an idea what is the proposed system all about.
Implementation
This phase will let the developers implement the finished system. It will
now launch in the university or it will now be handed to the client. Developers
should be sure that it meets the requirements of the client and have an assurance
that it will not fail from the first launch.
Maintenance
Maintenance is the backbone of system success. Maintenance will be
conducted once the system is deployed to our clients, to maintain good
performance all throughout the school year, maintenance will be done if the
clients make a request. The researchers will also conduct a yearly maintenance to
ensure their satisfaction.
HIPO CHART
each module. ... The overall design of the system is documented using HIPO
charts or structure charts.
EX:
Context Diagram
The Context Diagram shows the system under consideration as a single high-
level process and then shows the relationship that the system has with other external
entities (systems, organizational groups, external data stores, etc.)
EX:
D E P A R T M E N T OF I N F O R M A T I O N T E C H N O L O G Y
QUEZON CITY POLYTECHNIC UNIVERSITY
Ex:
D E P A R T M E N T OF I N F O R M A T I O N T E C H N O L O G Y
QUEZON CITY POLYTECHNIC UNIVERSITY
A use case diagram is a way to summarize details of a system and the users
within that system. It is generally shown as a graphic depiction of interactions among
different elements in a system. Use case diagrams will specify the events in a system and
how those events flow, however, use case diagram does not describe how those events are
implemented
EX:
D E P A R T M E N T OF I N F O R M A T I O N T E C H N O L O G Y
QUEZON CITY POLYTECHNIC UNIVERSITY
Process/System Flowchart
EX:
D E P A R T M E N T OF I N F O R M A T I O N T E C H N O L O G Y
QUEZON CITY POLYTECHNIC UNIVERSITY
Entity-Relationship Diagram
EX:
D E P A R T M E N T OF I N F O R M A T I O N T E C H N O L O G Y
QUEZON CITY POLYTECHNIC UNIVERSITY
D E P A R T M E N T OF I N F O R M A T I O N T E C H N O L O G Y