SAQA All qualifications and part qualifications registered on the National Qualifications Framework are public property. Thus the only payment that can be made for them is for service and reproduction. It is illegal to sell this material for profit. If the material is reproduced or quoted, the South African Qualifications Authority (SAQA) should be acknowledged as the source.
SOUTH AFRICAN QUALIFICATIONS AUTHORITY 
REGISTERED UNIT STANDARD: 

Perform requirements analysis 
SAQA US ID UNIT STANDARD TITLE
259277  Perform requirements analysis 
ORIGINATOR
SGB Computer Sciences and Information Systems 
PRIMARY OR DELEGATED QUALITY ASSURANCE FUNCTIONARY
-  
FIELD SUBFIELD
Field 10 - Physical, Mathematical, Computer and Life Sciences Information Technology and Computer Sciences 
ABET BAND UNIT STANDARD TYPE PRE-2009 NQF LEVEL NQF LEVEL CREDITS
Undefined  Regular  Level 6  Level TBA: Pre-2009 was L6  25 
REGISTRATION STATUS REGISTRATION START DATE REGISTRATION END DATE SAQA DECISION NUMBER
Reregistered  2018-07-01  2023-06-30  SAQA 06120/18 
LAST DATE FOR ENROLMENT LAST DATE FOR ACHIEVEMENT
2024-06-30   2027-06-30  

In all of the tables in this document, both the pre-2009 NQF Level and the NQF Level is shown. In the text (purpose statements, qualification rules, etc), any references to NQF Levels are to the pre-2009 levels unless specifically stated otherwise.  

This unit standard does not replace any other unit standard and is not replaced by any other unit standard. 

PURPOSE OF THE UNIT STANDARD 
This unit standard will enable learners to perform requirements analysis in order to validate that the requirements meet the business need.

A learner credited with this unit standard will be able to:
  • Organise requirements.
  • Prioritise requirements.
  • Specify and model requirements.
  • Determine assumptions and constraints.
  • Verify and validate requirements. 

  • LEARNING ASSUMED TO BE IN PLACE AND RECOGNITION OF PRIOR LEARNING 
  • Communication at NQF Level 5.
  • Understanding of requirements processes at NQF Level 5.
  • Facilitation skills at NQF Level 5. 

  • UNIT STANDARD RANGE 
    N/A 

    Specific Outcomes and Assessment Criteria: 

    SPECIFIC OUTCOME 1 
    Organise requirements. 

    ASSESSMENT CRITERIA
     

    ASSESSMENT CRITERION 1 
    The business case, solution scope and initial requirements documents are examined in order to organise and structure the requirements in a logical format. 

    ASSESSMENT CRITERION 2 
    The initial requirements are structured and organised into logical sets. 
    ASSESSMENT CRITERION RANGE 
    The organisation of requirements includes but is not limited to multiple levels of requirements, packaging related functions together.
     

    ASSESSMENT CRITERION 3 
    A structured requirements document is produced to be used in requirements analysis. 

    SPECIFIC OUTCOME 2 
    Prioritise requirements. 

    ASSESSMENT CRITERIA
     

    ASSESSMENT CRITERION 1 
    The business priority of each of the listed requirements is negotiated with stakeholders using various techniques. 
    ASSESSMENT CRITERION RANGE 
    Techniques include but are not limited to voting, ranking, benefit analysis.
     

    ASSESSMENT CRITERION 2 
    Logical dependencies between requirements and requirements packages are identified as input for the project planning process. 

    ASSESSMENT CRITERION 3 
    A prioritised requirements list is produced using the business and project priorities and the identified dependencies between requirements. 

    ASSESSMENT CRITERION 4 
    The prioritised requirements are communicated with all stakeholders in order to obtain agreement on the sequence of development of the requirements. 

    SPECIFIC OUTCOME 3 
    Specify and model requirements. 

    ASSESSMENT CRITERIA
     

    ASSESSMENT CRITERION 1 
    Requirements are documented using standard practices for writing textual specifications. 
    ASSESSMENT CRITERION RANGE 
    Standard practices include but are not limited to use case narrative, structured requirements, user stories.
     

    ASSESSMENT CRITERION 2 
    Requirements are modelled using various modelling techniques in order to understand and communicate the understanding of requirements to all stakeholders. 
    ASSESSMENT CRITERION RANGE 
    Modelling techniques include but are not limited to use case model, context diagram, system interaction diagram, process model, activity diagram, data flow diagram, user interface model, prototype, state machine, class diagram, entity relationship diagram.
     

    ASSESSMENT CRITERION 3 
    Requirement attributes are captured to ensure that requirements are fully documented to a level where they can be used to design and implement a solution. 

    ASSESSMENT CRITERION 4 
    Business rules are documented using various techniques to ensure that they are understood by all stakeholders. 
    ASSESSMENT CRITERION RANGE 
    Techniques include but are not limited to natural language, structured text, pseudocode, decision tree, decision table.
     

    SPECIFIC OUTCOME 4 
    Determine assumptions and constraints. 

    ASSESSMENT CRITERIA
     

    ASSESSMENT CRITERION 1 
    Stakeholder requests are examined to determine whether they are actual requirements or based on assumptions about what can be delivered by the solution team. 

    ASSESSMENT CRITERION 2 
    Constraints which the stakeholders wish to impose on the solution are analysed and documented as quality requirements to ensure that the delivered solution will comply with all constraints. 

    ASSESSMENT CRITERION 3 
    Quality requirements are documented to ensure that the solution delivered can be tested against these requirements. 
    ASSESSMENT CRITERION RANGE 
    Quality requirements include but are not limited to performance, control, conformance, compliance, geographical, interface to external systems, operational, ergonomics.
     

    SPECIFIC OUTCOME 5 
    Verify and validate requirements. 

    ASSESSMENT CRITERIA
     

    ASSESSMENT CRITERION 1 
    The defined requirements are verified and validated to ensure that they will solve a business problem, satisfy a business need or provide a business opportunity. 

    ASSESSMENT CRITERION 2 
    Requirements are documented in the form of a requirement specification that can be understood by all stakeholders. 

    ASSESSMENT CRITERION 3 
    The requirement specification is communicated to all stakeholders using appropriate techniques to ensure that they are complete. 

    ASSESSMENT CRITERION 4 
    The requirement specification is signed-off by all stakeholders so that it can be used as a baseline for design and implementation of an appropriate solution. 


    UNIT STANDARD ACCREDITATION AND MODERATION OPTIONS 
  • An individual wishing to be assessed (including through RPL) against this Unit Standard may apply to an assessment agency, assessor or provider institution accredited by the relevant ETQA, or an ETQA that has a Memorandum of Understanding with the relevant ETQA.
  • Anyone assessing a learner against this Unit Standard must be registered as an assessor with the relevant ETQA or with an ETQA that has a Memorandum of Understanding with the relevant ETQA.
  • Any institution offering learning that will enable achievement of this Unit Standard or assessing this Unit Standard must be accredited as a provider with the relevant ETQA or with an ETQA that has a Memorandum of Understanding with the relevant ETQA.
  • Moderation of assessment will be conducted by the relevant ETQA at its discretion. 

  • UNIT STANDARD ESSENTIAL EMBEDDED KNOWLEDGE 
  • Progressively elaborate stated requirements to sufficient level of detail that accurately defines the business need within specified scope.
  • Progressively elaborate the solution definition in order to enable the project team to design and build a solution that will meet the needs of the business and stakeholders.
  • Analyze the stated requirements of our stakeholders to ensure that they are correct.
  • Assess the current state of the business to identify and recommend improvements.
  • Document the quality requirements.
  • Produce a requirements specification document.
  • Communicate the requirements specification.
  • Verify requirements specification is complete and of acceptable quality.
  • Validate requirements specification meets the business need. 

  • UNIT STANDARD DEVELOPMENTAL OUTCOME 
    N/A 

    UNIT STANDARD LINKAGES 
    N/A 


    Critical Cross-field Outcomes (CCFO): 

    UNIT STANDARD CCFO IDENTIFYING 
    Identifying and solving problems in which responses display that responsible decisions using critical and creative thinking have been made when:
  • Organising requirements.
  • Modelling requirements. 

  • UNIT STANDARD CCFO WORKING 
    Working effectively with others as a member of a team, group, organisation, and community during:
  • Prioritising requirements.
  • Modelling requirements.
  • Determining assumptions and constraints. 

  • UNIT STANDARD CCFO ORGANISING 
    Organising and managing oneself and one's activities responsibly and effectively through:
  • Documenting requirements. 

  • UNIT STANDARD CCFO COLLECTING 
    Collecting, analysing, organising and critically evaluating information to better understand and articulation of:
  • Organising requirements.
  • Analysing requirements.
  • Determining assumptions and constraints. 

  • UNIT STANDARD CCFO COMMUNICATING 
    Communicating effectively using visual, mathematical and/or language skills in the modes of oral and/or written persuasion when:
  • Communication requirement specification to stakeholders. 

  • UNIT STANDARD CCFO SCIENCE 
    Using science, technology and indigenous knowledge effectively and critically, showing responsibility towards the environment and health of others through:
  • Modelling requirements. 

  • UNIT STANDARD CCFO DEMONSTRATING 
    Demonstrating an understanding of the world as a set of related systems by recognising that problem-solving contexts do not exist in isolation when:
  • Analysing requirements.
  • Determining assumptions and constraints. 

  • UNIT STANDARD ASSESSOR CRITERIA 
    N/A 

    REREGISTRATION HISTORY 
    As per the SAQA Board decision/s at that time, this unit standard was Reregistered in 2012; 2015. 

    UNIT STANDARD NOTES 
    N/A 

    QUALIFICATIONS UTILISING THIS UNIT STANDARD: 
      ID QUALIFICATION TITLE PRE-2009 NQF LEVEL NQF LEVEL STATUS END DATE PRIMARY OR DELEGATED QA FUNCTIONARY
    Core  83026   National Certificate: Information and Communications Technology (ICT) Software Testing  Level 5  NQF Level 05  Reregistered  2023-06-30  MICTS 
    Core  63909   National Certificate: Business Analysis  Level 6  Level TBA: Pre-2009 was L6  Reregistered  2023-06-30  MICTS 


    PROVIDERS CURRENTLY ACCREDITED TO OFFER THIS UNIT STANDARD: 
    This information shows the current accreditations (i.e. those not past their accreditation end dates), and is the most complete record available to SAQA as of today. Some Primary or Delegated Quality Assurance Functionaries have a lag in their recording systems for provider accreditation, in turn leading to a lag in notifying SAQA of all the providers that they have accredited to offer qualifications and unit standards, as well as any extensions to accreditation end dates. The relevant Primary or Delegated Quality Assurance Functionary should be notified if a record appears to be missing from here.
     
    NONE 



    All qualifications and part qualifications registered on the National Qualifications Framework are public property. Thus the only payment that can be made for them is for service and reproduction. It is illegal to sell this material for profit. If the material is reproduced or quoted, the South African Qualifications Authority (SAQA) should be acknowledged as the source.