LEEDS BOYS COLLEGE

D I KHAN
CLASS :
12TH
TEACHER NAME : SAFEER
HUSSAIN
CHAPTER NO : 2 nd
CHAPTER NAME : SDLC
**********************************************************
**********

SDLC:
SDLC (Software Development Life Cycle) is a step-by-step process used to plan,
design, build, test, and release software. It helps teams create high-quality software efficiently.

SDLC AND ITS IMPORTANCE:

1. Structured Process – SDLC provides a clear step-by-step framework
to develop software efficiently.

2. Better Planning – Helps define project goals, timelines, and resources

before development starts.

3. Reduces Errors – Early testing and validation prevent major issues in

later stages.

4. Cost-Effective – Detects problems early, saving time and money on

fixes.

5. Quality Assurance – Ensures the final product meets user

requirements and standards.

6. Risk Management – Identifies potential risks early and minimizes

failures.
 7. Clear Documentation – Maintains records for future updates and
team collaboration.

8. Customer Satisfaction – Delivers a well-tested, reliable product that

meets user needs.

By following SDLC, companies can build software smoothly and successfully.

OBJECTIVE OF SDLC:
1. Deliver High-Quality Software – Ensure the final product is reliable,
efficient, and meets user expectations.

2. Meet Customer Requirements – Align development with business

needs and user demands.

3. Control Development Costs – Minimize unnecessary expenses

through proper planning and risk management.

4. Ensure Timely Delivery – Complete projects within scheduled

deadlines.

5. Improve Efficiency – Optimize resources (time, money, effort) for

maximum productivity.

6. Enhance Collaboration – Provide a structured approach for smooth

teamwork among developers, testers, and stakeholders.

7. Reduce Risks & Errors – Identify and fix issues early in the
development process.

8. Support Maintenance & Scalability – Build software that is easy to

update, maintain, and scale for future needs.

By following these objectives, SDLC ensures successful and sustainable

software development.

STAKEHOLDERS OF SDLC:
A stakeholder is any individual,
group, or organization that has an interest in a software project. They can
influence or be impacted by the project’s outcome.

ROLE OF STAKEHOLDER :
 1. Define Requirements – Stakeholders (clients, users) provide input on features,
functionality, and business needs in Written Formate.

2. Planning– Help set goals and budget. Decide what is needed.

3. Project Guidance – Product owners/managers ensure and guide business goals

4. Feedback & Testing – End-users and testers validate the software for usability and
functionality.

5. Risk Management – Identify potential risks (legal, technical, financial) and suggest
mitigation.

6. Quality Assurance – Ensure the final product meets industry standards and compliance.

7. Change Management – Review and approve modifications during development.

8. Post-Launch Support – Provide copy of software to stakeholder to check the software .

9. Stakeholders ensure the project stays on track, meets objectives, and delivers value.

PHASES OF SDLC:
1. Planning

 This is the first step.

 The team thinks about what needs to be done.
 They decide the goals, timeline, and who will do what.

2. Feasibility Study

 The team checks if the project is possible.

 They look at cost(benefit), time(schedule), skills, and tools.
 Ecnonomic Feasibility ,Technical feasibility ,Operational Feasaibility ,Legal Feassibility.
 They ask: Can we really do this? Is it worth it?

3. Analysis phase

 Talk to the people who will use the software.

 End user needs ,expectation
  Check available resources (staff,cost,time,Machinary)
 Will the system improve the org?(cost,branding our company produce good will)

4. Requirement Gathering

 Study the requirements carefully.( gather needs ,req on paper)

 Make sure everything is clear and understood.
 User features must in detailed.(color picture,intrerface…….etc)
 Plan how the software will work.

5. Design

 Create the blueprint (Design) of the software

 How to develop? What to develop?
 Let suppose we make a website used which programming language(HTML,CSS ,JS) and
which h/w and s/w need for this website (HP LAPTOP , 8GB ROM H/W REQ)
(WINDOW S/W)
 Design tools are used and compulsory in design phase(Alogirthm and flow charts)
 Decide how the screens will look, and how everything will work inside.

6. Coding

 Developers write the code to build the software.

 Make Database
 User interface screen (user put the command(communicate) to use the user interface
screen)
 Technical work perform on this phase.
 This is where the real building starts.

7. Testing

 Before the software is delivered to customer.

 Test run must make sure its software is 100% and meet customer expectation .
 Does Functionality meet the customer? (R.E)
 Performance must be checked
 Check the software for mistakes (bugs).
  If any error detect so move to remove this error for those team who developed this s/w.
 Make sure it works correctly.
 Reduce shortcoming.

8. Deployment

 After testing Available for the users to use the desired software.
 1st step is to install and activate the system(For example Resturnment management
system)
 Training the staff( how to use the software if not so staff not used the staff properly)
 Remove Old system and deploy now system (Conversion)
 Setps:

1)Direct deployment.(remove old system and add new system)

2)Paralel dep:(Run old system for some time and deploy new system )

3)Phased dep:(some parts add to the staff sytem so old system working till new sytem
updated)

 The software is given to users.

 It is now ready to be used in the real world.

Diagrammatic Representation of SDLC

Phases
Key Takeaways:

 SDLC ensures a systematic approach to software development.

 Each phase has defined inputs, processes, and outputs.
 Testing and maintenance are crucial for long-term success.

This structured approach helps in delivering high-quality software efficiently.

🚀

Roles of Personnel in SDLC:

The Software Development Life Cycle (SDLC) involves different people
with specific roles. Each person contributes to making the software
successful. Let’s break it down in simple terms with examples!

Management
 Role:They provide the overall direction and resources for the software project,
ensuring it aligns with the company's goals.

 In simple terms:The boss or leaders who decide what the software project is for
and how important it is.
Project Manager

 Role:They manage the day-to-day activities, resources, and schedule to make sure
the project is completed on time and within budget.
 In simple terms:The person in charge of the project team, making sure everyone is
working together and on the right tasks.
System Analyst

 Role:They translate the customer's needs and business requirements into detailed
specifications for the system to be built.
 In simple terms:A detective who figures out what problems the software needs to
solve and what features it should have, acting as a bridge between the customer and
the technical team.
Programmer (or Developer)

 Role:They write the code and build the software according to the designs and
specifications provided by the analysts and architects.
 In simple terms:The person who builds the software by writing instructions (code) that
computers can understand.
Software Tester

 Role:They test the software to find bugs and errors, ensuring that it works correctly
and meets the customer's expectations.
 In simple terms:The quality checker who makes sure the software works as it's
supposed to and doesn't have any mistakes.
Customer

 Role:The user or client who needs the software. They provide the initial ideas and
requirements, give feedback throughout the project, and approve the final product.
 In simple terms:The person who wants the software and provides the requirements
and feedback, ensuring the final product actually helps them.
Diagram: How SDLC Team Works Together

┌─────────────┐
│ Management │ ← Approves Budget & Goals
└──────┬──────┘
↓
┌──────┴──────┐
│Project Manager│ ← Manages Team & Deadlines
└──────┬──────┘
↓
┌──────┴──────┐
│System Analyst│ ← Defines Requirements
└──────┬──────┘
↓
┌──────┴──────┐
│ Programmer │ ← Writes Code
└──────┬──────┘
↓
┌──────┴──────┐
│Software Tester│ ← Finds Bugs
└──────┬──────┘
↓
┌──────┴──────┐
│ Customer │ ← Uses & Gives Feedback
└─────────────┘

Real-Life Example (E-commerce App Development)

1. Management says: "Build an app to boost sales."

2. Project Manager plans: "6 months timeline, $50K budget."
3. System Analyst defines: "Users need login, cart, and payment."
4. Programmer codes: "Uses Java for backend, React Native for mobile."
5. Tester checks: "Does the app work on iOS and Android?"
6. Customer tries it and says: "The checkout is confusing!" → Team
improves it.

DIFFERENTIATE B/W ALGORITHM AND PSEUDO CODE:

Algorithm:

 An algorithm is a step-by-step process to solve a problem.

 It is written in plain and simple language (not a programming language).
  Example: Steps to make tea (boil water → add tea leaves → add sugar → add milk →
serve).

Pseudocode:

 Pseudocode looks like a program but is written in simple English mixed with
programming style.
 It shows how the actual code will look but is not a real programming language.
 Example:

Start
Boil water
Add tea leaves
Add sugar
Add milk
Serve tea
End