Reference and guide to SFIA version 7. Framework status: Development. Show revision-marked text

Requirements definition and management REQM

(modified)

The elicitation, analysis, specification and validation of functional and non-functional requirements and constraints to a level that enables effective development and operations of new or changed software, systems, processes, products and services. The management of requirements throughout the whole of the delivery and operational life cycle of the software, system, processes, products or service. The negotiation of trade-offs that are both acceptable to key stakeholders and within budgetary, technical, regulatory, and other constraints. The adoption and adaptation of requirements management lifecycle models based on the context of the work and selecting appropriately from plan-driven/predictive approaches or more adaptive (iterative and agile) approaches.

Requirements definition and management: Level 6

(modified)

Develops organisational policies, standards, guidelines and quality targets for requirements definition and management. Champions the importance and value of requirements management principles and the selection of appropriate requirements management lifecycle models. Develops new methods and organisational capabilities and drives adoption of and adherence to policies and standards. Plans and leads scoping, requirements definition and priority setting for complex, strategic programmes.

Requirements definition and management: Level 5

(modified)

Plans and drives scoping, requirements definition and prioritisation activities for large / complex initiatives. Selects, adopts and adapts appropriate requirements definition and management method, tools and techniques selecting appropriately from plan-driven/predictive approaches or more adaptive (iterative and agile) approaches. Obtains input from and formal agreement to requirements from a diverse range of stakeholders. Negotiates competing priorities and conflicts. Establishes the requirements baseline. Ensures changes to requirements are investigated and managed. Contributes to the development of organisational methods and standards.

Requirements definition and management: Level 4

(modified)

Contributes to selection of the requirements approach for projects, selecting appropriately from plan-driven/predictive approaches or more adaptive (iterative and agile) approaches. Defines and manages scoping, requirements definition and prioritisation activities for initiatives of medium size and complexity. Facilitates input from stakeholders, provides constructive challenge and enables effective prioritisation of requirements. Reviews requirements for errors and omissions. Establishes the requirements base-line, obtains formal agreement to requirements, and ensures traceability to source. Investigates, processes and applies requests for changes to base-lined requirements.

Requirements definition and management: Level 3

(modified)

Defines and manages scoping, requirements definition and prioritisation activities for small scale changes and assists with more complex change initiatives. Follows agreed standards to elicit and document detailed requirements using the most appropriate techniques. Provides constructive challenge to stakeholders as required. Prioritises requirements and documents traceability to source. Reviews requirements for errors and omissions. Inputs to the requirements base-line. Investigates, processes and applies requests for changes to base-lined requirements.

Requirements definition and management: Level 2

(modified)

Assists in the definition and management of requirements. Uses standard techniques to elicit, specify and document requirements for simple subject areas with clearly-defined boundaries. Supports the creation of a requirements baseline. Investigates, processes and applies requests for changes to base-lined requirements