Unit of competency Outline

Date retreived
23/07/2026 11:01 PM AWST

Whilst all efforts are made to provide accurate and timely information from the relevant source/documentation, please be aware that the information supplied may not be the most current version. The accuracy of the detail has not been confirmed by the Department and therefore should not be relied upon without first confirming the contents.

Identify physical database requirements

Identify physical database requirements

Unit of competency
National Code
ICADBS401A
State Code
D7767
TGA Status
Replaced
DTWD Status
Replaced
Current Release Number
1.00
Current Release Date
18/07/2011
View on TGA
State Implementation and Classification
Approved Date
29/09/2011
Field of Education
020303 - Database Management
Original Release Date
29/09/2011
Nominal Hours
35
Description
This unit describes the performance outcomes, skills and knowledge required to identify the physical requirements of a database, including a data dictionary and security and design specifications.No licensing, legislative, regulatory or certification requirements apply to this unit at the time of endorsement but users should confirm requirements with the relevant federal, state or territory authority.
Notes
Elements and Performance Criteria
1. Identify database scope
  • 1.1 Review requirements of the user and current system architecture
  • 1.2 Determine database size from requirements and technical specifications
  • 1.3 Document database and scope of project
  • 1.4 Evaluate several database-management systems against requirements and make appropriate selection
2. Identify database requirements
  • 2.1 Review technical specifications for the database
  • 2.2 Identify database tables and relationships
  • 2.3 Identify database data dictionary, table attributes and keys
  • 2.4 Develop database reports based on acceptance criteria and requirements
3. Identify security requirements
  • 3.1 Review system-security plan
  • 3.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.3 Identify, evaluate and record database performance, recovery and audit trail needs
4. Seek client feedback and approval
  • 4.1 Present database scope, technical requirements and security documentation to user for feedback
  • 4.2 Review user feedback and adjust database documentation as required
  • 4.3 Present database documentation to user for final approval
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:
application
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:
application
business
computers
financial system
information system
management system
network
software.
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.
Replaces
State Code National Code Title Type
D0040 ICAB4060B Identify physical database requirements Unit of competency
Replaced By
State Code National Code Title Type
AUX21 ICTDBS401 Identify physical database requirements Unit of competency