User Requirements

Home
Members
Schedule
Archive
Search
Discussions
Contact Information
Members data area

User Requirements

Purpose

To completely and unambiguously define the functionality of the system from a users perspective, that is the interactions and functional requirements required to use (ATC including the MOD), operate and maintain (the Asset Operators), and manage (the Asset Manager) the facilities and supporting equipments.

To provide requirements that will be used to define, implement and measure the performance of the delivered system(s) from a User’s perspective.

The User Requirements are to be defined in terms of the minimum functionality that is necessary to safely and efficiently perform each role.

Derivation and Source Requirements

The User Requirements will be derived from the Concept of Operations to support the Cardinal Point Specification.

Composition

The User Requirements will define the User’s requirements for:

·       ATC including, AC, TC, MOD.

·       Asset Operators including Logistics,

·       Asset Manager.

For each group of Users the Users requirements will define all the functionality that is necessary for the User to successfully perform their role.  This includes:

·       User functionality

·       Required information from the System.

·       Systems reaction and response times to inputs and external events.

·       Human Machine Interfaces.

·       The User’s roles and any specific functionality for each role.

Quality Criteria

Do the User Requirements support and align with the relative Concept of Operations?

Do the User Requirements support and align with the Cardinal Point Specification?

Are the requirements defined to an appropriate level of detail, not too much or not too little?

Do the requirements support the procurement strategy, that is do they support the procurements of a COTS system?

Are the requirements clearly measurable in terms of well defined and credible success criteria?

Are the requirements SMART requirements, which are specific, measurable, achievable, realistic and timely?

Are the User Requirements achievable within the schedule and costs constraints?

Quality Method and Skills

The User Requirements will be developed in conjunction with representatives from each User Group. They will be reviewed collectively to ensure that the requirements are unambiguous and consistent.

The VCRI will be updated as part of the development of the User Requirements to identify which system the requirements will be applied and provide assurance that the requirements can be met.

The User Requirements will be reviewed by the Project Team to ensure traceability into the Project’s design documentation and specifications.

Home | Members | Schedule | Archive | Search | Discussions | Contact Information | Members data area

 (c) Safeflight.co.uk
Last updated: 07-08-2005.