ITRW225VBC - Index of

Study guide compiled by: 

Mrs L Drevin 

Study guide adopted by: 

Mrs I Koen 

Stelselontleding en –ontwerp II 

System Analysis and Design II 

STUDY GUIDE FOR 

ITRW225VBC 

*ITRW225VBC* 

VAAL TRIANGLE CAMPUS 

Printing arrangements and distribution by Department Logistics (Distribution Centre) 

Printed by The Platinum Press (018) 294 8879/(016) 981 9401 

Copyright © 2011 edition. Date of revision 2012 

North-West University, Vaal Triangle Campus 

All rights reserved. No part of this book, may be reproduced in any form or by any means 

without written permission from the publisher. It includes the making of photocopies of the 

whole or parts of this book.

INHOUDSOPGAWE 

Afdeling 1 ......................................................................................................... iv 

Module inligting ......................................................................................................................iv 

Tydverdeling ..........................................................................................................................iv 

Algemeen:..............................................................................................................................iv 

Studiemateriaal ...................................................................................................................... v 

Klasbywoning ......................................................................................................................... v 

Werkswyse ............................................................................................................................ v 

Evaluering ..............................................................................................................................vi 

Afdeling 2 ....................................................................................................... viii 

Inleiding ............................................................................................................................... viii 

Algemene wenke ................................................................................................................. viii 

Wenke i.v.m. die klassituasie en die leerproses ................................................................... viii 

Wenke vir die werk aan u Projek ............................................................................................ x 

Afsluiting ................................................................................................................................ x 

Afdeling 3 ......................................................................................................... xi 

Werksprogram .......................................................................................................................xi 

Module uitkomste ...................................................................................................................xi 

Handboek se webwerf .......................................................................................................... xii 

Studie ikone .......................................................................................................................... xii 

Aksiewerkwoorde ................................................................................................................. xiii 

Waarskuwing teen plagiaat .................................................................................................. xiv 

ii

MODULE CONTENTS 

Section 1 ......................................................................................................... iv 

Module information ................................................................................................................iv 

Time division ..........................................................................................................................iv 

General ..................................................................................................................................iv 

Study material ........................................................................................................................ v 

Prescribed text books ............................................................................................................ v 

Class attendance ................................................................................................................... v 

Working method ..................................................................................................................... v 

Role of the lecturer ................................................................................................................. v 

responsibilities of the learner ................................................................................................. v 

Library ....................................................................................................................................vi 

Evaluation ..............................................................................................................................vi 

Requirements for admission to the examination .................................................................... vii 

Section 2 ....................................................................................................... viii 

Introduction .......................................................................................................................... viii 

General tips ......................................................................................................................... viii 

Attitude and motivation ........................................................................................................ viii 

Utilising your time ................................................................................................................. viii 

Tips concearning classes and the learning process ............................................................. viii 

The class situation ............................................................................................................... viii 

At home/hostel .......................................................................................................................ix 

Tests and examination ...........................................................................................................ix 

Tips for the work on your project ............................................................................................ x 

Conclusion ............................................................................................................................. x 

Section 3 ......................................................................................................... xi 

Work schedule .......................................................................................................................xi 

Module objectives ..................................................................................................................xi 

Text book website ................................................................................................................. xii 

Study icons ........................................................................................................................... xii 

Action verbs ......................................................................................................................... xiii 

Warning against plagiarism .................................................................................................. xiv 

ii

Leereenheid 1 Uitvoerbaarheidstudie en stelselvoorstelle ................................... 1 

Leereenheid 2 Stelselontwerp ................................................................................. 3 

Leereenheid 3 Toepassingsargitektuur en modellering ........................................ 6 

Leereenheid 4 Databasisontwerp............................................................................ 9 

Leereenheid 5 Afvoerontwerp en prototipering ................................................... 12 

Leereenheid 6 Invoerontwerp en prototipering .................................................... 14 

Leereenheid 7 Gebruikerskoppelvlak-ontwerp .................................................... 16 

Leereenheid 8 Stelselkonstruksie en Implementering ........................................ 19 

Leereenheid 9 Stelselbedryf en ondersteuning ................................................... 21 

Leereenheid 10 Objek-georienteerde ontwerp en modellering ............................. 24 

Afdeling 4 Voorbeeld vraestel ........................................................................ 27 

Afdeling 5 Projek ............................................................................................. 29 

iii

Study unit 1 Feasibility analysis and system proposal...................................... 1 

Study unit 2 Systems design ............................................................................... 3 

Study unit 3 Application Architecture and modelling ........................................ 6 

Study unit 4 Database design .............................................................................. 9 

Study unit 5 Output design and Prototyping .................................................... 12 

Study unit 6 Input design and Prototyping ....................................................... 14 

Study unit 7 User interface design .................................................................... 16 

Study unit 8 Systems construction and implementation ................................. 19 

Study unit 9 System operations and support ................................................... 21 

Study unit 10 Object-oriented design and Modeling .......................................... 24 

Section 4 Example examination paper ......................................................... 27 

Section 5 Project ............................................................................................ 29 

iii

AFDELING 1 

MODULE INLIGTING 

Module kode: ITRW 225 

Beskrywende Naam: Stelselontleding en –ontwerp II 

PU-vlak 2 

Nasionale vlak 5(b) 

Krediete 16 (160 ure) 

Kontak periodes 1.5 ure teorie , 1.5 ure prakties 

TYDVERDELING 

Aktiwiteit Weke Ure/week Totaal 

Klas (kontaktyd, klastyd en klastoetse) 13 3 39 

Opdragte 10 1 10 

Selfstudie en voorbereiding 12 1.5 18 

Semestertoets en voorbereiding 1 6 6 

Eksamen en voorbereiding 1 11 11 

Praktiese klas 12 2 24 

Projek 12 4 48 

Voorlegging en demonstrasie 4 

Totaal 160 

ALGEMEEN: 

Welkom terug by Rekenaarwetenskap & Inligtingstelsels na die winter vakansie. Ons hoop 

dat u veel waarde sal put uit hierdie kursus deurdat u verder die fases in stelselontleding en 

–ontwerp sal bestudeer. 

Voorvereistes: ITRW123 of ITRW124 en ITRW213 

Dosent: Mrs I Koen 

iv 

8-139 

Telefoon: 016 910 3294 

E-pos: 10199748@nwu.ac.za 

Spreekure: Soos op eFundi aangedui – sonie kom reël anders met dosent 

Lokaal: 12-G04; 9A-106 (Renoster) 

Periodes: Do 1 & 2; Di 5 & 6

SECTION 1 

MODULE INFORMATION 

Module code: ITRW225 

Descriptive name Systems Analysis and Design II 

PU Level 2 

National Level 5(b) 

Credits 16 (160 hours) 

Contact Periods 1.5 hours theory, 1.5 hours practical 

TIME DIVISION 

Activity Weeks Hours/week Total 

Class (Contact time, class & class tests) 13 3 39 

Assignments 10 1 10 

Self-study and preparation 12 1.5 18 

Semester test and preparation 1 6 6 

Examination and preparation 1 11 11 

Practical class 12 2 24 

Project 12 4 48 

Presentation and demonstration 4 

Total 160 

GENERAL: 

Welcome to Computer Science and Information systems after the winter holidays. We hope 

that you will benefit from this module, studying the next few phases of systems analysis and 

design. 

Prerequisites: ITRW123 or ITRW124 and ITRW 213 

Lecturer: Mrs I Koen 

iv 

8-139 

Telephone: 016 910 3294 

E-mail: 10199748@nwu.ac.za 

Consulting hours: As indicated on eFundi – or arrange with the lecturer 

Lecturing room: 12-G04; 9A-106 (Rhino) 

Periods: Thu 1 & 2; Tue 5 & 6

STUDIEMATERIAAL 

VOORGESKREWE HANDBOEKE 

1. Bentley LD & Whitten JL, 

Systems Analysis and Design for the Global Enterprise 

7th edition 

Uitgegee deur Mc Graw Hill. 

ISBN 0077114841 (Bundle ed) of 0-07-110766-5 – sonder sagteware 

2. Hierdie studiegids 

KLASBYWONING 

Volgens regulasies. Aangesien klastoetse wel sonder vooraf kennisgewing gegee kan word, 

is dit noodsaaklik dat alle klasse bygewoon word, tensy anders gereël. 

WERKSWYSE 

ROL VAN DIE DOSENT 

Die studiegids verskaf aan u 'n raamwerk van die semester se werk. Ons beklemtoon die 

belangrikheid van selfwerksaamheid in hierdie kursus. Die dosent tree op as fasiliteerder in 

die kursus en leerders se probleme sal ook bespreek word in die klas. 

VERANTWOORDELIKHEDE VAN DIE LEERDER 

Van u word verwag om voor 'n periode die werk aandagtig deur te lees sodat interaksie kan 

plaasvind en die klas nie in 'n eengesprek sal verander nie - volg die uitkomstes om uself te 

lei in u voorbereiding. Skryf kernaantekeninge en voorbeelde vir uself neer. U kan in die 

handboek volg en notas daarby neerskryf. Vra dadelik as iets vir u nie baie duidelik is nie. 

Gee u samewerking in die klas sodat interaksie gemaklik kan plaasvind. Moet nie slaafs 

probeer afskryf nie, luister eerder want die werk staan tog in die handboek - tensy die dosent 

sê dat sy nou werk behandel buite die handboek. Die leerder moet die gevallestudies in die 

hoofstukke se inleidings baie goed deurlees. Voorbereiding vir elke hoofstuk moet ook 

gedoen word – lees die werk oorsigtelik deur voor die klasgeleentheid. 

Daar sal gereeld klastoetse geskryf word oor die afgehandelde werk. Wees dus gereed 

daarvoor - die punt vir die klastoetse sal deel uitmaak van u semesterpunt. Gereelde 

klasbywoning spreek vanself. 

Die praktiese projek is 'n gerekenariseerde stelsel wat in groepsverband ontwikkel moet 

word. Dit is ‘n voortsetting van die stelsel wat gedurende die eerste semester in ITRW 213 

beplan is. U moet vroegtydig begin om betyds klaar te kry aangesien probleme tog opduik 

sonder dat mens daarvoor beplan het. Kom weekliks bymekaar om u vordering/probleme te 

bespreek. Doen u eie werk – anders leer u niks nie. Hou rugsteun van u werk. 

v

STUDY MATERIAL 

PRESCRIBED TEXT BOOKS 

1. Bentley LD & Whitten JL, 

Systems Analysis and Design for the Global Enterprise 

7th edition 

Uitgegee deur Mc Graw Hill. 

ISBN 0077114841 (Bundle ed) of 0-07-110766-5 – without software 

2. This study guide 

CLASS ATTENDANCE 

According to regulations. Since class tests may be given without prior notice, it is essential 

that students attend all classes, unless other arrangements are made. 

WORKING METHOD 

ROLE OF THE LECTURER 

The study guide provides you with a framework of the semester’s work. We emphasise the 

importance of self-study in this course. The lecturer acts as a facilitator in the course and 

learners’ problems will also be discussed during class. 

RESPONSIBILITIES OF THE LEARNER 

It is expected of you to read attentively through the work so that interaction is possible and 

the class does not become a monologue on the side of the lecturer – follow the outcomes to 

guide you in your preparation. Write core notes and examples for yourself. You can follow 

the textbook and add your own notes. Ask immediately if something is not clear. Give your 

co-operation during class in order to facilitate interaction. Do not try to take notes slavishly, 

rather listen in class since the work is in the textbook anyway– unless the lecturer indicates 

that the work he/she is discussing is not in the textbook. The learner must read carefully 

through the case studies in the introduction of each chapter. The student should also be 

prepared for the work in the chapter - read through each new chapter before the contact 

session. 

Class tests will be written regularly on work that was covered in class. Be prepared for this – 

marks obtained for class tests will constitute part of your semester mark. The importance of 

regular class attendance speaks for itself. 

The practical project is a computerised system that must be developed in groups. It is a 

continuation of the project you have planned during the first semester in ITRW 213. You 

need to start ahead of time in order to finish within the submission deadline; unplanned 

problems are bound to arise and you may need time to address these. Meet on a weekly 

basis to discuss your progress and problems. Do your own work, otherwise you do not learn 

anything. Keep back-ups of your work. 

v

Elke leerder sal ook geleentheid kry om 'n mondelinge voorlegging in die klas - voor u 

klasmaats en dosent - te maak van 'n afgespreekte aspek of fase van u projek. Die 

voorlegging moet tussen 4 en 6 minute duur en u moet van gepaste hulpmiddels gebruik 

maak. 

Die projek moet ontwikkel word volgens die stelselmodelle wat in ITRW 213 ontwikkel is. Die 

projek sowel as die stelselmodelle moet op 'n afgespreekte tyd aan die dosent/praktiese 

assistent en medeleerders voorgelê word waartydens u moet verduidelik die hoe stelsel 

ontwerp en ontwikkel is. U moet 'n bevredigende punt hiervoor kry vir eksamentoelating aan 

die einde van die semester. 

Hou asseblief die rekenaarlokale en klaskamers netjies. 

Kom vra gerus as u probleme ondervind met enige aspek van die werk. 

BIBLIOTEEK 

Die hele biblioteek is tot u beskikking. Gebruik dit gerus om bykomende inligting oor die 

kursus te bekom, asook om van interessanthede te wete te kom. Daar is ook verskeie 

rekenaartydskrifte wat u mag gebruik vir opdragte of vir eie inligting. 

U kan ook biblioteek of Internet opdragte kry van tyd tot tyd oor vakverwante onderwerpe. 

Die rekenaarwetenskapboeke se standnommers begin by 004 ... 006. 

Vooraan elke leereenheid word aangedui hoe lank dit sal neem om te voltooi. Die handboek 

gebruik ‘n gevallestudie benadering wat vereis dat elke leerder die gevallestudie vooraan 

elke hoofstuk moet deurwerk en die besprekingsvrae moet kan beantwoord, voordat die 

hoofstuk bestudeer word. 

Elke leereenheid sal dan eindig met ’n klastoets en prakties toepassing itv die praktiese 

projek wat aan gewerk moet word en/of opdragte wat gegee word. 

EVALUERING 

U sal op verskeie wyses getoets word deur die semester om te bepaal of u die uitkomstes 

bereik het. 

1 Klastoetse 

vi 

Ε Klastoetse wat bydra tot die deelnamepunt word weekliks geskryf. 

Ε Klastoetse handel oor die werk wat behandel word en kennis van vorige werk is 

noodsaaklik. 

Ε Onderrigtoetse wat handel oor die vorige periode se werk kan sonder vooraf 

waarskuwing gegee word. 

Ε Jy moet alle werk wat in die studiegids behandel word so voorberei dat jy enige 

tyd daaroor ’n onderrigtoets kan skryf. 

Ε Leer is ’n kumulatiewe proses en nuwe kennis bou op voorkennis. Dit is dus 

noodsaaklik om te kontroleer dat die uitkomste vir elke deel van die werk 

bemeester is. 

Ε Indien klas en toetsbywoning goed is, word die swakste klastoets(e) nie vir die 

berekening van die deelnamepunt gebruik nie. Geen hertoetse nie.

Each learner will get the opportunity to do an oral presentation in the class explaining a 

certain section of the project – in front of the lecturer and members of the class. The time 

allowed for this presentation will be 4 to 6 minutes and you should make use of all suitable 

teaching aids. 

The project must be developed according to the system models designed in ITRW 213. 

Learners must present their system as well as the system models to the lecturer or the 

assistant on a scheduled time. During this presentation, learners must explain the how the 

system was designed and developed. A good mark for this presentation is required for 

admission to the examination at the end of the semester. 

Please keep the computer rooms neat and clean. 

Discuss any problems with the work with your lecturer. 

LIBRARY 

The entire library is available to you. Use this facility in order to obtain as much additional 

information as possible. There are computer magazines that may be used for assignments or 

for your own information. 

You might get assignments that will require of you to visit the library or to look up some 

information on the Internet. 

Computer Science subject books are located on the 004 ... 006 shelves in the library. 

The time that it will take to complete the study unit is indicated at the start of each 

study unit. The textbook uses a case study approach that requires of each learner to read the 

chapter and answer the questions on the case study before the chapter is studied. 

A class test will be written and a practical application regarding the project and/or other 

assignments will be done at the end of each study unit. 

EVALUATION 

You will be assessed in several ways in order to make sure that you have reached the 

learning objectives. 

1 Class tests 

vi 

Ε Weekly class tests will contribute towards your evaluation mark. 

Ε Class tests will be set on the work to be done during the period but knowledge of 

work that was previously done is also important. 

Ε Shorter tests on the work presented in the previous lecture, can also be written 

without prior notice. 

Ε Learners must prepare all the work indicated in this study guide in order to be 

able to write these short class tests at all times. 

Ε Learning is an accumulative process and new knowledge is built on previous 

knowledge. It is important to ensure that you always master the learning 

objectives of all the study units. 

Ε If class and test attendance is satisfactory, the lowest mark(s) obtained in class 

tests, might be dropped. No tests will be rewritten.

2 Praktiese projek 

Dit bestaan uit ‘n praktiese projek wat die groep moet ontwikkel volgens die beplanning wat 

gedoen is gedurende die eerste semester in ITRW 213. Daar sal van die groep verwag word 

om die projek in verskillende stadiums van ontwikkelling te demonstreer. Aan die einde van 

die semester moet die volledige werkende stelsel aan die dosent gedemonstreer word vir 

punte. Elke lid van die groep sal ‘n beurt kry om verskillende afdelings van die projek te 

verduidelik. 

3 Klasopdragte 

Dit behels vrae en gevallestudies soos van tyd tot tyd deur die dosent aan u verskaf. 

4 Semestertoets 

5 Semestereksamen 

Deelnamepunt 

Die deelnamepunt word bereken deur alles hierbo genoem in ag te neem. Die praktiese 

projek sal ook 'n groot deel uitmaak van die punt. Suksesvolle voltooiing van u projek se 

ontleding is 'n vereiste vir eksamentoelating. 

Die deelnamepunt sal bereken word soos aangedui op u weeklikse skedule. 

VEREISTES VIR EKSAMENTOELATING 

‘n Deelnamepunt van ten minste 40% word vereis vir toelating tot die eksamen. Die leerder 

kry altyd twee eksamengeleenthede om sy/haar eksamen af te handel. 

Opmerkings 

• Die tweede geleentheid is altyd die laaste geleentheid. 

• Geen bewys vir afwesigheid van die eerste geleentheid is nodig nie, hetsy siekte, dood 

van ‘n naasbestaande of enige ander rede. 

• Indien ‘n leerder by die tweede geleentheid afwesig is (ongeag die rede) of druip, is 

geen verdere geleentheid beskikbaar nie. Indien ‘n module nie tydens die eerste of 

tweede eksamengeleentheid geslaag is nie, kan die module slegs herhaal word deur 

van nuuts af daarvoor te registreer en opnuut ‘n deelnamebewys te verwerf. 

vii

2 Practical project 

This consists of a project that you must develop during the semester. It is a continuation of 

the project that you planned during the first semester in ITRW 213. You will be required to 

demonstrate the project at different stages of development. At the end of the semester the 

group will be required to demonstrate the complete working system to the lecturer. The 

members of the group will take turns to explain different sections of the project. 

3 Assignments 

This consists of questions and case studies that will be given from time to time. 

4 Semester test 

5 Semester examination 

Participation mark 

The participation mark will be calculated by incorporating all of the above-mentioned. The 

practical project will contribute more than the other tests. The successful completion of the 

project is a prerequisite for admission to the examination. 

The participation mark will be calculated as indicated on your weekly schedule. 

REQUIREMENTS FOR ADMISSION TO THE EXAMINATION 

A participation mark of at least 40% is required for admission to the examination. The learner 

will always get two opportunities to do his/her final examination. 

Remarks 

• The second session is the last opportunity to write the examination. 

• No proof in respect of absenteeism from the first session is necessary, no matter what 

the reason may be. 

• If you did not write the first examination and you miss or failed the second examination 

for whatever reason, there shall be no further more opportunities to complete this 

course. If you did not pass the first or the second opportunity, you will have to repeat 

this module completely by registering for the module again and obtaining a new 

participation mark. 

vii

AFDELING 2 

Wenke vir die bestudering van Rekenaarwetenskap en Inligtingstelsels 

INLEIDING 

Hierdie wenke is opgestel om u te help met u studie in Rekenaarwetenskap. Hoofsaaklik het 

Rekenaarwetenskap te make met die oplos van probleme met behulp van die rekenaar. 

Daar sal dus klem gelê word op selfwerksaamheid en praktiese toepassing van die werk ten 

opsigte van die projek. 

ALGEMENE WENKE 

HOUDING EN MOTIVERING 

’n Positiewe houding is ‘n voorvereiste vir sukses. Indien u gemotiveerd is om u klasse by te 

woon en al u verantwoordelikhede nakom is 'n groot deel van die stryd al gewonne. Geniet 

elke kursusmodule en sien elke probleem as 'n uitdaging wat u graag wil baasraak. U sal 

ook sien dat 'n dieper benadering teenoor leer wenslik is omdat u dan nie net feitekennis 

bymekaar maak nie, maar ook die werk verstaan en verbande kan trek met ander kennis - 

selfs in ander vakke. 

Wees vindingryk en kreatief met u probleem-oplossingsmetodes. As die werk moeilik is, 

probeer maar weer en moenie tou opgooi nie, hulp is beskikbaar by assistente of u dosent. 

U moet ook nie angstig wees en bekommerd raak nie - dit kan teenproduktief wees. Doen 

goeie beplanning van u tyd en wees positief ingestel teenoor u werk. 

BENUTTING VAN U TYD 

Om suksesvol te wees in u studies is dit baie belangrik dat u u tyd goed sal bestuur. Daar is 

baie aktiwiteite by die universiteit wat eise aan u sal stel. Konsentreer op die belangrikste 

aktiwiteite en beplan hoe u u tyd daaraan gaan spandeer. U is nou die verantwoordelike 

persoon en u behoort u tyd sinvol te beplan om u studies sowel as ander aktiwiteite op 

kampus te akkomodeer. Onthou dat praktiese opdragte soos u projek baie tyd in beslag 

neem. U sal lank voor die tyd reeds moet begin met die projek om betyds klaar te wees. 

Moenie die aand (of die week) voor die sperdatum eers daarmee begin nie - daar sal nie 

genoeg tyd wees nie. 

WENKE I.V.M. DIE KLASSITUASIE EN DIE LEERPROSES 

VERLOOP VAN 'N KLASSESSIE 

• Ons probeer 'n oorsig te kry oor die vorige periodes(s) se werk wat dan sal aansluit by 

die nuwe werk. 

• Vrae oor die vorige werk kan gevra word en onduidelikhede sal uit die weg geruim 

word. 

• Huiswerkopdragte sal bespreek of ingehandig word. 

• Oor die nuwe werk sal 'n oorsig gegee word en die uitkomste sal gestel word. 

• Die hoofpunte sal beklemtoon word en moeilike dele verduidelik word. Voorbeelde en 

toepassings sal die werk verder belig. 

• Huiswerkopdragte kan aan u gegee word wat in die klas of vir tuiswerk gedoen word. 

(Individueel of in groepverband – soos bespreek in die klas ) 

viii

SECTION 2 

Tips in respect of the study of Computer Science and Information Systems 

INTRODUCTION 

These tips are compiled to assist you your studies of Computer Science. Computer Science 

mainly has to do with ways to solve problems by using the computer. Emphasis will be 

placed on self-study and practical application of the work in terms of the project. 

GENERAL TIPS 

ATTITUDE AND MOTIVATION 

A positive attitude is a prerequisite for success. If you are motivated to attend all your classes 

and you are well prepared for each class, you will have a good chance of succeeding in your 

studies. Enjoy your studies and approach each problem as a challenge that you want to meet 

successfully. Try to obtain more from your studies than just memorising facts. Try to see the 

relationship between different learning units and even different subjects. 

Be creative when solving problems. Even if the work is difficult, do not lose faith in yourself – 

You can always get help from the assistants or the lecturer. Don’t panic, as this is counter 

productive. Plan your time well and be positive at all times. 

UTILISING YOUR TIME 

In order to be successful in your studies, you have to manage your time well. There are 

many activities at the university that will demand time and time management is crucial. 

Concentrate on the important activities and spend more time on them. You the responsible 

person now and you have to plan your time sensibly in order to accommodate your studies 

as well as other activities on campus. Remember that practical assignments such as your 

project will take up a lot of your time. You will have to start well in advance with the project in 

order to finish in time. Do not try to start and complete the project a day (or a week) before 

the deadline. There will not be enough time. 

TIPS CONCEARNING CLASSES AND THE LEARNING PROCESS 

THE CLASS SITUATION 

• We shall attempt to provide an overview of the work completed in the previous 

session(s), and relate this to the new material. 

• Questions can be asked on the previous work and uncertainties will be sorted out. 

• Homework will be discussed or handed in. 

• An overview will be given on the new material and learning objectives will be pointed 

out. 

• Important aspects will be emphasised and difficult sections will be discussed. 

Examples and applications will be discussed, if necessary. 

viii

• Tydens die afgespreekte periode sal klastoetse geskryf word en u moet deeglik 

daarvoor voorbereid wees. Dit sal korter tipe vrae wees of klein gevallestudies. 

• Dit is baie belangrik dat u konsentreer in die klas en ‘n verwantskap kan sien tussen 

die vorige werk en die nuwe werk. U sal die werk beter verstaan as u goed voorberei is 

vir elke klas, aandag gee in die klas en deelneem aan besprekings. 

• Doen gereeld u huiswerk en gaan die werk weer tuis deur, sodat u die doelwitte kan 

baasraak. Tydens klastyd is daar nie genoeg tyd om werk te herhaal nie. 

BY DIE HUIS/KOSHUIS 

• U behoort elke dag deur die dag se werk te gaan om te verseker dat u die werk 

verstaan en waar dit in u kursus inpas. Onduidelikhede moet die volgende periode aan 

die dosent gestel word en uit die weg geruim word. Probeer u self te toets teenoor die 

gestelde doelwitte. 

• Doen u huiswerk getrou - so toets u uself om te kyk of u die werk verstaan. 

• U behoort hoofpunte in u stuk werk (hoofstuk) te kan identifiseer soos die dosent dit 

ook sal uitlig en te kan onderskei tussen belangrike feite en ander inligting wat 

voorbeelde of besprekings is. Som die werk op om u beter voor te berei vir toetse en 

eksamens. 

• U kan van begripskaarte gebruik maak sodat u in een oogopslag die verbande tussen 

feite kan sien en die geheelbeeld van 'n leereenheid kan vaslê. ‘n Handige webwerf 

van konsepkaarte is : http://cmap.coginst.uwf.edu/ . Daar is ook ‘n gratis program 

beskikbaar met beperkte funksies om sulke kaarte te konstrueer. 

TOETSE EN EKSAMENS 

Die volgende kan as 'n leermetode gesien word. Onthou dat die tipe vrae sal verskil van 

klastoetse, semestertoetse en eksamens. Die vraesteltipe sal met u bespreek word voor die 

toetsgeleentheid. Skryf netjies en leesbaar. 

• Identifiseer die hoofpunte in elke leereenheid nadat u dit deurgelees het. 

• Identifiseer nou die feite in elke hoofpunt. 

• Probeer 'n geheelbeeld te kry om te sien waar elke stukkie inligting inpas. (U kan 

weereens die begripskaarte hier gebruik). 

• Herhaal die feite totdat u dit vir uself kan opnoem of neerskryf. 

• Stel vir uself ook vrae op en dan kan u nadat 'n gedeelte geleer is, uself toets. 

• Maak vir u 'n samevatting om al die nodige verbande te trek en die belangrikste 

aspekte te beklemtoon. 

• Die belangrike is hier die verstaan van werk en nie net die kennisreproduksie nie. 

Basiese definisies en terme moet geken word, maar die res van die inligting moet u in 

die geheelbeeld van die kursus kan inpas. Werk volg op mekaar en raak moeiliker en 

vorige kennis is belangrik om die volgende te kan akkommodeer. 

ix

• You will receive assignments to complete in class or at home. (Individual or in groups, 

as discussed in class). 

• Class test will be written on specified dates and you must be well prepared for these 

tests. It will consist of short questions as well as mini case studies. 

• It is important to concentrate in class and to make a connection between the 

previous work and new material. You will understand the work better if you are well 

prepared for each class, pay attention in class and take part in discussions. 

• Complete your homework regularly and make sure that you have mastered the 

objectives. There is not enough time to repeat work during class time. 

AT HOME/HOSTEL 

• You should review the work that was done during the day at home so as to ensure that 

you understand the work and see how it fits into the course. Uncertainties should be 

clarified during the next contact session. Test yourself by ensuring that you have 

mastered the learning outcomes. 

• Do your homework on a regular basis. By doing this, you will ensure that you 

understand the work fully. 

• You should identify the main concepts in each module (chapter) as indicated by the 

lecturer and distinguish between important facts and other information used as 

examples or discussions. Make abstracts of the work in order to be better prepared for 

tests and the examination. 

• You can make use of visual abstracts and diagrams which will assist you in relating the 

facts with the overall framework of the study unit. where possible, as these are 

important learning aids. A handy web site of visual diagrams is 

http://cmap.coginst.uwf.edu/ At this site you will find free software (with limitations), to 

construct concept cards. 

TESTS AND EXAMINATION 

The following may be considered as a learning method. Remember that the type of 

questions might differ in the tests, semester tests and the examination. The type of 

question paper will be discussed before the evaluation session. Write neatly and clearly. 

• Identify the main concepts in every learning unit after you have read it. 

• Identify the facts in each main section. 

• Try to obtain an overall view in order to see where each fact contributes to the overall 

view. (You can use the concept cards to assist you with this) 

• Repeat the facts until you can write it down without any difficulty. 

• Test yourself by compiling your own review questions on the material that you have 

studied. (plan the questions, study the work and test yourself afterwards) 

• Summarise the work to be able to identify related concepts and to emphasize all the 

important facts. 

• The important idea is to understand the work and not to merely reproduce facts of 

knowledge. It is important to know important definitions and terms, but for the rest, you 

must be able to fit it into the overall view of the module. The current work will be related 

to work done previously and will be more difficult as well. Prior knowledge is therefore 

important in order to accommodate new work. 

ix

WENKE VIR DIE WERK AAN U PROJEK 

U sal heelwat teorie-tipe werk leer en hoor in die klastye. Dié kennis en metodes moet egter 

toegepas word in die ontwikkelling van u projek. Beplanning en ontwerp is baie belangrik 

wanneer u u projek doen. 'n Bouer kan tog nie 'n huis bou sonder 'n plan en spesifikasies 

nie. Netso kan u nie 'n probleem oplos voordat u gedink het oor die probleem en 'n plan van 

aksie bedink het nie. Tipiese vrae wat u uself kan afvra is: 

• Wat word as invoer benodig? In watter formaat? Hoe lyk die invoerlêers? 

• Wat word as uitvoer benodig? In watter formaat? Hoe lyk die lêeruitlegte? 

• Is daar enige besluite wat geneem moet word? 

• Is daar sprake van herhaling? 

• Ens. 

Nou eers kan u aan die algoritme dink, dit toets en dan kodeer in 'n rekenaartaal. Dan volg 

ontfouting en toetsing. Onthou om gedurig u probleemstelling in gedagte te hou en te vra of 

ek die regte probleem reg oplos. 

• Onthou om gedurig goeie programstyl aan die dag te lê en genoegsame kommentaar 

in u program te sit. Hou weergawes van u pogings om sodoende makliker 

veranderings aan te bring en weer terug te herstel. 

• Moenie ure op 'n fout spandeer nie - kry hulp by 'n mede-leerder of assistent of dosent. 

• Kreatiewe denke en vindingrykheid is belangrike eienskappe wat u behoort te gebruik 

tydens programontwerp. U sal die vaardighede nie leer deur net deur 

programvoorbeelde te lees nie, oefening en nogmaals praktiese sessies voor die 

rekenaar is baie belangrik. Dink net, u kry ervaring so terwyl u studeer! 

• Konsekwente werk is belangrik omdat nuwe vaardighede en metodes bygeleer word 

soos die semester vorder. Moet dus nie agter raak nie en oefen gereeld die nuwe werk 

in. 

In hierdie spesifieke kursus sal u ander vaardighede leer – die programmeringdeel vir u 

projek moet uself bemeester. Onderwerpe soos projekbestuur, data-insameling, modelle 

daarstel deur UML te gebruik sal ook vir u gestalte kry. Dit is dus belangrik dat u hierdie 

nuwe vaardighede ook sal bemeester. 

AFSLUITING 

Bestudeer en gebruik gereeld u studiegids om die uitkomstes van die module in oog te hou. 

Vra u kort-kort af: waar trek ons nou, waarheen is ons op pad en hoe pas die nuwe werk by 

die ou werk in? Nuwe kennis moet met ou kennis geïntegreer word sodat nuwe horisonne 

vir u kan oopgaan. Werk gereeld en beplan hoe u u tyd gaan spandeer. Pas teoretiese 

kennis toe tydens die ontwikkelling van u projek. Sien u projek as 'n uitdaging en geniet u 

kursus! 

x

TIPS FOR THE WORK ON YOUR PROJECT 

A lot of theoretical work will be covered during lectures. You must apply the theoretical 

knowledge in practise when developing your project. 

• Planning and design are very important when you do your project. A builder cannot 

build a house unless a plan and specifications have been approved. In the same 

sense, it is fatal to try to solve a problem without thinking about it first and setting out a 

plan of action. 

x 

Typical questions to be answered are the following. 

Ε What is the input? In what format? What is the format of the input files? 

Ε What output is needed? In what format? What is the format of the output files? 

Ε Are there any decisions to be made? 

Ε Are there actions to be repeated? 

Now that you have all the above information, you can think of an algorithm, testing and 

coding in a computer language. Debugging and testing follows. Remember to make sure that 

you solve the correct problem correctly. 

• Adopt a good programming style and insert comments, where necessary. Keep a 

record of the different versions. 

• Do not spend too much time on errors – rather seek help from a friend, an assistant or 

a lecturer. 

• Creativity is important and should be practised during the process of problem solving. 

You will gain valuable experience only if you try your best, practice and spend time to 

solve problems. 

• Work regularly, as you will gain much experience as the semester progresses. Do not 

fall behind. 

This module will teach you other skills - you have to master the programming skills 

yourself. Topics such as project management, data collection, models by making use 

of UML etc., will also be introduced. It is important to master these skills to be able to 

use in your project. 

CONCLUSION 

Use your study guide on a regular basis to make sure that you have mastered the objectives. 

Ask yourself on a constant basis: where we are and where are we heading. How does the 

new work relate to the previous work done? Integrate new and previous knowledge to get an 

overview. Plan your time and work on a regular basis. Apply the theoretical knowledge in 

practise while developing your project. Regard your project as a challenge and enjoy the 

course!

AFDELING 3 

WERKSPROGRAM 

WEEK Hoofstuk in 

handboek 

ONDERWERP 

1 11 Leereenheid 1: Uitvoerbaarheidstudie en stelselvoorstel 

2 12 Leereenheid 2: Stelselontwerp 

3 & 4 13 Leereenheid 3: Toepassingsargitektuur en Modellering 

5 14 Leereenheid 4: Databasisontwerp 

6 15 Leereenheid 5: Uitvoerontwerp en prototipering 

6 16 Leereenheid 6: Invoerontwerp en prototipering 

7 17 Leereenheid 7: Gebruikerskoppelvlakontwerp 

8 19 Leereenheid 8: Stelselkonstruksie en implementering 

9 20 Leereenheid 9: Stelselbedryf en ondersteuning 

Projek: Gebruikershandleiding 

10 18 Leereenheid 10: Objek-georiënteerde Ontleding en 

Modellering m.b.v. UML 

Projek: Stelselfinalisering 

11,12 Projek: Stelseldemonstrasie 

13 Hersiening 

MODULE UITKOMSTE 

Voordat u ’n stelsel kan ontleed, ontwerp en implementeer moet teoretiese voorkennis eers 

bemeester wees. 

Kennis: 

Na afloop van die kursus sal die leerders kan demonstreer dat hulle oor voldoende kennis 

van en insig in die fases en tegnieke van die stelselontwikkelingslewensiklus beskik om te 

kan toepas wanneer ’n stelsel beplan, ontleed en ontwerp word. 

Vaardighede: 

Die leerder sal na afhandeling van hierdie kursus kan bewys dat hy/sy die fases en tegnieke 

van stelselontleding kan toepas in ’n projek. Hulle moet ’n praktiese projek kan bestuur deur 

projekbestuurstegnieke te gebruik. Die leerder sal kreatief en probleemoplossend kan dink 

en optree wanneer ’n gerekenariseerde stelsel ontwerp en ontwikkel word. Groepwerk moet 

suksesvol aangepak kan word en ‘n verskeidenheid tersaaklike dokumentasie moet 

saamgestel kan word en ‘n stelselaanbieding moet ook gemaak word. 

xi

SECTION 3 

WORK SCHEDULE 

WEEK Chapter in 

the text book 

TOPIC 

1 11 Study unit 1: Feasibility Study and System proposal 

2 12 Study unit 2: Systems Design 

3 & 4 13 Study unit 3: Application Architecture and Modelling 

5 14 Study unit 4: Database Design 

6 15 Study unit 5: Output Design and Prototyping 

6 16 Study unit 6: Input Design and Prototyping 

7 17 Study unit 7: User Interface Design 

8 19 Study unit 8: Systems Construction and Implementation 

9 20 Study Unit 9: Systems Operations and Support 

Project: User manual 

10 18 Study unit 10: Object-Oriented Analysis and 

Modelling using UML 

Project: Finalising the system 

11,12 Project: Demonstration session 

13 Revision 

MODULE OBJECTIVES 

Before you can analyse, design and implement a system, theoretical knowledge needs to be 

mastered. 

Knowledge: 

After having completed the course learners will be able to demonstrate that they dispose of 

sufficient knowledge of, and insight into the phases and techniques of the systems 

development life cycle in order to be able to apply this knowledge to the planning, analysis 

and design of a system. 

Skills: 

After having completed the course the learner will be able to prove that he/she can apply the 

phases and techniques of systems development in the context of a project. Learners must 

be able to manage a practical project by using project management techniques. The learner 

will be able to think and act creatively and with a view to solving the problem at hand when a 

computerised system is designed and developed. Group work must be completed 

successfully. 

xi

Gesindheid en houding: 

Die leerder moet deurentyd bewus wees dat 

• stelsels vir die gebruiker ontwikkel word en dat hulle voorkeure en werkwyses in ag 

geneem moet word gedurende stelselontleding en -ontwerp; 

• stelsels met noukeurigheid en op ooreengekome wyse voltooi moet word; 

• inligting rakende die kliënt met die nodige konfidensialiteit hanteer moet word; en 

• rekenaarhulpbronne eties en verantwoordelik gebruik moet word. 

HANDBOEK SE WEBWERF 

Die uitgewers van die handboek self het ‘n webwerf geskep met handige verwysings, 

verduidelikings en template van dokumente vir u eie gebruik. Gebruik dit gerus tydens 

voorbereiding, opdragte en projek afhandeling. 

www.mhhe.com/whitten 

http://highered.mcgraw-hill.com/sites/0073052337/information_center_view0/ 

STUDIE IKONE 

xii 

Individuele oefening. 

Bestudeer die aangetoonde 

materiaal in die 

handboek/artikel, ens. 

Hersiening. 

Skryf die klastoets 

volgens skedule. 

Bestudeer nou die volgende 

gedeelte/verduideliking / 

bespreking, aandagtig. 

Uitkomste. 

Gevallestudie. 

Geskatte studietyd.

Attitude: 

The learner must always bear in mind that 

• Systems are developed for users, and their preferences and working methods must be 

taken into account during systems analysis and design; 

• Systems must be completed accurately and according to the agreed upon manner; 

• Information about the client should be treated with the necessary confidentiality; and 

• Computer resources should be used ethically and responsibly. 

TEXT BOOK WEBSITE 

The publishers of the textbook have created a website with handy references, explanations 

and templates of documents for your own use. Feel free to use this during your preparation, 

assignments and projects. 

www.mhhe.com/whitten 

http://highered.mcgraw-hill.com/sites/0073052337/information_center_view0/ 

STUDY ICONS 

xii 

Individual 

exercise. 

Study the 

indicated 

material(s) in the 

textbook/article, 

etc. 

Revision. 

Write the class 

test according to 

schedule. 

Study the 

following 

section/explanatio 

n / discussion, 

attentively. 

Outcomes. 

Case study. 

Approximate study 

time.

AKSIEWERKWOORDE 

Vrae, hetsy in toetse of eksamens, bevat altyd sekere sleutel- of aksiewerkwoorde. Studente 

moet weet wat die aksiewoorde beteken en wat van hulle by die beantwoording van die 

vraag verlang word. Met die oog hierop word hier onder ’n kort lysie van sulke woorde 

verskaf. ‘n Kort omskrywing van aksiewerkwoorde met ‘n hoë gebruiksfrekwensie in 

vraestelle sal die lysie nog meer toepaslik maak. 

• Noem 

Hier word net die feite kort en saaklik neergeskryf. 

• Beskryf 

Hier word prestasie op die kennisvlak verwag. Eienskappe, feite of resultate word op ‘n 

logiese, goed gestruktureerde wyse weergegee. Geen kommentaar of beredenering is nodig 

nie. 

• Definieer 

Kennisreproduksie word vereis. Dit is ‘n duidelike, kernagtige en gesaghebbende 

beskrywing van ‘n begrip sodat die betekenis daarvan duidelik blyk. 

• Gee ‘n oorsig 

‘n Groot volume kennis moet op ‘n logiese en sistematiese wyse saamgevat en weergegee 

word, sonder dat die essensie van die saak verlore raak. 

• Verduidelik 

Die saak word eenvoudig gestel sodat die leser dit sal verstaan, gewoonlik in jou eie woorde. 

Hier moet van illustrasies, beskrywings en voorbeelde gebruik gemaak word, terwyl ook 

redes vir uitsprake en resultate gegee word. 

• Bewys 

Staaf die feite deur die logiese aanvoering van aanvaarbare feite. 

• Vergelyk 

Hierdie vraag moet versigtig hanteer word. Die een saak moenie eers beskryf of bespreek 

word en dan later die volgende nie. Feite, gebeure of probleme word teenoor mekaar gestel 

en ooreenkomste en verskille word na vore gebring. 

• Bespreek 

Hierdie tipe vraag veronderstel insig en onderskeidingsvermoë wanneer ‘n toepassing en 

beoordeling gemaak word. Hier word op analitiese wyse die verskeie aspekte van die saak 

of stelling ondersoek en gestel. 

• Ontleed/analiseer 

Die inhoud word in dele of elemente verdeel en bespreek. Oorsake en gevolge word bepaal 

en onderlinge verwantskappe word vasgestel. 

xiii

ACTION VERBS 

Questions, whether asked in tests or examination papers, always contain certain key words 

or action verbs. Learners must know the meaning of these action verbs and what is 

expected of them when they answer questions. With this in mind, the following short list of 

the most frequently used action verbs in examination papers is given with a short description 

of what is expected of a learner when answering these questions. 

• List / name 

Only the facts are required in a brief and simple format. 

• Describe 

Reproduce the facts on a knowledge level. Characteristics, facts or results must be 

mentioned in logical and well-structured way. No opinion, comment or argument is needed. 

• Define 

Reproduce facts. Give the clear and precise meaning of a concept, very often definitions 

have to be learnt word for word. 

• Give an overview 

Summarise and reproduce a large volume of knowledge in a logical and systematic way 

without compromising the essence of the matter. 

• Explain 

Clarify or give reasons for something, usually in your own words. You must prove that you 

understand the content. It may be useful to use examples, descriptions and illustrations. 

Also supply reasons for statements made as well as results. 

• Proof 

Proof the facts by supplying logical and acceptable facts. 

• Compare 

Point out the similarities (things that are the same) and the differences between objects, 

ideas or points of view. The word “contrast” can also be used. When you compare two or 

more objects, you should do so systematically - completing one aspect at a time. 

• Discuss 

This type of question requires insight and power of judgment when an application or a 

judgement is made. You have to investigate and explore aspects of a matter in an analytical 

way. 

• Analyse 

Identify parts or elements of a concept and describe them one by one. Determine the 

causes and effects as well as the mutual relationships. 

xiii

• Evalueer 

Met evalueer word verwag dat ‘n saak aan die hand van sekere kriteria beoordeel word. ‘n 

Waarde-oordeel word oor die saak uitgespreek en dit moet gemotiveer word. 

Dosente sal waar nodig in die klasse ook verdere toeligting oor hierdie (en ander tersaaklike 

terme) verskaf. Vir u eie doel is dit egter belangrik om vooraf te weet wat van u verwag word 

as so ‘n aksiewerkwoord in ‘n vraestel voorkom. 

WAARSKUWING TEEN PLAGIAAT 

WERKSTUKKE IS INDIVIDUELE TAKE EN NIE GROEPAKTIWITEITE NIE (TENSY DIT 

UITDRUKLIK AANGEDUI WORD AS ‘N GROEPAKTIWITEIT) 

Kopiëring van teks van ander leerders of uit ander bronne (byvoorbeeld die studiegids, 

voorgeskrewe studiemateriaal of direk vanaf die internet) is ontoelaatbaar – net kort 

aanhalings is toelaatbaar en slegs indien dit as sodanig aangedui word. 

U moet bestaande teks herformuleer en u eie woorde gebruik om te verduidelik wat u 

gelees het. Dit is nie aanvaarbaar om bestaande teks/stof/inligting bloot oor te tik en die 

bron in 'n voetnoot te erken nie – u behoort in staat te wees om die idee of begrip/konsep 

weer te gee sonder om die oorspronklike skrywer woordeliks te herhaal. 

Die doel van die opdragte is nie die blote weergee van bestaande materiaal/stof nie, maar 

om vas te stel of u oor die vermoë beskik om bestaande tekste te integreer, om u eie 

interpretasie en/of kritiese beoordeling te formuleer en om 'n kreatiewe oplossing vir 

bestaande probleme te bied. 

Wees gewaarsku: Studente wat gekopieerde teks indien sal 'n nulpunt vir die opdrag 

ontvang en dissiplinêre stappe mag deur die Fakulteit en/of die Universiteit teen 

sodanige studente geneem word. Dit is ook onaanvaarbaar om iemand anders se werk 

vir hulle te doen of iemand anders in staat te stel om u werk te kopieer – moet dus nie 

u werk uitleen of beskikbaar stel aan ander nie! 

xiv

• Evaluate 

A certain matter must be evaluated according to a certain criteria. This means that you 

should indicate whether you agree or disagree about a certain statement or view. You 

should then describe what you agree/disagree about and give reasons for your view. 

Lecturers will give more information on relevant terms during lectures if required. It is to your 

own benefit to know what is required of you when these action verbs appear in a question 

paper. 

WARNING AGAINST PLAGIARISM 

ASSIGNMENTS ARE INDIVIDUAL TASKS AND NOT GROUP ACTIVITIES. (UNLESS 

EXPLICITLY INDICATED AS GROUP ACTIVITIES) 

Copying of text from other learners or from other sources (for instance the study guide, 

prescribed material or directly from the internet) is not allowed – only brief quotations are 

allowed and then only if indicated as such. 

You should reformulate existing text and use your own words to explain what you have read. 

It is not acceptable to retype existing text and just acknowledge the source in a footnote – 

you should be able to relate the idea or concept, without repeating the original author to the 

letter. 

The aim of the assignments is not the reproduction of existing material, but to ascertain 

whether you have the ability to integrate existing texts, add your own interpretation and/or 

critique of the texts and offer a creative solution to existing problems. 

Be warned: students who submit copied text will obtain a mark of zero for the 

assignment and disciplinary steps may be taken by the Faculty and/or University. It is 

also unacceptable to do somebody else’s work, to lend your work to them or to make 

your work available to them to copy – be careful and do not make your work available 

to anyone! 

xiv

1 UITVOERBAARHEIDSTUDI 

UITVOERBAARHEIDSTUDIE UITVOERBAARHEIDSTUDI E EN EN 

EN 

STELSELVOORSTELLE 

STELSELVOORSTELLE 

Bentley & Whitten, Hoofstuk 11 

Jy behoort ongeveer 4 ure te neem om hierdie leereenheid suksesvol deur te werk. 

Lees die gevallestudie op bladsy 414. 

Hierdie leereenheid is op bladsye 414-441 van die handboek gebaseer. Goeie stelselontleders 

bekyk allerlei alternatiewe oplossings vir ‘n stelselprobleem. In hierdie hoofstuk sal 

u leer hoe om hierdie alternatiewe te analiseer en te dokumenteer 

Na afhandeling van hierdie leereenheid moet die leerder in staat wees om : 

• Uitvoerbaarheidskontrolepunte in ’n stelselontwikkelings lewensiklus te kan identifiseer. 

• Alternatiewe stelseloplossings te kan identifiseer. 

• Ses tipes uitvoerbaarheidstoetse te kan beskryf. 

• Verskeie koste-voordele ontledings te kan uitvoer – ook deur toekomstige tyd in 

berekening te bring 

• Te kan beplan vir ‘n formele voorlegging aan die stelsel rolsplelers. 

1

1. FEASIBILITY FEASIBILITY FEASIBILITY ANALYSIS ANALYSIS AND 

AND 

SYSTEM SYSTEM SYSTEM PROPOSAL 

PROPOSAL 

Bentley & Whitten, Chapter 11 

You should spend about 4 hours on mastering this study unit. 

Read the case study on page 414 

This study unit is based on pages 414-441 of the textbook. Good systems analysts 

thoroughly evaluate alternative solutions before proposing change. In this chapter you will 

learn how to analyze and document those alternatives. 

After having completed this study unit the learner must be able to: 

• Identify feasibility checkpoints in the systems life cycle. 

• Identify alternative system solutions. 

• Define and describe six types of feasibility and their respective criteria. 

• Perform various cost-benefit analyses using time-adjusted costs and benefits 

• Plan for a formal presentation to system owners and users. 

1

Wanneer verskeie moontlike oplossings voorgestel word vir ‘n stelselprobleem, moet daar op 

‘n grondige wyse besluit word watter een om te kies. 

Hierdie leereenheid gee ‘n kykie na die uitvoerbaarheidsontleding waarin elke moontlike 

stelselkandidaat opgeweeg word teen die ander op grond van tegniese, bedryfs, ekonomiese 

en skedule en ander faktore. 

Koste en voordele word in berekening gebring (bl 419-414). ‘n Kandidaatsmatriks word 

gebruik en ‘n geweegde metode van vergelyking tussen die kandidate se uitvoerbaarheid 

word aangewend. Sien fig 11-6. 

‘n Verslag en mondelinge voorlegging volg hierop om alle aandeelhouers op hoogte te hou. 

Doen die volgende oefeninge nadat hierdie hoofstuk bestudeer is: 

• Problems and exercises: no 2,3,4,7. bl 438 

• Projects and research: no 1. bl 439 

• Minicases: no 1. bl 441 

Lees die opsomming deur op bl 437. 

Gaan terug na die leeruitkomste en stel vas of al die uitkomste bereik is. Dui ook aan wat 

jou geskatte vlak van bemeestering (in persentasie uitgedruk) is. 

Klastoets op datum soos aangedui. 

PROJEK 

Vir u jaarprojek kan ‘n kandidaatsmatriks opgestel word en uitvoerbaarheids-ontledings 

gedoen word. 

2

When several possible solutions are proposed to solve a system problem, the best solution 

must be identified in a substantiated way. 

This study unit looks at feasibility analysis where all the possible candidate solutions are 

evaluated and compared with regard to technical, operational, economical, scheduling and 

other factors. 

Costs and benefits are taken into account (p 419-414). A candidate matrix is used and a 

measured method of comparing the feasibility of the candidate solutions is applied. See fig 

11-6. 

A report as well as an oral presentation follows to keep the system owners updated. 

Do the following exercises after studying this chapter: 

• Problems and exercises: no 2,3,4,7. page 438 

• Projects and research: no 1. page 439 

Read the Chapter review on page 437 

Read the learning outcomes again and make sure that you have reached them. On what 

level of achievement do you think you are now (indicated as a percentage)? 

Class test on the date indicated by the lecturer. 

PROJECT 

Compile a candidate matrix and do a feasibility analysis on your project. 

2

2 STELSELONTWERP 

STELSELONTWERP 



Lees die gevallestudie op bladsy 446 

Hierdie leereenheid is op bladsye 446-472 van die handboek gebaseer. 

Hierdie hoofstuk handel oor die ontwerp fases betrokke by die FAST stelsel ontwikkelings 

metodologie. 


• Die ontwerp fases te beskryf i.t.v. die inligtingstelsel boublokke. 

• Te onderskei tussen verskeie stelsel ontwerp strategieë. 

• Die take wat voorkom in die ontwerp fases te beskryf i.t.v. rekenaargebaseerde 

oplossings vir plaaslike ontwikkelings projekte. 

• Die ontwerp fases te beskryf i.t.v. rekenaargebaseerde oplossings waarby van 

kommersiële sagteware-oplossings gebruik gemaak word. 

3

2. SYSTEMS SYSTEMS DESIGN 

DESIGN 




This study unit is based on pages 446-472 of the textbook. 

This chapter deals with the design phases involved in the FAST systems development 

methodology. 


• The design phase in terms of your information building blocks. 

• Differentiate between several systems design strategies. 

• Describe the design phase tasks in terms of a computer-based solution for an in-house 

development project. 

• Describe the design phase in terms of a computer-based solution involving procurement 

of a commercial systems software solution. 

3

‘n Oorsig word gegee van stelselontwerp met verwysing na verskillende benaderings wat 

gevolg kan word, bl 446-453 

Stelselontwerp vir plaaslike ontwikkelingsprojekte sowel as projekte waar daar gebruik 

gemaak word van kommersiele pakkette work bespreek op bl 453-467. 





• Doen ‘n Internet soektog oor stelselontwikkelingsmetodologieë. Gee ‘n 3 bladsy 

beskrywing en opsomming in oor so 2- 3 nuwer/moderner benaderings tot 

stelselontwikkeling. Gee ook u oorspronklike artikels hiermee saam in. 





4

An overview of systems development is provided with reference to the different approaches 

that can be followed, p. 446-453. 

Systems development for local development projects as well as projects where commercial 

applications are used are discussed on p. 453-467. 


• Problems and exercises: no 2,3,4,10. p 469 

• Projects and research: no 1. p 470 

• Minicases: no 1. p 471 

• Search the Internet for system development methodologies. Write a 3 page report / 

summary on 2 – 3 newer or more modern approaches to system development. Hand in 

the articles that you have used as well. 

Read the chapter review on page 468. 

Go back to the learning outcomes and determine whether those outcomes have been 

attained. Also indicate your estimated level of mastery (as a percentage). 


4

PROJEK 

Aangesien hierdie hoofstuk slegs ‘n oorsig gee oor die tegnieke wat gebruik word tydens die 

ontwerpsfase van die stelselontwikkelingslewensiklus, sal ontwerpsprobleme wat voortspruit 

uit die aanvanklike stelselontledingfase (met verwysing na die ontledingsdokument wat aan 

die einde van die kursuseenheid ITRW 213 ingehandig is) aangespreek word. 

Na afhandeling van hierdie leereenheid moet die volgende uitsette t.o.v. die 

projek gelewer word: 

• Die logiese data modelle. 

• Die logiese proses modelle. 

• Die prototipes. 

5

PROJECT 

This chapter gives an overview of all the techniques used during the design phase of a 

system development cycle. Problems in the design that arised from the original system 

development phases ( with reference to the documentation handed in at the end of the ITRW 

213 course) can be addressed at this stage. 

After completion of this study unit, the following must be compiled correctly 

and handed in with regard to your project: 

• The logical data models. 

• The logical process models. 

• The prototypes. 

5

6 

3 TOEPASSINGSARGITEKTU 

TOEPASSINGSARGITEKTUUR 

TOEPASSINGSARGITEKTU UR 

EN EN MODELLERING 

MODELLERING 




Hierdie leereenheid is op bladsye 476-515 van die handboek gebaseer. 

Hierdie hoofstuk handel oor die ontwerp van die inligtingstelsel toepassingsargitektuur met 

die klem op fisiese proses modelle. Die toepassingsargitektuur en fisiese proses modelle 

behels o.a. tegnieke vir data verspreiding, prosesse, en koppelvlakke tussen netwerk 

bestemmings in ‘n verdeeldeverwerkings-omgewing. 


• Die inligtingstelsargitektuur te defineer i.t.v. data, prosesse, en kommunikasie. 

• Te onderskei tussen logiese en fisiese datavloeidiagramme, en te beskryf hoe die 

fisiese datavloeidiagram gebruik word om die inligtingstelsel se argitektuur te 

modelleer.

6 

3. APPLICATION APPLICATION ARCHITEC 

ARCHITECTURE 

ARCHITEC 

ARCHITECTURE 

TURE 

AND AND MODELLING 

MODELLING 




This study unit is based on pages 476-515 of the textbook. 

This chapter deals with the design of the information system application architecture with 

emphasis on physical process models. The application architecture and physical process 

models entail, inter alia, techniques for data distribution, processes, and interfaces between 

network destinations in a distributed processing environment. 


• Define an information system’s architecture in terms of knowledge, processes, and 

communications. 

• Differentiate between logical and physical data flow diagrams and explain how physical 

data flow diagrams are used to model an information system’s architecture.

• Beide gesentraliseerde en verspreide verwerkings alternatiewes vir inligtingstelselontwerp 

te beskryf. Dit moet insluit verskeie ‘client/server’ en internet gebaseerde 

opsies. 

• Alternatiewe stelselontwerp opsies te beskryf t.o.v. data verspreiding en databasisse, 

gebruiker –en stelselkoppelvlakke, en sagteware-ontwikkelings omgewings. 

• Strategieë vir die bepaling van ‘n inligtingstel se argitektuur te beskryf. 

• Fisiese datavloeidiagramme te teken vir die voorstelling van ‘n inligtingstelsel se 

argitektuur en prosesse. 

Bl 476-483 gee ‘n oorsig van wat toepassingsargitektuur behels en daar word gekyk na die 

komponente waaruit ‘n fisiese datavloeidiagram bestaan. Hierdie komponente verteenwoordig 

fisiese entiteite soos bv. ‘n drukker vir die uitvoer van data, ‘n databasis op ‘n 

bediener rekenaar, of selfs ‘n persoon wat inligting moet invoer ens. Die gedeelte wat 

voorkom in Bl 483-502 behandel konsepte soos bv verspreideverwerking en hoe dit 

voorgestel kan word deur fisiese datavloeidiagramme. Strategieë vir die ontwikkeling van 

datavloeidiagramme word behandel op bl.502-511. 


• Problems and exercises: no 3,5,9,11. bl 512. 

• Projects and research: no 2,5. bl 513 






7

• Describe both centralized and distributed computing alternatives for information system 

design, including various client/server and Internet-based computing options 

• Describe an alternative information system design for database and data distribution, 

user and system interface, and software development environments. 

• Describe strategies for developing or determining the architecture of an information 

system. 

• Draw physical data flow diagrams for an information system’s architecture and 

processes. 

Pages 476-483 provide an overview of application architecture and show the components of 

a data flow diagram. These components represent physical entities such as, for example, 

the printer for the export of data, a database on a server computer, or even a person who 

must capture information, etc. In the next section, pages 483-502, concepts such as 

distributed processing and how this can be presented by means of physical data flow 

diagrams are addressed. Strategies for the development of data flow diagrams are 

addressed on p. 502-511. 


• Problems and exercises: no 3,5,9,11. p 512. 

• Projects and research: no 2,5. p 513 






7

PROJEK 



• Die fisiese proses model. 

• Die fisiese data model. 

• Die netwerk argitektuur datavloeidiagram 

8

PROJECT 

After completion of this study unit, the following must be compiled correctly 

and handed in with regard to your project: 

• The physical process model. 

• The physical data model. 

• The network architecture DFD 

8

4 DATABASISONTWERP 

DATABASISONTWERP 




Hierdie leereenheid is op bladsye 518-547 van die handboek gebaseer en handel oor 

databasisontwerp. ‘n Databasis is ‘n versameling van interafhanklike lêers wat gebruik word 

vir die effektiewe stoor en bestuur van ‘n inligtingstelsel se data. 


• Te onderskei tussen konvensionele lêerstelsels en moderne, relasionele databasisse. 

• Definisies en voorbeelde te kan gee van velde, rekords, leêrs en databasisse. 

• ‘n Moderne data argitektuur te beskryf wat sal insluit leêrs, operationele databasisse, 

datapakhuise, persoonlike databasisse en databasisse vir werkgroepe. 

• Te onderskei tussen die rolle van stelselontleders, data administrateurs, en databasisadministrateurs. 

• Die argitektuur van ‘n databasisbestuurstelsel te beskryf. 

9

4. DATABASE DATABASE DESIGN 

DESIGN 




This study unit is based on pages 518-547 of the textbook and deals with database design. 

A database is a collection of interdependent files used for the effective storage and 

management of an information system’s data. 


• Distinguish between conventional file systems and modern, relational databases 

• Describe the use of fields, records, files and databases. 

• Describe modern data-architecture which includes files, operational databases, data 

warehouses, personal databases and databases for work groups. 

• Distinguish between the roles of the system analysts, data administrators, and 

database administrators. 

• Describe the architecture of a database management system. 

9

• Te beskryf hoe entiteite, attribute, en verwantskappe wat gevind word in ‘n logiese data 

model ge-implementeer word in ‘n relasionele databasis. 

• ‘n Logiese data model te transformeer na ‘n fisiese, relasionele databasis skema. 

• SQL te gebruik om ‘n databasis struktuur te genereer. 

‘n Inleiding tot databasisse volg op bl.518-520. Databasis konsepte wat van belang is vir die 

stelselontleder vir die ontwerp van ‘n databasis word behandel op bl.520-528. Die ontwerp 

en bestuur van moderne relasionele databasisse word behandel op bl 528-541. 


• Problems and exercises: no 1,3,6,9,11. bl 544 


• 

Verdere oefeninge: 

• Besoek die volgende webwerf om meer van SQL te leer. U moet instaat wees om 

eenvoudige SQL navrae te kan saamstel. 

10 

http://www.profsr.com/sql/sqlintro.htm 

Doen ten minste die aanlyn lesse 1 tot 3 om te leer hoe om basiese databasis ontwerp 

te doen, SQL navrae te doen en Access daarvoor te kan gebruik. U moet die Select, 

Insert, Update en Delete met verdere opsies kan gebruik (bv. Where). 

• Doen ‘n Access opdrag soos deur u dosent aan u verskaf, stel tabelle saam, stel 

verwantskappe en stel verskeie queries (navrae) saam. Kyk ook hoe die SQL stellings 

lyk wat gegeneer is. 

Gebruik hierdie moontlikhede ook in u jaarprojek. 



jou geskatte vlak van bemeestering (in persentasie uitgedruk) is.

• Describe how entities, attributes and relationships found in a logical data model are 

implemented in a relational database. 

• Transform a logical data model to a physical, relational database scheme. 

• Use SQL to generate a database structure. 

Pages 518-520 provide an introduction tot databases. Concepts pertaining to databases that 

are important to the system analyst for the design of a database are dealt with on p. 520-528. 

The design and management of modern relational databases are discussed on p. 528-541. 


• Problems and exercises: no 1,3,6,9,11. p 544 


Further exercises: 

• Use the following website to learn more about SQL. You must be able to do simple SQL 

queries. http://www.profsr.com/sql/sqlintro.htm 

10 

Do the online lessons – at least 1 to 3 to see how to design databases, structure SQL 

queries and use Access to do it. You must be able to do Select, Insert, Update en Delete 

with further options (eg Where). 

• Do the Access exercise that your lecturer presents to you. Design the tables, 

relationships and structure the queries. Take a look at the SQL statements that are 

generated. 

Use these possibilities in your year project. 




Class test on the date indicated by the lecturer.


PROJEK 



• Die skep van ‘n databasis skema volgens die data model. 

• Die konstruksie van ‘n databasis volgens die databasis skema. 

11

PROJECT 

After completion of this study unit, the following outputs must be delivered 

with regard to your project: 

• The database schema according to the data model. 

• The construction of the database according to the database schema. 

11

12 

5 AFVOERONTWERP AFVOERONTWERP EN 

EN 

PROTOTIPERING 

PROTOTIPERING 




Hierdie leereenheid is op bladsye 550-579 die handboek gebaseer en handel oor die 

ontwerp van inligtingstelsel uitvoer. 


• Tussen interne, eksterne en terugkeer dokumente te onderskei. 

• Tussen detail, opsommings en uitsonderingsverslae te onderskei. 

• Verskeie uitvoer implementeringsmetodes te ken. 

• Tussen tabelvorm, sones, grafiese en beskrywende formate van inligtingvoorstellings 

te onderskei. 

• Tussen area, balk, kolom, sektor, lyn, radar en stippelgrafieke te onderskei en weet wat 

elkeen se gebruik is. 

• Algemene riglyne te gee vir goeie uitvoer ontwerp en te kan toepas.

12 

5. OUTPUT OUTPUT DESIGN DESIGN AND 

AND 

PROTOTYPING 

PROTOTYPING 




This study unit is based on pages 550-579 of the textbook and deals with the design of 

information system outputs 

After having completed this study unit the learner will be able to: 

• Distinguish between internal, external, and turnaround outputs. 

• Differentiate between detailed, summary and exception reports. 

• Identify several output implementation methods. 

• Differentiate among tabular, zoned, and graphic formats for presenting information. 

• Distinguish among area, bar, column, pie, line, radar and scatter charts and their uses. 

• Describe and apply several general principles that are important to output design.

• Uitvoere m.b.v. prototipering te definieer en rekenaaruitvoere te ontwerp. 

‘n Oorsig van verskillende tipes inligtingstelseluitvoere word weergegee op bl. 550-558. Die 

ontwerp van uitvoere deur die gebruik van prototipes word behandel op bl 558-573. 









PROJEK 



• ‘n Werkende weergawe van al die uitvoerskerms. 

• Program kodes wat data verkry uit die databasis, die nodige verwerkings doen en die 

resultate deurgee na die uitvoerskerms. 

13

• Define outputs by means of prototyping and design computer outputs. 

An overview of different types of output of an information system is given on pages 550-558. 

How to design and prototype outputs is discussed on pages 558 – 573. 

Do the following exercises after studying this chapter : 








PROJECT 



• A working version of the output screens of the project. 

• Programming code to extract data from the database, do the necessary calculations 

and produce the required results on the outputs screens. 

13

14 

6 INVOERONTWERP INVOERONTWERP EN 

EN 

PROTOTIPERING 

PROTOTIPERING 




Hierdie leereenheid is op bladsye 582-611 van die handboek gebaseer en handel oor die 

ontwerp van inligtingstelsel invoer. 


• Gepaste formaat en media te definieer vir rekenaar invoer. 

• Die verskil tussen datavaslegging, data-invoeging en data-invoer te verduidelik. 

• Verskillende outomatiese data versamelingstegnologieë te beskryf. 

• Menslike faktore in ag te neem wanneer invoer ontwerp word. 

• Interne kontroles te ontwerp vir invoer. 

• Gepaste skermkontroles te kies vir die grafiese gebruikerskoppelvlak. 

• ‘n Webgebasseerde invoerkoppelvlak te ontwerp.

14 

6. INPUT INPUT DESIGN DESIGN AND AND 

AND 

PROTOTYPING 

PROTOTYPING 




This study unit is based on pages 582-611 of the text book and deals with the design of 

information system inputs. 


• Define the appropriate format and media for a computer input. 

• Explain the difference between data capture, data entry, and data input. 

• Identify and describe several automatic data collection technologies. 

• Apply human factors to the design of computer inputs. 

• Design internal controls for computer inputs. 

• Select proper screen-based controls for input attributes that are to appear on a GUI input 

screen.

‘n Oorsig van verskillende tipes inligtingstelselinvoere word weergegee op bl. 582-598. Die 

ontwerp van invoere deur die gebruik van prototipes word behandel op bl 598-606. 









PROJEK 



• ‘n Werkende weergawe van al die invoerskerms. 

• Program kodes wat data verkry vanaf die invoerskerms, dit verifieer/verwerk, en dit 

stoor in die databasis. 

15

• Design a web-based input interface. 

An overview of different types of inputs of an information system is given on pages 582-598. 

How to design and prototype inputs is discussed on pages 598 – 606. 








Class test on the date indicated by the lecturer 

PROJECT 



• A working version of the input screens of the project. 

• Programming code to extract data from the input screens, verify/ process the input and 

save it to a database 

15

16 

7 GEBRUIKERSKOPPELVLAK 

GEBRUIKERSKOPPELVLAK- 

GEBRUIKERSKOPPELVLAK 

ONTWERP 

ONTWERP 





ontwerp van die gebruikerskoppelvlak. Die gebruikerskoppelvlak defineer die interaksie 

tussen die gebruiker en die inligtingstelsel. 


• Te onderskei tussen verskillende tipes rekenaargebruikers en ontwerp-oorwegings vir 

elk. 

• Verskeie menslike faktore in ag te neem en te inkorporeer wanneer 'n gebruikerskoppelvlak 

ontwerp word. 

• Uitvoer- en invoerontwerp te integreer in ‘n oorkoepelende gebruikerskoppelvlak om 

dialoog tussen mens en masjien te bewerkstellig.

16 

7. USER USER INTERFACE INTERFACE DESIG DESIGN DESIG N 




This study unit is based on pages 614-645 of the textbook and deals with the design of user 

interfaces. The user interface defines the interaction between the user and the information 

system. 


• Distinguish between different types of computer users and design considerations for 

each. 

• Identify several important human engineering factors and guidelines and incorporate 

them into a design of a user interface. 

• Integrate output and input design into an overall user interface that establishes the 

dialogue between users and computer.

• Die rol van bedryfstelsels, webblaaiers en ander tegnologieë vir gebruikerskoppelvlak 

ontwerp. 

• Gepaste gebruikerskoppelvlak strategieë toe te pas vir 'n inligtingstelsel. U moet 'n 

toestandsoorgangsdiagram kan gebruik vir die beplanning van die gebruikerskoppelvlak 

van 'n inligtingstelsel. 

• Gepaste skermkontroles te kies vir die grafiese gebruikerskoppelvlak. 

• Te beskryf hoe prototipering gebruik kan word om 'n gebruikerskoppelvlak te ontwerp. 

‘n Inleiding tot gebruikerskoppelvlakke, verskillende tipe rekenaar gebruikers, en menslike 

faktore wat inaggeneem moet word met die ontwerp van ‘n gebruikerskoppelvlak word 

behandel op bl.614-617. Tegnologiese oorwegings by gebruikerskoppelvlakontwerp asook 

verskillende gebruikerskoppelvlakstyle word behandel op bl. 617-633. Die ontwerp en 

prototipering van gebruikerskoppelvlakke word behandel op bl.633-639. 




• Minicases: no 1,2. bl 644 





PROJEK 



• Gewysigde invoer- en uitvoerskerms wat ontwerp is volgens Microsoft standaarde. 

• Gewysigde invoer- en uitvoerskerms wat prosesvloei vergemaklik. 

17

• Understand the role of operating systems, web browsers, and other technologies for user 

interface design. 

• Apply appropriate user interface strategies to an information system. Use a state 

transition diagram to plan and coordinate a user interface for an information system. 

• Describe how prototyping can be used to design a user interface. 

Pages 614-617 provide an introduction to user interfaces, different types of computer users, 

and human factors that must be taken into account with the design of a user interface. 

Technological considerations taken into account when designing a user interface as well as 

different user interface styles are dealt with on p. 617-633. The design and prototyping of 

user interfaces are found on p. 633 - 639. 




• Minicases: no 1,2. p 644 





PROJECT 



• Revised input and output screens designed according tot Microsoft standards. 

17

• Gewysigde invoer- en uitvoerskerms met foutkontrole op alle invoer- en instruksievelde. 

18

• Revised input and output screens to enhance the flow of the processes. 

• Revised input and output screens with error controls on all the input and output fields. 

18

8 STELSELKONSTRUKSIE STELSELKONSTRUKSIE EEN 

E EN 

N 

IMPLEMENTERING 

IMPLEMENTERING 





benadering wat gevolg word vir die konstruksie en implementering van die finale 

inligtingstelsel. 


• Die doel van konstruksie en implementeringsfases te verduidelik en te beskryf - asook 

die fases in terme van die inligtingsboublokke te beskryf. 

• Hierdie fase in terme van hooftake, rolle, invoere en uitvoere te bespreek. 

• Verskeie toepassingsprogramme en stelseltoetse te identifiseer. 

• Stelselomskakelingstrategieë te beskryf. 

19

8. SYSTEMS SYSTEMS CONSTRUCTION 

CONSTRUCTION 

AND AND IMPLEMENTATION 

IMPLEMENTATION 




This study unit is based on pages 684 – 698 of the textbook and deals with the approach to 

be followed for the construction and implementation of the final information system. 


• Explain the purpose of the construction and implementation phases of the systems life 

cycle. 

• Describe the systems construction and implementation phases in terms of major tasks, 

roles, inputs, and outputs. 

• Explain several application program and system tests. 

• Identify several system conversion strategies. 

19

Die konstruksiefase van die inligtinstelsel word uiteengesit op bl.684-689 en die 

implementeringsfase van die inligtingstelsel op bl.689-694. 


• Problems and exercises: no 3,5,9. bl 696 

• Projects and research: no 2,3,4. bl 697 






PROJEK 

Aangesien die projek teen hierdie stadium in ‘n gevorderde fase van ontwikkeling is, sal 

meeste van die moduletyd spandeer word op toetsing van die stelsel. 



• Volledige toetsing van die stelsel. 

• ‘n Toetsdokument wat aandui watter data gebruik is as toetsgevalle, en wat die 

uitkomste was van die toetsing. 

20

The construction phase of the information system is explained on p. 684-689 and the 

implementation phase of the information system on p. 689-694. 


• Problems and exercises: no 3,5,9. p 696 







PROJECT 

Since your project is now in an advanced stage of development, most of the module time will 

be spend on testing the system. 



• Completely tested system. 

• A test document indicating the data that was used for each testing case that was done 

as well as the results of all the tests. 

20

9 STELSELBEDRYF STELSELBEDRYF EN 

EN 

ONDERSTEUNING 

ONDERSTEUNING 

ONDERSTEUNING 




Hierdie leereenheid is op bladsye 702-719 van die handboek gebaseer. Stelselbedryf en 

ondersteuning is ‘n deurlopende aktiwiteit wat plaasvind na voltooing en implementering van 

die inligtingstelsel. 


• Stelselbedryf en -ondersteuning te beskryf. 

• Die rol van 'n 'repository', programbiblioteek en databasis in stelselbedryf en - 

ondersteuning te bespreek. 

• Tussen onderhoud, herstel, tegniese ondersteuning en vernuwing te kan onderskei as 

ondersteuningsaktiwiteite. 

• Take wat met foutherstel te make het tydens instandhouding te beskryf. 

21

9. SYSTEM SYSTEM SYSTEM OPERATIONS OPERATIONS AN AND AN 

SUPPORT 

SUPPORT 




This Study Unit is based on pages 702 – 719 of the textbook. Systems operation and 

support constitute an ongoing activity that continues after completion and implementation of 

the information system. 


• Define systems operations and support. 

• Describe the relative roles of a repository, program library, and database in systems 

operations and support. 

• Differentiate between maintenance, recovery, technical support, and enhancement as 

system support activities. 

• Describe the tasks required to maintain programs in response to bugs. 

• Describe the role of benchmarking in system maintenance. 

21

• Die rol van die normtoetse tydens stelselonderhoud te beskryf. 

• Die rol van die stelselontleder tydens stelselherstel te beskryf. 

• Die vorme van tegniese ondersteuning deur die stelselontleder aan die gebruikers te 

beskryf. 

• Die take te beskryf wat deel vorm van stelselverbetering sowel as die verwantskap 

tussen die verbeterde en die oorspronklike ontwikkellingsproses. 

• Die rol van stelselverbetering en heringenieurswese te beskryf. 

‘n Oorsig van stelselbedryf en ondersteuning word weergegee op bl. 702-705. Die redes vir 

stelselondersteuning asook die take verwant aan stelselondersteuning word behandel op 

bl.705-710. Die redes vir stelselverbeterings asook die take verwant aan stelselverbetering 

word behandel op bl.710-714. 


• Problems and exercises: no 1,3,5. bl 716 







22

• Describe the system analyst’s role in system recovery. 

• Describe forms of technical support provided by a systems analyst for the user 

community. 

• Describe the tasks that should be and may be performed in system enhancement and the 

relationship between the enhancement and the original systems development process. 

• Describe the role of reengineering in system enhancement. Describe three types of 

reengineering. 

Pages 702-705 provide an overview of systems operation and support. The reasons for 

systems support as well as the tasks related to systems support are dealt with on p. 705-710. 

The reasons for system enhancements as well as the tasks related to system improvement 

are discussed on p. 710-714. 


• Problems and exercises: no 1,3,5. p 716 







22

PROJEK 



• ‘n Gebruikershandleiding wat die gebruik van die stelsel beskryf. Gebruik reeds 

geskryfte handleidings as voorbeeld. ‘n Kort gids is ook handig, bv. ‘quick start’. 

• Interaktiewe hulpmiddels wat gebruik van die gebruikerskoppelvlak vergemaklik. 

23

PROJECT 



• A user manual giving a description of how to use the system. Use existing manuals as 

examples when you compile your manual. A quick start description can be handy as 

well. 

• Interactive help can be added to make the user interface easier to use. 

23

24 

10 10 OBJEK OBJEK-GEORIENTEERDE 

OBJEK GEORIENTEERDE 

GEORIENTEERDE 

ONTWERP ONTWERP EN EN EN MODELLERI 

MODELLERING 

MODELLERI 

MODELLERI NG 



Hierdie leereenheid is op bladsye 648-679 van die handboek gebaseer. Hierdie leereenheid 

is die tweede van twee leereenhede oor objek georienteerde hulpmiddels en tegnieke. 

Hierdie module fokus op objekmodellering tydens die stelselontwerpfase. 


• Tussen entiteite, koppelvlak en kontrole objekte te kan onderskei. 

• Die konsept van ‘n afhanklikheidsverwantskap kan verduidelik, asook die omstandighede 

kan beskryf waar dit van toepassing is. 

• Die konsep van navigeerbaarheid kan verduidelik en waarom dit gebruik word. 

• Die drie vlakke van sigbaarheid te verduidelik. 

• Die verskil aan te toon tussen gedrag van ‘n objek en ‘n metode van ‘n objek. 

• Die basiese konsep van objek verantwoordelikheid te verstaan en te weet wat die 

verband is met boodskap versending tussen objektipes. 

• Die belangrikheid van objekhergebruik tydens stelselontwerp te verduidelik. 

• Die verskil aan te toon tussen ontwerpspatrone, objek raamwerke en komponente. 

• Die aktiwiteite te bespreek wanneer objekontwerp voltooi word.

24 

10. 10. OBJECT OBJECT-ORIENTED OBJECT OBJECT ORIENTED DESIGN DESIGN 

DESIGN 

AND AND MODELING 

MODELING 

MODELING 



This study unit is based on pages 647-679 of the textbook. This study unit is the second of 

two study units concerning object-oriented tools and techniques. This study unit focuses 

specifically o tools and techniques that are used during system design. 


• Differentiate between entity, interface, and control objects. 

• Understand the concept of a dependency relationship and the circumstances under 

which it is used. 

• Describe association navigability and explain why it is used. 

• Define visibility and explain its three levels. 

• Explain the difference between a behavior and a method 

• Understand the basic concept of object responsibility and how it is related to message 

sending between object types. 

• Explain the importance of object reuse during systems design. 

• Differentiate between design patterns, object frameworks, and components. 

• Describe three activities involved in completing object design.

• Die verskil aan te toon tussen ontwerps beskrywing m.b.v. ‘n ‘use case’ en ontledings 

beskrywing m.b.v. ‘n ‘use case’. 

• Objek robuustheidsdiagram te konstrueer. 

• 'n Ideale objekmodel 'CRC' kaart en sekwensie diagram te konstrueer. 

• 'n Klas diagram te konstrueer wat die ontwerpspesifikasies aandui. 

• Aktiwiteits- en implementeringsdiagramme te identifiseer. 

‘n Inleiding tot objek-georienteerde ontwerp word weergegee op bl. 648-655. Hier word veral 

gekyk na die voorstelling van data as objekte en watter eienskappe hierdie objekte bevat. Op 

bl.656-666 word gekyk na die stappe wat gevolg moet word tydens objek-georienteerde 

ontwerp. Die gebruik van ‘UML’ diagramme vir die dokumentering van ‘n objek-georienteerde 

ontwerp word verduidelik op bl.666-674 








25

• Differentiate between a design use-case narrative and an analysis use-case narrative. 

• Construct an object robustness diagram. 

• Describe CRC card modelling. 

• Construct state chart and sequence diagrams. 

• Construct a class diagram that reflects design specifics. 

• Construct component and deployment diagrams. 

Pages 648-655 provide an introduction to object orientated design. This section particularly 

looks at the presentation of data as objects and which characteristics these objects display. 

Pages 655-666 indicates the steps to be followed during object orientated design. The use 

of UML diagrams for the documentation of object orientated design is explained on p. 666- 

674. 




Read the chapter review on page 674 




25

PROJEK 



• Indien u objekgerig werk in u jaarprojek kan u van bogenoemde modellering en 

dokumentering gebruik maak. 

26

PROJECT 



• If you are using the Object oriented approach, you can use the above to model and 

document the system. 

26

AFDELING 4 

VOORBEELD VRAESTEL 

Vraag 1 / Question 1 

Voorbeeld vraestel 

1. Hoe verskil die take van ‘n data-administrateur, databasis-administrateur en 

stelselontleder 

How do the tasks of a data administrator, database administrator and system analyst 

differ? (6) 

2. Skets die fisiese datamodel van u jaarprojek. 

Sketch the physical datamodel of your year project. (10) 

3. Normaliseer die volgende afhanklikheidsdiagram tot op 3NF. Verduidelik die stappe 

wat u volg. 

Normalize the following dependency diagram to 3NF. Explain the steps that you follow. 

Underline: keyfield Onderstreep: sleutelveld 

Arrows: dependencies Pyltjies: afhanklikhede 

Brackets: repetition Hakies: herhalende groep 

Vraag 2 Question 2 

Gee riglyne oor hoe rekenaaruitvoere meer leesbaar gemaak kan word. Gee enige 

uitvoerontwerp van u projek om die riglyne ook toe te pas (in ‘n skets). 

Give guidelines which may enhance readability of computer outputs. Apply these guidelines 

to any output from your project last year (make a sketch). (15) 

(10) 

27

SECTION 4 

EXAMPLE EXAMINATION PAPER 


Example examination paper 

1. Hoe verskil die take van ‘n data-administrateur, databasis-administrateur en 

stelselontleder 

How do the tasks of a data administrator, database administrator and system analyst 

differ? (6) 

2. Skets die fisiese datamodel van u jaarprojek. 

Sketch the physical datamodel of your year project.. (10) 

3. Normaliseer die volgende afhanklikheidsdiagram tot op 3NF. Verduidelik die stappe 

wat u volg. 

Normalize the following dependency diagram to 3NF. Explain the steps that you follow. 

Underline: keyfield Onderstreep: sleutelveld 

Arrows: dependencies Pyltjies: afhanklikhede 

Brackets: repetition Hakies: herhalende groep 


Gee riglyne oor hoe rekenaaruitvoere meer leesbaar gemaak kan word. Gee enige 

uitvoerontwerp van u projek om die riglyne ook toe te pas (in ‘n skets). 

Give guidelines which may enhance readability of computer outputs. Apply these guidelines 

to any output from your project last year (make a sketch). (15) 

(10) 

27

Voorbeeld vraestel 


Beskryf die proses hoe ‘n stelsel se invoer ontwerp kan word. Gee voorbeelde waar gepas. 

Describe the input design process. Give examples where applicable. (10) 


Wanneer u ‘n gebruikerskoppelvlak ontwerp moet u ‘n sekere mens-faktore (human 

engineering factors) in ag neem en inkorporeer in u ontwerp. Gee ‘n kortlikse oorsig oor die 

faktore. 

When designing the user interface, you should incorporate important human engineering 

factors. Give a brief overview of these factors. (10) 


1. Beskryf 3 vlakke van toetsing tydens stelselkonstruksie. 

28 

Desribe 3 levels of testing when a system is constructed. (6) 

2. Maak ‘n skets om die stelsel implementeringstake aan te toon. 

Make a sketch to show the system implementation tasks. (8) 


1. Bespreek die tipiese take wanneer ‘n program of stelsel instand gehou moet word. 

Describe the typical system maintenance tasks. (12) 

2. Wat is programmatuurmetrieke en gee voorbeelde. 

What is software metrics and give examples. (5) 


Definieer of omskryf die volgende terme: 

Define or describe each of the following terms: 

7.1 Objek / Object 

7.2 Enkapsulasie / Encapsulation 

7.3 Oorerwing / Inheritance 

7.4 ‘Use case’ diagramme / Use case diagrams 

7.5 Polimorfisme / Polymorphism 

7.6 Komponent / Component 

7.7 Aktiwiteitsdiagram / Activity diagram 

7.8 Kontrole objek / Control object (8)

Example examination paper 


Beskryf die proses hoe ‘n stelsel se invoer ontwerp kan word. Gee voorbeelde waar gepas. 

Describe the input design process. Give examples where applicable. (10) 


Wanneer u ‘n gebruikerskoppelvlak ontwerp moet u ‘n sekere mens-faktore (human 

engineering factors) in ag neem en inkorporeer in u ontwerp. Gee ‘n kortlikse oorsig oor die 

faktore. 

When designing the user interface, you should incorporate important human engineering 

factors. Give a brief overview of these factors. (10) 


1. Beskryf 3 vlakke van toetsing tydens stelselkonstruksie. 

28 

Describe 3 levels of testing when a system is constructed. (6) 

2. Maak ‘n skets om die stelsel implementeringstake aan te toon. 

Make a sketch to show the system implementation tasks. (8) 


1. Bespreek die tipiese take wanneer ‘n program of stelsel instand gehou moet word. 

Describe the typical system maintenance tasks. (12) 

2. Wat is programmatuurmetrieke en gee voorbeelde. 

What is software metrics and give examples. (5) 


Definieer of omskryf die volgende terme: 

Define or describe each of the following terms: 

7.1 Objek / Object 

7.2 Enkapsulasie / Encapsulation 

7.3 Oorerwing / Inheritance 

7.4 ‘Use case’ diagramme / Use case diagrams 

7.5 Polimorfisme / Polymorphism 

7.6 Komponent / Component 

7.7 Aktiwiteitsdiagram / Activity diagram 

7.8 Kontrole objek / Control object (8)

AFDELING 5 

PROJEK 

Projek 

1. Algemeen 

As deel van u prakties van ITRW213, het u begin met ‘n projek wat ‘n gerekenariseerde 

stelsel se beplanning en ontwerp behels het. U voltooi hierdie semester die fisiese ontwerp, 

ontwikkeling en implementering daarvan. Verslae en ander dokumentasie moet m.b.v. 'n 

woordverwerker gedoen word. 

2. Wat word van u verwag? 

U voltooi wat u mee begin het in die eerste semester in ITRW213. Die voorgeskrewe 

handboek gee u teoretiese riglyne. 

So bv word in hfst 9,13 verwys na prosesmodelle. 

Hfst 11 wys hoe koste voordele ontleding gedoen kan word en uitvoerbaarheidsmatrikse op 

te stel op kandidaatstelsels teen mekaar op te weeg. U sal ook van hierdie tegnieke gebruik 

maak vir u projek. 

Hfst 12 verwys na verskillende ontwerpmetodes en gee ‘n kykie na proses en datamodelle 

asook prototipes. U moet dit ook doen vir u projek. 

Hfst 13 wys hoe logiese modelle omgeskakel kan word na fisiese modelle – prosesmodel, 

datamodel en netwerkargitektuur. U moet u projek se modelle ook in fisiese modelle 

omskakel. 

Hfst 14 verduidelik databasis ontwerp en u moet die databasis ontwerp, die tablle 

normaliseer en die databasis fisies opstel in terme van u projek 

Hfst 15,16 en 17 bespreek prototipering by uitvoerontwerp, invoerontwerp en 

gebruikerskoppelvlakke. U moet prototipes opstel van u projek: invoere, uitvoere, 

koppelvlakke. Gebruik ook ‘n modelleringstegniek om die dialoog voor te stel. 

Hfst 19 verduidelik die konstruksie en implementeringsfase van ‘n projek en u moet dan ook 

behoorlike toetsing doen van spesifiksies en programkode en die stelsel in geheel. 

Hfst 20 bespreek stelsel instandhouding. 

Hfst 10 en 18 verduidelik die objekgerigte benadering tot stelselontleding en –ontwerp. 

3. Verslae wat u moet inhandig: Datum: 

1. Fisiese modelle: data, proses, netwerkargitektuur datavloeidiagramme, prototipes 

2. Databasis skema soos elektronies geskep 

3. Voorbeeld kode bv. verifiering van data op invoerskerms 

4. Toetsdokument 

5. Gebruikershandleiding 

Onthou om gedurig die oorkoepelende projek aktiwiteite soos in hfst 3 bespreek in gedagte 

te hou. (Bv beplanning mbv MS Project). 

29

SECTION 5 

PROJECT 

Project 

1. General 

Part of the ITRW 213 course required of you to plan and design a computerised project. This 

semester you will do the physical design, development and implementation of the project. 

Reports as well as other documentation must be done using a word processor. 

2. What is required of you? 

You have to complete the project that you have started in ITRW 213. The prescribed 

textbook will give you theoretical guidelines. 

For example, chapters 9 and 13 refer to process modelling. 

Chapter 11 shows how costs benefits analysis can be done and how to set up a feasibility 

matrix when comparing candidate systems. You have to use these techniques in your 

project. 

Chapter 12 refers to different design models and introduces process and data models as well 

as prototypes. These must be done practically as part of your project. 

Chapter 13 shows how logical models can be converted into physical models – process 

model, data model and network architecture data flow diagrams. You have to convert the 

logical models of your project into physical models. 

Chapter 14 explains database design. You must be able to design the database, normalise 

the tables and construct the database physically in terms of your project. 

Chapters 15,16 and 17 discuss prototyping during output design, input design and designing 

of the user interface. You have to set up prototypes of the input, output and user interface of 

your system. Use modelling techniques to indicate the dialogue. 

Chapter 19 explains the construction and implementation phases of a project. You have to 

do proper testing of specifications and programming code of your system. You have to test 

the entire system. 

Chapter 20 discusses maintenance of a system. 

Chapters 10 and 18 explain the object oriented approach to system analysis and design. 

3. Reports to be handed in: Date: 

1. Physical models: data, process, network architecture DFD, prototypes 

2. Database schema that has been created electronically 

3. Example code e.g. data code verifying the input from the input screen 

4. Test document 

5. User manual 

Remember to keep the overall project activities in mind discussed in chapter 13. (E.g. 

planning by making use of MS Project). Everything should be written on a CD and the 

programmes should be installed from the CD for presentation purposes. 

29

Projek 

Sit alles saam op ’n CD – ook u programme, sodat u dit kan installeer daarvanaf wanneer u 

die stelsel demntreer.. 

4. Projekdemonstrasie 

U moet as groep die projek kom demonstreer en die volgende dokumente saambring: 

30 

• Alle modelle van u stelsel 

• Gebruikershandleiding 

• Toetsdokument 

• Voorbeeldkode 

• Voorbeeld verslae wat u stelsel genereer 

• Dagboek van tydsbesteding 

• CD 

• Konsensus oor elke groeplid se bydrae tot die projek.

Project 

4. Project demonstration 

You have to present the project as a group. Bring along the following documents: 

30 

• All the models of your system 

• User manual 

• Test document 

• Example code 

• Example of reports that your system can generate 

• Diary of the time you have spend on the project 

• CD 

• Consensus about each group member’s contribution to the project.

Projek 

ITRW225 Bepunting: Finale Projek 

GROEPNAAM (OF PROJEK SE NAAM ): ________________________________________ 

NAME VAN DIE LEDE: _______________________________________________________ 

__________________________________________________________________________ 

KORT BESKRYWING VAN DIE ONDERWERP: ___________________________________ 

__________________________________________________________________________ 

__________________________________________________________________________ 

PROGRAMMERINGSTAAL: ___________________________________________________ 

Toetsdokument: Inhoud, tegniese versorging, genoegsame 

gevalle en aanvaardingstoetsing 

Gebruikershandleiding: Inhoudsopgawe en indeks, ‘getting 

started’, maklike volg van instruksies, tegniese versorging 

Voorlegging /20 

Stelsel self: Afgerondheid en funksionaliteit, 

Skep rekords, opdateer data, vertoon, verwyder data, 

Geldigheidstoetse, korrektheid van toevoer en afvoer 

Afvoer: Profesionele uitleg, goed beplan, 

Berekeninge, sorteer, vinnige en effektiewe soek van data 

Gebruikersvriendelikheid, helpfunksie 

Voorbeeld kode /10 

Kompleksiteit/ moeilikheidsgraad /10 

Bonuspunte 

TOTAAL /150 

Vorige werk (modelle en prototipes) CD /50 

Geniet die werk aan u projek! 

/20 

/30 

/60 

/200…100 

31

Project 

ITRW225 Marks: Final Project 

NAME OF THE GROUP (OR PROJECT): ________________________________________ 

NAMES OF THE GROUP MEMBERS: ___________________________________________ 

__________________________________________________________________________ 

SHORT DESCRIPTION OF THE TOPIC: _________________________________________ 

__________________________________________________________________________ 

__________________________________________________________________________ 

PROGRAMMING LANGUAGE: _________________________________________________ 

Test document: Contents, technical compilation, enough 

cases and acceptance tests 

User manual: Table of content and index, ‘getting started’, 

easy to follow instructions, technical compilation 

Presentation /20 

System itself: Professional and functional 

Create records, update data, display data and information, 

remove data 

Validation tests, correctness of input and output 

Output: Professional layout, well planned 

Calculations, sorting, fast and effective searching of data 

User friendly, help function 

Code /10 

Complexity/ level of difficulty /10 

Bonus marks 

TOTAL /150 

Previous work (models and prototypes) CD /50 

Enjoy the project! 

/20 

/30 

/60 

/200 … /100 

31

ITRW225VBC - Index of

Create successful ePaper yourself

Delete template?

Save as template?