CS331 Tutorial Exercises:

Exercise One: Requirements should be correct, complete, VII. Save medical/treatment records.
consistent, clear and concise.
See the following SRS Document and check if the VIII. Automatically generate forms such as sick sheets,
requirements specifies meet the above characteristics performance appraisals, leave forms.
====================================
======================= IX. Create Custom Reports.
Project Name: Development Version No: 1.0
of intergrated human X. Store attendance register for Employees.
resources and payroll
system XI. Allow adhoc queries.
Created By: A. Shah Date Created: 1st October
2008 XII. Import/Export Facility from MS Excel.
Organisation: Software Contact Details:
Experts software@123.co.tz XIII. Security: ability to define different access levels for
various functions.
1. Background:
This project shall involve the development of an HR/ Payroll
system b) Payroll Functionality

2. Functional Requirements: I. Fully integrated with Human resource

I. A Database that can hold Employees personal management application.
records including Names, Date of birth, place of
birth, place of domicile, family details, date of II. Process payroll for 150 staff.
employment, designation, date of confirmation,
education details, end of employment and other III. Create user defined tax table and table for
pertinent details, for at least 150 staff. other deductions.

II. Set up definitions of vacant positions and enable
monitoring of the recruitment process.
III. Register new staff.
IV. May maintain full employment history including
promotions, disciplinary actions, absences.
V. Ability to set up a leave roster and automatically
compute leave for all people.
VI. Plan training programs.
IV. Compute taxes, benefits and deductions.
V. Produce pay slips.
VI. Ability to produces payroll for individuals,
groups or the entire workforce.
VII. Import/Export Facility from MS Excel.
4. Non Functional Requirements:
Use Friendly
Fast

5. Constraints:
None
====================================
=======================
Exercise Two: Consider the examples of projects which
failed and try to point out where in the software engineering
process, mistakes were made.
Therac-25 (1985-1987)
Six people were overexposed during radiation treatments
for cancer by Canada's Therac-25 radiation therapy
machine. Three of these patients were believed to have
died from the overdoses. The root cause was a lack of
quality assurance, which lead to an over-complex,
inadequately tested, under-documented system developed,
and subsequently to the failure to take adequate corrective
action. (Pooley & Stevens, 1999)
London Ambulance System (1992)
A succession of software engineering failures, especially in
project management, caused 2 failures of London's
(England) Ambulance dispatch system. The repair cost was
estimated at £9m, but it is believed that people died who
would not have died if ambulances had reached them as
promptly as they would have done without the failures.
Denver baggage handling system
The Denver airport baggage handling system was so
complex (involving 300 computers) that the development
overrun prevented the airport from opening on time. Fixing
the incredibly buggy system required an additional 50% of
the original budget - nearly $200m.
Taurus (1993)
Taurus, the planned automated transaction settlement
system for the London Stock Exchange was canceled after 5
years of failed development. Losses are estimated at £75m
for the project and £450m to customers. (Pooley & Stevens,
1999)
Ariane 5 (1996)
The Ariane 5 rocket exploded on its maiden flight in June [4],
1996 because the navigation package was inherited from
the Ariane 4 without proper testing. The new rocket flew
faster, resulting in larger values of some variables in the
navigation software. Shortly after launch, an attempt to
convert a 64-bit floating-point number into a 16-bit integer
generated an overflow. The error was caught, but the code
that caught it elected to shut down the subsystem. The
rocket veered off course and exploded. It was unfortunate
that the code that failed generated inertial reference
information useful only before lift-off; had it been turned off
at the moment of launch, there would have been no trouble.
(Kernighan, 1999)
E-mail buffer overflow (1998)
Several E-mail systems suffer from a "buffer overflow error",
when extremely long e-mail addresses are received. The
internal buffers receiving the addresses do not check for
length and allow their buffers to overflow causing the
applications to crash. Hostile hackers use this fault to trick
the computer into running a malicious program in its place.
USS Yorktown (1998)
A crew member of the guided-missile cruiser USS Yorktown
mistakenly entered a zero for a data value, which resulted in
a division by zero. The error cascaded and eventually shut
down the ship's propulsion system. The ship was dead in
the water for several hours because a program didn't check
for valid input. (reported in Scientific American, November
1998)

Mars Climate Orbiter (September 23rd, 1999)

The 125 million dollar Mars Climate Orbiter is assumed lost

by officials at NASA. The failure responsible for loss of the
orbiter is attributed to a failure of NASA’s system engineer
process. The process did not specify the system of
measurement to be used on the project. As a result, one of
the development teams used Imperial measurement while
the other used the metric system of measurement. When
parameters from one module were passed to another during
orbit navigation correct, no conversion was performed,
resulting in the loss of the craft.
http://mars.jpl.nasa.gov/msp98/orbiter/

====================================
========================
Exercise 3:
You have been given the task of designing a web site that
presents the tourist attractions in Dar es Salaam . The web
site must have the following feature:
o An interactive map of the city
o A list of hotels , their locations and their rates
o A list a description of the tourist attraction
o A Swahili phrase book
o Any other useful information.

Use the Story boarding technique to elicit requirements for

the website