Formats and tools
- Unit Description
- Reconstruct the unit from the xml and display it as an HTML page.
- Assessment Tool
- an assessor resource that builds a framework for writing an assessment tool
- Assessment Template
- generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
- Assessment Matrix
- a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
- Wiki Markup
- mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
- Evidence Guide
- create an evidence guide for workplace assessment and RPL applicants
- Competency Mapping Template
- Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
- Observation Checklist
- create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)
- Self Assessment Survey
- A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
- Moodle Outcomes
- Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
- Registered Training Organisations
- Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver DEFEA003, 'Use enterprise architecture tools'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Use enterprise architecture tools' on fishpond.com.au. This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to ntisthis.com for every purchase, so go nuts :)
Elements and Performance Criteria
ELEMENT | PERFORMANCE CRITERIA |
1. Operate enterprise architecture software tools | 1.1 Enterprise architecture software tools are selected and used in accordance with organisational requirements. 1.2 The enterprise information technology support system is used to operate the selected enterprise architecture tools as required. |
2. Use enterprise architecture operational tools | 2.1 Descriptions are prepared for high level operational concepts and operational node connectivity. 2.2 Operational information exchange matrices are prepared. 2.3 A command relationship chart is prepared and agreed upon. 2.4 Business activities, relationships between activities, inputs and outputs are modelled. 2.5 Business activity sequences and timings are prepared in accordance with the organisation’s business rules, business activity reforms and critical sequences. 2.6 A logical data model of business activity is prepared for submission to stakeholders. |
3. Use enterprise architecture systems tools | 3.1 Systems descriptions are prepared and agreed with stakeholders. 3.2 Systems matrices are developed to meet project requirements and agreed with stakeholders where required. 3.3 System technology forecasts are prepared and agreed to. 3.4 System rules for the business architecture are modelled. 3.5 The physical implementation of the logical data model of the business activity is modelled to capture systems requirements. |
4. Use enterprise architecture technical tools | 4.1 A technical system profile is created, and support levels required for the development of the intended system are gauged in consultation with stakeholders. 4.2 An information technology strategy is developed for intended system development. 4.3 Enterprise information technology performance requirements from enterprise business requirements are derived so that appropriate standards, configurations and products relevant to the intended system are developed. 4.4 a technology standards report is created in which standards are described and forecast in accordance with business guidelines. |