You are on page 1of 2

J0069

Laboratory Exercise

Requirements Gathering and Storyboarding


Objectives:
At the end of the exercise, the students should be able to:

identify the client requirements, and


use storyboards to communicate ideas about the clients needs.

Materials:

PC or Laptop with internet connection

Basic Principles:
What is Requirements Gathering (RG)?
As the name implies, requirements gathering involves gathering of information to the potential users and the
environment in which the system will be used so that we may deeply understand and help the users to figure
out their needs that can be successfully provided within the cost and schedule parameters available to the
development team. This can be done through a combination of interview and observance of the prospect
company through user surveys and analysis of existing manual system.
What is Storyboarding?
Storyboarding refers to demonstrating to the potential users how a system will look like (from screens,
dialogs, toolbars, and other elements one believes the software should provide) or how the different parts of
a system, could work/relate to one another through a set of drawing/painting tools (pen-and-paper sketches
(shown in Figure 2.1) or computer-based), which depicts a set of user activities that occur in an existing or
envisioned system or capability.

Figure 2.1 Pen-and-Paper Sketches

02 Laboratory Exercise 1

*Property of STI
Page 1 of 2

J0069

Procedures:
1. Ask the group to create a standard instrument (in tabular form), which will serve as their basis in
gathering clients system requirements based on the company they have chosen on their 01
Laboratory 1. The instrument shall compose of the following:
a. Functions that a system needs This provides descriptions of how modules of the system
interacts through events, states, and state transitions.
b. Types of input and output required
c. Environment in which the system will be used (technical or non-technical)
d. User groups This defines the players, or the users of the system.
e. Key usable issues This represents the behavior of the users as they interact with the
system as well as the behavior of the system as it interacts with the user.
2. Create a storyboard based on system requirements gathered. Use Microsoft Powerpoint as your
storyboard presentation tool to build one Powerpoint slide for each of the steps in the use case
to show the user how you intent the system to work.

Example:

02 Laboratory Exercise 1

*Property of STI
Page 2 of 2

You might also like