ContentsApplication DesignDesign parameters

Previous: Application Design | Next: Functional

Design parameters are the definition of the goal your application is striving for. All too often, the developer and the sponsor have very different ideas about what is trying to be accomplished. These differences need to be worked out as early as possible. In an ideal world, they would be resolved before any coding.

More often than not, however, it is necessary to at least develop a prototype before everyone can agree on what should be delivered. The prototype should get the idea across, address the basic design parameters, and give everyone a place to start their criticism.

In our example of a chart of salary history against the cost of living, many assumptions have been made. This example is being built without the benefit of end user input, so it represents a prototype at best. Prototypes are a great place to start for any application. They have one clear goal: to get something working.

Design parameters should be clearly defined and prioritized. If they are, the decisions we face are easier. If they aren't, the decisions may not be any better than educated guesses.

There are three types of design parameters, each of equal importance at some point.

ContentsApplication DesignDesign parameters

Previous: Application Design | Next: Functional