This post explains how A/L ICT papers ask about systems analysis and design, and how to learn it from the ground level. Unit 7 is tested in every new-syllabus paper from 2019 to 2026. Students lose marks here because they learn the stages as a list of words. The papers ask about one system, from its first problem to its deployment.
The post has four parts:
- How the papers ask: the marks, the scenario format and the stages of one system (sections 1 and 2).
- The joins: how one system joins Python, databases, web and business (section 3).
- The two skills that need care: requirements with scalability, and a process description that becomes Python code (sections 4 and 5).
- How to learn it: build a small system step by step, then try past papers (sections 6 and 7).
1. How the papers ask about Unit 7
Unit 7 has questions in all eight new-syllabus papers, from 2019 to 2026. Each paper has 4 to 10 MCQs and 6 to 16 Paper II marks from this unit. That is 53 MCQs in the eight papers. The 2023 (held 2024) Paper II marks are estimates, because that paper has no marking scheme.
Which levels carry the marks
Four levels carry most of the MCQs. Analysing the current system (7.6) has 12, development models (7.3) have 11, testing (7.8) has 9 and deployment (7.9) has 5. Analysis (7.6) also carries the most Paper II marks: data flow diagrams and requirements come up in every paper.
The scenario format
A Paper II question on this unit starts with a scenario: a hotel, a travel agency, a school library or a bank. Then each part asks about one stage of that system. 2023 (held 2024) P-II A Q4 has seven parts on one system that books the school lab computers, from a data flow diagram to a reason to reject a package. So students must know where each stage sits in the life of a system, not only its definition.
The unit has 68 periods in the syllabus, more than any other Grade 12 unit. A/L ICT units by weight shows that Unit 7 gets about 15% of the periods and about 10% of the marks.
2. One system from problem to deployment
The unit is the life of one system, told in stages. Each stage gives an output that the next stage uses. Learn the stages in this order, with their outputs, and each past paper part finds its place.
The stages and their outputs
- Preliminary investigation (7.5): find the problems in the current system. The Teachers' Guide calls it the first stage of the life cycle (Teachers' Guide 7.5, page 178) (ගුරු අත්පොත 7.5, පිටුව 211).
- Feasibility study (7.5): check whether the new system is practical and worth it. The output is a report, and the project is approved or stopped on it (Teachers' Guide 7.5, page 179) (ගුරු අත්පොත 7.5, පිටුව 211).
- Requirement analysis (7.6): list what the system must do and how well it must do it.
- Analysis tools (7.6): draw the context diagram, the data flow diagrams and the logical data structure.
- Design (7.7): build the logical design, write the process descriptions, and design the tables.
- Development (7.8): write the programs and build the database.
- Testing (7.8): run test cases, from unit testing to acceptance testing.
- Deployment (7.9): install, move the data, train users and switch over.
- Maintenance (7.9): fix errors and add new requirements after the system is in use.
Four feasibility types although the books say three
Both Teachers' Guides say that feasibility is checked on "three main aspects", then list four: technical, economic, operational and organisational (Teachers' Guide 7.5, page 178) (ගුරු අත්පොත 7.5, පිටුව 211). The Sinhala Guide also says "සාධක තුනක්" and lists four. Learn all four. The official 2025 marking scheme asks for all four in 2025 P-II A Q2(a)(i): finding A is technical, B is economic, C is operational and D is organisational (2025 ලකුණු දීමේ පටිපාටිය, පිටුව 36). The Sinhala Guide uses two names for the fourth type, "ආයතනික" and "සංවිධානීය". The 2025 scheme uses "ආයතනික ශක්යතාව".
The order changes with the model
The waterfall model runs the stages once, in order. The Teachers' Guide says it suits "systems where requirements are clear and stable" (Teachers' Guide 7.3, page 174) (ගුරු අත්පොත 7.3, පිටුව 205). The spiral, agile and prototyping models repeat the stages. 2026 P-II B Q10(a)(ii) gives a waterfall project in which the school adds two new features halfway. Students name the limitation and suggest a better model. Our own worked answer, not official: the waterfall model does not take a requirement change easily after its stage is over, so an iterative model such as agile suits this project better. Both Guides say the agile model suits systems where requirements are "fixed or changing" (Teachers' Guide 7.3, page 175) (ගුරු අත්පොත 7.3, පිටුව 206).
3. Where the unit joins other lessons
A system needs data, programs, screens and a business around it, so the unit joins four other units. The papers join them in one question, or keep one scenario across several questions.
Python (Unit 9)
The process descriptions are the bridge to code. An elementary process description has "enough details for program specification" and is "written in plain text or pseudo code" (Teachers' Guide 7.6, page 182) (ගුරු අත්පොත 7.6, පිටුව 215). At the design stage, the Guide asks for the descriptions in pseudo code (Teachers' Guide 7.7, page 184) (ගුරු අත්පොත 7.7, පිටුව 218). Pseudo code is the same tool that Unit 9 uses for algorithms (9.3). 2024 P-II A Q4(c)(ii) asks for one such description: a hotel's final bill with a 10% service charge. Section 5 works it out.
Testing joins Python too. The Sinhala Teachers' Guide gives two Python programs for white box testing in groups (ගුරු අත්පොත 7.8, පිටු 220 සහ 221). The English Guide does not have this exercise.
Databases (Unit 8)
The logical data structure becomes the database. The design stage maps each entity to a table, each attribute to a field and the unique attribute to the primary key. Then it normalises all tables to 3NF (Teachers' Guide 7.7, page 184) (ගුරු අත්පොත 7.7, පිටුව 219). That is the same work as ER mapping (8.6) and normalisation (8.7) in Unit 8. 2025 P-II A Q2 puts both in one question: part (a) is a feasibility study and requirements, part (b) maps an ER diagram to relations. 2021 (held 2022) P-I Q27 asks for the order of the database design steps.
Web (Unit 10)
A system often runs as a website, so the unit joins PHP and MySQL (10.7). 2026 P-II B Q10 is one event registration system in three parts. Part (a) asks for requirements and a development model. Part (b) gives events.php and register.php and asks for SQL. Part (c) asks for a deployment method. PHP and MySQL past paper questions covers the code side.
Business (Unit 12)
An organisation can buy a package instead of building a system, and the unit joins business there. The Guide lists the gap between the package and the business process, and three choices for each gap: ignore it, change the business process, or extend the package (Teachers' Guide 7.10, page 191). The Sinhala Guide explains the gap analysis but does not give the three choices (ගුරු අත්පොත 7.10, පිටුව 233). 2026 P-II A Q2(a)(iv) and 2026 P-II A Q2(a)(v) ask for the process change that fits a package. Part (b) of the same question moves to e-business (12.1, 12.2).
One library across the 2026 paper
The 2026 Paper II keeps one idea, a library, across three questions. 2026 P-II A Q1 shows a book table in HTML and a book issue form sent to issue_book.php. 2026 P-II A Q2 analyses a school library system with a data flow diagram and test cases. 2026 P-II B Q9 asks for Python functions that calculate and search the fines for late books. A student who has built one small library system has met all three.
4. Requirements and scalability
A functional requirement says what the system does. A non-functional requirement says how well it does it, or within what limits (Teachers' Guide 7.6, page 180) (ගුරු අත්පොත 7.6, පිටුව 214). Every new-syllabus paper has at least one question on requirements, in Paper I or in Paper II.
Sort each requirement with one question
Ask: "Is this something the system does, or a quality of how it does it?" The official 2025 scheme gives these answers for 2025 P-II A Q2(a)(iv) (2025 ලකුණු දීමේ පටිපාටිය, පිටුව 37):
- Functional: book tours online, get the invoice online, let authorised people update or delete tour details, and make reports.
- Non-functional: the system is secure, it is available 24 hours a day (24x7), and it responds within three seconds.
Write requirements the IEEE way
The Guide writes requirements with the IEEE words: essential requirements use "shall", and nice-to-have requirements use "should" (Teachers' Guide 7.6, page 180) (ගුරු අත්පොත 7.6, පිටුව 214). For example: "The system shall issue a receipt after each registration." Write each requirement as one sentence about one need.
Where scalability fits
Scalability means that a system keeps working well when its users or its data grow. The syllabus and the Teachers' Guides do not use the word. In the papers it comes as a non-functional requirement or as a feasibility finding:
- 2025 P-II A Q2: the agency's demand is growing, and the system must be available 24x7 and respond within three seconds. The scheme files the growth finding D under organisational feasibility.
- 2026 P-II B Q10(a): the system must let students reach it "at any time from different places". That is a non-functional requirement.
5. From a process description to Python
A process description is an algorithm for one process. Write it in pseudo code first, then the code is a short step. 2024 P-II A Q4(c)(ii) asks for the description of process 2, "produce the final bill", for a hotel. The final bill adds a 10% service charge to the total.
The process description
Here is our own worked answer, not official:
BEGIN Produce final bill
READ room charge, restaurant charge, service centre charge
total = room charge + restaurant charge + service centre charge
final bill = total + total * 10 / 100
OUTPUT final bill
END
The same process in Python
def final_bill(room, restaurant, service_centre):
total = room + restaurant + service_centre
return total + total * 10 / 100
print(final_bill(1000, 500, 500)) # 2200.0
Each line of the pseudo code becomes one line of Python. REPEAT UNTIL to Python in 2026 MCQ 40 shows the same move from pseudo code to Python for a loop.
Test cases join testing and Python
A test case is a set of actions that checks one feature (Teachers' Guide 7.8, page 185) (ගුරු අත්පොත 7.8, පිටුව 220). Black box testing uses only the inputs and the expected outputs. White box testing reads the code and tests its statements, branches and paths. 2026 P-II A Q2(a)(vii) describes a tester who runs test cases for valid and invalid ID types without knowing the inside of the module. Our own worked answer, not official: that is black box testing, because the tester checks only inputs and outputs.
The Sinhala Teachers' Guide's first white box program gives a good test. It finds the largest of 14, 10 and 13 with if, then if and else. It prints 13, not 14, because the second if should be elif (ගුරු අත්පොත 7.8, පිටුව 221). Its second program reads the height with int(input(...)), so a height such as 1.7 stops it with an error. A white box test finds both faults. Run them and fix them.
The Sinhala Guide also calls black box testing "කාල මංජුසා පරීක්ෂාව" (ගුරු අත්පොත 7.8, පිටුව 220). "කාල" means time, so this reads as a misprint for "කළු" (black). The English Guide says black box testing (Teachers' Guide 7.8, page 185).
6. Build a small system to learn the unit
Build one small system from start to end. Each stage then has a real output, and the definitions follow from the work. The syllabus already asks for this: Unit 14 is a 30-period project that goes through the stages from problem identification to implementation (Teachers' Guide 14.1, pages 112 and 113) (ගුරු අත්පොත 14.1, පිටු 113 සහ 114). The Sinhala Guide also tells teachers to give students an assignment to build a database system with the knowledge from Unit 7 (ගුරු අත්පොත 7.6, පිටුව 213) (ගුරු අත්පොත 7.7, පිටුව 218). The English Guide does not print this assignment.
A school library loan system in ten steps
Pick a small system that students know well. A school library loan system fits, and it follows the 2026 paper. Keep each step small.
- Problem statement (7.5): write one paragraph on what goes wrong in the current paper register.
- Feasibility (7.5): write one line for each type: technical, economic, operational and organisational.
- Requirements (7.6): write five functional requirements with "shall" and three non-functional ones, one of them about growth.
- Diagrams (7.6): draw the context diagram, then a level 1 data flow diagram with members, the librarian, the processes and the data stores.
- Tables (7.7, 8.7): turn the entities into tables such as MEMBER, BOOK and LOAN, and normalise them to 3NF.
- Process descriptions (7.7): write the "calculate fine" process in pseudo code.
- Python (9.9, 9.10): write
calculate_fine(late_days)and a search function over a list of tuples, as in 2026 P-II B Q9. - Web (10.7): make one form that issues a book, with PHP that inserts a row into LOAN.
- Testing (7.8): write a table of test cases with input, expected output and actual output. Include invalid inputs.
- Deployment (7.9): try it with one class first. That is a pilot deployment.
Grow it and watch what breaks
Add 1,000 made-up books and members, then search again. Note what gets slow and which requirement covers it. That is scalability in practice, and it shows why a non-functional requirement needs a number, such as "responds within three seconds".
The written report
The Teachers' Guide gives a short report format: title, abstract of the solution, system overview and analysis, system design, the system components with brief code segments, and test data with output (Teachers' Guide 14.1, page 113) (ගුරු අත්පොත 14.1, පිටුව 114). Keep the report to 4 to 6 pages, as the Guide says.
7. Past paper questions to try
Try these in the order of the stages. Answer each part with the stage name first, then the reason.
- 2022 (held 2023) P-II A Q2(a) and 2025 P-II A Q2(a)(i): preliminary investigation and feasibility types (section 2).
- 2025 P-II A Q2(a)(ii): recommend the project with two reasons (section 2).
- 2026 P-II B Q10(a)(ii): a better model when the requirements change (section 2).
- 2025 P-II A Q2(b) and 2021 (held 2022) P-I Q27: from analysis to tables (section 3).
- 2026 P-II B Q10(b): SQL for an event registration system (section 3).
- 2026 P-II A Q2(a)(iv) and 2026 P-II A Q2(a)(v): a package and the business process change (section 3).
- 2025 P-II A Q2(a)(iv), 2026 P-II B Q10(a)(i) and 2021 (held 2022) P-II A Q4(a): functional and non-functional requirements (section 4).
- 2021 (held 2022) P-II A Q4(c), 2024 P-II A Q4(c)(i) and 2026 P-II A Q2(a)(vi): data flow diagrams (section 4).
- 2024 P-II A Q4(c)(ii): a process description (section 5).
- 2026 P-II A Q2(a)(vii) and 2021 (held 2022) P-II A Q4(d): black box and white box testing (section 5).
- 2023 (held 2024) P-II A Q4(f) and 2026 P-II B Q10(c): deployment methods (section 6).
Sources
- G.C.E. (A/L) Information and Communication Technology question papers, 2019 to 2026, Department of Examinations, Sri Lanka.
- G.C.E. (A/L) 2025 Information and Communication Technology marking scheme, Paper II, Department of Examinations, Sri Lanka, pages 36 and 37 (Sinhala medium, with the English questions).
- The 2024 and 2026 answers in this post are our own worked answers, not official.
