Database Reference
In-Depth Information
A3.9 Summary and Concluding Remarks
Here is a summary of what we have covered in this Chapter:
•
It is important to conduct a research on the requirements of a
software system to be developed. By so doing, we determine the
synergistic interrelationships, information entities, operations,
business rules, and security mechanisms.
•
In conducting the software requirements research, obtaining
answers to questions commencing with the words WHAT,
WHERE, HOW, WHEN and WHY is very important.
•
Information gathering strategies include interviews,
questionnaires and surveys, sampling and experimenting,
observation and document review, prototyping, brainstorming
and mathematical proofs.
•
The interview is useful when the information needed must be
elaborate, or clarification on various issues is required. The
interview also provides an opportunity for the software engineer
to win the confidence and trust of clients. In preparing to conduct
an interview, the software engineer must be thoroughly prepared,
and must follow well-known interviewing norms.
•
A questionnaire is viable when any of the following situations
hold: A small amount of information is required of a large
population; the time frame is short but a vast area (and/or
dispersed population) must be covered; simple answers are
required to a number of standard questions. The software
engineer must follow established norms in preparing and
administering a questionnaire.
•
Sampling is useful when the information required is of a
quantitative nature or can be quantified, no precise detail is
available, and it is not likely that such details will be obtained
via other methods. The software engineer must be familiar with
various sampling techniques, and know when to use a particular
technique.
•
Review of source documents will provide useful information
about the input, data storage, and output requirements of
the software system. This activity could also provide useful
information on the processing requirements of the software
system.
•
Prototyping involves providing a trial model of the software for
user critique. User responses are used as feedback information to
revise the system. This process continues until a software system
meeting user satisfaction is obtained. The software engineer
should be familiar with the different types of prototypes.
