Page 200 - Educational Technology A Primer for the 21st Century

12.3 Original Requirements Analysis 193

Table 12.1 Elements of original requirements
Demand Originator
Project name
Time requirement
Original requirement Main plan and ordering or acquired the original requirement
description through the user interview
Acquire the requirement through the user interview, and the
product plan must be clear; who the product is meant for, who
pays for it, when will it be needed, and so on
Acquire the requirement through the main plan, the product
plan needs to know what the purpose of the main plan is, under
what condition does the main plan put forward this
requirement, and why this requirement is put forward and so
on
Target user
Design purpose The designer can abstract the design purpose based on the
original requirement
(That is why the main plan/user puts forward this original
requirement)
Using scenario
Product form Alternatives: mobile APP, VR APP, connecting to the system,
independent Web, independent client end, components, other
Priority adapting platform Alternatives: 101PAD, mobile phone, PC client end, WEB
version, VR equipment, etc.
Required material list
Signing and confirming by
the demand side
Keyword:

scenario, time requirement, product form, priority adapting platform, signing and
confirming of the originator and keyword, as shown in Table 12.1.

12.3.3 The Websoft Case

The chairman of the Websoft Company held a meeting with its CTO (Chief
Technology Officer) to discuss the eye protection function of the student tablet.
They determined what modules of functions this product should have, which
aspects of design need more attention, and other core contents.
After receiving the meeting recording, the designer analyzed and generated the
information structuralized of the meeting recording into a piece of the original
requirement table, as shown in Table 12.2.