NTISthis.com

Evidence Guide: ICADBS401A - Identify physical database requirements

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

 

ICADBS401A - Identify physical database requirements

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

Identify database scope

  1. Review requirements of the user and current system architecture
  2. Determine database size from requirements and technical specifications
  3. Document database and scope of project
  4. Evaluate several database-management systems against requirements and make appropriate selection
Review requirements of the user and current system architecture

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine database size from requirements and technical specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document database and scope of project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate several database-management systems against requirements and make appropriate selection

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify database requirements

  1. Review technical specifications for the database
  2. Identify database tables and relationships
  3. Identify database data dictionary, table attributes and keys
  4. Develop database reports based on acceptance criteria and requirements
Review technical specifications for the database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify database tables and relationships

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify database data dictionary, table attributes and keys

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop database reports based on acceptance criteria and requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify security requirements

  1. Review system-security plan
  2. Clarify and confirm chosen database-management system and user security required for the database to ensure database security is aligned to security-system plan
  3. Identify, evaluate and record database performance, recovery and audit trail needs
Review system-security plan

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Clarify and confirm chosen database-management system and user security required for the database to ensure database security is aligned to security-system plan

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify, evaluate and record database performance, recovery and audit trail needs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Seek client feedback and approval

  1. Present database scope, technical requirements and security documentation to user for feedback
  2. Review user feedback and adjust database documentation as required
  3. Present database documentation to user for final approval
Present database scope, technical requirements and security documentation to user for feedback

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review user feedback and adjust database documentation as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Present database documentation to user 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 ability to:

analyse client requirements

identify technical considerations affecting the physical design of a database

produce a security plan for the database.

Context of and specific resources for assessment

Assessment must ensure access to:

user-business requirements

technical documentation defining architecture platform and operating system specifications

database-supplier technical specifications and manuals

data samples

database package

appropriate learning and assessment support when required

modified equipment for people with special needs.

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:

review of the final database, specifying business rules, agreed budget and timeframe

evaluation of documentation, detailing:

database directories

calculation of space requirements for tables

additional space requirements

design of node groups

security plan.

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 non-English speaking background may need additional support.

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

Required Skills and Knowledge

Required skills

analytical skills to review user requirements, system architecture and security plan

communication skills to liaise with user

literacy skills to:

produce database reports

review user feedback

problem-solving skills to develop technical solutions

technical skills to evaluate, identify and determine database requirements using database modelling.

Required knowledge

broad knowledge of:

database design

general features and capabilities of current industry-accepted hardware and software products

quality assurance practices

client business domain

current principles of databases

detailed technical knowledge of database requirements.

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.

Requirements may relate to:

business

network

people in the organisation

system.

User may include:

department within the organisation

person within a department

third party.

System architecture may include:

configuration:

large memory model

requests per second

small memory model

database software:

DB2

Informix

Ingres

Microsoft Structured Query Language (MS SQL) server

Mini SQL (mSQL)

MySQL

Oracle

Sybase

operating system:

Novell NetWare

multi-user ability

Linux

Mac

Windows.

Database may include:

commercial off-the-shelf (COTS) database packages

object-relational databases

proprietary databases

relational databases.

Database-management systems may include:

distributed or centralised

online

partitioned geographically

thematically distributed.

Acceptance criteria may include:

cost implications

logistical considerations

technical

timeframe.

System may include:

business

computers

financial system

information system

management system

network

software.