Criterion 3 assesses students’ skills in documenting a software requirements specification. Students will document the functional and non-functional requirements, constraints and scope as well as the user characteristics and the technical environment for the proposed software solution. The software requirements specification is to be presented as a formal document. Analytical tools developed in Criterion 2 are to be included in the appendix of the software requirements specification. An outline of the content required in the software requirements specification is in the _Support material_. Students will document evidence of their critical and creative thinking using questions and follow-up questions to clarify the development of the solution requirements as part of the Analysis stage in Criterion 2 and 3. Refer to the Skills underpinning the Analysis stage in the Units 1 to 4: Problem-solving methodology specifications on page 18 of the study design. The evidence from this task is observed through Observation 3 and assessed through Criterion 3. # Rubric | **Assessment Criteria** | **Indicators** | **Levels of Performance** | | | | | | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Not shown** | | | **1–2 (very low)** | **3–4 (low)** | **5–6 (medium)** | **7–8 (high)** | **9–10 (very high)** | | **Unit 3 Outcome 2**<br><br>**3.    Skills in** **documenting <br>a software requirements specification.** | ·     Documents the proposed software solution as part of <br>an SRS. | Insufficient evidence | Lists solution requirements. | Outlines the purpose and requirements of the proposed software solution in a formal document. | Documents the functional and non-functional requirements of the proposed software solution.<br><br>Documents the constraints that may impact the development of the proposed solution.<br><br>Documents the analytical tools. | Describes the characteristics of the users for the proposed software solution.<br><br>Describes the scope of the proposed software solution. | Describes the technical environment in which the proposed software solution will operate.<br><br>Organises the formal document using clear headings, sections and appendices. | | ·     Documents the process of critical and creative thinking through critical analysis, the use of questions and follow-up questions to clarify the development of the software requirements specification. | Identifies the data that needs to be collected to inform the development of the software requirements specification. | Outlines the use of questions to critically analyse the data collected to inform the development of the software requirements specification. | Write questions to critically analyse the development of the software requirements specification. | Evaluates questions to critically analyse the development of the software requirements specification. | Writes follow-up questions to clarify the data collected to inform the development of the software requirements specification. | | | | | | | | | | | |