Artifacts > Implementation Artifact Set > Component


Component

A component represents a piece of software code (source, binary or executable), or a file containing information (for example, a startup file or a ReadMe file). A component can also be an aggregate of other components; for example, an application consisting of several executables.
UML representation: Components, possibly stereotyped as, for example, «application», «document», «executable», «file», «library», «page», «table» or «test component»
Role: Implementer
Optionality: Use of any of the stereotypes is optional.

Input to Activities:
  • Fix a Defect
  • Integrate System
  • Perform Unit Tests
  • Review Code
Output from Activities:
  • Implement Component
  • Fix a Defect
  • Perform Unit Tests






Templates, Case-Study, Report.. To top of page

The Word template can be bought through a template package. Case studies and reports are freely available in the table below.

Word
Template
Case
Study
Report
--- ---

Purpose To top of page

A component represents a physical asset of the development process: files of some sort that contain source, configurations, executables, and other physical products of development.

Properties To top of page

Property Name

Brief Description

UML Representation

Name Component name The attribute "Name" on model element

Timing To top of page

Components may be created in the Inception Phase during the creation of User Interface Prototypes; though this is relatively minor. Architecturally significant components are created in the Elaboration Phase as the architectural prototypes are developed. Remaining components are created in the Construction Phase. Components are updated during the Transition Phase as defects are found and fixed.

Responsibility To top of page

An implementer is responsible for the component, and ensures that:

  • The component implements the corresponding design correctly, and fulfills the design specifications.
  • The component is readable.
  • Source code files are unit tested.

Tailoring To top of page

The type of component to use depends on the programming language and the implementation environment in general. For examples of different types of components.

Feedback © 2014 Polytechnique Montreal