Courses / Application of ICT (GEN-103) – BS 1st Semester

Week 6 Theory – Software Development Life Cycle (SDLC)

Week 6 – Software Development Life Cycle · 60 min read · 27 MCQs to check yourself

What is SDLC?

The Software Development Life Cycle (SDLC) is a structured, step-by-step process used to plan, analyse, design, build, test, deploy and maintain software (or an information system). It defines what must be done at each stage, who does it and what output each stage produces.

Importance of SDLC

Phases of SDLC

 1 Planning ─► 2 Analysis ─► 3 Design ─► 4 Development (Coding)
                                                 │
 7 Maintenance ◄─ 6 Deployment ◄─ 5 Testing ◄────┘
        └──────────── feedback for the next cycle ───────┘

1. Planning (preliminary investigation / feasibility study)

2. System analysis (requirements analysis)

3. System design

4. Development (coding / implementation)

5. Testing

6. Deployment (installation / implementation)

7. Maintenance

Personnel involved in SDLC

Person Role
Project Manager Plans the project, sets schedule and budget, assigns tasks, monitors progress, manages risks and communicates with stakeholders. Responsible for delivering on time and within budget.
System Analyst The bridge between users and developers: studies the existing system, gathers requirements, prepares the SRS, and designs the solution (DFDs, specifications).
Programmer (Software Developer) Writes, debugs and documents program code according to the design; fixes errors found in testing.
Software Tester (QA Engineer) Designs test cases, tests the software, reports bugs and verifies fixes; ensures quality.
Customer / End User Provides requirements, reviews designs, participates in acceptance testing, and finally uses the system; gives feedback.

Others: database administrator, UI/UX designer, network administrator, technical writer, trainer.

SDLC models (approaches)

Model Idea Suitable when
Waterfall Phases in strict sequence; each completes before the next begins Requirements are clear and fixed
Prototyping A quick working model is built and refined with user feedback Requirements are unclear
Spiral Repeated cycles with risk analysis in each loop Large, high-risk projects
Incremental / Iterative System built in small parts (increments) Early delivery of core features
Agile (Scrum) Short iterations (sprints of 1–4 weeks), continuous customer feedback, working software delivered frequently Changing requirements, modern apps
V-Model Each development phase has a matching testing phase Safety-critical systems

Software Development Life Cycle: Explained (AltexSoft)

Software Engineering – Crash Course Computer Science #16

Short and long questions

1. What is SDLC? Explain its importance and any two SDLC models.

Model answer

SDLC is a systematic, phased process (planning, analysis, design, development, testing, deployment, maintenance) for building software. Importance: gives a clear roadmap and deliverables; ensures requirements are met; controls cost and schedule; detects errors early; improves quality, documentation and communication; reduces risk. Waterfall model: phases follow one another in sequence; simple and easy to manage; good for fixed requirements; difficult to accommodate changes. Agile model: development in short sprints with continuous customer involvement; working software delivered frequently; adapts easily to changing requirements; needs close teamwork.

2. Write any four advantages (importance) of SDLC.

Model answer

(1) Clear planning and goals for each phase; (2) better control of cost and time; (3) early detection of errors and higher quality; (4) better communication and documentation; (5) reduced project risk.

3. Define SDLC.

Model answer

The Software Development Life Cycle is a structured process consisting of phases — planning, analysis, design, development, testing, deployment and maintenance — used to develop high-quality software that meets user requirements within time and budget.

4. Explain the phases of SDLC in detail.

Model answer

1. Planning: identify the problem and scope; conduct a feasibility study (technical, economic, operational, schedule, legal); prepare budget and schedule. 2. Analysis: study the current system; gather requirements through interviews, questionnaires and observation; define functional and non-functional requirements; produce the SRS. 3. Design: plan how the system will work – architecture, modules, DFDs, database tables, user interfaces, reports and algorithms; produce the design document. 4. Development: programmers write and integrate code, create the database and fix errors. 5. Testing: unit, integration, system and acceptance (alpha/beta) testing to find and remove bugs and confirm requirements are met. 6. Deployment: install the system, convert data, train users, provide manuals; changeover methods – direct, parallel, pilot, phased. 7. Maintenance: corrective, adaptive, perfective and preventive maintenance throughout the system's life; major changes begin a new cycle.

5. What are the types of maintenance?

Model answer

Corrective (fix bugs), adaptive (adjust to new environment), perfective (add features/improve performance) and preventive (prevent future problems).

6. Name the four levels of testing.

Model answer

Unit testing, integration testing, system testing and acceptance testing (alpha and beta).

7. What is a feasibility study? Name its types.

Model answer

A feasibility study checks whether a proposed system is practical and worth developing. Types: technical, economic (cost–benefit), operational, schedule and legal feasibility.

8. Describe the personnel involved in SDLC and their responsibilities.

Model answer

Project manager: plans the project, sets budget and schedule, assigns tasks, monitors progress, manages risk and communicates with stakeholders. System analyst: investigates the current system, collects requirements, prepares the SRS, designs the system and links users with developers. Programmer: writes, tests (debugs) and documents code according to the design; fixes reported bugs. Software tester: prepares test plans and cases, performs testing at different levels, reports defects and ensures quality. Customer/end user: provides requirements, reviews prototypes/designs, performs acceptance testing, uses the system and gives feedback. Other roles may include database administrator, UI/UX designer and trainer.

9. What is the role of a software tester?

Model answer

A tester designs and runs test cases, finds and reports bugs, verifies that fixes work and ensures the software meets requirements and quality standards.

10. What is the role of a system analyst?

Model answer

A system analyst studies the existing system, gathers and documents user requirements (SRS), designs the new system's logic and acts as a link between users/management and programmers.

11. What is the waterfall model?

Model answer

The waterfall model is a linear SDLC model in which phases are performed in strict sequence — each phase is completed and approved before the next begins. It is simple but inflexible to changes.

This lesson ends with a quiz of 27 MCQs. Open the lesson on PrepOasis to take it and save your progress.

Previous: Week 5 Lab 5 – MS Word: Interface, Documents, Editing Text, Page Borders and Table of Contents · Next: Week 6 Lab 6 – MS Word: Symbols, Equations, Font, Paragraph and Page Formatting, Find & Replace

All lessons in Application of ICT (GEN-103) – BS 1st Semester