NTISthis.com

Evidence Guide: ICAPRG403A - Develop data-driven applications

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

 

ICAPRG403A - Develop data-driven applications

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

Design data-access layer (DAL)

  1. Design DAL in a multi-layer application model
  2. Determine data-access application programming interface (API) for connecting to various data sources
Design DAL in a multi-layer application model

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine data-access application programming interface (API) for connecting to various data sources

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Establish a connection with a data source

  1. Create and manage connection strings
  2. Connect to a data source by using different data providers
  3. Create code to handle connection exceptions
Create and manage connection strings

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Connect to a data source by using different data providers

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create code to handle connection exceptions

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Execute commands and return results from the data source

  1. Query data from the data source
  2. Retrieve data from the data source as result sets
  3. Manage result sets
  4. Manage exceptions when retrieving data
Query data from the data source

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Retrieve data from the data source as result sets

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage result sets

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage exceptions when retrieving data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Modify data in the data source

  1. Insert, update or delete data
  2. Manage data integrity
  3. Manage exceptions when modifying data
Insert, update or delete data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage data integrity

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage exceptions when modifying data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Manage disconnected data

  1. Research a disconnected data management strategy
  2. Ensure that application can deal with disconnected data
Research a disconnected data management strategy

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Ensure that application can deal with disconnected data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document data-access layer

  1. Document the code
  2. Document database connectivity
Document the code

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document database connectivity

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:

design and code the data-access layer of multi-layer applications

retrieve and update data from various data sources.

Context of and specific resources for assessment

Assessment must ensure access to:

integrated development environment (IDE)

data access APIs

database management system software

database files

coding standard

specific tools and licences, depending on particular data-access API

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 candidate’s DAL design

evaluation of candidate’s data-access management strategy

verbal or written questioning to assess candidate’s knowledge of:

multi-layer applications

database access.

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 design complex multi-layer application model

communication skills to interact with developer to ensure proper implementation

learning skills to investigate potential new techniques to access data from various resources

literacy skills to:

read and interpret database design document

read basic technical data

problem-solving skills to develop and refine strategies to access data sources

technical skills to:

create code for the data-access layer

create structured query language (SQL) commands to select, insert, update or delete data

test and debug code.

Required knowledge

features of:

object-oriented design and multi-layer applications

relational database management systems

object-oriented programming at an intermediate level

SQL at a basic level.

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.

Multi-layer application may include:

business logic layer (BLL)

data-access layer (DAL)

user interface layer (UI).

Data-access application programming interface may relate to:

object-oriented set of libraries used to interact with data sources:

active data objects (ADO.NET)

ADO.NET Entity Framework

Java database connectivity (JDBC)

language integrated query (LINQ).

Data source may include:

databases:

Microsoft SQL server

MySQL

Oracle

Postgre Structured Query Language (Postgre SQL)

fat-files database

internal data

object data sources

XML database.

Data providers may include:

managed providers

Microsoft object linking and embedding (OLE) DB

native providers

open database connection (ODBC)

SQL client

third-party providers.

Query data may include:

access input and output parameters and return values

access stored procedures

create command objects.

Data integrity may include:

cascading deletes

cascading updates

constraints.

Disconnected data may include:

DataSet

DataTable

service data objects (SDO).