
Overview of the Phase
The functional and performance requirements flow on from the Feasibility Study and mirror the Concept Brief with more specific outcomes. A detailed list of the project parameters are compiled either by the Project Manager or the client or as a joint activity.
Requirements define what is to be designed, built and implemented, and they are gradually refined throughout the duration of the project. It is necessary to analyse the requirements that must be met in order to develop the product and create a set of criteria for the management, evaluation, and delivery components against which they will be measured. These typically include as complete as possible information about detailed tasks, user profiles, learning objectives, resources, content in greater detail, interface design, hardware, software, level of interaction and the general look and feel of the product. As the list of requirements may change during the life of the project, the requirements specifications should be general and flexible at this stage. An evaluation strategy plan, quality control, review budget and a mechanism to incorporate changes should also be included.
The importance of documenting the specifications cannot be overstated as they serve as the blueprint for the project. The specifications act as targets for designers, assisting them to determine whether the system will support the user, given constraints on cost and resources.
|
|