NTISthis.com

Evidence Guide: ICTDBS502 - Design a database

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

 

ICTDBS502 - Design a database

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

Determine database requirements

  1. Meet with the client, and conduct a user-needs analysis, to determine database functionality
  2. Analyse the results of a user-needs analysis to identify technical requirements
  3. Develop a conceptual model of the database
  4. Submit the conceptual model to the client for review
  5. Evaluate client feedback and make changes as required
Meet with the client, and conduct a user-needs analysis, to determine database functionality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the results of a user-needs analysis to identify technical requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a conceptual model of the database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit the conceptual model to the client for review

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate client feedback and make changes as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop a logical data model

  1. Identify the attributes and determine the data types
  2. Undertake the normalisation of attributes
  3. Develop an entity-relationship (ER) diagram in order to clarify the cardinality of relationships
  4. Document attributes, normalised data, and the ER diagram
  5. Forward documentation to the client for confirmation
Identify the attributes and determine the data types

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Undertake the normalisation of attributes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop an entity-relationship (ER) diagram in order to clarify the cardinality of relationships

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document attributes, normalised data, and the ER diagram

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Forward documentation to the client for confirmation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design the data structures

  1. Confirm primary and foreign keys for tables
  2. Review client business rules
  3. Identify the referential integrity constraints
  4. Establish database management system constraints and incorporate into database design
  5. Develop the validation rules for data
  6. Design indexes and develop the data dictionary
  7. Document the database design
Confirm primary and foreign keys for tables

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review client business rules

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify the referential integrity constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish database management system constraints and incorporate into database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop the validation rules for data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design indexes and develop the data dictionary

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the database design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design queries, screens and reports

  1. Design the user interface for database, including menus, input screens and outputs
  2. Design queries, based on requirements
  3. Design output reports, based on requirements
  4. Compare the physical design with the conceptual model, or user-needs analysis
  5. Incorporate changes as required
Design the user interface for database, including menus, input screens and outputs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design queries, based on requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design output reports, based on requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare the physical design with the conceptual model, or user-needs analysis

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Incorporate changes as required

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design access and security systems

  1. Review the business security plan as a basis for commencing the access and security design
  2. Design the password and access system for the database
  3. Identify multiple-user requirements
  4. Develop client access profiles using the client business model
Review the business security plan as a basis for commencing the access and security design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Design the password and access system for the database

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Identify multiple-user requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop client access profiles using the client business model

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm the database design

  1. Identify the database backup and recovery requirements
  2. Develop and document the database backup and restore procedures
  3. Submit the database, and documentation, to the client for final approval
Identify the database backup and recovery requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop and document the database backup and restore procedures

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit the database, and documentation, to the client 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. Determine database requirements

1.1 Meet with the client, and conduct a user-needs analysis, to determine database functionality

1.2 Analyse the results of a user-needs analysis to identify technical requirements

1.3 Develop a conceptual model of the database

1.4 Submit the conceptual model to the client for review

1.5 Evaluate client feedback and make changes as required

2. Develop a logical data model

2.1 Identify the attributes and determine the data types

2.2 Undertake the normalisation of attributes

2.3 Develop an entity-relationship (ER) diagram in order to clarify the cardinality of relationships

2.4 Document attributes, normalised data, and the ER diagram

2.5 Forward documentation to the client for confirmation

3. Design the data structures

3.1 Confirm primary and foreign keys for tables

3.2 Review client business rules

3.3 Identify the referential integrity constraints

3.4 Establish database management system constraints and incorporate into database design

3.5 Develop the validation rules for data

3.6 Design indexes and develop the data dictionary

3.7 Document the database design

4. Design queries, screens and reports

4.1 Design the user interface for database, including menus, input screens and outputs

4.2 Design queries, based on requirements

4.3 Design output reports, based on requirements

4.4 Compare the physical design with the conceptual model, or user-needs analysis

4.5 Incorporate changes as required

5. Design access and security systems

5.1 Review the business security plan as a basis for commencing the access and security design

5.2 Design the password and access system for the database

5.3 Identify multiple-user requirements

5.4 Develop client access profiles using the client business model

6. Confirm the database design

6.1 Identify the database backup and recovery requirements

6.2 Develop and document the database backup and restore procedures

6.3 Submit the database, and documentation, to the client 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. Determine database requirements

1.1 Meet with the client, and conduct a user-needs analysis, to determine database functionality

1.2 Analyse the results of a user-needs analysis to identify technical requirements

1.3 Develop a conceptual model of the database

1.4 Submit the conceptual model to the client for review

1.5 Evaluate client feedback and make changes as required

2. Develop a logical data model

2.1 Identify the attributes and determine the data types

2.2 Undertake the normalisation of attributes

2.3 Develop an entity-relationship (ER) diagram in order to clarify the cardinality of relationships

2.4 Document attributes, normalised data, and the ER diagram

2.5 Forward documentation to the client for confirmation

3. Design the data structures

3.1 Confirm primary and foreign keys for tables

3.2 Review client business rules

3.3 Identify the referential integrity constraints

3.4 Establish database management system constraints and incorporate into database design

3.5 Develop the validation rules for data

3.6 Design indexes and develop the data dictionary

3.7 Document the database design

4. Design queries, screens and reports

4.1 Design the user interface for database, including menus, input screens and outputs

4.2 Design queries, based on requirements

4.3 Design output reports, based on requirements

4.4 Compare the physical design with the conceptual model, or user-needs analysis

4.5 Incorporate changes as required

5. Design access and security systems

5.1 Review the business security plan as a basis for commencing the access and security design

5.2 Design the password and access system for the database

5.3 Identify multiple-user requirements

5.4 Develop client access profiles using the client business model

6. Confirm the database design

6.1 Identify the database backup and recovery requirements

6.2 Develop and document the database backup and restore procedures

6.3 Submit the database, and documentation, to the client for final approval