Hardware Evaluation Team
- Hardware Evaluation Team
- a team that performs evaluates the deliverable
hardware design, implementation, and testing work products and the processes that were used to perform them
As illustrated in the preceding figure, Hardware Evaluation Team is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Evaluation Team
- Subclasses:
The typical team-specific responsibilities of a Hardware Evaluation Team are to:
- Evaluate the hardware design document.
- Evaluate the hardware components.
- Evaluate the related test work products.
The hardware evaluation team typically inherits the
common team responsibilities from the
team method component.
The hardware evaluation team typically consists of persons playing the following roles:
- Technical Leader,
who facilitates the evaluation meeting and evaluates the hardware design and components for technical quality.
- System Architect,
who evaluates the hardware design for quality and conformance to the system architecture.
- Hardware Architect,
who evaluates the hardware design for quality and conformance to the hardware architecture.
- Hardware Engineer,
who evaluates the hardware components for the quality of the implementation.
- Test Engineer,
who evaluates the hardware components for adequate unit and integration testing.
- Quality Engineer,
who evaluates the work products for quality and conformance to the endeavor process and relevant conventions.
- Technical Writer,
- Acts as scribe at the evaluation meeting(s).
- Summarizes the evaluation team’s findings in the
evaluation summary report.
- Delivers the evaluation summary report to the:
The hardware evaluation team typically performs the following
team-specific tasks in an incremental, iterative, parallel, and time-boxed manner:
The hardware evaluation team typically inherits the
common team tasks from the
team method component.
The architecture evaluation team typically produces the following work products:
- Evaluations should not devolve into walkthroughs that require the work products’ developers
to explain them to the evaluators. 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 inspect it prior to the evaluation.
- A single person may play multiple roles on an evaluation team if
he or she has the necessary expertise to fulfill multiple roles.
This is especially true on small endeavors.
- An architecture evaluation team typically inherits the
common team guidelines from the
team method component.