Information Technology Reference
In-Depth Information
domain requirements. Domain analysis is a term used to describe the systematic
activity of identifying, formalizing and classifying the knowledge in a problem
domain. Problems of requirements elicitation can be grouped into three categories:
problems of scope, problems of understanding, and problems of volatility. Vali-
dating requirements is showing that the requirements properly define the system
that the customer wants. Then this chapter describes how to derive use cases from
the requirements. Creating use cases involves:
• Identifying all the different users of the system
• Creating a user profile for each category of user
Software Requirements Specification (SRS) consists of a complete description
of the external behavior of the software system. Finally, this chapter displays the
complete template of SRS.
5.9 Exercises
1. Specify which of these are functional and non-functional requirements:
• The ticket distributor must enable a traveler to buy weekly passes
• The ticket distributor must be written in java
• The ticket distributor must be easy to use
• The ticket distributor must always be available
• The ticket distributor must provide a phone number to call when it fails
2. Identify and briefly describe three types of requirements that may be defined
for a computer based system.
3. Describe types of non-functional requirements that may be placed on a sys-
tem. Give examples of each of these types of requirement.
4. Write a set of non-functional requirements for the ticket-issuing system.
Suggest how the engineer is responsible for drawing up a system requirements
specification and how they might keep track of the relationships between
functional and non-functional requirement.
5. Using your knowledge of how an ATM is used, develop a set of use-cases that
could serve as a basis for understanding the requirements for an ATM system.
6. Give
a
non-functional
requirement
that
can
be
handled
without
having
detailed knowledge about the target software product.
7. Distinguish between a use case and a use case diagram.
8. During requirement elicitation we try to reconcile domain knowledge
requirements and use case requirements. Explain the difference between these
two kinds of requirement. Should one of them take precedence over the other
in the requirement determination process? Give reasons why.
9. Describe the typical structure of a requirement specification document.
