Database Reference
In-Depth Information
Although information requirements are derived by observing business func-
tions and processes, the approach must be clearly data-oriented. In other words,
the emphasis is not on how the functions and processes are carried out but on
what data are required for performing the business functions and processes.
This is a new mind-set for analysts who had previously worked on designing and
deploying applications. In applications, you are designing the “how” of the
processes. But in a database system, you are designing the “what” of the data
requirements. So keep requirements definition for a database system data-oriented.
Come up with the elements of data required for each process and for each
function.
At the end of the phase, the analysts pull all the data requirements together and
consolidate them. This aggregation step eliminates any duplicate statements of
requirements and aggregates all data required for individual business objects. A
requirements definition document is produced to conclude the phase.
Requirements Gathering Methods
It may appear that the requirements definition phase is a formidable effort because
of its extreme importance. Many project teams think of the project as mainly con-
sisting of design and implementation. However, requirements drive these later
phases, and without properly defined requirements the phases that follow cannot
be successful. If requirements definition is so significant, are there standard methods
that can be applied universally?
Undoubtedly, each organization will have its own special requirements and these
special requirements may warrant innovative techniques. Nevertheless, most
requirements gathering methods follow a set pattern. You now know the purpose
of this phase and what is expected at the end of the phase. But how do you reach
the desired end and document the information requirements?
A summary list of the major standard methods follows. In the subsequent sub-
sections, we will elaborate on a few of the important ones.
Interviews.
This is a common technique. Personal interviews cannot be replaced by
other methods. Still, one-on-one interviews produce the best results.
Group sessions.
When it is convenient and desirable to meet a user group as a
whole, group sessions work well. Here you save time by not interviewing the people
in the group one by one.
Observation of processes.
The combination of all processes within an organiza-
tion makes up the entire business. So if you review each process beginning to end,
you will be able to get a handle on what information is needed at the several points
along the way.
Review of applications.
The current computer applications are used to run the busi-
ness now. These applications store, retrieve, and update data. The storage, retrieval,
and update techniques may not be satisfactory. That is one of the main reasons for
moving to a database system. However, much can be learned from the data ele-
ments used by the existing applications.
Search WWH ::
Custom Search