System Development Life Cycle (SDLC)

• The System Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from initial feasibility study through maintenance.
• The SDLC provides a structured sequence of steps for developing new information systems and associated software projects.
• The SDLC framework isn't always linear; its implementation can be iterative, depending on the project's requirements.

Common SDLC Stages

• Planning: Outlining the project's goals, scope, and feasibility.
• Requirements: Defining and documenting the system requirements.
• Design: Designing the system architecture components.
• Development: Building and testing the system.
• Integration and Testing: Integrating individual components and testing the system as a whole.
• Implementation: Deploying the system to the production environment.
• Maintenance: Ongoing support, updates, and bug fixes.
• Disposal: Planning end-of-life of a system, including data migration and hardware disposal.

1. Planning

• Involves defining the project's objectives, scope, and feasibility.
• Assessment of whether the project is worth pursuing.
• Key activities include:
  • Identifying the problem or opportunity
  • Determining project scope
  • Conducting a feasibility study (technical, economic, operational, etc.)
  • Defining project goals and objectives
  • Develop a project plan, including timelines, resources, and budget
• Output: Project plan and feasibility report.

2. Requirements

• Focuses on gathering and documenting detailed requirements for the system.
• Requirements can be functional (what the system should do) and non-functional (how well it should do it).
• Key activities include:
  • Gathering requirements from stakeholders through interviews, surveys, workshops, etc.
  • Documenting requirements in a clear and concise manner (e.g., use cases, user stories, etc.)
  • Creating a requirements traceability matrix to ensure that each requirement is addressed
• Output: Requirements documentation.

3. Design

• Involves creating a blueprint for the system based on the documented requirements.
• Focuses on defining the system architecture, modules, interfaces, and data.
• Key activities include:
  • Developing a high-level architectural design
  • Designing the database schema
  • Designing user interfaces (UI) and user experience (UX)
  • Specifying hardware and software requirements
• Output: System design specification.

4. Development

• The actual coding and building of the system components according to the design specifications.
• Translating design documents into actual code.
• Key activities:
  • Writing code
  • Conducting unit testing of individual components
  • Following coding standards and best practices
  • Code review
• Output: Functional system components and code.

5. Integration and Testing

• Individual components are integrated and tested as a complete system.
• Ensures that all parts of the system work together correctly.
• Key activities include:
  • Integrating individual components
  • Conducting system testing (functional, performance, security, etc.)
  • Performing user acceptance testing (UAT) with stakeholders
  • Bug fixing and re-testing
• Output: Tested and integrated system.

6. Implementation

• The process of deploying the system to the production environment.
• Making the system available to end-users.
• Key activities include:
  • Data migration from old systems to the new system
  • Training end-users on how to use the new system
  • System deployment
  • Providing initial support to users
• Output: Operational system in the production environment.

7. Maintenance

• Providing ongoing support for the system after it has been deployed.
• Addressing bugs, implementing enhancements, and adapting the system to changing requirements.
• Key activities include:
  • Monitoring system performance
  • Providing help desk support
  • Applying bug fixes and patches
  • Implementing system updates and upgrades
• Output: Maintained and updated system.

8. Disposal

• Planning for the end-of-life of a system.
• Involves migrating data, decommissioning hardware, and ensuring that sensitive data is properly handled.
• Key activities include:
  • Planning for data migration or archiving
  • Decommissioning hardware and software
  • Ensuring data security and compliance
• Output: Secure and compliant system disposal.