Work Product (Artifact): Implementation Element








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










Work Product (Artifact): Implementation Element















These artifacts 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.






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.



Relationships



RolesResponsible:



Implementer


Modified By:



Input ToMandatory:



Execute Developer Tests


Implement Developer Test


Integrate Subsystem


Optional:


None

External:


None





Properties



Optional


Planned



Tailoring



Representation OptionsUML Representation: Work product, possibly stereotyped as, for example, <<application>>, <<document>>, <<executable>>, <<file>>, <<library>>, <<page>>. File folders (directories) are represented as packages. See  Guideline: Implementation Element for modeling guidance. For examples of different kinds of Implementation Elements, and for guidance on how Implementation Elements should appear in visual models, see  Guideline: Implementation Element.



More Information



Guidelines


Compilation Dependency in Implementation


Testing and Evaluating Components








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







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