Requirements Evaluation Team

Definition

Requirements Evaluation Team

the team that evaluates the deliverable application development requirements work products and the processes by which they are developed

Classification

As illustrated in the preceding figure, Requirements Evaluation Team is part of the following inheritance hierarchy:

• Type: Concrete
• Superclass: Evaluation Team
• Subclasses:
  • None

Responsibilities

The typical team-specific responsibilities of a Requirements Evaluation Team are to:

• Evaluate the deliverable requirements work products.
• Notify the requirements team of any defects found.
• Recommend improvements to the process regarding:
  • The requirements engineering activity and tasks.
  • The standards, templates, and evaluation checklists for the deliverable requirements work products

The Requirements Evaluation team typically inherits the common team responsibilities from the team method component.

Roles

The Requirements Evaluation team typically consists of persons playing one or more of the following roles:

• Technical Leader, who facilitates the inspection meeting and evaluates the requirements work products for technical quality.
• Project Manager, who evaluates the requirements work products for impact on schedule and cost.
• Metrics Analyst, who evaluates the requirements work products for impact on schedule and cost.
• Domain Expert, who evaluates the requirements work products for correctness and completeness.
• Business Strategist, who evaluates the requirements work products for conformance to the business strategy.
• Security Analyst, who evaluates the requirements work products for security defects.
• User Analyst, who evaluates the requirements work products for usability defects.
• Database Architect, who evaluates the requirements work products for database feasibility.
• Security Architect, who evaluates the requirements work products for security feasibility.
• Hardware Architect, who evaluates the requirements work products for hardware feasibility.
• Software Architect, who evaluates the requirements work products for software feasibility.
• System Architect, who evaluates the deliverable requirements work products for system feasibility.
• Test Engineer, who evaluates the requirements work products for testability.
• Process Engineer, who evaluates the requirements work products for conformance to the associated standards and inspection checklists.
• Quality Engineer, who evaluates the requirements work products for quality and conformance to the relevant conventions.
• Technical Writer, who acts as scribe at the inspection meeting, summarizes the inspection team’s findings in the inspection summary report, and delivers the report to the requirements team.

Tasks

The Requirements Evaluation team typically performs the following team-specific quality engineering tasks in an iterative, incremental, parallel, and time-boxed manner:

• Requirements Evaluation:
  Inspect the requirements work products:
  • Application Vision Statement
  • Requirements Executive Summary
  • System Requirements Specification
  • External API Specification
  • Glossary
  • Domain Model Document

The Requirements Evaluation team typically inherits the common team tasks from the team method component.

Work Products

The Requirements Evaluation team typically produces all or part of the following quality engineering work products:

• Inspection Report, which documents an individual inspector’s findings.
• Inspection Summary Report, which summarizes the finding of the entire inspection team.

Guidelines

• Inspections should not devolve into walkthroughs. The work products should stand on their own.
• To the extent practical, the developers of a work product should:
  • Not be the only evaluators of it.
  • Also informally evaluate it prior to the evaluation.
• The Requirements Evaluation team typically inherits the common team guidelines from the team method component.