|
This my (Dirk Bade @UFC or GYPSC::BADE coordinating germany's AI-CC)
feedback to the document:
DPM Techniques - Software Prototyping
Document-ID TEC-02-0 Rev A 10-OCT-1990
The overall impression is good, table of contents acceptable, index missing.
Page Statement
1.1 close collaboration between user and developer...
comment: the third party is the people who ordered the project !
Often the system to be developed is wanted by a central
function in order to let it run in distributed subfunctions
which may have a different vision.
1.1 dynamic specification
comment: we consider prototypes to be integral part of the design phase
and therefore become a component of the final specification
1.4 use of artificial intelligence techniques
comment: AI is neither a risk factor nor gold plating - if not
used in the wrong place. Our experience from standard project
with integrated AI components (OPS5) is that the AI-modules
allow modifications to be performed in a much safer way than
e.g. modules in C-code.
1.5 3 prototypes
2.6 with minimum functionality
comment: we just talk of horizontal and vertical prototypes.
horizontal prototypes implement just one layer (e.g. the user
interface) while vertical prototypes implement a cut through
the whole application (e.g. starting from the user interface
with typical database access, work on a typical data set
and final output to screen and/or database). Vertical prototypes
can eliminate performance concerns, while horizontal prototypes
are done to prove the right understanding of the whole
application. Both can be evolutionary.
2.1 extensive prototyping is wasted effort if the required
functionality is clearly understood.
comment: no. prototypes can be used to test the acceptance with the
end users and that way test the feasibility of the whole project.
2.5 project team separates..
comment: the prototyping team should be as small as possible.
One full-time specialists preferred to many part-time assignments.
3.1 user must commit... developer must ensure... manager must provide
comment: this is certainly necessary but sounds like wishful thinking.
In praxi, the participants will only collaborate if their
acceptance was carefully tested and stays alive. This is
best obtained if the prototype remains as close as possible
to ready-for-demo state throughout its development. Vertical
prototypes are best suited for that purpose.
|