NTISthis.com

Evidence Guide: DEFEA001 - Use an enterprise architecture framework

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

DEFEA001 - Use an enterprise architecture framework

What evidence can you provide to prove your understanding of each of the following citeria?

Create common views for a specific business architecture

  1. Relevant information for a specific business architecture is identified and summarised.
  2. An integrated enterprise architecture dictionary is used.
  3. An architecture compliance statement is prepared.
  4. A capability maturity profile is prepared in consultation with stakeholders.
Relevant information for a specific business architecture is identified and summarised.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

An integrated enterprise architecture dictionary is used.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

An architecture compliance statement is prepared.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

A capability maturity profile is prepared in consultation with stakeholders.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create operational views for a specific business architecture

  1. Descriptions are created/developed for a high level operational concept and operational node connectivity.
  2. An operational information exchange matrix is prepared.
  3. A command relationship chart is prepared and agreed to.
  4. Business activities, relationships between activities, inputs and outputs are modelled.
  5. The business activity sequence and timing is developed in accordance with the organisation’s business rules, business activity reforms and critical sequences.
  6. A logical data model of the business activity is created/developed and agreed by stakeholders.
Descriptions are created/developed for a high level operational concept and operational node connectivity.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

An operational information exchange matrix is prepared.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

A command relationship chart is prepared and agreed to.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Business activities, relationships between activities, inputs and outputs are modelled.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

The business activity sequence and timing is developed in accordance with the organisation’s business rules, business activity reforms and critical sequences.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

A logical data model of the business activity is created/developed and agreed by stakeholders.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create systems views for a specific business architecture

  1. Systems descriptions are prepared and agreed with stakeholders.
  2. Systems matrices are developed to meet project requirements and agreed with stakeholders where required.
  3. A system technology forecast is prepared and agreed to.
  4. System rules for the business architecture are modelled.
  5. The physical implementation of the logical data model of the business activity is modelled to capture systems requirements.
Systems descriptions are prepared and agreed with stakeholders.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Systems matrices are developed to meet project requirements and agreed with stakeholders where required.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

A system technology forecast is prepared and agreed to.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

System rules for the business architecture are modelled.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

The physical implementation of the logical data model of the business activity is modelled to capture systems requirements.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create technical views for a specific business architecture

  1. A technical system profile is created, and support levels required for the development of the intended system are gauged in consultation with stakeholders.
  2. An information technology strategy is developed for intended system development.
  3. The enterprise information technology performance requirements from the enterprise business requirements are derived so that appropriate standards, configurations and products relevant to the intended system are developed.
  4. A technology standards description/forecast is created in which standards are described and forecast in accordance with business guidelines.
A technical system profile is created, and support levels required for the development of the intended system are gauged in consultation with stakeholders.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

An information technology strategy is developed for intended system development.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

The enterprise information technology performance requirements from the enterprise business requirements are derived so that appropriate standards, configurations and products relevant to the intended system are developed.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

A technology standards description/forecast is created in which standards are described and forecast in accordance with business guidelines.

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Assessment must confirm the ability to:

create and document the required enterprise architecture using the agreed set of enterprise architecture tools

use enterprise architecture tools in a range of (3 or more) contexts (or occasions, over time) for an extended period with extensive reference to representative stakeholders

Consistency in performance

Evidence must be gathered over time in a range of contexts to ensure the person can achieve the unit outcome and apply the competency in different situations or environments

Context of and specific resources for assessment

Context of assessment

Competency should be assessed in the workplace or in a simulated workplace environment.

Specific resources for assessment

legislation, policy, procedures and protocols relating to enterprise architecture

capacity for monitoring and sampling over an extended period with extensive reference to representatives

case studies and workplace scenarios to capture the range of situations likely to be encountered when using enterprise architecture tools

Required Skills and Knowledge

This describes the essential skills and knowledge and their level, required for this unit.

Required Skills

undertaking technical writing

using effective communication with diverse stakeholders, including negotiation

responding to diversity, including gender and disability

applying procedures relating to work health and safety and environment in the context of using an enterprise architecture framework

Required Knowledge

undertaking technical writing

applying systems analysis

using enterprise architecture software and hardware

using effective communication with diverse stakeholders, including negotiation

responding to diversity, including gender and disability

applying procedures relating to work health and safety and environmental requirements in the context of using enterprise architecture tools

Range Statement

The Range Statement relates to the Unit of Competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording in the Performance Criteria is detailed below.

Stakeholders may include:

all those individuals and groups both inside and outside the organisation that have some direct interest in the organisation enterprise architecture development and use, such as:

employees at all levels of the organisation

clients

union and association representatives

government

ministers

public sector bodies that set standards such as information security standards, fraud control standards, ethics etc

Systems descriptions may include:

system evolution description

system interface description

systems communication description

systems event/trace description

systems functionality description

systems state transition description

Systems matrices may include:

operation activity to system function traceability matrix

system information exchange matrix

system performance parameters matrix

systems to systems matrix