Demonstration
A
demonstration is the
quality engineering
technique modeling the execution of a [partially complete]
application or prototype in order to obtain feedback from the
audience.
People can often understand an executable work product
easier by seeing it demonstrated than by sitting through a
presentation or reading documentation.
The typical objectives of a demonstration are to:
- Inform the audience of the current state and capabilities
of the application or prototype.
- Obtain feedback from the audience (e.g., new requirements
and defects identified).
Demonstrations can typically begin when the following
preconditions hold:
- The work product can be execute.
- The work product does not contain any defects that would
prevent a successful demonstration.
- The audience is available for the demonstration.
Demonstrations are typically complete if the following
postconditions hold:
- The demonstration has been successfully held.
- Audience feedback has been captured.
During demonstrations, the following producers typically
perform the following steps:
- The development team
- Ensures that the application or prototype is ready to
be demonstrated (i.e., is without significant
defects).
- Determines the purpose of the demonstration (e.g.,
determines the questions they would like answered by the
audience).
- Determines the audience of the demonstration.
- Obtains facilities in which to hold the
demonstration.
- Schedules the demonstration.
- Informs the audience of the location, time, date, and
purpose of the demonstration.
- Prepares the application or prototype for the
demonstration.
- Demonstrates the application or prototype to the
audience.
- Answers audience questions, and asks the audience
questions.
- Collect and record the audience's feedback.
- The audience members:
- Provide their feedback to the development team.
Demonstrations typically produce all or part of the
following work products:
Demonstrations are typically subject to the following
limitations: