DESIGN

Models can now be produced by developers to understand what the system should finally look like. Ideas or components that were previously discussed can be included or completely discarded.

Once a selection of models have been designed and developed, a system description is written, it does not mention specifics. It may state the type of interface or operating system, but not any particular brands. There is an opportunity to make changes if there are any problems or mistakes which surface, further into development could prove expensive and could cause delays. The written document helps communication between the developer and the client, it ensures that the final system is consistent with the original goals and specifications set out in the terms of reference.

The designs and descriptions can be reviewed by all parties to ensure that everything has been included and is agreed upon. A prototype model of the system may be built for the client to explore. We have a general description of the system, without naming specific details or information.