Requirements Definition

If you don’t know what your users need, then how are you going to deliver it to them?  A clearly articulated requirements definition is of significant benefit to an organization embarking on the development of an identity solution. A requirements definition should clearly outline the business context in which the system will be used, the functional requirements of the system and any organizational policies that need to be adhered to. Once completed, the requirements definition can be used as input into the solution architecture and can act as the basis for testing the solution once developed.
Typically requirements definitions are integrated into readiness assessments or as preparatory work for solution architectures and designs. However, they can be executed independently.

A thorough Requirements Definition includes:

• A definition of the business context and business requirements;
• Identification of the specific use-cases as dictated by the business requirements;
• A concise statement of the functional requirements for the system; and
• A description of the technical requirements that must be adhered to comply with organization IT Standards and Policies.

The benefit of Avaleris’ Requirements Definition service offering is a clear statement of the organization’s business needs and the technical constraints within which a solutions architecture must address. The requirement definition can also serve as basis for a pilot’s evaluation criteria.