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