ZIMBABWE

MINISTRY OF PRIMARY AND SECONDARY EDUCATION

SOFTWARE ENGINEERING
SYLLABUS
FORMS 5 - 6

2015 - 2022

Curriculum Development and Technical Services

P. O. Box MP 133
Mount Pleasant
Harare

© All Rrights Reserved

2015
Software Engineering Syllabus Forms 5 - 6

ACKNOWLEDGEMENTS

The Ministry of Primary and Secondary Education wishes to acknowledge the following for their valued
contributions in the development of this syllabus:

• The National Software Engineering Panel comprising representatives from:

- Computer Studies Secondary Teachers
- Zimbabwe School Examinations Council (ZIMSEC)
- Teachers’ and Technical Colleges
- Universities
- Computer Society of Zimbabwe (CSZ)
• United Nations Children’s Fund (UNICEF)
• United Nations Educational, Scientific and Cultural Organisation (UNESCO)

i
Software Engineering Syllabus Forms 5 - 6

CONTENTS
ACKNOWLEDGEMENTS......................................................................................................................i

CONTENTS............................................................................................................................................ii

1.0 PREAMBLE.....................................................................................................................................1

2.0 PRESENTATION OF SYLLABUS...................................................................................................1

3.0 AIMS.................................................................................................................................................1

4.0 SYLLABUS OBJECTIVES..............................................................................................................1

5.0 METHODOLOGY AND TIME ALLOCATION...................................................................................2

6.0 TOPICS............................................................................................................................................2

7.0 SCOPE AND SEQUENCE CHART.................................................................................................3

8.0 COMPETENCY MATRIX..................................................................................................................5

FORM 5..................................................................................................................................................5

FORM 6..................................................................................................................................................9

9.0 ASSESSMENT.................................................................................................................................12

10.0 GLOSSARY/APPENDICES...........................................................................................................15

ii
Software Engineering Syllabus Forms 5 - 6

1.0 PREAMBLE 1.5 Cross-Cutting Themes

1.1 Introduction The teaching and learning of Software Engineering

should integrate the following cross cutting themes:
Software engineering is the branch of computing that
creates practical and cost effective solutions to real life Cross Cutting Themes Examples
problems by applying scientific knowledge. This syllabus Life skills Computer based
is designed to cover the two years of advanced second- systems
ary education. It equips learners with software devel- Enterprise skills and financial Project
opment skills and prepares them for self-sustenance, literacy management
professional development and lifelong learning. Collaboration Project teams
Gender equality Encouraging
1.2 Rationale equal
opportunities in
Software plays a central and underpinning role in as- the use of ICTs
pects of daily life such as communications, governance, Environmental issues Feasibility study
manufacturing, banking and finance, education, transpor- during system
tation, entertainment, medicine, agriculture and law. development
Disaster Risk Management System security
This course equips the learner with fundamentals of
software engineering including understanding system re-
quirements, effective methods of design, coding, testing,
2.0 PRESENTATION OF
teamwork and the application of software engineering
tools. The course provides an opportunity for the learner SYLLABUS
to identify socio-economic problems in a real world set-
ting and develop practical and sustainable solutions. The Software Engineering syllabus is presented as one
document for Forms 5 and 6.
1.3 Summary of Content
3.0 AIMS
The Software Engineering Syllabus covers software
development processes, securing computer systems,
The syllabus aims to enable learners to:
adherence to professional and ethical standards and
business initiative.
3.1 appreciate the benefit of software design in
solving everyday problems
1.4 Assumptions 3.2 develop software systems
3.3 appreciate the ever evolving nature of com-
It is assumed that learners: puter systems
3.4 be confident and creative in the development
• have passed Computer Science and Mathematics of software projects
at Form 4 level or equivalent 3.5 adhere to ethical practices when developing
• have acquired skills in system development software
• are conversant with at least one programming
language
4.0 SYLLABUS OBJECTIVES

Learners should be able to:

• identify software development needs and chal-

lenges that require various solutions
• formulate solutions to meet desired needs based
on user requirements
• justify the need for ethical, legal, security and

1
Software Engineering Syllabus Forms 5 - 6

social responsibilities in software development 6.0 TOPICS

• analyze the impact of computer based solutions on
individuals, organizations, and society
• develop software projects using modern software The syllabus consists of the following topics:
engineering techniques and tools
• apply entrepreneurial skills to commercialize soft- 6.1 Software Process Models
ware products 6.2 Software Project Management
• apply the concepts of system development pro- 6.3 Software Design
cesses in problem solving 6.4 Data Structures and Algorithms
• demonstrate the ability of teamwork during soft- 6.5 Programming
ware development 6.6 Security and Ethics
• use knowledge from other disciplines in the devel- 6.7 Quality Assurance and Testing
opment of computer applications 6.8 Enterprise in Software Engineering
• demonstrate an awareness of the evolving nature
of computer systems

5.0 METHODOLOGY AND TIME

ALLOCATION

5.1 Methodology

The teaching and learning of Software Engineering is

based on a learner-centred approach. The following
methods are recommended:

• Problem solving
• e-Learning
• Multi-media
• Simulation and modeling
• Discovery
• Experimentation
• Project-based learning
• Question and answer
• Demonstrations
• Team teaching
• Discussion
• Educational Tours
• Research and Presentations
• Expert guest presentations Software Engineering Syllabus Forms 5 - 6

5.2 Time Allocation

This learning area should be allocated at least 12 periods

of 35 - 40 minutes per week, that is, 4 theory periods and
8 practical periods. Learners should be engaged in each
of the following at least once a year: Educational Tour,
Exhibition, Seminar and a week of practical orientation.

2
Software Engineering Syllabus Forms 5 - 6

7.0 SCOPE AND SEQUENCE CHART

7.0 SCOPE AND SEQUENCE CHART

TOPIC FORM 5 FORM 6

7.1 Software Process Models  Software Engineering Application Areas
 Process Models
7.2 Software Project Management  Characteristics of software projects
 Project management skills
 Software Crisis/Failure
 Project Planning
 Project Scheduling
7.3 Software Design  Software Design strategies  Architectural design
 Interface design  Detailed design

7.4 Data Structures and Algorithms  Pseudo-code structures

 Sorting and searching algorithms
 Dynamic and static data structures

7.5 Programming  Web based programming  Object Oriented Programming

 Database systems  Advanced Programming

7.6 Security and Ethics  Common threats and software vulnerabilities

 System Security
 Risk management techniques
 Ethics
 Security policy
 Cyber crime

7.7 Quality Assurance and Testing  Testing Approaches  Software Quality Attributes
 Testing Levels  Software Quality Assurance
 Safety and security
 ISO standards

Forms 5 – 6 Software Engineering Syllabus 3

Page
6
Software Engineering Syllabus Forms 5 - 6

7.8 Enterprise in Software Engineering  Careers in Software Engineering

 Business Viability
 Marketing Strategies
 Intellectual Property Rights

‘
]

Forms 5 – 6 Software Engineering Syllabus

4 Page
7

Software Engineering Syllabus Forms 5 - 6

 4

Software Engineering Syllabus Forms 5 - 6

8.0 COMPETENCY MATRIX

FORM 5
8.0 COMPETENCY MATRIX

FORM 5
TOPIC OBJECTIVES CONTENT SUGGESTED SUGGESTED
Learners should be able to: (KNOWLEDGE, SKILLS, LEARNING ACTIVITIES AND NOTES LEARNING
ATTITUDES) RESOURCES
8.1 Software  identify opportunities for  application areas for system  Selecting possible application areas  Software
Process software development development such as education, as groups Development
Models government, banking and mining Forums
 National ICT Policy
 outline the stages of  Process Models:  Discussing the stages and activities  CASE tools
each process model - SDLC generic model of each process model  Word processing
- RAD software
- Prototyping  Innovation hub
- Object Oriented Centres
 explain the importance  Project Documentation  Producing the documentation for  Software
of documentation in their group project development
software development companies
 develop a project using  Applying software process models to
process models a project

8.2 Software  explain characteristics  Characteristics of software projects  Describing characteristics of  Software Crisis
Project software projects software projects articles
Management  identify project  Project management skills  Discussing project management  Y2K problem Case
management skills skills Study
 Applying project management skills  Internet
in software development
 explain common causes  Software Crisis/Failure  Discussing the issues relating to
of software project software crisis
failures  Investigating the causes of software
project failure in a given scenario

Forms 5 – 6 Software Engineering Syllabus

Page
8
Software Engineering Syllabus Forms 5 - 6

TOPIC OBJECTIVES CONTENT SUGGESTED SUGGESTED

Learners should be able to: (KNOWLEDGE, SKILLS, LEARNING ACTIVITIES AND NOTES LEARNING
ATTITUDES) RESOURCES
 develop a realistic  Project Planning  Constructing a project plan  Project Plan
project plan - Software Development Plan Guideline
 evaluate a project plan - Quality Assurance Plan  Analysing project proposals  PMBOK Guide
- Validation Plan  Software Extension
 identify the relevant - Configuration Management Plan  Determining the skill sets of project for Project
skills for a project team - Maintenance Plan team members Management Guide
- Staff Development Plan
 determine the time  Project Scheduling  Calculating the amount of time  Project
resource needed for required for project completion management
project completion software
 develop project  Tools for Schedule Development  Designing a project schedule using  Statistical tools
schedules using - Critical Path Method (CPM) tools :CPM and GANTT charts
appropriate tool(s) - GANTT Chart  Designing GANTT charts

8.3 Software  outline software design  Software Design strategies  Discussing software design  Internet
Design strategies - Structured design strategies  CASE tools
- Function oriented design  Web design tools
- Object oriented design e.g HTML, Joomla,
 apply appropriate user  Interface design  Designing user interface for their Wordpress
interface design - User interface group projects  Design tools such
principles used in - Web based design as MicroSoft Visio,
Software Development Adobe Photoshop,
CorelDraw
8.4 Data  use pseudocode  Pseudo-code structures  Formulating trace tables for a  Multi- Media
Structures structures in algorithm given algorithm Tutorials
and design
Algorithms  apply sorting and  Sorting algorithms  Using sorting and searching  Open source
searching algorithms in - Bubble algorithms to solve problems packages
problem solving - Quick
 Searching algorithms  Discussing the concept of data
- Linear structures
- Binary
 outline static and  Dynamic and static data structures  Using operations on data
dynamic data structures - Trees structures
- Arrays

Forms 5 – 6 Software Engineering Syllabus

6 Page
9

Software Engineering Syllabus Forms 5 - 6

 6

Software Engineering Syllabus Forms 5 - 6

TOPIC OBJECTIVES CONTENT SUGGESTED SUGGESTED

Learners should be able to: (KNOWLEDGE, SKILLS, LEARNING ACTIVITIES AND NOTES LEARNING
ATTITUDES) RESOURCES
 perform operations on
binary trees and arrays

8.5 Programming  develop a web based  Web Application Development  Creating a web application  Client side
application - client side development following appropriate design programming
- server side development principles languages such
as Java Script
 distinguish database  Database Systems  Server side
systems - File based database systems  Creating a database programming
- Relational database systems  Comparing and contrasting tools such as
- Database Management Systems database systems PHP, VB.Net
- Normalization (2nd normal form)  Database
 develop a database for a  Integrating database systems to a packages such
web based application web application as Microsoft
Access, SQL and
 normalize database MySQL
tables up to 2nd normal  Normalizing database tables up to
form 2nd normal form

8.6 Security and  analyze common threats  Common threats and software  Evaluating major counter  Antivirus
ethics and vulnerabilities of vulnerabilities such as: measures to software and system software
software systems - Malware attacks  Firewalls
- Botnets  Anti-spyware
- Phishing  Video Clips
 examine user level  System Security  Applying security techniques in  Library functions
security measures - User level security measures designed solutions  Programming
o Antispyware/ antivirus  Conducting case studies on packages such
o Firewalls different attack scenarios as Visual Basic,
- Programming and Security Java and C++
 identify sources of  listing tools used to eliminate
vulnerability arising at vulnerabilities at programming
the programming level level
 explain tools used to  applying security features found in
eliminate vulnerabilities programming languages
at programming level

Forms 5 – 6 Software Engineering Syllabus

7 Page
10
Software Engineering Syllabus Forms 5 - 6

TOPIC OBJECTIVES CONTENT SUGGESTED SUGGESTED

Learners should be able to: (KNOWLEDGE, SKILLS, LEARNING ACTIVITIES AND NOTES LEARNING
ATTITUDES) RESOURCES
 explore techniques and  Risk management techniques  Conducting case studies on Risk  Tools such as Logic
practices of risk analysis and management Manager
management  Formulating a disaster recovery
plan in case of system failure:
 system back-ups
 System restore
 identify code of ethics and  Ethics  Applying code of ethics and  Data Protection
professional practices in professional practices in SE Act
Software Engineering (SE)  Second Science
 demonstrate ethical  People and security  Discussing ethical issues in SE Technology and
practices in SE Innovation Policy
 identify relevant legislative  Data protection legislation  Describing relevant legislative and of Zimbabwe
and regulatory frameworks regulatory frameworks in SE (2012)
in systems security  Print and
 analyse various types of  Security Policies  Analyzing the effects of cybercrime Electronic Media
Cybercrime  Cybercrime from case studies  Case Studies on
Data Protection
and Legislation
issues
 National ICT
Policy
8.7 Quality  use different testing  Testing Approaches  Applying testing approaches to all  Automated
Assurance approaches in software - Black box testing the levels of the group project testing tools such
and Testing development - White box testing as HTML unit,
 outline various testing  Testing Levels  Validating software through the Selenium
levels in system - Unit testing various testing levels  CASE Tools
development - Module testing  Demonstrating the use of  Multimedia
- System testing automated testing tools tutorials
- Acceptance testing  Expert Guest

FORM 6

Forms 5 – 6 Software Engineering Syllabus

Page
11

Software Engineering Syllabus Forms 5 - 6

 8

Software Engineering Syllabus Forms 5 - 6

FORM 6

TOPIC OBJECTIVES CONTENT SUGGESTED SUGGESTED

Learners should be able (KNOWLEDGE,SKILLS, LEARNING ACTIVITIES AND NOTES LEARNING
to: ATTITUDES) RESOURCES
8.8 Software  explain the architectural  Architectural design  Discussing the design process for  Multimedia
Design design process and - Organisation given systems such as embedded, tutorials
architectural models - Control modelling database, banking, mining,  CASE tools
- Modular decomposition education and web based  Design Tools
 Such as Microsoft
 outline the importance of  Architectural models  Discussing the importance of Visio, Corel Draw,
architectural styles in - Static architectural styles in software Adobe Photoshop
Software Design - Dynamic design  Expert Guest
- Interface
 Architectural styles  Researching on architectural styles
- Client server
- Service oriented
- Layered
 demonstrate how  Detailed Design  Applying detailed design in software
detailed design is used - Analysis models development
to further decompose - Design models  Conducting educational tours to IT
analysis and design companies and manufacturing
models industries

Forms 5 – 6 Software Engineering Syllabus

Page
12
Software Engineering Syllabus Forms 5 - 6
FORM 6 Continued…
TOPIC OBJECTIVES CONTENT SUGGESTED SUGGESTED
Learners should be able to: (KNOWLEDGE, SKILLS, ATTITUDES) LEARNING ACTIVITIES LEARNING
AND NOTES RESOURCES
8.9 Programming  outline features of Object  Object Oriented Programming  Implementing classes  Object Oriented
Oriented Programming - Classes  Demonstrating the use Programming tools
(OOP) - Encapsulation of Singleton and Model such as Java,
- Polymorphism View Controller( Python, VB.NET,
- Inheritance MVC)design patterns PHP
 design games and mobile  Advanced Programming  Designing mobile device  Animation software
applications - Mobile applications applications such as Scratch,
- Gamming and Animations  Designing games with Adobe Creative
indigenous orientation Suite

8.10 Quality  explain software quality  Software Quality Attributes  Discussing the  Field trips
Assurance and Testing attributes and their importance importance of quality  ISO Standards
in quality assurance process assurance attributes in Documents
software quality
management
 Discussing the
importance of software
tools and techniques
 demonstrate the use of quality  Software Quality Assurance  Applying quality
assurance tools and - Quality policy assurance tools and
techniques in quality - Tools and techniques techniques in their
management o Inspection software projects
o Audit trials
 outline the importance of  Safety and Security Management  Discussing the
safety and security importance of ISO
management in quality standards in software
assurance development

 recognize appropriate ISO  ISO Standards (ISO 9000)  Applying ISO

Standards Standards relevant to
their project areas
 Conducting case
studies related to quality
assurance and testing in
software management

Forms 5 – 6 Software Engineering Syllabus

Page
13

10

Software Engineering Syllabus Forms 5 - 6

 10

Software Engineering Syllabus Forms 5 - 6

8.11 Enterprise  identify careers in SE  Careers in SE  Identifying careers in SE  Expert guests

in Software  Conducting educational presentation
Engineering  describe the duties done by  Business viability: tours to software  Print and
SE professionals - Benefits realization development companies Electronic Media
- Cost analysis  Participating in IT  Internet
- Trade off analysis expos/fairs/events  Business
 evaluate cost effective  Discussing on cost journals
solutions in SE effective solutions in SE  Statistical tools
 outline ways of marketing  Return on investment  Researching on viability  Print and
software of software Electronic Media
development project  Expert Guest
 evaluate marketing  Marketing strategies  Designing marketing
strategies strategies
 recognize intellectual  Intellectual Property Rights  Discussing intellectual
property rights property issues

Forms 5 – 6 Software Engineering Syllabus

11 Page
14
Software Engineering Syllabus Forms 5 - 6

9.0 ASSESSMENT

In order to have a holistic assessment of the learner from form 5 to 6, learners will be assessed in the aspects of con-
tinuous and summative assessment with each contributing to the learner’s final grade.

9.1 Assessment Objectives

Learners will be assessed in the following areas:

(i) Knowledge and Understanding

Learners should be able to:
• describe the use of software engineering in a range of information processing systems
• explain the systematic development of solutions to problems and the appropriate techniques for implementing such
solutions
• describe and explain the need for the use of SDLC in software development

(ii) Problem Solving

Learners should be able to:
• analyze the situation and identify the parts which are appropriate for a computer based solution
• design, implement and document an effective solution using appropriate software and programming languages
• implement the system development life cycle to produce effective and documented and tested systems

(iii) Communication Skills

Learners should be able to:
• develop an understanding of the component parts of computer systems and how they inter-relate including soft-
ware, data, hardware, communications and people
• interpret and organize information
• recognize and present information in a variety of forms
• use ICT tools to disseminate information about applications of computers, problems and their solutions

(iv) Practical Skills

Learners should be able to:
• design and develop a solution to a problem using any programming language
• demonstrate proficiency in the creation, design and implementation of computer solutions using prescribed pro-
gramming packages.
• conduct research using the internet

12
Software Engineering Syllabus Forms 5 - 6

9. 2 Scheme of Assessment
Software Engineering learning areas will be examined through continuous and summative assessment as follows.

Assessment of learner performance in Advanced level SE

100%

Continuous assessment 30 % Summative Assessment 70%

Paper 3 Paper 4 Paper 1 Paper 2

Coursework Projects 30% 40%
10% 20%

Profiling
Continuous assessment mark Summative Assessment mark
=30% = 70%

Profile

FINAL MARKS 100 %

Exit
Profile

13
 Profile

Software Engineering Syllabus Forms 5 - 6

EXIT PROFILE

The Scheme of Assessment is intended to encourage positive achievement by all learners.

The Scheme of Assessment
The subject is intended
will be examined in 4 to encourage
papers positive
as shown achievement
in the table below.by all learners.
The subject will be examined in 4 papers as shown in the table below.

Paper Form of Assessment Type of Paper Duration Total Weighting

marks
1 Summative Assessment Free Response 3 Hours 100 30
2 Practical 3 Hours 100 40
3 Continuous assessment Coursework 5 terms 100 10
4 Project 4 terms 100 20
TOTAL 400 100%

9.3 Specification Grid

Forms (i)
5–69.3
Software Engineering
Specification
Content Grid Syllabus
distribution
9.3 Specification Grid
(i) Content distribution
PAPER 1
PAPER (i)
1 Content distribution
TOPIC WEIGHTING (30%)
PAPER 1
Software Process Models 20
TOPIC WEIGHTING (30%)
Software Project Management 15
Software Process Models 20
Software Design 15
Software Project Management 15
Data Structures and Algorithms 10
Software Design 15
System security and Ethics 15
Data Structures and Algorithms 10
Quality Assurance and Testing 15
System security and Ethics 15
Enterprising in Software Engineering 10
Quality Assurance and Testing 15
TOTAL 100
Enterprising in Software Engineering 10
TOTAL2
PAPER 100
SECTION WEIGHTING (40%)
PAPER 2
Software Design 15
SECTION WEIGHTING (40%)
Data Structures and Algorithms 10
Software Design 15
Programming 60
Data Structures and Algorithms 10
System Security and Ethics 5
Programming 60
Quality Assurance and Testing 10
System Security and Ethics 5
TOTAL 100
Quality Assurance and Testing 10
TOTAL 100
(ii) Skills distribution
(ii) Skills distribution

All (ii)and
All internal
internal Skills
and distribution
external
external tests
tests on
on cognitive
cognitive skills
skills (theory)
(theory) shall
shall be
be 40%
40% knowledge
knowledge and
and understanding
understanding 50%
50% problem
problem solving and 10% Pr
solving and and
All internal 10%external
Practicalpractical
Skills. tests shall be 100% practical skills. Thus the weighting of questions based on the skills for the subje
All internal
be internal and external tests on cognitive skills (theory) shall be 40% knowledge and understanding 50% problem solving and 10% Pr
as follows:
All and external practical tests shall be 100% practical skills. Thus the weighting of questions based on the
All internal and external practical tests shall be 100% practical skills. Thus the weighting of questions based on the skills for the subje
skills
be asfor the subject, Software Engineering, will be as follows:
follows:
SKILL Paper 1(%) PAPER 2(%)
Knowledge and 40 10
SKILL
Understanding Paper 1(%) PAPER 2(%)
Knowledge and 40 10
Understanding
Problem Solving 50 30
Practical Skills 10 60
Problem Solving 50 30
TOTAL 100 100
Practical Skills 10 60
TOTAL 100 100

Forms 5 – 6 Software Engineering Syllabus

Forms 5 – 6 Software Engineering Syllabus

14
Software Engineering Syllabus Forms 5 - 6

9.4 paper Descriptions

Paper 1: Theory (100 Marks)

The paper consists of 10 to 12 compulsory questions.

Paper 2: Practical (100 Marks)

The paper consists of 7 practical questions each worth 20 marks and the candidate is to choose 5.

Paper 3: Coursework (100 marks)

Coursework is made up of 7 items which comprises of five practical assignments and two theory tests. Practical
assignments and tests are set, marked and recorded internally by teachers. Each of these assignments and tests
should match the skills distribution table given above. The internal practical assignments are spaced equitably from
the beginning of term one in Form 5 up to the end of term two in Form 6. The internal theory coursework tests should
be written one in Form 5 and one in Form 6 however the tests should be within the range term two in Form 5 and end
of term two in Form 6. All marked practical and theory scripts including the compiled mark schedule will be submitted
to ZIMSEC.

Paper 4: Project (100 marks)

Examination Centres are advised to encourage their candidates to identify real life problems within their environment
and develop solutions in line with the project guide lines. The project will require candidates to have practical program-
ming experience including writing their own programs, executing (running), testing and debugging them. Knowledge of
programming language syntax will be examined in the project report. The higher ability candidates are to be encour-
aged to extend their practical programming beyond the scope of these tasks. The project work should be carried out
from term two in Form 5 to end of term two in Form 6.The marked project reports including the compiled mark sched-
ule will be submitted to ZIMSEC.

10.0 GLOSSARY/APPENDICES
APPENDIX I: GLOSSARY OF TERMS USED IN QUESTION PAPERS

It is hoped that the glossary will be helpful to learners as a guide. The glossary has been deliberately kept brief not
only with respect to the number of terms included but also to the descriptions of their meanings. Learners should ap-
preciate that the meaning of a term must depend in part on its context.

1 Define is intended literally for only a formal statement or equivalent paraphrases being
required.

2 State implies a concise answer with little or no supporting argument e.g. numerical
answer that can readily be obtained by inspection.

3 List requires a number of points generally each of one word with no elaboration, where
a number of points is specified this should not be exceeded.

4 Explain implies reasoning or some reference to theory depending on the context.

5 Describe expected to state in words (using diagrams where appropriate) the main points of
the concept.

6 Outline implies brevity that is restricting the answer to given essentials.

7 Predict/deduce required to produce the expected answer by making a logical connection

betwee other pieces of information.

15
 Software Engineering Syllabus Forms 5 - 6

8 Suggest it is used in two main contexts that is either to imply that there is no unique answer or to
imply that learners are expected to apply their general knowledge.

9 Find is a general term that may alternatively be interpreted as calculate, measure,

determine etc.

10 Determine often implies that the quantity concerned cannot be measured directly but is obtained by
calculation.

APPENDIX II: ACRONYMS

APPENDIX II: ACRONYMS

SDLC System Development Life Cycle

SE Software Engineering
VB Visual Basic
PHP Hypertext PreProcessor
HTML Hypertext Markup Language
MySQL Structured Query Language
OOP Object Oriented Programming
ICT Information and Communication Technology
Internet International Network
ISO International Standard Organisation
Y2K Millennium bug Year 2000
CASE Computer Aided Software Engineering
CPM Critical Path Method
PMBOK Project Management Body of knowledge
RAD Rapid Application Development
DFD Data Flow Diagram
MVC Model View Controller

APPENDIX III: PROJECT GUIDE

APPENDIX III: PROJECT GUIDE
The project must not exceed 60 pages excluding appendices. The project must include the following layout:
The project must not exceed 60 pages excluding appendices. The project must include the following layout:
1. Cover Page
1. Cover Page 2. Table of Contents
2. Table of Contents
3. Project Content (Sections)
3. 4. Appendices
Project Content (Sections)
4. Appendices The Appendices include any two of the following
 Sample of completed questionnaires
The Appendices include any two of the following
 Sample of interview questions with respondent answers
• Sample of completed questionnaires
 Sample documents
• Sample
NB the project must beofspiral
interview questions with respondent answers
bound.
• Sample documents
SECTION ANB (25the
marks)
project must be spiral bound.

Selection, Investigation and Analysis

SECTION A (25 marks)
 Define a problem
Selection,
- Investigation
Choice of problem and
areaAnalysis
and background analysis. [3]

Forms 5 – •6 Software
Define a problem
Engineering Syllabus
-
Choice of problem area and background analysis.[3]
• Investigation of the current system
- Data analysis using DFDs, flow charts and ERDs
- Research instruments e.g. questionnaire, record inspection, interviews and observation.
- Identify problems with the current system.[5]
• Feasibility study[5]

16
Software Engineering Syllabus Forms 5 - 6

• Requirements specification
-
User
-
Software
-
Hardware.[4]
• Aims and objectives. [5]
• Evidence that the research has been carried out.[3]
- Examples are filled in questionnaires, interviews with respondent answers, sample documents and write up on
observation.

SECTION B (25 marks)

Design
• Consideration of alternative method.[3]
-
Justification of proposed solution
[2]
• Input design
- Appropriate data capture forms and screen layouts[4]
• Data Structures/File design[5]
OR
• Object Oriented Design
- Class diagrams
- Use Case diagrams
- Sequence diagrams
• Overall Plan [3]
• Output Design
- Specification and design of the required output
- Interface design (on screen commands)[5]
• Test Strategy/Test Plan
- Select test plan and justify[3]

SECTION C (25 marks)

Software Development

• Techniques that improve the structure, appearance and clarity of the code that is:
- Procedures
- Functions
- Scope of variables (local and global)
- Use of comments
- Blank lines
- Indentation[10]
• Technical documentation
- Algorithms
 pseudo codes
 flowcharts for modules
- codes/program listing [7]

• User documentation
- Installation
- Starting the systems
- Navigation of the system
- Exiting the system [8]

17
Software Engineering Syllabus Forms 5 - 6

SECTION D (15 marks)

Testing and Evaluation

• User Testing
- Design and select test data
- Test for standard, extreme and abnormal/invalid data
- Evidence of testing to be shown through sample runs and error messages [5]

• System Testing
- Ease of use
 clarity of instruction to the user
- Reliability
 produce reliable results, there should be no bugs
- Effectiveness
 The system should work efficiently
- Produce results with minimum del[5]
• Evaluation Limitations of the system
- Extent of success in meeting the system objectives as stated in the system requirement specification
- Achievements
- Limitations
- Evaluate results against the system objectives – achievements and limitations
- Opportunities for future development [5]

SECTION E (10 marks)

General Expectations

• Depth of Knowledge and Understanding

- Reflects the degree of computing in the project
- Is the code fairly standard?
- Different techniques implemented[2]

• Degree of Originality
- Imagination and innovation
- Has an attempt been made to do something different/unique? [2]

• Overall conduct of the project

- Is the work carefully organized? The degree of help to be reflected[1]
• Quality of the completed report
- Written report should be easy to follow
- Defined sections, page numbers and an index. [5]

APPENDIX IV: RESOURCES AND EQUIPMENT

Infrastructure and Equipment

For a school to run the Software Engineering Syllabus for examination purposes, the under listed infrastructure and
equipment need to be in place

Computer Laboratory

Personal Computers to accommodate 1 learner per computer

NB it is encouraged that the learner be in possession of Laptop or tablet.
18
Software Engineering Syllabus Forms 5 - 6

A printer
Air conditioned laboratory
Open source and /or Licensed software
Computer Desks and Chairs to accommodate the number of students
Dustless Displays for the Teacher (securely-mounted Whiteboard, LCD projector)
Computer Repair Toolkit
Internet connectivity
Alternative power source such as generator, solar, ups

Theory Classroom

Classroom furniture to accommodate the learners

Writing Surface for the Teacher (e.g. securely-mounted Whiteboard, LCD projector)

In both the above cases, there should be adequate lighting and ventilation.

19