[next | previous |return]

3.   Specifications

Once we have agreed upon the scope of work and contract rates, we send out the consulting agreement for your signature, and schedule a more in-depth meeting to define the functional specifications for the project. Working with you, we develop the Functional Specifications document and Project Plan.

Functional Specifications

This document outlines the goals, stakeholders and required functionality of the software or web site, and often includes use cases which detail what steps a user would take in order to accomplish a specific task on your site or software.

For example, a use case for logging in to a membership area on a site might read as follows:

1. Correct Login:
   • Login Screen displays text fields for username and password.
   • User enters correct username and password, and presses SUBMIT button.
   • System authenticates user and presents them with a welcome screen.
2. Incorrect Login:
   • Login Screen displays text fields for username and password.
   • User enters incorrect username and password, and presses SUBMIT button.
   • System returns an error message and prompts user to try again.

Project Plan

The project plan details the steps involved in the project, from requirements gathering to development to test and release, and outlines the time allocated for each step in the process. Major milestones are assigned due dates, which are agreed upon in advance by all parties. The project plan is developed based on an initial set of requirements, and may be modified down the road if the project requirements or scope of work change. All modifications to the project plan are documents and signed off by key stakeholders.

What's in a Name?

... (the) name of Yalia (denotes) a quick-minded, sensitive nature. It gives you a creative ability in art, music, singing, or fancywork and an appreciation for refined surroundings. [more]

Hit REFRESH (F5) for another article tidbit, or click here to see all articles.