0% found this document useful (0 votes)
4 views3 pages

System Development Life Cycle Overview

This document outlines Chapter III of a project on Object Oriented Programming, focusing on the System Methodology using the waterfall model in the system development life cycle (SDLC). It details the phases of requirements gathering, design, implementation, testing, deployment, and maintenance, emphasizing the importance of security and reliability in the application. The methodology includes research techniques and aims to inform business decisions through systematic data collection.

Uploaded by

boyjainalabirin
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
0% found this document useful (0 votes)
4 views3 pages

System Development Life Cycle Overview

This document outlines Chapter III of a project on Object Oriented Programming, focusing on the System Methodology using the waterfall model in the system development life cycle (SDLC). It details the phases of requirements gathering, design, implementation, testing, deployment, and maintenance, emphasizing the importance of security and reliability in the application. The methodology includes research techniques and aims to inform business decisions through systematic data collection.

Uploaded by

boyjainalabirin
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

Zamboanga Peninsula Polytechnic State University

College of Information Computing Science

RT Lim Boulevard, Zamboanga City

“Chapter III”

In Partial Fulfillment of the

Requirements in IT ELEC 01

Object Oriented Programming

Submitted by:

Jainal, Adzman I.

Submitted to:

Minah P. Quiñal

Instructor

October 18, 2022

1
Chapter III

System Methodology

In this chapter, we discussed the system development life cycle (SDLC) method by using
waterfall model in the development of the system. It also discussed the requirements, design,
implementation, test, installation, and maintenance. The methodology may include google
research, and other research techniques, and could include both present and historical
information. Methodology is the process used to collect information and data for the purpose of
making business decisions.

3.1 Requirements

In this Phase the requirements are gathered by the business analyst and they are analyzing by the
team. Requirements are documented during this phase and clarification can be sought.

3.2 Design

The developer and other members of the team work on the software architecture, high level and
low-level design for the project. It is decided that the business application needs to have
redundant backup and failover capabilities such that system is accessible at all times.

Figure 1.1

2
3.3 Implementation

The development team works on coding the project. They take the design documents/ artifacts
and ensure that their solution follows the design finalized by the architect. Since the application
is a The 25th apparel and security was a high priority in the application requirements, they
implement several security checks, audit logging features in the application. They also perform
several other activities like a senior developer reviewing the other developers code for any
issues. Some developers perform static analysis of the code.

3.4 Testing

The testing team tests the complete application and identifies any defects in the application.
These defects are fixed by the developers and the testing team tests the fixes to ensure that the
defect is fixed. They also perform regression testing of the application to see if any new defects
were introduced.

3.5 Deployment

The team builds and installs the application on the servers which were procured for the business
application.

3.6 Maintenance

During the maintenance phase, the team ensures that the application is running smoothly on the
servers without any downtime. Issues that are reported after going live are fixed by the team and
tested by the testing team.

You might also like