Role: Implementer







var defaultQueryStr = '?proc={F2AD342D-0F3B-4E19-A351-75ECDCB806F5}&path={F2AD342D-0F3B-4E19-A351-75ECDCB806F5},{26723872-54F2-48C0-8384-0F595BD86EAD},_CR-7gRi2Edq_uI8xTPML6g';
var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=null;
contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, false, true, false);










Role: Implementer















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






Relationships



Performs:


Execute Developer Tests


Implement Developer Test


Responsible for:


Developer Test


Implementation Element


Implementation Subsystem





Additionally Performs:Modifies:


Developer Test


Test Log






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].



Properties



Multiple Occurrences


Optional


Planned



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


RUP/XP Guidelines: Pair Programming


RUP/XP Guidelines: Test-first Design and Refactoring





Whitepapers


Developer Testing


Mapping from Design to Code


Runtime Observation & Analysis


RUP/XP Guidelines: Pair Programming


RUP/XP Guidelines: Test-first Design and Refactoring








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







contentPage.onload();
contentPage.processPage.fixDescriptorLinks();