Tutorial Letter 101 / Studiebrief 101 School of Computing ... - Name

Advanced Systems Analysis and Development
Gevorderde Stelselontleding en Ontwikkeling
INF305F/SED401I/SWE401I
Tutorial Letter 101 / Studiebrief 101
School of Computing / Skool vir Rekenaarkunde
INF305F/SED401I/SWE401I/101/0/2010
inf305@osprey.unisa.ac.za
http://www.osprey.unisa.ac.za
https://my.unisa.ac.za/portal

Important notice:
Since 2005 the national Department of Education has required that in order to be considered for
examination admission a learner must submit at least one assignment before 30 June 2010.
Belangrike nota:
2
Vanaf 2005 vereis die nasionale Departement van Opvoeding dat, om vir eksamentoelating in aanmerking
te kom, 'n student ten minste een werkopdrag voor 30 Junie 2010 moet indien.
To all Afrikaans speaking learners / Aan alle Afrikaanssprekende leerders:
Hierdie studiebrief is slegs in Engels beskikbaar. Indien u sukkel om sekere dele van die inhoud te verstaan,
kontak gerus u dosente.
ASSIGNMENT DUE DATE NOTICE
Assignment 1 - Multiple-choice 03 May 2010
Used for exam admission.
INF305F: 860733 SED401I: 216939 SWE401I: 313044
Assignment 2 – Theory 05 July 2010 Used for year mark calculation.
Assignment 3 – Self-evaluation Tutorial Letter 102
Used for exam preparation by learner
him/herself.

3
Contents
INF305F/SED401I/SWE401I/101
1 INTRODUCTION ................................................................................................................................. ........................ 5
2
3
ABOUT THIS MODULE ............................................................................................................................................. 5
COMMUNICATION WITH UNISA AND FELLOW LEARNERS ........................................................................ 5
3.1 WHO TO PHONE FOR
WHAT? ................................................................................................................................... 5
3.2 COMMUNICATION CHANNELS
................................................................................................................................. 6
3.3 INTERNET ACCESS TO ON-LINE MATERIAL AND DISCUSSION FORUM ....................................................................... 6
3.4 DISCUSSION FORUM ................................................................................................. .............................................. 7
3.5 E-MAIL ................................................................................................................................................................... 7
3.6 PHONE CALLS ......................................................................................................................................................... 8
3.7 NO FAXING PLEASE ................................................................................................................................................ 8
3.8 WRITTEN COMMUNICATION .............................................................................................................................. ..... 8
3.9 COMMUNICATION WITH OTHER MODULE LEARNERS ............................................................... ............................... 9
4 ISSUES PERTAINING TO THIS MODULE ............................................................................................................. 9
5
6
7
4.1 PREREQUISITE SKILLS ............................................................................................................................................ 9
4.2 CO-OPERATIVE LEARNING (GROUP WORK) ............................................................................................................ 9
STUDY MATERIAL ..................................................................................................................................................... 9
5.1 PRESCRIBED TEXTBOOK ......................................................................................................................................... 9
5.2 TUTORIAL LETTER 102 ........................................................................................................................................... 9
STUDY MATTERS ..................................................................................................................................................... 10
6.1 SYLLABUS ............................................................................................................................................................ 10
EXAMINATION MATTERS ..................................................................................................................................... 10
7.1 ENQUIRIES ABOUT DATES AND VENUE S ........................ ......... ..................... .......................................................... 10
7.2 A SPECIAL EXAMINATION TUTORIAL LETTER ........................................................................................................ 11
7.3 EXAMINATION ADMISSION .... .......... ............................... ....... ............................................................................... 11
8 FREQUENTLY ASKED Q UESTIONS ............................. ........ .................................................................. ............. 11
8.1 I CANNOT FIND THE TEXTBOOK ............................................................................................................................ 11
8.2 I HAVE NOT RECEIVED CERTAIN S TUDY MATERIAL ............. ... ............................
................................................... 11
8.3 DOWNLOADING STUDY MATERIAL FROM THE WEB ............................................................................................... 11
8.4 I WANT TO FORM A STUDY GROUP - WHERE DO I FIND THE OTHER LEARNERS? ..................................................... 12
8.5 WHEN DO I GET MY ASSIGNMENT BACK? ............................................................................................................. 12
8.6 WHAT MARKS DID I GET FOR MY ASSIGNMENT? ................................................................................................... 12
9 ASSIGNMENT MATTERS ........................................................................................................................................ 12
9.1 DUE DATES ........................................................................................................................................................... 12

4
9.2 STRUCTURE OF THE ASSIGNMENTS ....................................................................................................................... 13
9.3 YEAR MARK ......................................................................................................................................................... 13
9.4 MODEL SOLUTIONS .............................................................................................................................................. 13
9.5 SUBMITTING AN ASSIGNMENT .............................................................................................................................. 13
9.6 HAVE WE RECEIVED YOUR ASSIGNMENT? ............................................................................................................ 14
9.7 RELATION BETWEEN ASSIGNMENTS AND THE EXAMINATION .............................................................................. 14
ASSIGNMENT 1 ................................................................................................................................................................... 15
ASSIGNMENT 2 ................................................................................................................................................................... 22

1
Introduction
5
INF305F/SED401I/SWE401I/101
We present you with a comprehensive first tutorial letter to assist you in the best possible way to make
sure that you
have effective interaction with the lecturers for this module.
2 About this module
‘When computer software succeeds - when it meets the needs of the people who use it, when it
performs
flawlessly over a long period of time, when it is easy to modify and even easier to use - it can
and
does change things for the better. But when software fails - when its users are dissatisfied, when it
is error prone, when it is difficult to change and even harder to use - bad things can and do happen
(Pressman,
2010)’.
This
is the opening paragraph of the prescribed book, Software Engineering, A Practitioner’s Approach
by
Pressman, and summarizes the goal of this module - looking at the actions involved in building and
maintaining
software from a Software Engineering approach.
Prescribing
a relevant, usable, user-friendly, affordable textbook is a particularly difficult task. We
went
through a number of books during 2004 in search of a prescribed book that addresses the
important
issues in Software Engineering and we finally decided on Roger S. Pressman’s book. He is a
well-known
author in this specific application domain and we believe that the learners taking this
module
will gain not only from the chapters that we cover in depth, but also from the chapters that we
designate
as reading material.
We
trust that you will find the module interesting and enriching!
3 Communication with Unisa and fellow learners
3.1 Who to phone for what?
When you register, you should have received an inventory letter containing information about your
tutorial matter. See also the brochure entitled Your Service Guide @ Unisa (which you received with
your tutorial matter). Consult this document for the necessary contact people. Please do not telephone
the lecturers for services supplied by support departments. In respect to all administrative enquiries
only the UCC (Unisa Contact Centre) telephone and fax must be used. Enquiries will then be
channelled to the respective Departments.

6
• Calls – RSA only:
0861 670 411
• International Calls:
+27 11 670 9000
• Fax Number: (012) 429 4150 / +27 12 429 4150
• Email: study-info@unisa.ac.za
• The Lecturers for this module
COMMUNICATION WITH THE UNIVERSITY
Always have your student number
at hand when you call the University.
COS-ALL/2010
3.2 Communication channels
To increase the efficiency of managing this module, we have prioritized our communication channels.
Too much time is often wasted on inefficiency, where a learner has to call Unisa repeatedly, or has to
hold on until he or she
gets through to the right person, before finally resolving the query he or she had.
By
placing a priority on the communication channel, we provide a guarantee of a rapid response time.
In the following table, we list the available communication channels in order of highest to lowest
priority and then discuss each one in the subsequent paragraphs.
Channel Advantages General response time
Discussion
forum
Transparency - learners often experience the same types of problems and if a
query is placed on the discussion forum, everybody has access to the question as
well as its answer
Internet Access Much of the material that is available in printed form is available ‘much sooner’
on the web for downloading.
E-mail Please use the module
e-mail address. Do not send mail to lecturers directly. Within 2 working days
Telephone
Written letters 2 - 6 weeks
Within 2 working days
Immediately
Immediately only if the
lecturer is not currently busy
with another appointment
such as a learner or a meeting
or a workshop or a seminar or
a conference or examining a
learner, etc.
3.3 Internet access to on-line material and discussion forum
We have a departmental web server that is used as Internet access for learners enrolled for Computer
Science or Information System modules. It is also accessible through the addresses
http://osprey.unisa.ac.za,
http://it.unisa.ac.za, or
http://cs.unisa.ac.za.

7
INF305F/SED401I/SWE401I/101
To access the discussion forums, click on the Registered Learner tab, click on your
modules, submit,
refresh the screen and the di scussion forum will be on your left-hand side. The login and access code
for 2010 will be given in a general tutorial letter to learners but
it could be:
Login: MYDOWNLOAD
Password: SOC2010
During January 2011 the login/password combination for downloads will change from
MYDOWNLOAD/SOC2010 to something new.
Thus, 2010 material may no longer be
available for download in January 2011. You must therefore ensure that
you have
downloaded all the material you may require for supplementary examinations by 30
November 2010!!
Unisa also has other web servers. An important one is the myUnisa server. This server is one of the
Unisa servers that provide learner administration services, where you can do electronic submissions of
assignments, or check your records, etc. All tutorial letters for this module will be available on myUnisa
the moment that they are sent to Despatch for distribution.
3.4
Discussion forum
In this module we will use the discussion forum that can be found on the IT server for module-related
matters.
We use the discussion forum as our MAIN communication channel. Please access
it regularly (once a
week is fine). To access the discussion forum for this module, you must set up your browser only once.
T he procedure is the same as the one described in section 3.3. The first time tha t you go to the
departmental web site, go to:
osp rey.unisa.ac.za,
click o n the Registered
Student tab,
click on your modules,
submit,
refresh the screen
and the discussion forum will be on your left-hand side.
3.5
E-mail
We urgently request that you use the discussion forum for all electronic communication. There are
different threads in the discussion forum. Please use it to direct all your queries. Please
use the
module discussion forum instead of the module e-mail.

8
Reserve your e-mail messages for highly personal matters. The e-mail address for this module is
inf305@osprey.unisa.ac.za - please put your student number and module number next to the subject-
line, otherwise it may be deleted as spam.
Please do not use the personal e-mail addresses of the lecturing staff. The above address will ensure
that your e-mail will be
answered even if a particular lecturer is not available.
3.6 Phone
calls
Please consult your tutorial letters first to see whether we have not already addressed your
queries.
Since most learners experience the same problems, we address the most common problems
in the
tutorial letters.
Remember
that we are sometimes not available due to other departmental or university duties. If you
fail to reach us directly, please call the departmental secretary for she will be able to inform you about
when we will be available, or she will take a message, in which case you should leave a message
stating the reason for your call and your name, student number and telephone number. The
departmental secretary’s number is (012) 429-6122.
3.7 No faxing please
Due to the high cost, our School has a policy of not faxing material to learners. However, we do get
quite a number of learners faxing us regarding requests for extensions on certain study material, etc.,
and requesting
us to contact them in return. Facsimiles place an unnecessary administrative burden on
the
staff since there is only one fax machine in the office of a secretary. However, each lecturer has an
e-mail facility on his/her desk. With large modules, the burden simply becomes too large to carry if the
lecturers have to go looking for faxes. Please, if you need to contact us urgently, use the discussion
forum or e-mail.
3.8 Written communication
Please mention your student number in all
written communication. All academic matters can be
addressed to:
The Registrar
UNISA
P O Box 392
PRETORIA
0003
Letters on any aspects regarding the module should be addressed as follows:
The Lecturer (INF305F) or (SED401I) or (SWE401I)
School of Computing
UNISA
P.O. Box 392
PRETORIA
0003

9
INF305F/SED401I/SWE401I/101
3.9 Communication with other module learners
Phone the Unisa Contact Centre and ask for a list of learners of this module in your environment, or
join our discussion forum and start communicating with other learners.
4 Issues pertaining to this module
4.1 Prerequisite skills
Learners enrolled for this module must have a background in systems analysis and design obtained
through previous undergraduate module work.
4.2 Co-operative learning (Group Work)
In this module you may work in groups, BUT each person must submit his or her own assignment.
Take note that all members of a group cannot submit a copy of the same assignment, but each
person
must submit his or her own assignment, using his or her
own words to describe the solution. If you
work in a group, it is important
to say who worked together, so that we can evaluate submitted
assignments in that light.
5 Study material
5.1 Prescribed textbook
The following textbook
(referred to as Pressman in the remaining text), is prescribed for this module:
Software Engineering: A Practitioner’s Approach, Roger S. Pressman, Seventh Edition, International
Edition 2010, McGraw Hill
• ISBN: 978-007-126782-3
• PLEASE buy the book
as soon as you register for the module. More than one university prescribes
the book and if you wait, you will probably not find a copy.
• We recommend that you first phone the list of bookstores (in Your Service Guide @ Unisa) to get the
local price for the book before using an on-line store.
• Please consult
the list of official booksellers and their addresses in Your Service Guide @ Unisa.
• If you have any difficulties with obtaining books from these bookshops, contact the Contact Centre
at 0861 670 411 (South Africa) or +27 11 670 9000 (Internationally), or send
an e-mail to
vospresc@unisa.ac.za
• Important note: No assignment
can be done without the prescribed book.
5.2 Tutorial
letter 102
We do not wish to burden you with much MORE reading material than that which is already accessible
in the textbook. We include a self-study assignment in Tutorial Letter 102, to help with the
examination
preparation.

6 Study matters
10
6.1 Syllabus
We use the textbook and additional material that we will
send out in the form of tutorial letters.
The 7th edition of Software Engineering: A Practitioner's
Approach contains 32 chapters organized
into
five parts. The book comprises approximately 900 pages. For this module, only the following will
be covered:
Chapter Heading Comments
Chapter 1: Software & Software Engineering Read
Chapter 2: Process Models Study
Chapter 3: Agile Development Study
Chapter 4: Principles that Guide Practise Study
Chapter 5: Understanding Requirements Study
Chapter 6: Requirements Modeling Read
Chapter 8: Design Concepts Study
Chapter 9: Architectural Design Read
Chapter 10: Component-Level Design Study
Chapter 11: User Interface Design Read
Chapter 12: Pattern-Based Design Read
Chapter 13: WebApp Design Read
Chapter 17: Software Testing Strategies Study
Chapter 18: Testing Conventional Applications Study
Chapter 19: Testing Object-Oriented Applications Study
Chapter 20: Testing Web Applications Read
7 Examination matters
7.1 Enquiries about dates and venues
U nisa is an enormous institution and we, the lecturers, have nothing to do with examinations except for
setting the paper - long before October / November - and receiving the papers afterwards for marking.
We can therefore not give you any relevant information regarding examination
dates or venues. Please
contact the Contact Centre for examination details. Take note of the dates of your examinations and
arrange with your employer for
leave in good time. Check that there are no clashes on your
examination timetable. Should there be any such clashes, kindly inform the Contact Centre without
delay or Examination Administration (e-mail: exams@unisa.ac.za).

11
INF305F/SED401I/SWE401I/101
7.2 A special examination tutorial letter
A special examination tutorial letter will be sent to you informing you about any issues regarding the
paper. This includes
matters such as the format of the paper.
7.3 Examination admission
You gain admission to the examination by submitting one assignment before 30 June 2010. Note that
this assignment must be done satisfactorily. For a written assignment or answer you may not submit
just
one or two sentences. For assignments in multiple-choice format, you may not submit an empty
assignment – you have to select an answer for each question. For your year mark (see section
9.3) you
need to submit
Assignment 2.
8 Frequently asked questions
There are several reasons why you may
wish to contact Unisa and too often you are put on hold and
h ave to go from one person to another before you finally reach the correct person. Therefore, in this
section, we provide a list of common reasons why learners contact us and
information on how to
address these problems in the most efficie nt and quickest possible way.
8.1 I cannot find the textbook
PRESSMAN is a very popular book and more than one university pre scribes it. Please buy the book as
soon as possible to ensure that you do not have difficulty in obtaining the book later on.
D o not contact the lecturers for this module if you have problems obtaining the textbook.
U nfortunately we cannot help with the availability of textbooks since we have no contact with the book
dealers. Use the following guidelines if you experience difficulty in obtaining a textbook:
1. If your university book dealer does not have the book in stock, ask them to put your name
on their order list so that they can contact you as soon as the new stock arrives.
2. If your university book dealer
cannot help you, call the Contact Centre for further advice.
Never send in a sub-standard assignment
because you do not have the prescribed book. You
cannot and will not receive marks for not doing work because
you do not have a book!
8.2 I have not received certain study material
Printed material is only distributed by the Despatch Department. Unfortunately our School does not
have the facilities to fax copies of any study material. You can also visit our WEB site
(osprey.unisa.ac.za) and download the specific material if it is available (see section 3.3).
8.3 Downloading study material from the web
Please note that:

• Due to copyright regulations, we will not necessarily place all the material on the web.
12
• The material placed on the web will be in PDF-format. Please download the PDF-reader from
our WEB site and install it on your machine (once).
All tutorial letters should be downloada
for distribution.
ble from myUnisa the moment that we send them to Dispatch
8.4 I want to form a study group - where do I find the other learners?
The lecturers may not distribute any personal information about any learner. However, on the
registration form that each learner
fills in at the beginning of the academic year/term, the university
requires
to know whether or not the university may distribute the learner’s contact details to other
learners. This information is available via the Contact Centre. If you need contact information about
other learners in your area, the Contact Centre can
assist you in obtaining the necessary information.
8.5
When do I get my assignment back?
Turnaround time for marking is commonly between 4 and 5 weeks. If you have not received your
assignment back after this time, please read the discussion forum to see if any delays are being
experienced, or phone the Contact Centre.
8.6 What marks did I get for my assignment?
As soon as your assignment is marked the mark will be displayed on the myUnisa system. Usually the
multiple-choice assignment marks are available 2-3 weeks after the due date. The written assignments
may take longer.
9 Assignment matters
There are three assignments for this module. To gain examination admission you need to complete and
submit assignment 01. We do advise you to complete all the assignments so as to cover the content
matter
before the examinations.
9.1
Due dates
ASSIGNMENT
Assignment 1 - Multiple-choice 03 May 2010
DUE DATE NOTICE
Used for exam admission.
INF305F: 860733 SED401I: 216939 SWE401I: 313044
Assignment 2 – Theory 05 July 2010 Used for year mark calculation.
Assignment 3 – Self-evaluation Tutorial Letter 102
Used for exam preparation by learner
him/herself.

9.2 Structure of the assignments
Multiple-choice assignments
13
INF305F/SED401I/SWE401I/101
Assignment 01 is a multiple-choice assignment, which should either be completed on the computer
mark-reading sheet issued to you during registration, or be submitted electronically through myUnisa.
The multiple-choice
assignment is marked electronically on a predetermined date. For example, if the
submission date for a particular assignment is 03 May and the scheduled marking date is 03 May, then
all submitted assignments will be marked through batch processing by the computer one or two days
after the due date.
Written assignments
Assignment 2 and 3 are written assignments. Assignment 2 should be posted to Unisa or uploaded on
the myUnisa web site. Assignment 2 is used to determine your year mark. Assignment 3 is for selfevaluation
and can be used to provide additional examples in your preparation for the November and/or
January examinations.
9.3 Year mark
Each module leader may decide which assignments
will count towards the year mark. For
INF305F/SED401I/SWE401I you will receive a possible mark out of 10, which will count towards
your final mark for the year. For this module, we will use the mark
that you receive for Assignment 02.
9.4 Model solutions
Model solutions will
be posted to the module web site two to three weeks after the due date of each
assignment. A single printed version of solutions will also be sent to learners.
9.5 Submitting an assignment
You can submit your assignments in several ways.
1. electronically through the myUnisa server,
2. by postal mail,
3. By placing them in one of Unisa’s assignment
boxes.
Postal or assignment-box
submission of an assignment
1. Complete your assignment and place it in an assignment
cover provided during registration.
2. Put your assignment in an envelope and submit the assignment using the postal mail
or one of
Unisa’s assignment mail boxes.
Electronic submission of an assignment
1. Click on the electronic submission
link on myUnisa
for INF305F (or for SED401I) (or for
SWE401I) and complete your answers on the sheet
provided for the applicable
assignment.
2.
Upload your assignment.

14
9.6 Have we received your assignment?
If you used myUnisa to upload your assignment, you should immediately see that the assignment is on
the system, next to the applicable
assignment in the assignment list. If not, re-enter your answers. If you
used the postal system check myUnisa two to three days after submitting your assignment. If it is not on
the system, resubmit your assignment. Always keep copies of your answers so as to be able to give us
a copy in case something goes wrong.
It is your responsibility to check if your assignment was received by Unisa or not. We will be lenient
with problems up until
one week after the due date. After this date we will not consider any pleas
regarding
lost assignments.
9.7 Relation between Assignments and the Examination
Our assignments are designed with at least two goals in mind:
1. to make sure that you actually go through the work during the year and do not try to do it all in
the week before the examinations (this is accomplished through the multiple-choice questions
given to you in the assignments).
2. to teach you how
to think and argue critically on issues in this module.

15
INF305F/SED401I/SWE401I/101
Assignment 1 Total: 100
Submission Date: 03 May 2010
Prescribed work: Chapters: 1-6, 8-13, 17-20 Speed-read and answer these questions
Unique Number: INF305F: 860733 SED401I: 216939 SWE401I: 313044
Chapter 2
1. Which of the following are
recognized process flow types?
1. Concurrent process flow and Linear process flow
2. Iterative process flow and Linear process flow
3. Linear process flow and Spiral process flow
4. Spiral process flow and Concurrent process flow
2. Software processes can be constructed
out of pre-existing software patterns to best meet the needs
o f a software project.
1. True
2. False
3. Which of these are standards for assessing software processes?
1. SEI and ISO 9000
2. SPICE and ISO 9001
3. ISO 9000 and SPICE
4. ISO 9001 and SEI
4. The waterfall model of software development is
1. a reasonable approach when requirements are well defined.
2. a good approach when a working program is required quickly.
3. the best approach to use for projects with large development teams.
4. an old fashioned model that is rarely used any more.
5. The incremental model of software development is
1. a reasonable approach when requirements are well defined.
2. a good approach when a working core product is required quickly.
3. the best approach to use for projects with large development teams.
4. a revolutionary model that is not used for commercial products.

6. Evolutionary software process models
16
1. are iterative in nature?
2. can easily accommodate product requirements
changes?
3. do not generall y produce throwaway
systems?
4. All of the abov e.
Chapter
3
7.
Agility is nothing more than the ability of a project team to respond rapidly to change.
1.
True
2. False
8. Which of the following is not necessary to apply agility
to a software process?
1. Eliminate the use of project planning and testing
2. Only essential work products are produced
3. Process allows team to streamline tasks
4. Uses incremental product delivery strategy
9. How do you
create agile processes to manage unpredictability?
1. Requirements gathering must be conducted very carefully and
risk analysis must be conducted
before planning takes place.
2. Risk analysis must be conducted before planning takes place and software increments must be
delivered in short time
periods.
3. Software increments must
be delivered in short time periods and software processes must adapt
to changes incrementally.
4. Requirements gathering
must be conducted very carefully and software processes must adapt to
changes incrementally.
10. In agile software processes the highest priorities is to satisfy the customer
through early and
continuous delivery of valuable software.
1. True
2. False
11. Which one of the following traits needs to exist among the members
of an agile software team?
1. Competence
2. Decision-making ability
3. Mutual trust and respect
4. All of the above
12. In agile development, it is more important to build software that meets the customers’ needs
today than worry about features that might be needed in the future.

1. True
2. False
Chapter 4
13. Software engineering principles have about a three-year half-life.
1. True
2. False
17
INF305F/SED401I/SWE401I/101
14. Which of the following is not one of the core principles of software engineering practice?
1.
All design should be as simple as possible, but no simpler.
2. A software system exists only to provide value to its users.
3. Pareto principle (20% of any product requires 80% of the effort).
4. Remember what you produce others will consume.
15. Every communication activity should have a
allowed to dominate the proceedings.
1. True
2. False
facilitator to make sure that the customer is not
16. The agile view of iterative customer communication and collaboration is applicable to all software
engineering practice.
1. True
2. False
17. One
reason to involve everyone
1. adjust the granularity of the plan.
2. control feature creep.
3. get all team members to “sign up” to the plan.
4. understand
the problem scope.
on the software team in the planning activity is to
18.
Project plans should not be changed once they are adopted by a team.
1. True
2. False
Chapter 5
19. Requirements engineering is a generic process that does not vary from one software project to
another.

1. True
2. False
20. During project
inception the intent of the tasks are to determine
1. basic problem understanding.
2. nature of the solution needed.
3. people who want a solution.
4. All of the above.
21. Three things that make requirements elicitation difficult are problems of
1. Budgeting, scope and understanding.
2. scope, understanding and volatility.
3. understanding, volatility and budgeting.
4. volatility, budgeting and scope.
22. A stakeholder is anyone who will purchase the completed software system under development.
1. True
2. False
18
23.
It is relatively common for different customers to propose conflicting requirements, each arguing
that his or her version is the right one.
1. True
2. False
Chapter
8
24. Which
of the following are areas of concern in the design model?
1. Architecture, data and interfaces.
2. Data, interfaces and project scope.
3. Interfaces, project scope and architecture.
4. project scope, architecture and data.
25.
The importance of software design can be summarized in a single word.
1. accuracy
2. complexity
3. efficiency
4. quality
26. Which of
these are characteristics of a good design?

19
INF305F/SED401I/SWE401I/101
1. Exhibits strong coupling between its modules and implements all requirements in the analysis
model.
2. Implements all requirements in the analysis model and provides a complete picture of the
software.
3. Includes test cases for all components and implements all requirements in the analysis model.
4. Provides a complete picture of the software and includes test cases for all components.
27. Which of the following is not a characteristic
common to all design methods?
1. configuration
management
2. functional component representation
3. quality assessment guidelines
4. refinement heuristics
28. What types of abstraction are used in software
design?
1. Control, data and procedural.
2. Data, environmental and control.
3. Environmental, procedural and data.
4. Procedural,
control and environmental.
29. Which
of
the following can be used to represent the architectural design of a piece of software?
1. Dynamic models
2. Functional models
3. Structural models
4. All of the above
Chapter
10
30.
In the most general sense, a component is a modular building block for computer software.
1. True
2. False
31. In the context of object-oriented software engineering
a component contains
1. attributes and operations.
2. instances of each class.
3. roles for each actor (device or user).
4. set of collaborating
classes.
32. In traditional software
engineering, modules must serve in which of the following roles?
1. Control component
2. Infrastructure component

3. Problem domain component
4. All of the above
33. Software engineers always need to create components from scratch in order to meet customer
expectations fully.
1. True
2. False
34.
Which of the following is not one of the four principles used to guide component-level design?
1. Dependency Inversion Principle
2. Interface Segregation Principle
3. Open-Closed Principle
4. Parsimonious Complexity Principle
35.
The use of stereotypes can help identify the nature of components at the detailed design level.
1. True
2. False
Chapter 17
36. In software quality assurance
work there is no difference between software verification and
software validation.
1. True
2. False
37.
The best reason for using Independent software test teams
is that
1. software developers do not need to do any testing.
2. strangers
will test the software mercilessly.
3. testers do not get involved with the project until testing begins.
4. the conflicts
of interest between developers and testers is reduced.
38. What is the normal order of activities in which traditional software testing is organized?
a. integration testing b. system testing c. unit testing d. validation testing
1. c, a, d, b
2. d, c, a, b
3. c, b, a, d
4.
a, c, b, d
20
39.
By collecting software metrics and making use of existing software reliability models it is possible
to develop meaningful guidelines
for determining when software testing is done.

1. True
2. False
21
INF305F/SED401I/SWE401I/101
40. Which of the following strategic issues needs to be addressed in a successful software testing
process?
1. Conduct formal technical reviews prior to testing and specify requirements in a quantifiable
manner.
2. Specify
requirements in a quantifiable manner and use independent test teams.
3. Use independent test teams and wait till code is written prior to writing the test plan.
4. Wait till code is written prior to writing the test plan and conduct formal technical reviews prior
to testing.
Chapter 18
41. With thorough testing, it is possible to remove
all defects from a program prior to delivery to the
customer.
1. True
2. False
42.
Which of the following is a characteristic of testable software?
1. observability
2. simplicity
3. stability
4. all of the above
43. The testing technique that requires devising test cases to demonstrate that each program function is
operational
is called
1. black-box testing.
2. glass-box testing.
3. grey-box testing.
4. white-box testing.
44. The
testing technique that requires devising test cases to exercise the internal logic of a software
module is called
1. behavioral testing.
2. black-box testing.
3. grey-box testing.
4. white-box testing.
45.
What types of errors are missed by black-box testing and can be uncovered by white-box testing?
1. behavioral errors and performance errors
2. logic errors and typographical errors

3. performance errors and logic errors
4. typographical
errors and behavioral errors
Chapter 19
4 6. It is not possible to test object-oriented software without including error discovery techniques
applied to the system OOA and OOD models..
1. True
2. False
22
47. The correctness
of the OOA and OOD model is accomplished using formal technical reviews by the
software quality assurance team.
1. True
2. False
48. The consistency
of object-oriented models may be judged by reviewing the CRC card model.
1. True
2. False
49. Test case design for
OO software is driven by the algorithmic detail of the individual operations.
1. True
2.
False
50. Integration testing of object-oriented software can be accomplished by which of the following
testing strategies?
1. Cluster testing, thread-based
testing and use-based testing.
2. Glass-box testing, use-based testing and cluster testing.
3. Thread-based testing,
cluster testing and glass-box testing.
4. Use-based testing, glass-box testing and thread-based testing.
Assignment 2
Submission Date: 05 July 2010
Prescribed
work: Chapters: STUDY chapters 2, 3, 4, 5, 8, 10, 17, 18 and 19
Total: 100
Hint 1: This Assignment is long and will take a while to complete. After studying all the relevant
chapters,
plan at least one full week to do the assignment.
Hint 2: Each question must be answered in a short
essay type answer. Each answer should not be
longer than 15 sentences.

23
INF305F/SED401I/SWE401I/101
Chapter 2
Question 01: The concurrent process model defines a set of ‘states’. Describe in your own words what
these states represent,
and then indicate how they come into play within the concurrent process model.
[ 5]
Question 02: What are the advantages and disadvantages of developing software in which quality is
‘good
enough’? That is, what happens when we emphasize development speed over product quality?
[7]
Chapter 3
Question
03: Describe the XP concepts of refactoring and pair programming in your own words.
[5]
Question
04: Why is Crystal called a family of agile methods? [5]
Chapter 4
Question
05: Describe separation of concerns in your own words. [5]
Question 06: How does agile communication differ from traditional software engineering
communication?
How is it similar? [6]
Chapter 5
Question 07: Why is it that many software developers don’t pay enough attention to requirements
engineering?
Are there ever circumstances where you can skip it? [6]
Question 08: Why do we say that the requirements model represents a snapshot of a system in time?
[5]
Chapter 8
]
in your own words. [5]
Question 09: If a software design is not a program (and it isn’t), then what is it? [5
Question
10: Describe software architecture
Chapter 10
Question 11: Why are control components necessary in traditiona
in object-oriented software?
l software and generally not required
[5]
Question 12: Why is chunking important during the component-level design review process? [5]
Chapter 17
Question 13: Is it always possible to develop a strategy for testing software that uses the sequence of
testing steps described in Section 17.1.3? What possible complications might arise for embedded
systems?
Question 14: Why is a highly coupled module difficult to unit-test?
Chapter 18
Question 15: Can you think of any additional testing objectives that are not discussed in Section
14.1.1?
[5]
[6]
[5]

24
Question 16: Give at least three examples in which black-box testing might give the impression that
‘everything is OK’, while white-box tests might uncover an error. Give at least three examples in which
white-box testing might give the impression that ‘everything is OK’, while black-box tests might
uncover an error. [7]
Chapter 19
Question 17: Which is more valuable to object-oriented testing, white-box or black-box testing? Why?
[8]
Question 18:
What is the difference between thread-based and use-based strategies for integration
testing? How does cluster testing fit in? [ 5]
©
UNISA
2009