Chapter 3 The System Development Life Cycle (SDLC).pptx

Chapter 3 SAD

1. Course: CSC1108 - System Analysis & Design Semester: January 2024 Lecturer: Ms Jayashiry Morgan

2. Chapter 3: The System Development Life Cycle (SDLC)

3. Learning Outcomes: By the end of this session, students should be able to explain: 1. What is SDLC? 2. What are the phases in SDLC? 3. What are the products of SDLC phases? 4. Explain about the traditional waterfall SDLC

4. What is SDLC? SDLC stands for “Software Development Life Cycle”. SDLC is a collection of processes which are followed to develop a software. SDLC is a methodology that defines some processes which are followed to develop a high-quality software.

5. Importance of SDLC Ensures systematic and organized development. Enhances collaboration between stakeholders. Provides a framework for high-quality system development.

6. Phases of SDLC Each phase of the SDLC plays a crucial role in the successful development and deployment of a software system. The phases are interconnected, with outputs from one phase serving as inputs to the next, ensuring a systematic and well-managed development process.

7. Phase 1: Planning Objective : In the planning phase, the overall project scope, objectives, timeline, and resources are determined. The primary goal is to establish a clear understanding of the project requirements, constraints, and feasibility. Activities : Identifying project goals and objectives. Assessing project feasibility, including technical, financial, and organizational aspects. Developing a project plan with timelines, milestones, and resource allocation. Establishing communication channels and project governance.

8. Phase 2: Analysis Objective : The analysis phase focuses on understanding the needs and requirements of the end-users and stakeholders. It involves gathering, documenting, and analyzing information to define the system's functionality. Activities : Conducting interviews, surveys, and workshops to gather user requirements. Documenting functional and non-functional requirements. Analyzing current business processes and workflows. Identifying potential risks and challenges.

9. Phase 3: Design Objective : The design phase transforms the requirements gathered during the analysis into a blueprint for the actual system. It involves creating a detailed plan for how the system will be implemented. Activities : Logical Design : Defining system architecture, data models, and high-level system flow. Physical Design : Translating the logical design into a physical structure, specifying technologies, databases, and hardware. Creating prototypes or mock-ups for user interface design. Defining system interfaces and interactions.

10. Phase 4: Implementation Objective : The implementation phase involves the actual development of the system based on the design specifications. It is the stage where the code is written, tested, and refined. Activities : Writing code according to the design specifications. Conducting unit testing to ensure individual components work as intended. Integrating components and conducting system testing. Making necessary adjustments based on testing results.

11. Phase 5: Maintenance Objective : The maintenance phase involves the ongoing support, enhancement, and optimization of the system. It ensures that the system remains effective and meets changing user and business requirements. Activities : Addressing and fixing any issues or bugs discovered post-implementation. Making updates or enhancements to accommodate changing business needs. Performing routine maintenance tasks, such as system backups and security updates. Evaluating and implementing new technologies to improve system performance.

12. Products of SDLC Phases From textbook page 35

13. The Traditional Waterfall SDLC From textbook page 37

14. The Traditional Waterfall SDLC The Traditional Waterfall Model is a linear and sequential approach to software development that follows a structured and rigid process. It is called the "Waterfall" model because the development process flows steadily downwards through a series of phases, and each phase must be completed before moving on to the next.

15. Key Characteristics of Traditional Waterfall Model Structured Approach: Phases are well-defined and progress in a linear manner. Clear Milestones: Easily measurable progress at the end of each phase. Document-Driven: Emphasis on comprehensive documentation.

16. Use Cases of Traditional Waterfall Model Projects with Stable Requirements: When requirements are well-understood and unlikely to change. Regulated Industries: For projects requiring extensive documentation and regulatory compliance.

17. The Traditional Waterfall SDLC Advantages: Clear structure Well-documented Easy management Client involvement Predictable timelines Drawbacks: Limited Flexibility Not suitable for large projects Late visibility of product Rigidity

18. Watch This Video: Click Here