SDLC Life Cycle

The System Development Life Cycle (SDLC)

The System Development Life Cycle (SDLC) is a systematic process used to develop, implement, and
maintain information systems effectively. It provides a structured framework to ensure that systems
meet business requirements, are developed within budget, and operate efficiently after deployment.

Phases of SDLC

1. System Study (Preliminary Investigation or Problem Definition):

The first phase of SDLC is the system study, where the focus is on determining whether a
new system should be developed. This involves conducting a survey to analyse problems in
the current system (manual or automated) and collecting inputs from various sources.
Alternative solutions are explored, and a feasibility study is conducted to evaluate the best
solution. The selected solution's functions are then defined to lay the foundation for the new
system.

2. System Analysis (Determination of System Requirements):

In this phase, system analysis identifies the requirements for the new system. Data is
collected using tools such as interviews, observations, sampling, research, and
documentation. The collected data is analyzed, and all procedures and requirements are
documented. This phase ensures that the new system is designed to meet user needs and
outlines what the system will achieve.

3. System Design:
The system design phase focuses on creating a detailed plan for the new system. This
includes designing input/output screens, reports, databases, and processes. The design
specifies how the system will operate and provides detailed instructions for programmers.
These specifications ensure that all aspects of the system are clearly defined for
development.

4. System Development:
During system development, the design is transformed into a physical system. Programmers
write code using suitable programming languages and prepare technical documentation for
the system. This phase results in a working system that is ready for testing and
implementation.

5. System Testing:
System testing ensures that the developed system functions as intended. It is tested for
errors and evaluated to confirm that it meets user requirements. The system is used
experimentally to verify that it operates according to its specifications and provides the
desired results.

6. System Implementation:
In this phase, the system is installed and integrated into daily operations. Activities include
distributing the software to user sites, training users, and managing the transition from the
old system to the new one. This process, known as System Conversion, must be handled
carefully to avoid data loss or corruption during implementation.
 7. System Maintenance and Review:
The final phase involves maintaining the system to ensure its continued effectiveness. This
includes correcting errors, upgrading features, and adapting to changing user needs. System
maintenance provides ongoing support and ensures that the system continues to meet
organizational requirements.

Feasibility Study

A feasibility study is the most important activity in the system analysis phase. It analyzes the
proposed system from different aspects to determine how practical or beneficial the system will be
for the organization. It answers whether the system is feasible to design or not.

Need for Feasibility Study

• Determines whether the system meets the goals of the clients.

• Identifies strengths and limitations before starting system development.

• Defines the boundaries of the system's outline.

• Suggests new opportunities through the investigation process.

• Provides quality information for decision-making.

• Documents the investigated system.

Types of Feasibility Study

1. Economic Feasibility:
Focuses on the cost-effectiveness of the system. It calculates approximate costs
(development and operational) and evaluates the benefits of the system.

2. Technical Feasibility:
Assesses the availability of hardware, software, and support equipment for the complete
development of the system.

3. Operational Feasibility:
Concerns the smooth operation of the system and identifies potential problems during
system operations after deployment.

4. Behavioral Feasibility:
Examines user and societal acceptance of the new system. Traditional employees may resist
upgrading to a new system.

5. Social Feasibility:
Determines whether the proposed system will be acceptable to the people it affects.

6. Management Feasibility:
Determines whether the proposed system will be acceptable to the management.
 7. Schedule (Time) Feasibility:
Involves splitting the project into tasks and estimating the time and resources required to
complete each task. It determines deadlines and schedules tasks accordingly.

8. Legal Feasibility:
Addresses legal aspects of the system. If the system violates laws or regulations, it cannot
proceed. This includes considerations like copyright law, foreign law, trade regulations, and
tax laws.

Who is a Software Project Manager?

A Software Project Manager is a professional responsible for planning, organizing, leading, and
controlling software development projects. They ensure that the project is completed within the
defined scope, timeline, and budget while meeting quality standards. The SPM acts as a bridge
between stakeholders, development teams, and upper management, ensuring smooth
communication and collaboration.

What are the roles of a Software Project Manager?

The roles of an Software Project Manager can be divided into Managing People and Managing
Projects:

1. Managing People

• Leadership:
Acts as the project leader, inspiring and guiding the team toward project goals.

• Stakeholder Communication:
Serves as a liaison between clients, stakeholders, and the development team. Represents the
project as its spokesperson in meetings.

• Human Resource Management:

Manages team members, assigning tasks, resolving conflicts, and fostering growth. Motivates
the team to stay aligned with project objectives.

• Reporting Hierarchy:
Establishes and oversees a reporting structure to streamline communication and decision-
making.

2. Managing Projects

• Project Planning:
Defines the project scope, goals, and deliverables. Develops detailed project schedules,
budgets, and resource plans.
 • Execution and Monitoring:
Oversees all project management activities, tracks progress, and ensures compliance with
timelines and standards. Conducts risk analysis and takes preventive actions.

• Problem-solving:
Identifies and resolves project issues, proactively addressing challenges to ensure smooth
progress.

• Process and Quality Management:

Ensures processes are followed and quality benchmarks are met.

• Deliverables:
Ensures the final product aligns with stakeholder expectations and meets the agreed-upon
requirements.

Note: A Software Project Manager balances technical expertise, leadership, and organizational skills
to ensure the project's success while maintaining team satisfaction and stakeholder trust.

A stakeholder in a project is any individual, group, or organization that has an interest in, influence
on, or is impacted by the project's outcome, either directly or indirectly. Stakeholders can be internal
(within the organization) or external (outside the organization), and their involvement may vary
depending on their roles and the nature of the project.

A system analyst is a key person in the system development process who analyses the existing
system and designs, implements, and evaluates a new system that addresses the limitations of the
existing one.

Software engineers have extensive knowledge of programming languages, software development,

and computer operating systems. They apply engineering principles to software creation.

Differentiate between System Analyst and Software Engineer

Aspect System Analyst Software Engineer

Core Analyzes how systems serve business Designs and develops high-quality
Responsibility needs and suggests improvements. software.

Focus Explores and documents requirements. Creates software to meet requirements.

Tracks project progress, ensures quality

Develops, tests, and programs the
Role in Projects control, and communicates user
software.
preferences to developers.

Terms like "software engineer,"

Terminology A distinct role focused on analysis. "programmer," and "developer" are
often interchangeable.
Aspect System Analyst Software Engineer

Works with large data sets — scraping, Builds new software or adds features to
Data Handling visualizing, and ensuring system existing ones (desktop, web, mobile, or
compatibility. cloud).

Develops software to address problems,

Problem- Researches problems and recommends
focusing on architecture, OS, memory,
Solving system or software solutions.
and interfaces.

Experience and Typically more experienced and higher Typically less experienced and lower
Pay paid. paid.

Desirable Characteristics/Qualities/Attributes of a System Analyst

To be a successful system analyst, one must possess the following characteristics:

1. Knowledge of Organization:
A system analyst must understand how various functions of an organization operate. They
should have a thorough knowledge of the organization's structure, the relationships among
its departments, and its day-to-day operations.

2. Technical Knowledge:
A system analyst should have good knowledge of new technology and be well-trained in
relevant areas of computer science. They must be familiar with both the hardware and
software aspects of computers and their development processes. Understanding
programming concepts and techniques is crucial to designing systems that can be
implemented effectively.

3. Good Interpersonal Communication Skills:

A system analyst must be able to communicate intelligently with high-level management,
technical staff, non-technical users, programmers, and operators. They need to influence
people, change mindsets, motivate teamwork, and resolve conflicts. Being a good listener
and diplomat is essential.

4. Character and Ethics:

A system analyst must possess a strong moral character and a sense of ethics. The nature of
their job demands integrity and ethical behavior. Ethics involves understanding the
difference between "right" and "wrong" and acting accordingly.

5. Problem-Solving Skills:
A system analyst must have extensive experience in solving problems. They should be adept
at using appropriate analytical tools to address issues as necessary.

6. Systems Analysis and Design Skills:

A system analyst needs strong knowledge and experience in systems analysis and design.
Their primary responsibility is to analyse the requirements of a system and design it
accordingly.
Roles and Responsibilities of System Analyst in SDLC Phases

The major roles or responsibilities of a system analyst are:

1. Defining Requirements:
This involves understanding users' requirements by interviewing them to determine what
information is being used in the current system, how it is being used, and what their
expectations are for the proposed system.

2. Prioritizing Requirements:
Each user in the organization may have specific needs, but it may not be possible to fulfill
everyone's requirements. Therefore, the system analyst must prioritize the requirements of
various users to ensure the most critical ones are addressed first.

3. Gathering Data, Facts, and Opinions from Users:

The system analyst must collect all necessary data from users and consider their opinions.
The system's development must involve the active and willing cooperation of all users.

4. Analysis and Evaluation:

The system analyst analyses the functioning of the current information system within the
organization. They sift through the facts and opinions gathered and determine the best
characteristics for a new or modified system.

5. Solving Problems:
A system analyst must study problems in depth and suggest alternative solutions to the
management. They need to consider the difficulties in implementing each alternative and
the benefits, so the management can select the best solution.

6. Drawing Up Specifications:
The system analyst's job is to create functional specifications for the system to be designed in
a way that users can understand. The specifications must be non-technical for managers and
users, while being precise and detailed enough for system implementers. These
specifications should also account for potential future expansions.

7. Designing the System:

Once the specifications are approved, the system analyst designs the system. The design
must be clear to the implementers and modular so that it can easily accommodate changes if
needed.

8. Evaluating the System:

The system analyst evaluates the system after it has been in use for a reasonable period.
They decide when and how the evaluation will be conducted, gather user feedback, and
make necessary adjustments.

Importance of SDLC in the Software Development Process

The System Development Life Cycle (SDLC) is a systematic process used for developing an
information system. SDLC has significantly impacted program developers by simplifying the job of
software development and reducing its complexity.

The importance and necessity of SDLC are:

1. Facilitates Communication:
The SDLC process ensures constant communication between the developer and the client
during the development phase.

2. Helps Identify Missing Functionality:

The SDLC model makes it easy to identify missing functionalities in the system.

3. Provides Immediate Problem Resolution:

The SDLC model simplifies problem-solving by allowing immediate resolution of issues.

4. Supports Flexible and Innovative Designs:

SDLC models allow for designs that are flexible and encourage innovation.

5. Enables Adding Functions Later:

The SDLC model provides flexibility to add more functions and features even at a later stage
of development.