Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

  1. Identify entities and relationships
  2. Develop normalisation
  3. Validate model

Required Skills

Required skills

analytical skills to analyse business data

communication skills to liaise with clients

problemsolving skills to solve problems that arise with the entity relationships

technical skills to

develop entityrelationship models in tables

relate identifier selection to business domain

relate user specifications to data model

transfer customer requirements into data model

Required knowledge

detailed knowledge of

database identifiers and their impact on database usability

normalisation rules and processes

type hierarchies including subtypes supertypes roottypes related to development of structured data types

validation procedures and processes

function and features of

an approach to data modelling such as the entityrelationship model

keys eg unique keys composite keys primary keys and primary index

time stamps related to the use of keys

userdefined types structured types reference types and userdefined functions

particular business or domain

Evidence Required

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 ability to

model valid data objects

normalise the model

validate the model

Context of and specific resources for assessment

Assessment must ensure access to

appropriate learning and assessment support when required

modified equipment for people with special needs

client business requirements

database software

computeraided software engineering tools or other suitable software

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge The following examples are appropriate for this unit

observation of candidates use of computeraided software engineering CASE tool or other appropriate software

verbal or written questioning to assess candidates knowledge of

data modelling techniques

normalisation

entity relationship diagrams

review of completed data model and associated documentation prepared by candidate

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector workplace and job role is recommended where appropriate

Assessment processes and techniques must be culturally appropriate and suitable to the communication skill level language literacy and numeracy capacity of the candidate and the work being performed

Indigenous people and other people from a nonEnglish speaking background may need additional support

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge


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:

application service provider

applications

databases

gateways

internet service provider (ISP)

operating systems

servers.

Entities may include:

concept

object

person.

Data types may include:

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

character string

date-time and binary string

double-byte (or graphic) character string

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

numeric

structured types and reference types

user-defined type (UDT).

Relationships may include:

many-to-many

many-to-one

one-to-many

one-to-one.