![]() |
subject > system > prototype |
![]() ![]() | ||||
prototype (pilot system) | ||||
subject | fact |
prototype | is a synonym of pilot system | ![]() |
has definition A version of a system created primarily to learn more about the requirements, and not intended to be the final product | ![]() | |
has benefit it is easily modified many times in response to feedback from users | ![]() | |
has purpose to gather requirements by allowing software engineers to obtain early feedback about their ideas | ![]() | |
is a subtopic of 1.8 - The Eight Themes Emphasized in this Book | ![]() | |
is a subtopic of 4.6 - Some Techniques for Gathering and Analyzing Requirements | ![]() | |
is a kind of system | ![]() | |
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 complex if its scope is broad | ![]() | |
is in a state until an event occurs that causes it to change state | ![]() | |
is divided up into subsystems | ![]() |
Kinds of prototype :
Next system: safety critical system Up: system Previous system: object oriented system