ICASAD606A Analyse stakeholder requirements

Release: 1

ICASAD606A Analyse stakeholder requirements

Modification History

Release	Comments
Release 1	This Unit first released with ICA11 Information and Communications Technology Training Package version 1.0

Unit Descriptor

This unit describes the performance outcomes, skills and knowledge required to analyse stated requirements, determine potential solutions, and define possible features available to meet stakeholder needs.

Application of the Unit

This unit applies to senior business analysts in medium to large organisations who define the IT requirements (both stakeholder and solution requirements) of one or more stakeholder groups in enough detail to allow solution components to be constructed.

Their job roles combine high-level management, business and technical skills necessary to manage complex analysis efforts within the information and communications technology (ICT) industry, often as part of business critical IT projects.

Licensing/Regulatory Information

No licensing, legislative, regulatory or certification requirements apply to this unit at the time of endorsement but users should confirm requirements with the relevant federal, state or territory authority.

Pre-Requisites

Not applicable.

Employability Skills Information

This unit contains employability skills.

Elements and Performance Criteria Pre-Content

Element	Performance Criteria
Elements describe the essential outcomes of a unit of competency.	Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the required skills and knowledge section and the range statement. Assessment of performance is to be consistent with the evidence guide.

Elements and Performance Criteria

1. Prioritise requirements	1.1 Determine the basis for prioritisation of requirements 1.2 Resolve challenges in facilitating the prioritisation
2. Organise requirements	2.1 Articulate requirements at an appropriate level of abstraction 2.2 Devise appropriate models to describe the solution scope based on informational needs of stakeholders 2.3 Document dependencies and interrelationships among requirements
3. Specify and model requirements	3.1 Develop textual requirements 3.2 Generate matrices to convey or support identified requirements 3.3 Create models to document and communicate requirements and improvement opportunities
4. Define assumptions and constraints	4.1 Agree on assumptions to be defined and clarified as requirements are understood 4.2 Document and examine business constraints to identify options no longer available 4.3 Recognise and examine technical constraints that may restrict design or mandate standards to be followed
5. Verify requirements	5.1 Establish characteristics of requirements’ quality 5.2 Undertake verification activities iteratively throughout the requirements analysis process
6. Validate requirements	6.1 Identify and define stakeholder requirement benefit assumptions so that associated risks can be managed 6.2 Generate measurable evaluation criteria to assess success of requirements benefit post-implementation 6.3 Assign business value of requirements to assist in identifying candidates for elimination 6.4 Determine requirement dependencies for benefits realisation 6.5 Evaluate alignment with business case and opportunity cost to assist validation and decision making

Required Skills and Knowledge

This section describes the skills and knowledge required for this unit.

Required skills

analytical skills to review organisational and technical business solutions

communication skills to:

conduct focus groups and requirements workshops

conduct research and interviews

liaise with stakeholders

analytical skills to prioritise requirements

technical writing skills to develop requirements documents and specifications

technical modelling skills to develop models of systems, processes and solutions.

Required knowledge

business rules analysis

data flow diagramming

data modelling

functional decomposition

organisation modelling

process modelling

risk management strategies

scenarios and use cases

scope modelling

user stories.

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: define, specify and prioritise stakeholder and solution requirements to a standard that would allow construction of a business solution verify and validate the requirements to ensure necessary quality and support for stakeholder needs.
Context of and specific resources for assessment	Assessment must ensure access to: documentation, including appropriate policies, current business analysis practices, tools and legislation 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: evaluation of a simulated or workplace project in a medium to large enterprise direct observation of the candidate carrying out business analysis work verbal or written questioning to assess required knowledge and skills review of reports and plans prepared for the projects evaluation of a portfolio of the project work undertaken.
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.

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.

Basis for prioritisation may include:	difficulty of implementation relative value likelihood of success risk regulatory or policy compliance relationship to other requirements stakeholder agreement urgency.
Challenges may include:	non-negotiable demands, e.g. stakeholders wish to rank all requirements as high priority unrealistic tradeoffs, e.g. difficulty or complexity of implementing certain requirements may be overstated.
Appropriate level is determined by:	particular methodology being used whatever level of abstraction is appropriate for the audience.
Appropriate models may include:	data flow diagrams data models functional decomposition organisation models process models scenarios and use cases scope models user stories.
Business constraints may include:	organisational restrictions budgetary restrictions limits on the number of resources available restrictions based on skills of the project team and stakeholders scope restrictions time restrictions.
Technical constraints may include:	application software that must be used architecture decisions that are made that may impact the design of the solution, such as: development languages hardware and software platforms application software that must be used restrictions, such as resource use message size and timing software size maximum number of and size of files records and data elements enterprise architecture standards that must be followed.
Characteristics of requirements’ quality may include:	cohesiveness completeness consistency correctness feasibility modifiable testable unambiguous.

Unit Sector(s)

Systems analysis and design