5 - Description PDF

Preview

Summary

Description
...

Description

Faculty of Science, Engineering and Technology

User-Centred Design Task 5.1C Requirements Specifications ILO

Apply an evidence-based approach to software requirements elicitation and specification.

Purpose:

Writing good requirements is difficult, particularly when they need to be made explicit. In previous tasks you have been working to extract requirements from your data and models. In this task you will put them all together into one coherent document. You will also have the opportunity to negotiate the requirements proposed in UCD Requirements (i.e., add other requirements and/or re-prioritise the proposed requirements).

Group Task:

Write a set of requirements for the software

Resources:

Lecture Notes: Topic 05 - Requirements Specification Textbook: Hartson & Pyla Ch 5 (functional requ) and 10 (usability requ) UCD IEEE Template for SRS [provided on Doutfire task Resources]

To be marked as Complete your submission must have:

Use a modified version of the IEEE Template for Software Requirements Specification (SRS) Part 1: Context of Use ■ Accurately describes project and context of use Part 2: Interface, functional and non-nonfunctional requirements Set of Requirements that has the following characteristics: ■ organised logically into related categories of function or parts of the interface ■ requirements written in appropriate and consistent format (see UCD IEEE Template for SRS and previous tasks) at least 15 functional requirements ■ ■

Hint:

professional presentation, including proper sentences and paragraphs

Submission Note: If you have group members who do not want to participate in this C task, give them no ‘people power’/‘no effort’ when submitting on Doubtfire and add a note as to why.

User-Centred Design

Overview A requirements document (sometimes known as a Software Requirement Specification (SRS)) specifies what needs to be developed. Getting it wrong could cause the project to fail. Writing and presenting requirements in a clear and well organised way will help make sure everyone understands the requirements in the same way, and make them easier to review for mistakes and completeness. In this task you will further develop your ability to write requirements by preparing a document that systematically presents the project requirements.

Instructions 1. Bring together the requirements collected in previous tasks and organise them into related categories. Note: For the Task Model task you may only have provided one or two example requirements, for this task you should look for requirements at each sub-task of your HTA. 2. Look for any requirements that appear to be missing, or that you missed in your previous analysis. 3. Consider any extrapolations or constraints in the project. 4. Ensure you make reference to context of use in your Overview (either include appendices or refer to other Tasks). Note 1: An extrapolation is where you propose a requirement because it seems logically necessary, but you do not have data that directly supports it. Note 2: A constraint is a requirement imposed because of some limitation. For example, the need to work in with existing system, hardware, technology or budgetary (time/money) restrictions. 5. Complete the UCD IEEE SRS template. Note that the full template has been provided, but for the purpose of this task you only need to complete the specified sections (i.e., some sections have been marked as not required).

Note: When writing this Task: ■

create a coherent document that is easy for the reader to review and assess (e.g., grouping of related requirements using subheading and appropriate numbering),

■

provide a strong rationale for requirements,

■

provide traceability for the requirement (i.e., indicate where it came from).

Page 2 of 2 ...