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 ReservedSoftware 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)
Software Engineering Syllabus Forms 5 - 6 ii
CONTENTS
ACKNOWLEDGEMENTS ...i CONTENTS ...ii 1.0 PREAMBLE ...1 2.0 PRESENTATION OF SYLLABUS ...1 3.0 AIMS ...1 4.0 SYLLABUS OBJECTIVES ...15.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
Software Engineering Syllabus Forms 5 - 6
1.0 PREAMBLE
1.1 Introduction
Software engineering is the branch of computing that creates practical and cost effective solutions to real life problems by applying scientific knowledge. This syllabus is designed to cover the two years of advanced second-ary education. It equips learners with software devel-opment skills and prepares them for self-sustenance, professional development and lifelong learning.
1.2 Rationale
Software plays a central and underpinning role in as-pects of daily life such as communications, governance, manufacturing, banking and finance, education, transpor-tation, entertainment, medicine, agriculture and law. This course equips the learner with fundamentals of software engineering including understanding system re-quirements, effective methods of design, coding, testing, teamwork and the application of software engineering tools. The course provides an opportunity for the learner to identify socio-economic problems in a real world set-ting and develop practical and sustainable solutions.
1.3 Summary of Content
The Software Engineering Syllabus covers software development processes, securing computer systems, adherence to professional and ethical standards and business initiative.
1.4 Assumptions
It is assumed that learners:
• have passed Computer Science and Mathematics at Form 4 level or equivalent
• have acquired skills in system development • are conversant with at least one programming
language
1.5 Cross-Cutting Themes
The teaching and learning of Software Engineering should integrate the following cross cutting themes:
2.0 PRESENTATION OF
SYLLABUS
The Software Engineering syllabus is presented as one document for Forms 5 and 6.
3.0 AIMS
The syllabus aims to enable learners to:
3.1 appreciate the benefit of software design in solving everyday problems
3.2 develop software systems
3.3 appreciate the ever evolving nature of com-puter systems
3.4 be confident and creative in the development of software projects
3.5 adhere to ethical practices when developing software
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
Cross Cutting Themes Examples
Life skills Computer based
systems Enterprise skills and financial
literacy
Project management
Collaboration Project teams
Gender equality Encouraging equal
opportunities in the use of ICTs
Environmental issues Feasibility study
during system development
Software Engineering Syllabus Forms 5 - 6
Software Engineering Syllabus Forms 5 - 6
2 social responsibilities in software development • analyze the impact of computer based solutions on
individuals, organizations, and society
• develop software projects using modern software engineering techniques and tools
• apply entrepreneurial skills to commercialize soft-ware products
• apply the concepts of system development pro-cesses in problem solving
• demonstrate the ability of teamwork during soft-ware development
• use knowledge from other disciplines in the devel-opment of computer applications
• 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
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.
6.0 TOPICS
The syllabus consists of the following topics: 6.1 Software Process Models
6.2 Software Project Management 6.3 Software Design
6.4 Data Structures and Algorithms 6.5 Programming
6.6 Security and Ethics
6.7 Quality Assurance and Testing 6.8 Enterprise in Software Engineering
3
7.0
SCOPE
AND SEQUENCE CHART
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
6
7.0
SCO PE A ND S EQ UE NCE CH ART TO PI C FO RM 5 FO RM 6 7.1 Sof tware Pr oc es s Mo del s S of tware Eng in ee ring A pp lic ati on A re as P roc es s Mo del s 7. 2 So ftware Pr oj ec t M ana gem en t Charac teri st ic s of s of tw are proj ec ts P roj ec t m an ag em en t s ki lls S of tware Cr is is /Fai lure P roj ec t P lan ni ng P roj ec t S che du ling 7.3 Sof tware D es ign S of tware D es ign s trate gi es Int erf ac e d es ign A rc hi tec tural de si gn Deta ile d d es ig n 7.4 Data S truc tures a nd A lgo rit hm s Ps eud o-cod e s truc tures S orti ng an d se arc hi ng a lgo rithm s D yn am ic an d s tat ic da ta s truc tures 7.5 Pr og ram m ing W eb b as ed pro gram m ing Data bas e s ys tem s O bj ec t O rien te d P rog ram m ing A dv an ce d P rog ram m ing 7.6 Sec urit y an d E th ic s Com m on th rea ts an d sof twar e v ul nerab ilit ies S ys tem S ec urit y Ri sk m an ag em en t te chn iqu es E th ic s S ec urit y po lic y C yb er c rim e 7. 7 Q ual ity A ss ur anc e a nd T es ting T es ting A pproac hes T es ting Le ve ls Sof tware Q ual ity A ttr ibu tes Sof tware Q ual ity A ss uranc e S af et y an d s ec urit y IS O s tan d ardsSoftware Engineering Syllabus Forms 5 - 6 Software Engineering Syllabus Forms 5 - 6 4
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
7
‘ ] 7.8 Ente rpris e i n S of tware Eng ine eri ng Car ee rs in S of tw are E ng ine erin g B us in es s Vi ab ilit y Ma rk eti ng S trate gi es Int el lec tua l P ro pe rty Ri gh ts4 5
8.0
COMPETENCY
MA
TRIX
FORM 5
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
8
8.0
CO M PE TE NCY M AT RIX FORM 5 TO PI C O BJE CT IV ES Lea rn er s sho uld be abl e t o: CO NT ENT (KNO W LE DG E, SK IL LS, AT TIT UDES ) SU G G EST ED LE ARNING A CT IV IT IE S A ND NO TE S SU G G EST ED LE ARNING RE SO U RCE S 8.1 S of tw ar e Pr oc ess M od els ide nti fy op portun iti es for sof tw are d ev el op m en t outl in e t he s tag es of eac h proc es s m od el ex pl ai n t he im po rtan ce of do cum en tat ion i n sof tw are d ev el op m en t de vel op a proj ec t u si ng proc es s m od el s ap pl ic at ion areas for s ys te m de vel op m en t s uc h a s ed uc ati on, go vernm en t, b an ki ng an d m ini ng P roc es s Mo del s: S DLC ge ne ric m od el R AD Pr ot ot ypi ng -O bj ec t O rien te d P roj ec t Doc um enta tio n S el ec ting p os si bl e a pp lic at ion areas as group s Di sc us si ng the s ta ge s a nd a ct iv itie s of ea ch p roc es s m od el P rod uc ing the do cum en tat ion for the ir group proj ec t A pp ly in g s of tware proc ess m od el s to a p roj ec t S of tware Dev el opm en t Forum s Nati on a l I C T Po lic y C AS E t ool s W or d proc es si ng sof tw are Inn ov at io n h ub Cent res S of tware de vel op m en t co m pa ni es 8.2 S of tw ar e Pr oje ct M anag ement ex pl ai n ch arac teri st ic s sof tw are pr oj ec ts ide nti fy proj ec t m an ag em en t s ki lls ex pl ai n c om m on c au ses of s of tw are proj ec t fa ilures C ha rac teri st ic s of s of tw are proj ec ts P roj ec t m an ag em en t s ki lls S of tware Cr is is /Fai lure Des cr ibi ng c ha rac teris tic s o f sof tw are pr oj ec ts Di sc us si ng pr oj ec t m an ag em en t sk ills A pp ly in g p roj ec t m an ag em en t s ki lls in s of tw are d ev el op m en t D iscu ssi ng t he is sue s r el ati ng to sof tw are c ris is Inv es tig ati ng the c au ses of s of tw are proj ec t f ai lure in a g iv en s cen ari o S of tware Cr is is arti cl es Y 2K prob lem Cas e Stud y Int erne tSoftware Engineering Syllabus Forms 5 - 6 Software Engineering Syllabus Forms 5 - 6 6
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
9
TO PI C O BJE CT IV ES Lea rn er s sho uld be abl e t o: CO NT ENT (KNO W LE DG E, SK IL LS, AT TIT UDES ) SU G G EST ED LE ARNING A CT IV IT IE S A ND NO TE S SU G G EST ED LE ARNING RE SO U RCE S de vel op a rea lis tic proj ec t p lan ev al uate a p roj ec t p la n ide nti fy the re le va nt sk ills for a proj ec t te am P roj ec t P lan ni ng S of tware D ev el opm en t P la n -Q ua lit y As suranc e Pl an V al id ati on P lan Conf igu ra tio n M an age m en t P lan Ma inte nan ce P lan S taf f Dev el op m en t P la n Cons truc ting a proj ec t p lan Ana ly si ng proj ec t pro po sal s Dete rm ini ng the s ki ll s ets of proj ec t tea m m em be rs P roj ec t P lan G ui de line PM BO K G ui de S of tware E xten si on for Proj ec t Ma na ge m en t G ui de de term ine th e t im e res ou rc e n ee de d f or proj ec t c om pl eti on de vel op p roj ec t sc he du les us in g ap pro pria te t ool (s ) P roj ec t S che du ling Too ls for Sc he du le D ev el opm en t - Cr iti ca l P ath Me tho d (C PM) -G ANT T Cha rt Cal cu lat ing the am ou nt of ti m e req ui re d f or pr oj ec t c om pl eti on Des ign in g a proj ec t s che du le u si ng too ls :CP M an d GANT T c harts Des ign in g G AN TT c ha rts P roj ec t m an ag em en t sof tw are S tat is tic al to ol s 8.3 S of tw ar e Desi gn ou tli ne s of tware d es ign str ate gi es app ly ap pr op riate us er inte rfac e d es ign prin ci pl es us ed in Sof tware D ev el opm en t S of tware D es ign s trate gi es S truc tured de si gn F un cti on o rien ted d es ig n -O bj ec t o rien ted de si gn Int erf ac e d es ign Us er i nte rfac e W eb b as ed de si gn Di sc us si ng s of tw are d es ign str ate gi es Des ign in g u ser inte rfac e f or the ir group proj ec ts Inte rne t C AS E t ool s W eb d es ign too ls e.g HT ML , J oom la, W ord pre ss Des ign to ol s s uc h as Mi cr oS of t V is io , Ado be P ho tos ho p, Cor el Dr aw 8.4 Dat a St ru ct ure s and Algo rithm s us e p seu do cod e str uc tures i n al gorit hm de sig n app ly s ort in g a nd sea rc hi ng al go rit hm s i n probl em s ol vi ng ou tli ne stat ic an d dy na m ic data s truc tures Ps eud o-cod e s truc tures S orti ng a lg or ith m s B ub bl e -Q uic k S ea rc hi ng al go rit hm s L in ea r B in ar y D yn am ic an d s tat ic da ta s truc tures T re es A rra ys For m ul ati ng trac e ta bl es for a gi ven al go rit hm U sin g sort ing an d s ea rc hi ng al gorit hm s to s ol ve p ro bl em s D is cus si ng the c on ce pt of da ta str uc tures U si ng op era tio ns on da ta str uc tures M ult i- M ed ia Tuto rial s O pe n s ou rc e pa ck ag es6 7
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
10
TO PI C O BJE CT IV ES Lea rn er s sho uld be abl e t o: CO NT ENT (KNO W LE DG E, SK IL LS, AT TIT UDES ) SU G G EST ED LE ARNING A CT IV IT IE S A ND NO TE S SU G G EST ED LE ARNING RE SO U RCE S pe rfor m op erati ons on bi nar y tre es an d a rra ys 8.5 P ro gr amm ing de vel op a w eb ba se d ap plic at io n di sti ng ui sh d ata bas e sys te m s de vel op a da tab as e f or a web b as ed ap pl ic ati on no rm al iz e da tab as e tab les up to 2 nd no rm al fo rm W eb A pp lic at ion De vel op m en t c lien t s id e d ev el opm en t s erv er s id e d ev el opm en t Data bas e S ys tem s F ile ba se d d atab as e s ys te m s Rel ati ona l da tab as e s ys te m s D ata bas e M an age m en t S ys tem s -Nor m al iz at ion (2n d no rm al for m ) Cr ea ting a w eb a pp lic at ion fol lo wi ng ap pr op riate de si gn prin ci pl es Cr ea ting a d atab as e Com pa ring an d c on tras tin g da ta ba se s ys tem s Int eg ra tin g d ata ba se s ys te m s to a web a pp lic at io n Nor m al iz ing d ata bas e ta ble s up to 2n d no rm al for m Cl ien t s ide progr am m ing lan gu age s s uc h as J av a Sc ript Serv er s id e progr am m ing too ls s uc h as PHP , V B. N et Data bas e pa ck ag es s uc h as Mi cr os of t Acce ss , S Q L an d M yS Q L 8.6 S ec ur ity and eth ics an al yz e c om m on th rea ts an d v ul ne rab iliti es of sof tw are s ys tem s ex am ine us er l ev el sec urit y m ea sures ide nti fy s ourc es of vu lne ra bi lit y aris in g a t the pro gram m ing le ve l ex pl ai n t oo ls us ed to el im ina te v ul ne rab ilit ies at progr am m ing lev el Com m on th rea ts an d s of twar e vu ln er ab ilit ie s suc h as : M al war e B otn ets P hi shi ng S ys tem S ec urit y Us er l ev el s ec urit y m ea sures o Ant is py wa re/ an tiv irus o Fir ew alls P rog ram m ing an d S ec urit y Ev al uati ng m aj or c ou nte r m ea sures to s of tw are a nd s ys tem atta ck s Ap ply in g sec urit y t ec hn iqu es in de si gne d s ol ut io ns Cond uc tin g c as e s tud ies o n di fferent a tta ck s cen ario s lis ting too ls us ed to e lim ina te vu lne ra bi lit ies a t p ro gram m ing le ve l ap pl yi ng s ec urit y f ea tures fou nd in progr am m ing lan gu age s An tiv iru s sof tw are Fir ew alls An ti-sp ywar e Vid eo C lip s Li brar y f un cti ons Pr ogr am m in g pa ck ag es s uc h as V is ual B as ic , Jav a an d C+ +Software Engineering Syllabus Forms 5 - 6 Software Engineering Syllabus Forms 5 - 6 8
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
11
TO PI C O BJE CT IV ES Lea rn er s sho uld be abl e t o: CO NT ENT (KNO W LE DG E, SK IL LS, AT TIT UDES ) SU G G EST ED LE ARNING A CT IV IT IE S A ND NO TE S SU G G EST ED LE ARNING RE SO U RCE S ex pl ore tec hn iq ue s an d prac tic es of ri sk m an ag em en t Ri sk m an ag em en t te chn iqu es Cond uc tin g c as e s tud ies o n Ri sk an al ys is an d m an ag em ent For m ul ati ng a d is as ter r ec ov er y pl an i n c as e o f s ys tem fai lu re: sy st em ba ck -ups Sy stem res tore T oo ls s uc h as L og ic M ana ger ide nti fy c ode of et hi cs an d prof es si on al prac tic es in Sof tware E ng in ee ring (S E) dem on str ate et hi cal prac tic es in S E ide nti fy re le va nt l eg is lat iv e an d re gu lato ry fr am ew ork s in sy st em s s ec urit y a na lys e var iou s t yp es of C yb erc rim e E th ic s P eo pl e a nd s ec urit y Data protec tion le gi sl ati on S ec urit y P ol ic ies C yb er cr im e App ly in g c od e o f et hi cs an d prof es si on al prac tic es in SE D iscu ssi ng e th ica l i ssu es i n S E Des cr ibi ng rel ev an t l egi sl ati ve an d reg ul ato ry fr am ew ork s i n S E Ana ly zi ng th e ef fec ts of c yb er cr im e fro m c as e s tud ies Data P rote ct ion Ac t Sec on d S ci en ce Tec hn ol og y a nd Inn ov at io n P ol ic y of Zim ba bw e (2 01 2) Pr int an d Ele ct ro ni c M ed ia Cas e S tud ies o n Data P rote ct ion an d Le gi sl at io n issu es Nati on al ICT Po lic y 8.7 Q uali ty As sur ance and T es ting us e d iff erent t es ting ap pro ac he s in s of tware de vel op m en t ou tli ne v ario us te sti ng le vel s in s ys tem de vel op m en t T es ting A pproac hes B lac k bo x te sti ng W hi te bo x te sti ng T es ting Le ve ls Uni t tes ting Mo du le tes ting S ys tem te sti ng Ac ce pt anc e tes ting App ly in g t es ting ap proac he s to a ll the le vel s of th e gr oup proj ec t Val id ati ng s of tw are throu gh th e vari ou s te st ing le ve ls Dem on str ati ng the us e of au tom ate d t es tin g t ool s Auto m ate d tes tin g t ool s s uc h as HT ML u ni t , Sel en ium C AS E T ool s M ult im ed ia tut ori al s Ex pe rt G ues t FORM 68 9
FORM 6
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
12
TO PI C O BJE CT IV ES Lea rn er s sho uld be able to: CO NT ENT (KNO W LE DG E, SKIL LS , AT TIT UDES ) SU G G EST ED LE ARNING A CT IV IT IE S A ND NO TE S SU G G EST ED LE ARNING RE SO U RCE S 8.8 S of tw ar e Desi gn ex pl ai n th e arc hi tec tural de si gn proc es s an d arc hi tec tura l m od el s ou tli ne t he i m po rtan ce of arc hi tec tura l s ty les in Sof tware D es ign de m on str ate ho w de ta iled d es ig n i s us ed to f urther dec om po se an al ys is an d des ign m od el s A rc hi tec tural de si gn -O rga ni sat io n Cont ro l m od el lin g Mo du lar de com po si tio n A rc hi tec tural m od el s S tat ic D yn am ic Int erf ac e A rc hi tec tural s ty les Cl ien t s er ver S erv ic e o rien ted La yer ed Deta ile d De si gn A na ly si s m od el s -Des ign m od el s Di sc us si ng the d es ig n p roc es s f or gi ven sy stem s s uc h a s e m be dd ed , da ta ba se, ba nk ing , m ini ng , ed uc at ion an d w eb b as ed Di sc us si ng the im po rtan ce of arc hi tec tura l s ty les in s of twar e de sig n Res ea rc hi ng o n a rc hi tec tur al s ty les App ly in g d eta ile d d es ig n in s of tw are de vel op m ent Cond uc tin g e duc at ion al tou rs to IT co m pa ni es an d m an uf ac turi ng ind us tri es M ult ime di a tut ori al s C AS E t ool s Des ign T oo ls Su ch as Mi cr os of t Vis io , Cor el Dr aw , Ad ob e Pho tos ho p Ex pe rt G ues tSoftware Engineering Syllabus Forms 5 - 6 Software Engineering Syllabus Forms 5 - 6 10
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
13
FO RM 6 Co nt inu ed… TO PI C O BJE CT IV ES Lea rn er s sho uld b e a bl e t o: CO NT ENT (KNO W LE DG E, S KIL LS , A TT IT UDES ) SU G G EST ED LE ARNING A CT IV IT IE S AND N O TE S SU G G EST ED LE ARNING RE SO U RCE S 8.9 P ro gr amm ing ou tli ne f ea tures of O bj ec t O rien te d P ro gram m ing ( OOP ) de si gn g am es an d m ob ile ap plic at io ns O bj ec t O rien te d P rog ram m ing Cl as ses En ca ps ula tio n P ol ym orph is m Inh eri tan ce A dv an ce d P rog ram m ing Mo bi le a ppl ic ati on s G am m ing an d A ni m ati on s Im pl em en ting c las ses D em on str ati ng the us e of S ing let on an d Mo de l Vi ew Co ntrol ler( MV C) des ig n p atte rns Des ign in g m ob ile de vi ce ap plic at io ns D es ign in g gam es wi th ind ige no us orie nta tion O bj ec t O rien te d Pr og ram m ing too ls suc h a s J av a, Py tho n, V B.N ET , PH P A ni m ati on s of tware suc h a s Sc ratc h, Ado be Cr eati ve Sui te 8. 10 Q ual ity As sur ance and T es ting e xpl ai n s of tw are qu al ity att rib ute s a nd the ir i m po rtan ce in q ua lit y as sura nc e p roc es s d em on str ate th e us e o f qu al ity as suranc e to ol s a nd tec hn iqu es in qu al ity m an ag em en t o utl in e t he i m po rtan ce of saf et y an d s ec urit y m an ag em en t i n qu al ity as suranc e r ec og ni ze ap propr iate IS O Stan da rds Sof tware Q ual ity A ttr ibu tes S of tware Q ual ity A ss uranc e -Q ua lit y p olic y -Too ls an d t ec hn iqu es o Ins pe cti on o Aud it tr ial s S af et y an d S ec urit y M an ag em en t IS O S tan da rds (ISO 90 00) Di sc us si ng the im po rtan ce o f qu al ity as suranc e a ttr ibu tes in sof tw are q ua lit y m an ag em en t Di sc us si ng the im po rtan ce o f s of tw are too ls an d tec hn iqu es App ly in g q ua lit y as suranc e t ool s a nd tec hn iqu es in t he ir sof tw are pr oj ec ts Di sc us si ng th e im po rtan ce o f IS O stan da rds in s of tw are de vel op m en t App ly in g ISO Stan da rds re le van t to the ir proj ec t a rea s Cond uc tin g cas e stud ies re lat ed to q ua lit y as suranc e a nd t es ting in sof tw are m an ag em en t F iel d t rips IS O S tan da rds Doc um en ts10 11
Fo
rms 5
–
6
So
ftw
are
En
gi
nee
rin
g
Syl
lab
us
Pa
ge
14
8.11 En ter pr ise in So ftw ar e En ginee ring ide nti fy c are ers in SE de sc ribe the du ties do ne b y SE prof es si on al s ev al uate c os t ef fec tiv e sol ut ion s in S E ou tli ne w ay s o f m ar keti ng sof tw are ev al uate m ar keti ng str ate gi es rec og ni ze i nte llec tua l propert y r igh ts Car ee rs in S E B us in es s v ia bil ity : -Ben ef its rea liz ati on Cos t a nal ys is T rad e o ff an al ys is R etu rn on in ves tm en t Ma rk eti ng s trate gi es Int el lec tua l P ro pe rty Ri gh ts Id en tif yi ng c are ers in SE Cond uc tin g e duc at ion al tou rs to s of tw are de vel op m en t c om pa ni es Parti ci pa tin g i n I T ex po s/f ai rs /ev en ts Di sc us si ng o n c os t ef fec tiv e s ol uti ons in S E Res ea rc hi ng o n vi abi lit y of s of tw are de vel op m en t p roj ec t Des ign in g m ar keti ng str ate gi es Di sc us si ng inte llec tua l propert y i ss ue s Ex pe rt g ue sts pres en tat io n Pr int an d El ec tro ni c M ed ia Int erne t Bus in es s jo ur nal s Stat is tic al to ol s Pr int an d El ec tro ni c M ed ia Ex pe rt G ues t12 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, hardsoft-ware, 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.
Assessment of learner performance in Advanced level SE 100%
Continuous assessment 30 %
Continuous assessment mark
=30%
FINAL MARKS 100 %
Summative Assessment 70%
Summative Assessment mark
= 70%
Paper 3
Coursework
10%
Profiling
Profile
Exit
Profile
Paper 4
Projects
20%
Paper 1
30%
Paper 2
40%
9. 2 Scheme of Assessment
Software Engineering learning areas will be examined through continuous and summative assessment as follows. Software Engineering Syllabus Forms 5 - 6
14
The Scheme of Assessment is intended to encourage positive achievement by all learners. The subject will be examined in 4 papers as shown in the table below.
Forms 5 – 6 Software Engineering Syllabus
Page
16
The Scheme of Assessment is intended to encourage positive achievement 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
marks Weighting
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%
Profiling
Examination Mark =
70%
Profile
EXIT PROFILE
9.3 Specification Grid
(i)
Content distribution
PAPER 1
Forms 5 – 6 Software Engineering Syllabus
Page
17
9.3
Specification Grid(i) Content distribution PAPER 1
TOPIC WEIGHTING (30%)
Software Process Models 20
Software Project Management 15
Software Design 15
Data Structures and Algorithms 10
System security and Ethics 15
Quality Assurance and Testing 15
Enterprising in Software Engineering 10
TOTAL 100
PAPER 2
SECTION WEIGHTING (40%)
Software Design 15
Data Structures and Algorithms 10
Programming 60
System Security and Ethics 5
Quality Assurance and Testing 10
TOTAL 100
(ii) Skills distribution
All internal and external tests on cognitive skills (theory) shall be 40% knowledge and understanding 50% problem solving and 10% Practical Skills.
All internal and external practical tests shall be 100% practical skills. Thus the weighting of questions based on the skills for the subject, Software Engineering, will be as follows:
SKILL Paper 1(%) PAPER 2(%)
Knowledge and
Understanding 40 10
Problem Solving 50 30
Practical Skills 10 60
TOTAL 100 100
Forms 5 – 6 Software Engineering Syllabus
Page
17
9.3
Specification Grid(i) Content distribution PAPER 1
TOPIC WEIGHTING (30%)
Software Process Models 20
Software Project Management 15
Software Design 15
Data Structures and Algorithms 10
System security and Ethics 15
Quality Assurance and Testing 15
Enterprising in Software Engineering 10
TOTAL 100
PAPER 2
SECTION WEIGHTING (40%)
Software Design 15
Data Structures and Algorithms 10
Programming 60
System Security and Ethics 5
Quality Assurance and Testing 10
TOTAL 100
(ii) Skills distribution
All internal and external tests on cognitive skills (theory) shall be 40% knowledge and understanding 50% problem solving and 10% Practical Skills.
All internal and external practical tests shall be 100% practical skills. Thus the weighting of questions based on the skills for the subject, Software Engineering, will be as follows:
SKILL Paper 1(%) PAPER 2(%)
Knowledge and
Understanding 40 10
Problem Solving 50 30
Practical Skills 10 60
TOTAL 100 100
(ii) Skills distribution
All internal and external tests on cognitive skills (theory) shall be 40% knowledge and understanding 50% problem solving and 10% Practical Skills.
All internal and external practical tests shall be 100% practical skills. Thus the weighting of questions based on the skills for the subject, Software Engineering, will be as follows:
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. Software Engineering Syllabus Forms 5 - 6
16
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
Forms 5 – 6 Software Engineering Syllabus
Page
20
APPENDIX II: ACRONYMSSDLC 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
The project must not exceed 60 pages excluding appendices. The project must include the following layout: 1. Cover Page
2. Table of Contents
3. Project Content (Sections) 4. Appendices
The Appendices include any two of the following Sample of completed questionnaires
Sample of interview questions with respondent answers Sample documents
NB the project must be spiral bound. SECTION A (25 marks)
Selection, Investigation and Analysis
Define a problem
- Choice of problem area and background analysis. [3]
APPENDIX III: PROJECT GUIDE
The project must not exceed 60 pages excluding appendices. The project must include the following layout: 1. Cover Page
2. Table of Contents
3. Project Content (Sections) 4. Appendices
The Appendices include any two of the following • Sample of completed questionnaires
• Sample of interview questions with respondent answers • Sample documents
NB the project must be spiral bound. SECTION A (25 marks)
Selection, Investigation and Analysis • Define a problem
- 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]
• 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]
Software Engineering Syllabus Forms 5 - 6
18 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
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.