HUMERA Polytechnic College

Training, Teaching and Learning Materials Development

yes

LO 4: Submit analysis and gain agreement

\

INTRODUCTION Learning Guide # 1

This learning guide is developed to provide you the necessary information regarding the following content
coverage and topics –

This guide will also assist you to attain the learning outcome stated in the cover page.
Specifically, upon completion of this Learning Guide, you will be able to –
 prepare detailed documents according to documentation standards and organisational templates
 write documents in a style that is succinct and appropriate to the audience
 communicate data gathered to the client to gain consensus and agreement on business requirements
Learning Activities

1. Read the specific objectives of this Learning Guide.

2. Read the information written in the “Information Sheets 1” in pages 3-6.
3. Accomplish the “Self-check” in pages 7.
4. If you earned a satisfactory evaluation proceed to “Information Sheet 2”. However, if your rating is
unsatisfactory, see your teacher for further instructions or go back to Learning Activity # 1.
5. Read the information written in the “Information Sheet 2” in pages 8-11.
6. Accomplish the “Self-check” in page 12.
7. If you earned a satisfactory evaluation proceed to “Lap Test”. However, if your rating is
unsatisfactory, see your teacher for further instructions or go back to Learning Activity # 2.
8. Do the “LAP test” on page 13 (if you are ready) and show your output to your teacher. Your teacher
will evaluate your output either satisfactory or unsatisfactory. If unsatisfactory, your teacher shall
advice you on additional work. But if satisfactory you can proceed to Learning Guide 7.

 Your teacher will evaluate your output either satisfactory or unsatisfactory. If unsatisfactory, your
teacher shall advice you on additional work. But if satisfactory you can proceed to the next topic.

Learning Guide Date: 11-2014 Page 1 of 8

1st Revision Author: IT DEPARTMENT
HUMERA Polytechnic College
Training, Teaching and Learning Materials Development

Information Sheet 1
Report findings
Report findings
The contents and degree of detail for a Requirements Report will vary depending on the size and scope of a
project, but a Requirements Report is generally an informal document that can be easily understood by the
customer. The report may contain only business requirements, or it may extend to technical requirements and a
feasibility study. Your organisation will often provide a template for requirements documentation.
The purpose of the Requirements Report is to communicate and confirm the requirements. The next section
describes the purpose of the different sections of the report.

The requirements report

There are many templates available for writing a Requirements Report. This section looks at one possible report
layout. Here are some examples of alternative report layouts:
The IEEE Standard Structure for Requirements Documents (43 KB 2830_reading01.doc)
The Structure for a Requirements Document (45 KB 2830_reading02.doc)
Note: This resource discusses gathering data for business requirements only. The report template described
here covers a wider context than just business requirements.
The following headings may be used in a Requirements Report:
 Introduction
 System description
 Functional requirements
 Non-functional requirements
 Information domain
 Project costs
 Benefits
 Other project specific topics

Table 1: The table below summarises what each heading contains.

Requirements definition report elements

Introduction Purpose
Scope
Definitions
Overview of document
Systems description Overall system
Sub systems
Learning Guide Date: 11-2014 Page 2 of 8
1st Revision Author: IT DEPARTMENT
HUMERA Polytechnic College
Training, Teaching and Learning Materials Development
Operating environment
Functional requirements Logical view
Physical view
Non-functional requirements Performance
Quality
Business rules
Information domain Data definitions
Structure
Project costs Analysis
Software development
Hardware and network
Benefits Tangible
Intangible

These headings are described in detail below.

Introduction
The introduction defines the purpose of the document with a summary of the entire document.
The introduction should describe the scope of the system—i.e. what functions the system will implement.

System Description
This describes top-level functions of the system and the system environment. Diagrams (eg Use Cases and
Context Diagrams) can be used to model the system and interactions with its environment.
For example, if the system is a website, you could include a top level storyboard to demonstrate the main
functions to the client.

Functional Requirements
The functional requirements define the services that the system provides.
Examples of mandatory (“must”) and desirable (“may”) functional requirements might be:
 The system Must associate non-stock purchases of raw materials to a specified customer order
 The system Must associate design work as well as production work to customer special orders
 The system Must provide a users’ guide for products
 The system Must capture customer details online
 The system May have password protection for a members only section
 The system May track the completion status of customer special orders
Case diagrams, Data Flow diagrams and Statechart diagrams are common techniques used to describe the
system’s functions.
Storyboards
Learning Guide Date: 11-2014 Page 3 of 8
1st Revision Author: IT DEPARTMENT
HUMERA Polytechnic College
Training, Teaching and Learning Materials Development
A common technique for providing functional information for websites to the client is to provide a storyboard.
Storyboards are a visual representation of what a website interface is supposed to look like. They can consist
of a site map and a detailed representation of some or all of the pages in the site.
Here is an example of a site map:

Image: Sample site map

Figure 1: Sample site map

Here is an example of a mock up of a website page:

Image: Sample mock up of a website page

Figure 2: Sample mock up of a website page

Storyboards are most appropriate for use with website design. The storyboard has its foundation within the
visual arts field of film and television. The intention of a storyboard is to provide a visual representation of the
structure and content of an interface – whether it is a movie or a website. Storyboarding is used to lay out the
pages and media elements before actually creating the site. Through storyboarding, the designer can see what
the website will look like before constructing it. The technical requirements may include a detailed or
conceptual storyboard.
For more details about storyboards, review this extract (44 KB 2830_reading03.doc) from the Toolbox on
Certificate IV Web Design.

Learning Guide Date: 11-2014 Page 4 of 8

1st Revision Author: IT DEPARTMENT
HUMERA Polytechnic College
Training, Teaching and Learning Materials Development
Activity 1
To practise creating functional requirements, complete Activity 1 – Functional requirements located in the
Activities section of the Topic menu.

Non-Functional Requirements
Non-functional requirements define any constraints within which the current system operates. Examples of
this include database size, response times and web page download times.

Information domain
Information domain defines the data requirements of the system. ER diagrams, Class diagrams and Data
Dictionaries are common techniques used to describe a system’s data.
For websites, the storyboard information should be expanded to show what information (web pages) will be
included.

Project Costs
Project costs defines estimated costs of the project in terms of development and running costs.

Benefits
Benefits defines the areas that the new system will improve. This includes benefits measurable in dollars
(tangible benefits), and those that cannot be measured in dollars (intangible benefits) but are important
nonetheless.

Other project specific topics

Other project specific topics defines any other topics that may have an impact on the project. These may
include such things as methodology, legal implications or employee acceptance etc.
Requirements Definition Report Example (46 KB 2830_reading04.doc) This resource has been
abstracted from resources authored by Barrier Reef Institute of TAFE in consortium with TAFE Qld On-
Line.

Learning Guide Date: 11-2014 Page 5 of 8

1st Revision Author: IT DEPARTMENT
HUMERA Polytechnic College
Training, Teaching and Learning Materials Development

Self-Check 1 Written Test

Name:____________________ Date:_________________
Instruction: Answer all the questions listed below, if you have some clarifications- feel free to ask your teacher.

Please ask your trainer for the questionnaire for this Self-Check.

Learning Guide Date: 11-2014 Page 6 of 8

1st Revision Author: IT DEPARTMENT
 HUMERA Polytechnic College
Training, Teaching and Learning Materials Development

Operation Sheet 1 Functional requirements

Activity 1 - Functional requirements

A workshop was held with Bazaar Ceramics in order to determine the requirements for the proposed website.
The workshop was conducted to compile a comprehensive list of website feature and functions which were
ranked by participants in order of importance. The results of the workshop can be found in the Bazaar
requirements data (36 KB 2830_activity01.xls). It contains the requirements ranked in importance from highest
to lowest, high having a larger number and low having smaller number.
Pair up with another student. Together, analyse the information in the above document and work together to create a
list of mandatory and desirable functional requirements that will form part of a Requirements Report. Use the
relevant section of the Requirements Report Template (34 KB 2830_activity01.doc) for this.

Activity 2 – Role play: Presenting the requirements to the client

You are about to go to a meeting with your client at Bazaar Ceramics to present the mandatory and desirable
functional requirements. The goal of the role play is to deal with any objections your client may have, and to
reach agreement on the requirements.
Your teacher will assign you to teams of four – made up of the pairs from the previous activity.
In your pairs, prepare your presentation to the client. Consider the questions and objections your client may
have and how you will deal with them.
Round 1
Deliver the presentation to the client; the other pair plays the role of the client.
Round 2
Reverse roles (or rotate pairs) so that the pair who played the role of the client is now presenting their
requirements.
Each pair now gives feedback to the pair who presented to them. Give feedback on both the written document
(the Requirements Report) and the presentation itself.

Learning Guide Date: 11-2014 Page 7 of 8

1st Revision Author: IT DEPARTMENT
HUMERA Polytechnic College
Training, Teaching and Learning Materials Development

Lap Test Practical Demonstration

Name: _____________________________ Date: ________________

Time started: ________________________ Time finished: ________________

Instructions: You are required to perform the following individually with the presence of your
teacher.

 Please ask your trainer for the instructions for this lap test.

 Your teacher will evaluate your output either satisfactory or unsatisfactory. If

unsatisfactory, your trainer shall advice you on additional work. But if satisfactory, you
can proceed to the next topic.

Learning Guide Date: 11-2014 Page 8 of 8

1st Revision Author: IT DEPARTMENT