Share via


The Design Process

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The first thing that you must do when you begin designing an application is to identify your customers. Who will be using the application? It might be just one person, a small workgroup within your company, or an entire department. Perhaps you are a consultant building custom applications for other companies. Maybe you are building Office-based applications to package and sell through a retail outfit or over the Internet. Whoever your customers are, you should have a thorough understanding of their business processes and their requirements before you begin building your application.

In This Section

  • What Do Your Customers Want?
    The first step in the design process is to get a clear idea of what your customers want. This can take some time and patience, especially if your customers are not technical people by nature.
  • What Do Your Customers Need?
    What your customers want and what your customers require are not always the same thing.
  • At the Drawing Table
    When you have gathered as much information as you can from your customers, sit down with a pencil and paper, and sketch out the initial design for the application — the technologies to be used, the user interface, and the organization of the code.
  • Building a Prototype
    For most Microsoft® Office XP applications, you are not required to build a full-fledged prototype — the application you are building can act as the prototype you show to your customers.