Design Document: Identifying Functional Requirements

Unless the site is just straight text and images (which is not very engaging) it is likely to include some function(s). Functions can be things like guest books, hit counters, input forms and other more complex transactional elements such as database connectivity and shopping carts. From the master content inventory you should be able to identify what functional requirements the site is supposed to have. From this you will create a list of the functional requirements of the site.

In order to achieve the goal of providing a searchable database of owner manuals, a database of that information will have to be built and a way of searching that database (perfoming a query) and displaying the results will have to be created.

An important point to remember about a web sites functional requirements is that functionality can introduce various levels of complexity to your site. It is extremely important that you carefully review what the expected functional requirements are and ask yourself these questions.

• Is it feasible?
• Do you have the technology?
• Do you have the skills?
• Do you have the time?
• Do you have the money?
• Can you buy it?
• Can you build it?

Rank the importance of each requirement - Remember, you have a deadline to maintain.