Capability Pattern

These capability patterns are Capabilities used within the sense of EPF-Composer. As opposed to Business Capabilities of Business Services, etc. - although they are closely related and are probably ultimately the same thing at different levels of focus within the Enterprise.

The goal for these Capabilities is to try and find the highest level Business Capability for an Enterprise Architecture Practice that will contain epf.Phases, epf.Iterations, epf. Activites, epf.Task descriptors and epf.Milestones, which can be re-used in slightly different situations, with minor modifications (exclusions or extensions of the base). This allows for re-use of the base processes, in the spirit of inheritance.

Phase Capability Pattern Implemented in EPF
Feasibility Identify an obtain an EA Sponsor Yes
Develop a Proposal for an EA practice Yes
Establish the Capability to fund an EA Practice Yes
Inception Define EA vision and Mission Yes
Define EA Principles and Standards No
Define and Communicate EA Services and Benefits No
Establish a Taxonomy No
Establish an Ontology No
Gather an inventory of Business Process No
Gather an inventory of Applications No
Gather an inventory of Technology No
Manage EA Risks No
Acquire team resources No
Ensure Team training No
Establish an EA Planning process No
Define an EA Process Organisation and Relationships No
Identify and Implement tools to support EA No
Elaboration No
Define EA Motivation No
Assess Architectural Impact No
Establish Business Architecture Description (BAD) Views No
Establish System Architecture Description (SAD) Views No
Trace Business to Info-Systems Architecture No
Trace Info-Systems to Technology Architecture No
Build a Reference Architecture No
Build a Business Reference Architecture No
Build a Information Systems Reference Architecture No
Build a Technology Reference Architecture No
Define a Solution Adoption Lifecycle No
Define a Service Delivery Lifecycle No
Define EA Process No
Communicate Base EA Service Offerings No
Control Changes No
Control Configurations No
Establish an EA Meta-model No
Build Up a Central EA Model Repository No
Define Work Take-on and Triage No
Define an Architectural Risk Management process No
Define an Architectural Governance process No
Architecture-as-usual Define Enterprise Motivation No
Gather Business Architecture knowledge No
Manage EA Work and Iteration plans No
Assess Architectural Impact No
Assess proposed Project Architecture No
Gather Info-Systems Architecture knowledge No
Manage EA Knowledge in repository No
Gather Technology Architecture knowledge No
Define Target Business Architecture Views No
Define Data Architecture Views No
Define Security Architecture Views No
Develop Target Architectures No
Define Target Info-Systems Architecture Views No
Define Target Technology Architecture Views No
Communicate EA Knowledge No
Publish EA Knowledge No
Define Time-series Evolution (Roadmaps) No
Shape Projects Architecturally No
Manage Performance & Capacity No
Identify & Allocate Costs No
Monitor & Evaluate Team Performance No
Evolve EA Capability and Maturity No
Define EA Service Level Agreement's No
Govern Architecture No
Manage Service Delivery Lifecycle No
. No
[[[]]] No
[[[]]] No
[[[]]] No

Lots more to do here still…

Unless otherwise stated, the content of this page is licensed under GNU Free Documentation License.