Assessor Resource

ICAPRG506A
Design application architecture

Assessment tool

Version 1.0
Issue Date: March 2024


This unit is relevant to those who work as software architects, developers, designers, software engineers or programmers responsible for designing and building solution architects.

This unit addresses the knowledge and processes necessary to produce the high-level design (blueprint) of a system.

This unit describes the performance outcomes, skills and knowledge required to design the structure of software or systems components and how they interact. The unit focuses on layered architectural style.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)

Prerequisites

Not applicable.


Employability Skills

This unit contains employability skills.




Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

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.


Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)


Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

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.

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.

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Gather information regarding architectural requirements 
Establish and document architectural requirements 
Separate the areas of concern into logical layers 
Determine the cross-cutting concerns 
Define the system into components 
Identify the responsibilities of each component 
Identify interconnections between components 
Determine an appropriate strategy for communicating with external systems 
Interact with existing legacy components 
Determine culture-specific information 
Consider database design features 
Select appropriate user interface 
Develop software product for worldwide distribution 
Develop software product for specific country 

Forms

Assessment Cover Sheet

ICAPRG506A - Design application architecture
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:


Assessment Record Sheet

ICAPRG506A - Design application architecture

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: