NTISthis.com

Evidence Guide: ICAA5153B - Model data objects

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

 

ICAA5153B - Model data objects

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

Identify entities and relationships

  1. Analyse business data to understand operations
  2. Identify boundaries of the system
  3. Identify entities, attributes, data types and relationships of data
  4. Review business rules to determine impact
  5. Document relationships in an entity relationship diagram
Analyse business data to understand operations

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify boundaries of the system

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify entities, attributes, data types and relationships of data

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review business rules to determine impact

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document relationships in an entity relationship diagram

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop normalisation

  1. Identify suitable business data
  2. Undertake normalisation of business data and document results
  3. Compare normalisation results with entity relationship diagram
  4. Reconcile differences between data, if any
Identify suitable business data

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Undertake normalisation of business data and document results

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Compare normalisation results with entity relationship diagram

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Reconcile differences between data, if any

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Validate model

  1. Validate data model with client
  2. Resolve issues or recommendations arising
  3. Document completed data model
  4. Submit to client for final approval
Validate data model with client

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Resolve issues or recommendations arising

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document completed data model

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Submit to client for final approval

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

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

Evidence of the following is essential:

Assessment must confirm the ability to model valid data objects and normalise the model.

To demonstrate competency in this unit the learner will need access to:

Client business requirements

Database software

Context of and specific resources for assessment

The breadth, depth and complexity covering planning and initiation of alternative approaches to skills or knowledge applications across a broad range of technical and/or management requirements, evaluation and coordination would be characteristic.

Assessment must ensure:

self-directed application of knowledge and skills, with substantial depth in some areas where judgement is required in planning and selecting appropriate equipment, services and techniques for self and others.

Applications involve participation in development of strategic initiatives as well as personal responsibility and autonomy in performing complex technical operations or organising others. It may include participation in teams including teams concerned with planning and evaluation functions. Group or team coordination may also be involved.

Method of assessment

The purpose of this unit is to define the standard of performance to be achieved in the workplace. In undertaking training and assessment activities related to this unit, consideration should be given to the implementation of appropriate diversity and accessibility practices in order to accommodate people who may have special needs. Additional guidance on these and related matters is provided in ICA05 Section 1.

Competency in this unit should to be assessed using summative assessment to ensure consistency of performance in a range of contexts. This unit can be assessed either in the workplace or in a simulated environment. However, simulated activities must closely reflect the workplace to enable full demonstration of competency.

Assessment will usually include observation of real or simulated work processes and procedures and/or performance in a project context as well as questioning on underpinning knowledge and skills. The questioning of team members, supervisors, subordinates, peers and clients where appropriate may provide valuable input to the assessment process. The interdependence of units for assessment purposes may vary with the particular project or scenario.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, for example:

ICAA5154B Model data processes

An individual demonstrating this competency would be able to:

Demonstrate understanding of a broad knowledge base incorporating theoretical concepts, with substantial depth in some areas

Analyse and plan approaches to technical problems or management requirements

Transfer and apply theoretical concepts and/or technical or creative skills to a range of situations

Evaluate information, using it to forecast for planning or research purposes

Take responsibility for own outputs in relation to broad quantity and quality parameters

Take some responsibility for the achievement of group outcomes

Maintain knowledge of industry products and services

Required Skills and Knowledge

Required skills

Data modelling

Transferring customer requirements into data model

Developing entity-relationship models in tables

Relating identifier selection to business domain

Relating user specifications to data model

Required knowledge

Particular business or domain

Validation procedures and processes

Function and features of an approach to data modelling (e.g. the entity-relationship model)

Database identifiers and their impact on database usability

Function and features of user-defined types, structured types, reference types and user-defined functions

Type hierarchies (e.g. sub types, super types, root types with reference to the development of structured data types)

Features and function of keys (e.g. unique keys, composite keys, primary keys and primary index)

Features and function of time stamps in relation to the use of keys

Normalisation rules and processes

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, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

System may include but is not limited to:

databases

applications

servers

operating systems

gateways

application service provider

ISP

Entities may include:

person

object

concept

Relationships may include:

one-to-many

many-to-one

many-to-many

one-to-one

Data types may include the following categories:

numeric

character string

double-byte (or graphic) character string

date-time and binary string

large Object (LOB), binary large object (BLOB)

character large object (CLOB), double-byte character large object (DBCLOB)

user-defined type (UDT)

structured types and reference types