First Home Work

Chapter 9th Exercise Solution

Ian Sommerville Software

Engineering 8th edition

Prepared by Laith Obeidat

Submitted to Dr. Aysh Alhroob

Q 9.3:
List of Hazards as following:
1- Incorrect delivery of radiation.
2- Used information for incorrect patient.
3- Radiation delivered to incorrect body.
To reduce the probability for these hazards
1- Concern with previous doses results to compare with current
results and confirmation of dose by operator.
2- Ask patient to verify his/her information before starting work
on the machine.
3- Records site in previous treatment to compare with current
site, use light to clarify the vision and site confirmation by
operator before play machine.
Q 9.4:
The differences between safety & security specification
processes as following:
1- Not possible to specify security requirements quantitatively
but it is possible in safety.
2- Not possible to defined security standards but it is possible
in safety.
3- Generic threats rather than system specific hazards.
Q 9.5:
My suggestion to modify fault-tree analysis through put the
threats at the root of the tree and identifies the status that can
lead to that threat.
Q 9.6:
The deference between hardware and software failures as
following:

Hardware refers to the physical components of the computer

which can be felt and seen. Software refers to the programs that
allow the system to operate and perform different functions.
Q 9.7:
Because we can't depends on little of number of failures because
it is lead to unrealistically results into lifetime of a system

Q 9.8:

System

Suggested
value
Monitors
Should be
patient system available every
time in month
except 30
minutes/month
Word processor The failure not
system
occur 1/2000
hours used

Reliability
metric
AVAIL

ROCOF

Vending
machine
system

The failure
acceptable in
20000
demands

POFOD

Braking car
system

Should not fail

POFOD

Refrigeration
unit system

Should be
available every

AVAIL

Reasons
Not critical
system
because the
failure is
acceptable
Not critical
system
because the
failure is
avoidance
Not critical
system
because the
failure rate is
appropriate
So critical
system and
failure
unacceptable
Not critical
system

Management
report
generator

time in month
except 30
minutes/month
1/100 failure
per hours used

ROCOF

because the
failure is
acceptable
Not critical
system
because the
failure not
occurs real
problem

Q 9.9:
The failure

Reliability metric

Error in the database

access denied of
system service

ROCOF
AVAIL

Error information
delivery

ROCOF

Suggested value
of time
1 failure per 10 days
The service not
available for 10
minutes per 24
hours (one day)
1 failure per day

Q 9.10_A:
Four functional requirements for EPOS system to improve
system reliability as following:
1- The system must entered user name and password.
2- If the storage of the database is fully the system must be
notify.
3- If the bar code reader doesnt working then the system must
query through the touch screen into database.

4- The system must provide printed invoice after buying

process.
Q 9.10_B:
The reliability metric is (POFOD) because the response for this
system (A train protection system) should be correctly on request.

The functional system requirements for (A train protection

system) as following:
1- If the speed of train becomes less than limited speed then
the system must be show that for operator (driver).
2- If the train exceeds the speed over limited speed then the
system brakes of train must be reduce the speed.
3- The system must be recognized the speed of the train every
time (in any moment).
4- When red light received the system must give sound
notifications for the operator (driver).
5- When red light received the system must be confirm and
applied train brakes.
Q 9.11:
The safety is a non-functional requirement, it is more critical than
functional requirements it is needed to high experience and skills
to recognize and understand. Then the software engineers must
working as professionally, moreover the results from functional
requirements it is predicted but from non-functional requirements
unpredicted partly such as the security it is not has a standard.