|
(a) The requirements specification document
can be thought of as a formal
document that states clearly the functional and performance requirements
of a
software system. Carefully explain what is meant by the words functional
and
performance in relation to this document. Give examples of
requirements that
fall into each of these categories. [4]
(b) Balzer and Goldman proposed a number of principles to follow in
the creation
of the specification analysis document. Below are four such principles.
In your
own words, explain what each of them means:
- “A specification must be operational.”
- “A specification must encompass the system of which the software
is
component.”
- “Separate functionality from implementation.”
- “A specification must be localized and loosely coupled.”
[4]
(c) The following are typical causes of problems identified during
requirement
analysis. For each, based on your understanding of requirement analysis,
comment on the significance, and how it affects actual subsequent
software
development. [4]
- “Poor communication.”
- “Inadequate techniques and tools for developing specification.”
(d) Two communication techniques include the Preliminary Meeting/Interview,
and
the Facilitated Application Specification Technique (FAST). Both share
many
common characteristics, in that they focus on simplistic understanding
of the
software and system at hand. Based on your understanding of both techniques,
and the larger problems of requirement analysis, describe why these
communication techniques can be important. [3]
|