NTISthis.com

Evidence Guide: BSBITA401A - Design databases

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

 

BSBITA401A - Design databases

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

Design database

  1. Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy
  2. Develop a logical data model to identify and classify data into types
  3. Select appropriate software according to organisational and task requirements and required scope and functionality of database
  4. Confirm database design with appropriate person
Review organisational and task requirements to confirm scope and functionality of database design, including data redundancy

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a logical data model to identify and classify data into types

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Select appropriate software according to organisational and task requirements and required scope and functionality of database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm database design with appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop database

  1. Set field attributes according to data type and link databases by a common field in accordance with software procedures
  2. Identify primary key to uniquely identify data
  3. Identify foreign keys to establish associations between data
  4. Use software functions and formulae to meet organisational and task requirements
  5. Create password and access system according to organisational and task requirements
Set field attributes according to data type and link databases by a common field in accordance with software procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify primary key to uniquely identify data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify foreign keys to establish associations between data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Use software functions and formulae to meet organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create password and access system according to organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop queries, forms and reports

  1. Develop queries as required by organisational and task requirements
  2. Develop input screens or forms in order to access required data
  3. Develop reports according to organisational and task requirements
Develop queries as required by organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop input screens or forms in order to access required data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop reports according to organisational and task requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Test and finalise database

  1. Populate database with sample dataset for testing
  2. Assess and document effectiveness of data relationships, queries forms and reports
  3. Address any errors in database design
  4. Name and store database in accordance with organisational requirements and exit the application without data loss or damage
  5. Confirm database readiness with appropriate person
Populate database with sample dataset for testing

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assess and document effectiveness of data relationships, queries forms and reports

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Address any errors in database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Name and store database in accordance with organisational requirements and exit the application without data loss or damage

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm database readiness with appropriate person

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:

producing a database containing a minimum of three tables and incorporating queries, reports and forms

knowledge of advanced functions of database software app.

Context of and specific resources for assessment

Assessment must ensure:

access to office equipment and resources

access to sample data.

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:

direct questioning combined with review of portfolios of evidence and third party workplace reports of on-the-job performance by the candidate

review of databasedesign

review of database testing

demonstration of techniques.

Guidance information for assessment

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

IT use units

other IT analysis and design units.

Required Skills and Knowledge

Required skills

literacy skills to interpret and evaluate the purposes and features of databases

numeracy skills to utilise software functions and formulae, and to establish data relationships and queries

planning and organising skills to establish database design

problem-solving skills to address inconsistencies in database design and data relationships.

Required knowledge

advanced functions of database software applications

impact of formatting and design on the presentation and readability of data

key provisions of relevant legislation from all forms of government, standards and codes that may affect aspects of business operations, such as:

anti-discrimination legislation

ethical principles

codes of practice

privacy laws

occupational health and safety.

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.

Organisational and task requirements may include:

business requirements

consistent corporate image, including colour schemes and company logo

established guidelines and procedures for data usage

existing database templates

final output requirements for data

house styles

observing copyright legislation

organisation name, time, date, document title, filename or other fields in headers and footers

technical operating environment and platform

Scope and functionality of database may include:

concurrency of access requirements

data relationships

data structures

forms

queries

reports

screens

security features

table relationships

Software may include:

commercial software applications

organisational specific software

Appropriate person may include:

clients

colleagues

supervisors

Software functions may include:

adding, deleting, moving, re-labelling fields

altering field widths

calculations, formula

data protection

field definitions and attributes

formatting fields

formatting text

headers and footers

inserting and deleting blank lines and spaces

macros

append

delete

edit

exit

list

print

query

report

repeating (if available)

table, form and report wizards

Formulae may include:

formulae

addition

average

combinations of formulae

count

division

maximum

minimum

multiplication

subtraction

sum

Naming and storage may include:

authorised access

filing locations

organisational policy for backing up files

organisational policy for filing hard copies of spreadsheets

security

storage in folders and sub-folders

storage on disc drives, CD-ROM, USBs, tape or server back-up