![]() |
subject > system > prototype > paper prototype |
![]() ![]() | ||||
paper prototype | ||||
subject | fact |
paper prototype | has definition A set of pictures of a system used to demonstrate how the system would work if implemented | ![]() |
has benefit can often be a very powerful tool for eliciting ideas and feedback | ![]() | |
has benefit very easy to create | ![]() | |
has purpose to show to customers and users in sequence, to explain what would happen when the system runs | ![]() | |
is ideal for parallel development | ![]() | |
is a subtopic of 4.6 - Some Techniques for Gathering and Analyzing Requirements | ![]() | |
is a kind of prototype | ![]() | |
represents the user interface of a system | ![]() | |
prototype | may be developed using a rapid prototyping language | ![]() |
may not perform any computations | ![]() | |
should be produced early to get a view of potential problems | ![]() | |
should not be turned into the final system since it will be hard to maintain, and will contain many bugs | ![]() | |
usually contains part of the system's eventual functionality | ![]() | |
system | can have specification which is then implemented by a collection of components | ![]() |
exists even if its components change over the course of time, or are replaced by equivalent components | ![]() | |
has scope | ![]() | |
has part component | ![]() | |
has part hardware | ![]() | |
has part module | ![]() | |
has part software | ![]() | |
has part subsystem | ![]() | |
is divided up into subsystems | ![]() |
Up: prototype