System Development Life Cycle (SDLC) PDF

» System Development Life Cycle (SDLC) » Four Phases: 1. Planning 2. Analysis 3. Design 4. Implementation System Development Life Cycle (SDLC) » SDLC is the process of understanding how an Information System (IS) can support business needs, designing the system, building it, and deli...

» System Development Life Cycle (SDLC) » Four Phases: 1. Planning 2. Analysis 3. Design 4. Implementation System Development Life Cycle (SDLC) » SDLC is the process of understanding how an Information System (IS) can support business needs, designing the system, building it, and delivering it to users. » Systems are developed through a cycle of activities. » Building an information system is similar to building a house in many ways. (How?) » SDLC generally consists of four fundamental phases. » Each phase comprises a series of steps, relying on techniques (files and documents that provide understanding about the project). Lecturer: Dr. Mohammed Suleiman 2024/2025 General Phases of SDLC 1. Planning 2. Analysis 3. Design 4. Implementation System Development Life Cycle (SDLC) » In some projects, the SDLC phases follow sequentially. » In others, the SDLC is an iterative process. » In some situations, several phases may run concurrently. » Some organizations do not follow the SDLC phases in the exact same manner. Phases of SDLC » Some analysts divide the SDLC into additional phases. Why is planning necessary? » A good understanding of how the system will improve business. » Focus on business first, then on the technology. » Cooperation between business and IT is essential for creating a good system plan. 1. General Phases of SDLCPlanning ~ In this phase, the question "Why should we build a system?" is answered. Planning consists of two steps: A. Project initiation: Identifies the business value of the project. Explains how it will reduce costs and increase profits. A system request presents a brief summary of a business need and explains how the system will help the business make more profit. General Phases of SDLC ~ A system request is a document that explains the business reasons for building the system and the value it may return. ~ It is suggested and performed by the project sponsor. ~ It is submitted to the approval committee. » The business request form includes five elements: 1. Project sponsor: The person who will serve as the primary contact for the project.  2. Business need: The reason for building the system. General Phases of SDLC 3. Business requirements: The business capabilities that the system will provide. 4. Business value: The benefits that the system will create for the company. 5. Special issues or constraints: Issues relevant to the system's implementation. » The Information System department works with the system request department to conduct a feasibility analysis. General Phases of SDLC » Feasibility analysis examines key aspects of the proposed project, addressing the following issues: a) Technical feasibility b) Economic feasibility c) Organizational feasibility » The system request and feasibility analysis documents are submitted for project approval. General Phases of SDLC B. Project approval: » If the project is approved, it proceeds to project management. » The project manager assigns staff and provides a work plan. 1. Feasibility AnalysisTechnical Feasibility » Can we build the system? » Familiarity with the application—less familiarity increases risk. » Familiarity with technology—less familiarity increases risk. » Project size—larger projects have more risk. » Compatibility with the existing software and hardware—harder integration leads to higher risk. 1. Feasibility Analysis 2. Economic Feasibility » Should we build the system? ~ This is determined by identifying:Development costs 2. Tangible and intangible benefits and costs 3. Annual operating costs 4. Annual benefits 1. Feasibility Analysis 3. Organizational Feasibility » If we build the system, will it be used? ~ How well will the system be accepted by its users? ~ Assessment of Organizational Feasibility:How well do the project goals align with business objectives? (Strategic Alignment) 2. Conduct a stakeholder analysis. » A stakeholder is a person, group, or organization that can affect (or be affected by) the new system. Project Selection » Once the feasibility analysis is completed, a revised system request is submitted to the approval committee to decide whether to proceed with building the project, reject it, or put it on hold. ~ The approval committee examines the business need and the risk involved in building the system. ~ There is an "organizational portfolio" that the approval committee manages for all systems. Project Selection ~ The portfolio includes all projects, categorized by size (small, large) and risk (high risk, low risk). » After completing the feasibility analysis, the approval committee assigns the project to the organizational portfolio and decides whether it is large or small, high risk or low risk.