NTISthis.com

Evidence Guide: ICAPRG506A - Design application architecture

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

 

ICAPRG506A - Design application architecture

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

Gather and confirm architecture requirements

  1. Gather information regarding architectural requirements
  2. Establish and document architectural requirements
Gather information regarding architectural requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Establish and document architectural requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design layered architecture

  1. Separate the areas of concern into logical layers
  2. Determine the cross-cutting concerns
  3. Define the system into components
  4. Identify the responsibilities of each component
  5. Identify interconnections between components
Separate the areas of concern into logical layers

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Determine the cross-cutting concerns

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Define the system into components

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify the responsibilities of each component

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify interconnections between components

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Plan a strategy to re-use components

  1. Determine an appropriate strategy for communicating with external systems
  2. Interact with existing legacy components
Determine an appropriate strategy for communicating with external systems

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Interact with existing legacy components

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Design for globalisation and localisation

  1. Determine culture-specific information
  2. Consider database design features
  3. Select appropriate user interface
  4. Develop software product for worldwide distribution
  5. Develop software product for specific country
Determine culture-specific information

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Consider database design features

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Select appropriate user interface

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop software product for worldwide distribution

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop software product for specific country

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 layered applications to increase application performance, scalability and re-usability

create flexible and configurable applications and adapt to suit different locales

adapt a software product to a particular language and culture of the target market.

Context of and specific resources for assessment

Assessment must ensure access to:

specific requirements, including functional and non-functional requirements

tools to design software architecture

culture-specific information for the target culture or language

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 architecture requirements documentation

evaluation of software-layered architecture.

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:

assign a priority to each architectural requirement

determine areas of concern

communication skills to:

interact with others of different cultures to globalise a software product

interact with stakeholders to gather architectural requirements

initiative and enterprise skills to identify potential improvements to the structure of software and existing systems

literacy skills to:

maintain a complete list of architectural requirements

prepare architectural requirements questionnaire to system stakeholders

problem-solving skills to:

communicate with external systems

determine the possibility of reusing the existing legacy components

technical skills to:

analyse software requirements

design software applications.

Required knowledge

basic knowledge of database design

current software development methodologies

detailed knowledge of:

object-oriented programming

software development life cycle.

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.

Architectural requirements may include:

design requirement

functional requirements

non-functional requirements:

maintainability

performance

reliability

scalability

security

usability

quality requirements.

Layers may include:

business logic layer (BLL)

data-access layer (DAL)

services layer

user interface (UI) layer.

Cross-cutting concerns may include:

caching (improve performance)

communications (protocols)

configuration management

data protection

operational management

security:

authentication

authorisation.