DESIGN

SM-DUO app
PRODUCT DESIGN - <PRODUCT NAME>

<mm/dd/yyyy>

By:
<Student Name>
<Student Number >

VERSION HISTORY
Version Author Date Alterations Reason
File
0.0 …… ……… N/A Template Document
1.0 <name> <date> <filename> Formative Delivery
[Note to Author to view template comments, please make sure Word shows
the hidden text (File > Options > Display > Hidden Text), please remove
this sentence afterwards.]

Page 2 of 14
 TABLE OF CONTENTS

Table of Contents
1 PRODUCT DEFINITION...................................................................4
Current situation............................................................................4
Purpose of Product.........................................................................4
Contributions.................................................................................4
2 PERSONAS......................................................................................5
Data collection...............................................................................5
Skeleton 1: <audience>..................................................................6
Persona Poster: <name>................................................................8
3 USE CASES......................................................................................9
Storyboard....................................................................................9
Actors …………………………………………………………………………………………………………9
Use-Case Diagram..........................................................................9
Use-Case Specifications...................................................................9
Use-Case Specification: <ID> - <Name>.....................................9
4 TASK ANALYSIS............................................................................10
Task decomposition......................................................................10
Task flow diagram........................................................................10
Task model summary....................................................................10
5 INTERACTIVE PROTOTYPE DESIGN..............................................11
6 FEASIBILITY ANALYSIS................................................................12
Risks…........................................................................................12
Feasibility & Viability.....................................................................12
7 REFERENCES.................................................................................13
8 GLOSSARY OF TERMS...................................................................14

Page 3 of 14
1 Product Definition
Current situation
Purpose of Product
Contributions

Page 4 of 14
2 Personas
Data collection

Page 5 of 14
 Skeleton 1: <audience>

<image of the persona>

Persona description
a Name
b Title
c Short description
d Age
e Gender
f Identifying
tagline/nickname
g Quote
h Region, city, country
i Education level
j Marital status
k Computer and/or internet
use
l Frequently used products
m Income
n Spending habits:

Job, Role, Activities

a Specific company or
industry
b Job title or role
c Typical activities
d Challenges
e Important atypical
activities
f Responsibilities
g Daily commute

Goals
a Long-term
b Short-term
c Motivations:
d Work related goals
e Product-related goals
f General (life) aspirations

Context/Environment
a Timeline of a typical day
b Most frequent locations
c A day in the life
d When uses the product
e How frequent
f Where uses the product
Page 6 of 14
g How uses the product
h Why uses the product

Page 7 of 14
Persona Poster: <name>
3 Use Cases
Storyboard
Actors
Name Type Description
<Actor Name > <Primary/Secondary> <General description >

Use-Case Diagram
Use-Case Specifications
Use-Case Specification: <ID> - <Name>
Use Case <Id> & <Name> By <Author> &
<Date>
Timeframe <Frequency and Relevance <How important
duration> is this use case>
Actors <Actor list>
Description <Description of the Goal (intension of the actors)>
Pre-conditions <System state before Post-conditions <System state
the use case starts> after the use
case ends>
Scenario <List of steps, each step shall be identified>
Variations <Alternative path to specific steps depending of
issues/conditions/errors/etc >
Requirements <List of mandatory requests>
Notes <Anything else that might be relevant>
4 Task Analysis
Task decomposition

Stages
1 Identify goal High-level user goal when interacting with the product
2 Break into 4-8 tasks Should be specified in terms of objectives and between
them support the goal
3 Draw subtasks In textual form and as a layered diagram ensuring that
it is accurate and complete
4 Decide upon level of Until mandatory - optional tasks and plans are well
detail represented as a task flow diagram
5 Ensure consistency Decompositions and numbering are consistent
6 Present the analysis Check task model for consistency

Task flow diagram

Task model summary

Page 10 of 14
5 Interactive Prototype Design
Heuristics
1 Visibility of system [Max 25 words describe how the system should always
status keep users informed about what is going on]
2 Match between [Max 25 words describe how the system should speak the
system and the users' language, with words, phrases and concepts
real world familiar to the user. Follow real-world conventions,
making information appear in a natural and logical order.]
3 User control and [Max 25 words describe how users often choose system
freedom functions by mistake and will need a clearly marked
"emergency exit" to leave the unwanted state without
having to go through an extended dialogue. Support undo
and redo.]
4 Consistency and [Max 25 words what was done so users should not have
standards to wonder whether different words, situations, or actions
mean the same thing]
5 Error prevention [Max 25 words even better than good error messages is a
careful design that feeds-forward, which prevents issues
and problems.]
6 Recognition rather [Max 25 words describe what was done to Minimize the
than recall user's memory load by making objects, actions, and
options visible. The user should not have to remember
information or instructions]
7 Flexibility and [Max 25 words describe allow users to increase
efficiency of use performance, by allowing customization and accelerate
the user experience to both cater for both inexperienced
and experienced users]
8 Aesthetic and [Max 25 words describe how all unit of information in the
minimalist design product are relevant and adds to increase user
awareness]
9 Support users [Max 25 words describe how messages should be
expressed in plain language; precisely indicate the
situation and problem and hints solutions].
1 Help and [Max 25 words describe how even though it is better if
0 documentation the system can be used without documentation, what was
made to provide help and documentation. ]

Page 11 of 14
6 Feasibility Analysis

Internal Factors Users

1 # Users on launch [Target number of users on launch]
2 # Users after 1 [Total number of users after 1 year]
year
3 Security & Privacy [Max 25 words: Considerations on sensitive, private and
public data]
4 Monetization [Max 25 words: Revenue and required endorsement, e.g.,
in-app billing, appstore, adv based, paypal]
5 Moderation [Max 25 words: User miss-behavior and content filtering]
6 Customer Service [Max 25 words: Individual user support service]

Internal Factors Systems

1 Client Platform [Targeted device, Mobile, Browser, VR, AR]
2 Server Platform [Type of server platform, type of XaaS]
3 Backup policy [how and who is responsible for Backups daily, weekly,
monthly, and for how long the data is kept]
4 Monitoring policy [Max 25 words: how and who monitors the system, e.g.
Data analytics platform, e.g., Google Analytics, Roambi]
5 Storage [Max 25 words: Server network requirements considering
number of users after 1 year]

External Factors
1 Technological [Max 25 words: New trends, development cost alteration,
maintenance]
2 Economical [Max 25 words: New competitors, production,
distribution, shipping, production]
3 Social & Political [25 words: Trust, Privacy, Law, Patent, Embargos, Taxes,
Investments]
4 Competitive [25 words: Attractiveness of the area, development of
new knowledge]

Risks
Feasibility & Viability

Page 12 of 14
7 References

Page 13 of 14
8 Glossary of Terms
The following table provides definitions for terms relevant to this document.

Term Definition

Page 14 of 14