Analysis
Requirements
Design
Data Migration
Installation
Training
Support

Requirements elicitation

• Complete requirements capture at the stakeholder level
• Optimised requirement set based on analysis results
• Fully defines the desired end result
• Easy to understand basis for future contract

Everyone who has a stake in the proposed project is identified so that their needs can be addressed. This can range from managers and budget-holders to end-users and data entry clerks. We determine what each of them wants to experience at the completion and therefore elicit their requirements. Similar systems and existing documentation can yield further requirements. A basis for a requirements trade-off process is formed by using the results of the analysis previously completed. An optimum cost-effective set of requirements is developed and documented.

Our goal is to specify software capability that delivers business benefits while remaining within reasonable cost, time and resource limitations.

The stakeholder requirements (or user requirements) document is a complete definition of what the stakeholders need expressed in a simple language. Each separate requirement is clearly written in a single sentence so that it can be easily tracked throughout development. Each requirement is written so that a measurable test can verify it has been satisfied. When the final system is delivered this document is used to ensure that all the requirements have been satisfied.

Copyright © 2005 Archway Electronics Ltd