Courses / Computer Science XI (HSSC-I) – FBISE Complete SLO-Based Course
1.3 Systems Design: SDLC and Software Development Methodologies
Unit 1 – Computer Systems · 70 min read · 13 MCQs to check yourself
SDLC explained – Waterfall vs Agile vs Spiral vs V-Model
1. What is the SDLC?
The Software Development Life Cycle (SDLC) is a structured process for planning, creating, testing and maintaining software. It turns an idea into working software on time, within budget and with good quality, and it controls risk by finding problems early. Software development is an engineering activity: like building a bridge, it needs requirements, a design, careful construction, inspection and maintenance.
2. Phases and their activities
| Phase | Key activities | Output (deliverable) |
|---|---|---|
| 1. Planning & feasibility | Define the problem and scope; check technical, economic (cost–benefit), operational, legal and schedule feasibility | Feasibility report, project plan |
| 2. Requirement analysis | Interview users, questionnaires, observe the current system; list functional (what it does) and non-functional (speed, security, usability) requirements | Software Requirements Specification (SRS) |
| 3. Design | Architecture, database design, user-interface mock-ups, algorithms; draw UML diagrams (use-case, class, sequence), flowcharts and DFDs | Design document |
| 4. Coding (development) | Programmers write the code in a programming language following the design and coding standards | Source code, working modules |
| 5. Testing | Find and fix bugs: unit, integration, system and acceptance (user) testing | Test report, bug list |
| 6. Deployment (implementation) | Install the software, convert data, train users; choose a changeover method | Live system, user manual |
| 7. Maintenance | Corrective (fix bugs), adaptive (new OS/law), perfective (new features), preventive | Updated versions |
Implementation (changeover) methods
| Method | How | Best when |
|---|---|---|
| Direct (big-bang) | Old system stops, new starts the same day | Small, low-risk systems |
| Parallel | Old and new run together for a while | Critical data, e.g. hospital or bank – safest but most expensive |
| Pilot | New system tried in one branch/department first | Organisations with many branches |
| Phased | Introduced module by module | Large systems that can be split |
Case study (model paper): a city hospital upgrading patient-care software should use parallel (or pilot) implementation: patient records are life-critical, so the old system must keep running until the new one is proved correct; staff need time to be trained; data security must be tested before the old system is switched off.
3. Testing: black-box and white-box
| Black-box testing | White-box testing | |
|---|---|---|
| Tester knows the code? | No – only inputs and expected outputs | Yes – the internal logic and paths |
| Based on | Requirements / specification | Program structure (statements, branches, loops) |
| Done by | Independent testers, users | Programmers |
| Example | Enter marks 105 in a result app → expect "invalid marks" | Make sure every if and else branch of the grading code runs at least once |
| Also called | Functional / behavioural testing | Structural / glass-box testing |
Test data types: normal (valid, e.g. 75), boundary/extreme (0, 100), and erroneous/abnormal (−5, "abc").
Bug vs debugging: a bug is an error or fault that makes software behave incorrectly; debugging is the process of finding and removing it (Unit 3 covers Python debugging).
4. Software development methodologies
Waterfall model: linear and sequential. Requirements are fixed at the start and documented in detail.
- ✔ Simple to manage, clear milestones and documents, easy to estimate cost.
- ✘ Late testing, changes are very expensive, the customer sees the product only at the end.
- Best for: projects with stable, well-understood requirements – construction-like or safety-critical projects, government contracts, embedded systems.
Agile model: iterative and incremental. Work is done in short sprints (1–4 weeks); each sprint produces working software that the customer reviews. Scrum and Kanban are popular Agile frameworks. Roles in Scrum: product owner, scrum master, development team. Daily stand-up meetings keep everyone aligned.
- ✔ Welcomes changing requirements, early and continuous delivery, customer feedback, risks found early.
- ✘ Harder to predict final cost/time, needs an involved customer, less documentation.
- Best for: web and mobile apps, start-ups, marketing campaigns, research projects – anything where requirements change.
| Basis | Waterfall | Agile |
|---|---|---|
| Approach | Sequential | Iterative, incremental |
| Requirements | Fixed at the start | Can change every sprint |
| Customer involvement | Start and end | Continuous |
| Testing | After coding is complete | In every sprint |
| Delivery | One final product | Frequent working releases |
| Documentation | Heavy | Light ("working software over documentation") |
| Risk | Discovered late | Discovered early |
Model paper practice – which model? Building construction → Waterfall · developing a web application → Agile · digital marketing campaign → Agile · automobile production → Waterfall · public works projects → Waterfall · research projects → Agile.
Other models: Spiral (risk analysis in every loop – large, high-risk projects), V-model (each development phase has a matching test phase), Prototyping / RAD (quick working model shown to users).
5. UML and design patterns
UML (Unified Modeling Language) is a standard set of diagrams for designing software: a use-case diagram shows actors and what they can do; a class diagram shows classes, attributes and methods; a sequence diagram shows messages over time. A design pattern is a proven, reusable solution to a common design problem (e.g. Singleton, Observer, Model–View–Controller).
6. Planning a small project from start to end (example)
Project: "College Library App"
- Planning: goal = students search and reserve books; budget, 10-week schedule; feasible with free tools.
- Analysis: interview librarian and 20 students → requirements: search by title/author, reserve, due-date reminders; must work on phones.
- Design: screens sketched in Figma, database tables Books/Students/Loans, use-case diagram.
- Coding: Python/Flask back end, web front end, in 3 Agile sprints.
- Testing: black-box test cases (search for a missing book, reserve twice), white-box tests of the due-date function.
- Deployment: pilot in the CS department first, then the whole college; train library staff.
- Maintenance: fix bugs, add barcode scanning next term.
Understanding Waterfall and Agile approaches in the SDLC
Short and long questions
1. What is SDLC? Name its phases in order.
Model answer
The Software Development Life Cycle is a structured process used to plan, develop, test, deploy and maintain software so that it is delivered on time, within budget and with good quality. Phases: 1. Planning/feasibility 2. Requirement analysis 3. Design 4. Coding (development) 5. Testing 6. Deployment (implementation) 7. Maintenance.
2. Differentiate between black-box and white-box testing.
Model answer
| Black-box testing | White-box testing |
|---|---|
| Tester does not know the internal code | Tester knows the code and logic |
| Based on requirements – inputs and expected outputs | Based on program structure – statements, branches, loops |
| Done by testers/users | Done by programmers |
| Example: enter invalid marks and expect an error message | Example: make every if/else branch run at least once |
3. A city healthcare provider is upgrading its software to improve patient care and data security. Recommend the most suitable implementation method and justify it with two considerations.
Model answer
Recommended method: parallel implementation (old and new systems run side by side for a period). Justification: (1) patient records are critical – if the new system fails, the old one is still working, so no data or treatment is lost; (2) outputs of both systems can be compared to prove the new system is correct and secure before the old one is switched off. (Staff also get time to be trained.)
4. Identify whether the Waterfall or Agile model is more suitable: (a) building construction (b) developing a web application (c) digital marketing campaign (d) automobile production (e) public works project (f) research project.
Model answer
(a) Waterfall – fixed requirements, sequential stages. (b) Agile – requirements change, frequent releases. (c) Agile – the campaign is adjusted after feedback. (d) Waterfall – fixed design and production steps. (e) Waterfall – fixed contract, documented stages. (f) Agile – outcomes are uncertain and change as results come in.
5. What is feasibility study? Name any four types.
Model answer
A feasibility study checks, before development starts, whether the proposed system is possible and worthwhile. Types: technical (do we have the technology and skills?), economic (do benefits exceed costs?), operational (will users accept and use it?), schedule (can it be finished on time?), legal (does it follow the law?).
6. Give three advantages and two disadvantages of the Agile model.
Model answer
Advantages: (1) changes in requirements are welcomed at any sprint; (2) working software is delivered early and frequently; (3) continuous customer feedback improves quality and finds risks early. Disadvantages: (1) total cost and time are hard to predict; (2) needs constant customer involvement and produces less documentation.
7. Define bug, debugging and UML.
Model answer
Bug: an error or fault in a program that makes it produce wrong results or behave unexpectedly. Debugging: the process of locating, analysing and removing bugs. UML (Unified Modeling Language): a standard visual language of diagrams (use-case, class, sequence, activity) used to design and document software.
8. Explain the phases of the SDLC with the main activities and output of each phase. Relate each phase to a case study of a "College Library Management System".
Model answer
- Planning & feasibility – define scope, check technical, economic, operational and schedule feasibility; output: feasibility report. Case: goal is online search and reservation of books; cost of hosting and a 10-week plan approved.
- Requirement analysis – interviews, questionnaires, observation; functional and non-functional requirements; output: SRS. Case: librarian and students interviewed; must search by title/author, reserve, send due-date reminders, work on mobiles.
- Design – architecture, database, UI, algorithms, UML diagrams; output: design document. Case: tables Books, Students, Loans; screen mock-ups; use-case diagram.
- Coding – programmers write code using standards; output: source code. Case: web app built in sprints.
- Testing – unit, integration, system, acceptance; black-box and white-box; output: test report. Case: test reserving an unavailable book, overdue fine calculation.
- Deployment – installation, data conversion, training, changeover (direct/parallel/pilot/phased); output: live system. Case: pilot in CS department, then whole college; staff trained.
- Maintenance – corrective, adaptive, perfective, preventive; output: updated versions. Case: bugs fixed, barcode scanning added later.
9. Compare the Waterfall and Agile models. Which would you choose for developing a mobile app for an online shop and why?
Model answer
| Basis | Waterfall | Agile |
|---|---|---|
| Approach | Linear, sequential phases | Iterative, incremental sprints |
| Requirements | Fixed at the start | Can change every sprint |
| Customer involvement | Mainly at start and end | Continuous |
| Testing | After all coding | In every sprint |
| Delivery | One final release | Frequent working releases |
| Documentation | Detailed | Light |
| Risk | Found late, costly | Found early, cheap |
| Best for | Stable requirements: construction, embedded/safety systems | Changing requirements: web/mobile apps, start-ups |
| Choice: Agile. An online-shop app must react to customer feedback, competitors and new payment methods; Agile delivers a basic version quickly (browse, cart, checkout), then adds features (offers, tracking) sprint by sprint, testing all the time. |
This lesson ends with a quiz of 13 MCQs. Open the lesson on PrepOasis to take it and save your progress.
Previous: 1.2 Boolean Algebra, Identities, Duality and Karnaugh Maps · Next: 1.4 Networks: Topologies, Scalability and Reliability
All lessons in Computer Science XI (HSSC-I) – FBISE Complete SLO-Based Course