Formats and tools
- Unit Description
- Reconstruct the unit from the xml and display it as an HTML page.
- Assessment Tool
- an assessor resource that builds a framework for writing an assessment tool
- Assessment Template
- generate a spreadsheet for marking this unit in a classroom environment. Put student names in the top row and check them off as they demonstrate competenece for each of the unit's elements and performance criteria.
- Assessment Matrix
- a slightly different format than the assessment template. A spreadsheet with unit names, elements and performance criteria in separate columns. Put assessment names in column headings to track which performance criteria each one covers. Good for ensuring that you've covered every one of the performance criteria with your assessment instrument (all assessement tools together).
- Wiki Markup
- mark up the unit in a wiki markup codes, ready to copy and paste into a wiki page. The output will work in most wikis but is designed to work particularly well as a Wikiversity learning project.
- Evidence Guide
- create an evidence guide for workplace assessment and RPL applicants
- Competency Mapping Template
- Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners. A template for developing assessments for a unit, which will help you to create valid, fair and reliable assessments for the unit, ready to give to trainers and students
- Observation Checklist
- create an observation checklist for workplace assessment and RPL applicants. This is similar to the evidence guide above, but a little shorter and friendlier on your printer. You will also need to create a seperate Assessor Marking Guide for guidelines on gathering evidence and a list of key points for each activity observed using the unit's range statement, required skills and evidence required (see the unit's html page for details)
- Self Assessment Survey
- A form for students to assess thier current skill levels against each of the unit's performance criteria. Cut and paste into a web document or print and distribute in hard copy.
- Moodle Outcomes
- Create a csv file of the unit's performance criteria to import into a moodle course as outcomes, ready to associate with each of your assignments. Here's a quick 'how to' for importing these into moodle 2.x
- Registered Training Organisations
- Trying to find someone to train or assess you? This link lists all the RTOs that are currently registered to deliver ICAPRG419A, 'Analyse software requirements'.
- Google Links
- links to google searches, with filtering in place to maximise the usefulness of the returned results
- Books
- Reference books for 'Analyse software requirements' on fishpond.com.au. This online store has a huge range of books, pretty reasonable prices, free delivery in Australia *and* they give a small commission to ntisthis.com for every purchase, so go nuts :)
Elements and Performance Criteria
1. Gather and confirm client requirements | 1.1 Confirm requirements and scope with the client 1.2 Gather information regarding requirements via sources of information and business processes 1.3 Analyse client requirements to determine the project scope and the problem context or opportunity faced by the business 1.4 Document client requirements, project scope, related problems and sources of information |
2. Analyse functional and related non-functional requirements | 2.1 Map business processes using modelling tools, such as unified modelling language (UML) 2.2 Determine opportunities for business process efficiencies 2.3 Document functional and related non-functional processes |
3. Analyse the feasibility of a project | 3.1 Analyse the technical feasibility of the project 3.2 Analyse the operational feasibility of the project 3.3 Determine the budget and schedule feasibility of the project 3.4 Examine how the project will fit within the organisation |
4. Develop high-level system solutions | 4.1 Develop and document feasible solutions for client requirements 4.2 Explore and document the feasibility of each solution 4.3 Examine alternatives against project constraints 4.4 Document assumptions, dependencies and required resources 4.5 Produce a project risk analysis 4.6 Document future requirements |
5. Prepare and publish software-requirements documentation | 5.1 Develop software-requirements document 5.2 Submit software-requirements report to appropriate person for project approval |