Login  ·  Register

TRAK Community  ::  Wiki  ::  TRAK:EVp-02 Capability Hierarchy Viewpoint
Search Wiki  
  

Enterprise Architecture

Navigation - General

Keep Up to Date

Active Members:

Search:

 

Create or Find Page:

 

View TRAK:EVp-02 Capability Hierarchy Viewpoint

TRAK_logo_60.jpg

Title

EVp-02 - Capability Hierarchy Viewpoint

Version

7

Date

2nd March 2011

Overview

The EVp-02 - Capability Hierarchy Viewpoint is part of the Enterprise Perspective and one of the 21 TRAK Architecture Viewpoints.

It provides a way of describing the enduring capabilities needed to meet the enterprise’s goals and the dependencies between them. It also provides the means to create a hierarchy or taxonomy structure from capabilities.

It is the specification for the TRAK::EV-02 Capability Hierarchy architecture view.

Stakeholders Addressed

  • Builder of Enterprise
  • Developer of Enterprise
  • Maintainer of Enterprise
  • Owner of Enterprise

evp02StakeholderConcern_400.jpg
Full size:File:evp02StakeholderConcern 589.jpg

Concerns Addressed

What are the enduring capabilities the enterprise requires? How is capability measured?

Covered by TRAK IPR and licenses

Description

Describes the capabilities required by the Enterprise / Enterprise Goal(s) and dependencies on other Capabilities.

Covered by TRAK IPR and licenses

It helps to keep the Capability name short and atomic since this makes it easy for re-use and you can then see what other Systems realise the same Capability or what enterprises share the same capability.

Although a capability is a form of activity it helps to avoid adding a common prefix like ‘To be able to’ - which might be a temptation for those that recognise what ‘TUSBAT’ stands for ;-)

Mandatory Metamodel Tuples

EVp-02_mandatoryTuples.gif

Covered by TRAK IPR and licenses

Optional Metamodel Tuples

context

  • Organisation realises Enterprise
  • Enterprise aspires to Enterprise Goal
  • Enterprise Goal is quantified by Metric

    • universal

    If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.

    Covered by TRAK IPR and licenses

    Well-Formedness

    An EV-02 view shall contain:

    • at least one Enterprise (the subject of the view)
    • the subject Enterprise Enterprise must have at least one Capability

    If the task stakeholder is concerned with quantifying capability (recorded in the MV-02):

    Presentation

    • block diagram (blocks to represent Enterprise, Capability, Metric and Enterprise Goal)

    EVp-02_example_430.gif

    File:EVp-02 example.gif

    Covered by TRAK IPR and licenses

    Examples

    Views Needed to Construct

    See Minimum Allowed View Sets

    Covered by TRAK IPR and licenses

    Consistency Rules

    Covered by TRAK IPR and licenses

    Configuration History

    The TRAK Viewpoints project on Sourceforge (trakviewpoints.sourceforge.net) maintains a version-controlled repository. The change record is at http://trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log

    Comments

    The TRAK metamodel doesn’t contain the is a (specialisation / generalisation) relationship because creation of taxonomies is more concerned with organisation of collections of any architecture description element, not just capability, and associated with repository management.

    Taxonomy diagrams of any type of architecture description element can be included with an architecture description as a non-conforming product (see Conformance with TRAK in TRAK Enterprise Architecture Description document).

    References

    Other Frameworks

    See also:

    There is no equivalent in DNDAF to the TRAK Enterprise Perspective - see Architecture Framework Comparison.

     


    Category:Framework -> Viewpoint
    Category:Framework -> Specification
    Category:Enterprise
    Category:Strategic

    Categories:

  • Strategic
    •  

    © 2010 Eclectica Systems Ltd.