Role: Implementer

Role: Implementer

This role develops software components and performs developer testing for integration into larger subsystems, in accordance with the project's adopted standards.

Role Sets: Developers

Relationships


Modifies	Implementation Element Implementation Subsystem Developer Test Test Results Test Log
Process Usage	Implementation > Implement Components > Implementer Implementation > Integrate each Subsystem > Implementer

Main Description

The implementer role is responsible for developing and testing components, in accordance with the project's adopted standards, for integration into larger subsystems. When test components, such as drivers or stubs, must be created to support testing, the implementer is also responsible for developing and testing the test components and corresponding subsystems.

Further Reading

See Code Complete - A Practical Handbook of Software Construction [MCO93].

Staffing

Skills

The appropriate skills and knowledge for the implementer include:

knowledge of the system or application under test
familiarity with testing and test automation tools
programming skills

Assignment Approaches

An implementer may be assigned responsibility for implementing a structural part of the system (such as a class or implementation subsystem), or a functional part of the system, such as a use-case realization or feature.

It is common for a person to act as both implementer and designer, taking on the responsibilities of both roles.

It is possible for two persons to act as the implementer for a single part of the system, either by dividing responsibilities between themselves or by performing tasks together, as in a pair-programming approach.

More Information

Concepts	Developer Testing Mapping from Design to Code Runtime Observation & Analysis
Whitepapers	RUP/XP Guidelines: Test-first Design and Refactoring RUP/XP Guidelines: Pair Programming

© Copyright IBM Corp. 1987, 2006. All Rights Reserved.