NTISthis.com

Evidence Guide: ICTDBS401 - 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

 

ICTDBS401 - Identify physical database requirements

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

Identify the database scope

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

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine database size from the requirements and the technical specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Document the database design, and scope, of the project

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Evaluate several database management systems against the requirements, and make the appropriate selection

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify the database requirements

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

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify the database tables and relationships

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify the database data dictionary, table attributes and keys

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine the database reports based on the acceptance criteria and requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify the security requirements

  1. Review the system security plan
  2. Clarify and confirm that the database management system, and user security, aligns with the system security plan
  3. Identify, evaluate and record database performance, recovery and audit trail needs
Review the system security plan

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Clarify and confirm that the database management system, and user security, aligns with the system security 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 the user for feedback
  2. Review user feedback and adjust the database documentation, as required
  3. Present database documentation to the user for final approval
Present database scope, technical requirements and security documentation to the user for feedback

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review user feedback and adjust the database documentation, as required

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Present database documentation to the user for final approval

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify the database scope

1.1 Review the requirements of the user, and the current system’s architecture

1.2 Determine database size from the requirements and the technical specifications

1.3 Document the database design, and scope, of the project

1.4 Evaluate several database management systems against the requirements, and make the appropriate selection

2. Identify the database requirements

2.1 Review the technical specifications for the database

2.2 Identify the database tables and relationships

2.3 Identify the database data dictionary, table attributes and keys

2.4 Determine the database reports based on the acceptance criteria and requirements

3.Identify the security requirements

3.1 Review the system security plan

3.2 Clarify and confirm that the database management system, and user security, aligns with the system security 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 the user for feedback

4.2 Review user feedback and adjust the database documentation, as required

4.3 Present database documentation to the user for final approval

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Identify the database scope

1.1 Review the requirements of the user, and the current system’s architecture

1.2 Determine database size from the requirements and the technical specifications

1.3 Document the database design, and scope, of the project

1.4 Evaluate several database management systems against the requirements, and make the appropriate selection

2. Identify the database requirements

2.1 Review the technical specifications for the database

2.2 Identify the database tables and relationships

2.3 Identify the database data dictionary, table attributes and keys

2.4 Determine the database reports based on the acceptance criteria and requirements

3.Identify the security requirements

3.1 Review the system security plan

3.2 Clarify and confirm that the database management system, and user security, aligns with the system security 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 the user for feedback

4.2 Review user feedback and adjust the database documentation, as required

4.3 Present database documentation to the user for final approval

Evidence of the ability to:

analyse client requirements

identify the technical considerations affecting the physical design of a database

document the database requirements

review the security plan for the database.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain the principles of databases and database design

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

explain the quality assurance practices that apply to database design

identify the client’s business domain

describe database requirements appropriate for client’s business.