Guideline: Identify Technical Components
This guideline provides advice regarding considerations in identifying technical components.
Relationships
Related Elements
Main Description

Technical components have been described elsewhere, see Concept: Technical Component.  As that concept describes, technical components provide access to infrastructure services, such as logging, authentication, and reporting.  They often are independent of business domain, and thus they will be used broadly within service implementations.

Technical components often can be found in third-party or pre-existing in-house component libraries that offer support for the needed technical capabilities. 

In cases where you need to implement support for a technical capability yourself, standard OOAD approaches or guidance from IBM Rational's Component Software Architecture practice can be used to identify and design these components.  Given that technical components cut across business domains, it is likely that others will eventually want to reuse any technical componentry that you create.  Because of this, new technical components are best identified and created according to a governance process that is akin to what is used (or, what needs to be used) to drive an organizational-level service initiative.

More Information