Software Process

CSS CS Optional — Paper-I, Section-B, Topic V.

🔑 Definition

• Software Process = structured set of activities to turn a requirement into a delivered, working system.

📌 Generic Process Activities (all models = different arrangements of these 4)

• Specification — what should the system do, under what constraints.
• Development — design + implementation.
• Validation — checking it does what was asked.
• Evolution — changing it as needs change after delivery.

📌 Umbrella Activities (run throughout, not at one stage)

• SQA
• Project tracking
• Risk management
• Documentation
• Measurement/metrics

⚠️ MCQ Trap

• Happens once, at one stage → process activity.
• Happens continuously across the project → umbrella activity.
• e.g. Risk management = umbrella, NOT one of the 4 generic activities.

📜 Past-Paper Questions & MCQs (CSS 2016–2026)

2016 · Paper-I · Q7(c) · 5 marks

Q. Describe the Software Development Life Cycle (SDLC). Explain with the phases of the pure waterfall model.

Ans.

• SDLC is the structured process of planning, creating, testing, delivering and maintaining software.
• Waterfall phases (each phase finishes and passes its output to the next, like water falling):

Requirements → Design → Implementation (coding) → Testing → Deployment → Maintenance

• Requirements: gather and document what the system must do (SRS).
• Design: plan the architecture, data and interfaces (design document).
• Implementation: write the code from the design.
• Testing: verify and validate the system against requirements.
• Deployment and maintenance: release the software, then fix errors and add changes.
• Pros: simple, well documented and easy to manage. Cons: inflexible, late testing, and poor when requirements change.