[16] Software Development Process

This is the structured approach to developing software applications that ensures software is efficient and that the team works in a coordinated manner

The goal of this phase is to understand what the client or end-user needs.

• Requirements Gathering

• Design

• Development

• Testing

• Deployment

This phase requires a Software Requirements Specification (SRS).

• Requirements Gathering

• Design

• Development

• Testing

• Deployment

In this phase, you interview stakeholders, conduct surveys, and analyze business requirements

• Requirements Gathering

• Design

• Development

• Testing

• Deployment

The outcome of this phase is a clear, documented, understanding of the software's functionality and constraints

• Requirements Gathering

• Design

• Development

• Testing

• Deployment

The goal of this phase is to develop a blueprint for the software.

• Design

• Development

• Testing

• Deployment

• Maintenance

The outcome of this phase is to design documents, diagrams, and models that guide development

• Design

• Development

• Testing

• Deployment

• Maintenance

There are two types of design in Phase 2 of the SDLC. This type focuses on architecture and overall structure. It typically needs UML diagrams, system blueprints, and ER disagrams.

"What does the system do?"

• High-Level Design

• Low-Level Design

There are two types of design in Phase 2 of the SDLC. This type focuses on specific component designs, algorithms. It typically needs class diagrams, flowcharts, logic charts. This is where the pseudcode comes in.

"How will each component work?"

• High-Level Design

• Low-Level Design

The outcome of this phase is a working, testable software component/modules.

• Design

• Development

• Testing

• Deployment

• Maintenance