| <<< Design patterns | Index | CRC Cards Example >>> |
For a large systems, it is ideal to have a somewhat smaller, related working system, known as prototype.
Very successful when done well, a prototype approach is:
a scaled-down version of the system or a part of the system,
using reduced performance criteria,
enabling exploration of design and implementation choices,
invaluable when designing a user interface.
Danger of having the prototype become a product:
if design effort is not invested in the internal structure of the prototype, it could become
a maintenance nightmare while giving the illusion of an "almost complete" system,
an example of system of poor efficiency and scalability,
time and energy burner while that could have been better spent on the product.
Throw a prototype away before it becomes a burden!
| <<< Design patterns | Index | CRC Cards Example >>> |