Artifact: Implementation Element

	Implementation Elements are the physical parts that make up an implementation, including both files and directories. They include software code files (source, binary or executable), data files, and documentation files, such as online help files.
Other Relationships:	Part Of Implementation Model
Role:	Implementer
Optionality/Occurrence:	Use of any of the stereotypes is optional.
Templates and Reports:
Examples:
UML Representation:	Artifact, possibly stereotyped as, for example, <<application>>, <<document>>, <<executable>>, <<file>>, <<library>>, <<page>>. File folders (directories) are represented as packages. See Guidelines: Implementation Element for modeling guidance.
More Information:	Guideline: Compilation Dependency in Implementation Guideline: Implementation Element Guideline: Testing and Evaluating Components
Purpose Properties Timing Responsibility Tailoring

Input to Activities:  Analyze Runtime Behavior Execute Developer Tests Implement Design Elements Implement Developer Test Implement Testability Elements Integrate Subsystem Plan Subsystem Integration Review Code

Output from Activities:  Implement Design Elements

Purpose

Implementation Elements are parts of an implementation, specifically the lowest level units of physical composition, replacement, version control and configuration management. They include software code files (source, binary or executable), data files, and documentation files, such as online help files.

Properties

Timing

Implementation Elements may be created in the Inception Phase during the creation of proof-of-concept prototypes. Architecturally significant Implementation Elements are created in the Elaboration Phase as the architectural prototypes are developed. Remaining Implementation Elements are created in the Construction Phase. Implementation Elements are updated during the Transition Phase as defects are found and fixed.

Responsibility

An Implementer is responsible for the Implementation Element, and ensures that:

• Source files implement the design element(s) correctly and follow project coding guidelines.
• Derived files (such as executables) are derived from the right versions of source files.
• Files and directories are organized in accordance with project guidelines.
• Implementation Elements are versioned and delivered in accordance with project guidelines.

Tailoring

For examples of different kinds of Implementation Elements, and for guidance on how Implementation Elements should appear in visual models, see Guidelines: Implementation Element.

Rational Unified Process