Software Development Life Cycle (SDLC)

Keywords

• Software: A set of instructions or programs that tell computers how to perform specific tasks.
• Software Development Life Cycle (SDLC): The process of developing software from an initial idea to a finished product.
• Server: A computer or program that provides data to other programs or computers.

Software Development Life Cycle (SDLC)

• Any software starts with an idea to solve a user problem.
• This idea goes through a defined process called SDLC.
• SDLC is a method that outlines the stages for producing high-quality software.
• There are seven key phases in SDLC.

Seven Phases of SDLC

• Planning: The initial brainstorming and groundwork.
• Requirements: Analyzing and documenting the needs of the software.
• Designing and Prototyping: Creating the blueprint and a model of the software.
• Software Development: Actual coding of the software.
• Testing: Ensuring that the software functions as intended.
• Deployment: Putting the software into use/into the market.
• Operations and Maintenance: Ongoing operational support and improvements.

Advantages of Using SDLC

• Creates high-quality software.
• Improves customer service.
• Increases employee productivity.
• Saves money.

Team Roles in SDLC

• Project Manager: Manages budget, resources, and timelines.
• Business Analyst: Understands business needs and technical requirements.
• Designers: Plan the design of the product and user interface.
• Developers: Write the software code.
• Operations: Sets up the hardware for the software.
• Testers: Validate that the software meets the required quality.

Requirement Analysis (SRS)

• Requirement Analysis: Involves a detailed discussion with stakeholders on the project requirements.
• SRS Report Outline: Includes sections for introduction, literature survey, functional and non-functional requirements, SDLC Model, feasibility study, system architecture, development, testing/results, and conclusions.
• Functional Requirements: Define how the system works and responds to inputs.
• Non-Functional Requirements: Define the system's quality, such as performance, scalability, security and usability.

Design and Prototyping

• The design phase analyzes the project's requirements and plans the product.
• Designers often develop multiple design approaches.

Design Phasese

• System Design: Identifying modules and/ or pages that make up the system.
• Detailed Design: Explains the logic associated with each module/page within the system.

System Design Methodology

• Designers can use abstraction methodology to break systems into smaller parts to better focus on one segment of the system at a time.

Software Development

• Developers write the code based on the project design.
• Designers continue to plan the user interface.
• Testers analyze requirements to create test cases.

Testing

• Testing validates the software's functionality and quality.
• Errors found during testing are corrected before launch.
• Testing helps in finding and avoiding software defects.

Operations and Maintenance

• Encompasses ongoing operations and support of the software to ensure continued functionality (and identify future improvements).
• Includes: Performance, Feedback, Maintenance

SDLC Models

• Different models can be used to complete a software project, with each model having their unique approach to the distinct phases of the SDLC.
• The choice of model depends on the customer's requirements and the timeline for project completion.
• Examples: Waterfall model, Agile model.

Waterfall Model

• Documents requirements upfront.
• Phases are completed sequentially.
• Simple for understanding.
• Suitable for projects with well-defined requirements.
• Not flexible in handling changes in requirements.
• Can be slow.
• Difficulty handling large-scale projects.
• Limited feedback availability.

Agile Model

• Adaptable to changing requirements.
• Iterative approach.
• Frequent feedback and testing.
• Suitable for large-scale projects.
• Requires extensive documentation (Agile methods support documentation but it is not usually a heavy part of an Agile project.)
• Potential for time overrun if not properly managed.