The Software Development Life Cycle - Software Testing: Testing Across the Entire Software Development Life Cycle - page 49

prepare a table such as the one pictured in Table 2.3. The alternative designs occupy the
columns, and the rows address the relevant points. Sample entries illustrate how each
alternative design is evaluated and how notes are made of questions to be answered.
The last row contains the user choice and the rationale that supports that choice.

Table 2.3 Alternative designs evaluation table

Alternative 1 GUI
interface and access
back end

Alternative 2 Web
interface and access
back end

Alternative n Web
interface and oracle
back end

Key features Custom-tailored

interface to user needs
Good relational
database model

Advantages Developers

knowledgeable in
technology

Relational database
with capacity for
future expansion

Disadvantages Relational database

with limited capacity
for future expansion

Questions Will this configuration

be sufficient in
meeting user current
and future needs?

Could firm
outsource oracle
implementation?

User choice This alternative

preferred based
primarily on
functionality and
ability to meet target
cutover date

This is only one of many possible approaches to feasibility evaluation. Other ap-
proaches can evaluate the systems based on how well each meets the goals specifi ed
in the goal analysis form, employ quantitative evaluations of weighted criteria, and
so forth. [15]

2.7.3 Conduct JAD Sessions to Confirm Designs
and Evaluations

The developers meet with the business owner managers and senior business users to
confi rm that all of the feasible designs were considered and that each was thoroughly