Professional Documents
Culture Documents
Introduction
We have traditional requirements determination methods, like: interviewing, using
questionnaires, observing users in their work environment, and collecting procedures and
other written documents. And we have modern methods for collecting system requirements
(computer aided ones), like: joint requirements planning (JRP), group support systems, CASE
tools, discovery prototyping.
Performing requirements determination
Information on what the new system should do is gathered from as many sources as possible:
users of current system, from observing users, from the reports, forms and procedures. All this
is documented and made ready for structuring.
Main characteristics of a good systems analyst:
-
impertinence (ask questions about everything that exists and also about what may exist in
the future),
impartiality (find the best solution to a business problem or opportunity consider issues
raised by all parties),
relax constraints (eliminate unfeasibility, assume that anything is possible, traditions may
not always be reasonable),
attention to details (everything must fit together so that the system works properly),
The primary deliverables from requirements determination are various forms of information
gathered during the determination process: transcripts of interviews, notes from observations
and analysis of documents, analyzed responses from questionnaires, sets of forms, reports, job
descriptions, or computer-generated output such as system prototypes. We could group all this
information in three groups:
-
and informal systems (procedures) should be considered. Business forms are also very
useful (what data flow in and out of the system, what kind of data and which are
necessary). Report generated by current system may also be useful. If the current system
is computer-based than we may use: flow charts, data dictionaries, CASE tool reports,
user manuals.
Modern methods for determining system requirements
Main idea behind JRP is to bring together the key users, managers and systems analysts
involved in the analysis of the current system (similar to group interview). But JRP follows a
particular structure of roles and agenda, which enables to collect systems requirements from
all the key people simultaneously. Typical participants:
-
users key users of the system, who know the most about it
managers they provide insight into new organizational directions, motivations for the
system
system analysts they are there to learn from users and managers, and not to dominate the
process
IS staff other staff like programmers, or database analysts (they know some technical
limitations or ideas)
JRP sessions are usually held in special rooms with special equipment. Upper CASE tools can
be used during JRP (diagramming tools, display and report generation tools) in order to give
graphic form to system requirements, show it to users and make changes based on their
reactions. Also prototyping tools are good for presenting users with graphic illustrations of
what the alternative systems will look like.
Also group support systems may be used to support JRP sessions (because there are some
typical group meeting problems). Instead of giving everyone a few minutes to talk all
members of the group type their comments into computers and may see what everyone else
has been typing, but the comments are anonymous so bosses can also be criticized. Pros:
everyone has a chance to say something, important ideas are less likely to be missed, and
poor ideas more likely to be criticized. Cons: leader has lower ability to resolve conflicts and
the session may become less structured.
Discovery prototyping allows to quickly convert basic requirements (obtained during i.e.
interviews) into a working, though limited version of the desired information system. The
prototype will then be viewed and tested by the user and changes will be introduced. And this
will be repeated until all concrete specifications for the ultimate system are developed.
Prototyping is mostly useful when:
-
Questions:
1. Name four traditional techniques for collecting information during analysis. Give the
advantages and disadvantages of each method.
2. What is JRP and who takes part in a JRP session?
3. How has computing been used to support JRP?
4. What benefits do GSS provide?
5. Which type of CASE tools are appropriate for use during requirements determination?
6. What are the advantages and disadvantages of discovery prototyping?