SYSTEM DEVELOPMENT LIFECYCLE (SDLC) PHASES/STEPS

Defining the Problem Phase

Definition: In this phase, the problem to be solved or system to be developed is clearly defined.
Description: During this phase, developers collaborate with clients or stakeholders to understand
the purpose of the software. The goal is to make sure that everyone involved has a clear
understanding of the problem the software will solve. By defining the problem, the project can
have a strong foundation and clear direction from the start.

Planning Phase
Definition: The planning phase involves outlining the project scope, resources, timeline, and key
deliverables to ensure a structured approach to development.
Description: During this phase, the project team defines what the project will include, allocates
necessary resources such as personnel and budget, and creates a detailed timeline with
milestones and deadlines. The team also explores alternative solutions to the identified problem,
evaluating different approaches to ensure the most effective course of action. If no alternative
solutions are found, the data is organized into a comprehensive project plan and presented to
management for approval.

Feasibility Study Phase

Definition: The feasibility study is the analysis of a proposed system, to determine, whether it is
technically, financially/economically, legally and operationally feasible within the estimated cost
and time.
Description: Different feasibility studies are explained as follows:
Technical Feasibility: Do we have the right technology and skills to build this software?
Economic Feasibility: Is the project affordable, and will it provide good value?
Legal Feasibility: Does the project comply with any necessary laws and regulations?
Operational Feasibility: Will the software work well within the user's organization or
environment?
Schedule Feasibility: Whether a system can be completed within a specified timeframe?
If the project is determined to be feasible in these areas, it can move forward to the next phase.
Analysis Phase

During the analysis phase, developers collect detailed information about what the software needs
to do. They conduct interviews, surveys, and studies to understand the end user's requirements.

By the end of this phase, developers have a clear understanding of the requirements, which will
guide the design and development of the software.

Requirements Engineering Phase

The Requirements Engineering Phase in the Software Development Life Cycle (SDLC) is a
critical stage that focuses on gathering, analyzing, documenting, and managing the requirements
of the software project. This phase ensures that the final product meets the needs and
expectations of stakeholders and users.

Key Activities in the Requirements Engineering Phase

Requirements Gathering: The requirements gathering phase is the step where developers
collect and define what the software needs to do, based on the input from stakeholders and users.
This ensures everyone understands what the software should achieve.

1. Functional Requirements: These describe what the software should do. They outline the
specific tasks and features that the software must have. For example:

 Users should be able to log in and log out securely.

 There should be forms for users to enter their information.

2. Non-Functional Requirements: These explain how the software should work. They
focus on the quality and constraints of the software rather than specific tasks. For
example:

 The software should respond quickly to user actions.

 It should keep user data safe and secure.
Requirements Validation: This activity involves reviewing the documented requirements with
stakeholders to ensure they accurately represent their needs and expectations.

 Verification occurs after requirements have been accepted, concentrating on ensuring that the
requirements are well-defined and free of errors.

 Validation involves reviewing the elicited requirements to ensure they are complete and
accurate, confirming that they meet the actual needs of users and stakeholders.

Requirements Management: Throughout the project, requirements may change due to evolving
user needs or external factors. This activity focuses on tracking changes, ensuring that all
stakeholders are aware of updates, and maintaining the integrity of the requirements throughout
the software development process.

Importance of the Requirements Engineering Phase

The Requirements Engineering Phase is crucial because it lays the foundation for the entire
development process. Well-defined requirements lead to better design, development, and testing,
ultimately resulting in a product that meets user needs and reduces the risk of project failure.
Inadequate requirements engineering can lead to misunderstandings, and increased costs, making
this phase a vital component of successful software development.

Design Phase
Definition: The design phase involves creating a blueprint for how the software will look and
function.
Description: In this phase, developers plan the structure and design of the software. They decide
on elements such as the user interface (UI), database structure, and overall layout. For the user
interface, the project team designs mock-up screen layouts that the developers use to write the
code for the actual interface.
Development (Coding) Phase
Definition: The development phase is where the actual coding of the software takes place.
Description: In this phase, developers write the code based on the design specifications. The
developers design the database, generate the code for the data flow process and design the actual
user interface screens. During this phase, test data is prepared and processed as many times as
necessary to refine the code. Testing may also begin during this phase to catch and fix errors
early.
Testing Phase
Definition: Testing is the process of identifying and fixing errors or bugs to ensure the software
works correctly.
Description: During this phase, the software is tested rigorously to check that it performs as
expected and is free of bugs. The main purpose of testing/verification of the system is to
determine that whether it meets its required results or not.
Deployment Phase
Definition: Deployment is the release of the software to its intended users.
Description: Once the software passes testing, it is deployed or delivered to the client or end-
users. This phase may involve installing the software on user devices or setting it up on servers.
It also includes training users or providing documentation so they can use the software
effectively.
The four deployment methods are given below:
1. Direct Deployment: The old system is completely switched to the new system all at once. It’s
fast but risky because there’s no backup if something goes wrong.
2. Phased Deployment: The new system is introduced bit by bit in steps. This way, problems
can be fixed gradually, making it safer.
3. Parallel Deployment: Both the old and new systems run together for a while. This is safer
because users can still rely on the old system if needed, but it costs more to run both.
4. Pilot Deployment: The new system is first tested in one small area or department. If it works
well, it’s then spread to the rest of the organization, reducing the chance of big issues.
Maintenance Phase
Definition: Maintenance involves making updates and improvements to the software after it has
been deployed.
Description: After deployment, the software may require updates or bug fixes. The maintenance
phase ensures the software continues to operate smoothly and meets any new requirements or
changes in technology. Developers may also add new features or improvements based on user
feedback, keeping the software functional and relevant.