Design docs

27 Aug 2005 - 3:39am
8 years ago
3 replies
672 reads
sudhindra
2004

Hello all,

I am in the process of creating a document that a UI designer/information
architect would ideally extract from and record in his first few meetings
with the clients/development team. It should also serve as a document that
the team can go back to and refer in case of doubts emerging in course of
development. At the least, the document should act as a base for the UI
designer to design the information flow and user interaction.

Can anybody help me with that? Is there such a document ready? Or some such
material in place? Any kind of help is appreciated.

Thanks and Regards

Sudhindra

Comments

27 Aug 2005 - 6:44am
Peter Boersma
2003

Sudhindra Venkatesha Murthy said:
> I am in the process of creating a document that a UI
> designer/information architect would ideally extract from and record in
> his first few meetings with the clients/development team.

Could it be something like the RUP's[1] "Vision" document?

Below is the description that we put together for EzGov when we created
StUX, the Standards for User Experience[2].

Goal
----
The goal of the vision is to gain agreement on what problems need to be
solved, identify stakeholders to the system, define the boundaries of the
system, and describe primary features of the system.

Description
-----------
The Vision provides a high-level, sometimes contractual, basis for the more
detailed technical requirements. It captures the "essence" of the envisaged
solution in the form of high-level requirements and design constraints that
give the reader an overview of the system to be developed from a behavioural
requirements perspective. It communicates the fundamental "why and what" for
the project and is a gauge against which all future decisions should be
validated.
The Vision document can also be created during the feasibility stage of a
project and enhanced during the inception phase.

Contents
--------
1. Introduction – (including purpose, scope)
2. Positioning - (including background and problem statement)
3. Stakeholder and user descriptions – (including market demographics, user
environment and user profile, stakeholder and user summary,
stakeholder/project contacts, key stakeholder and user needs)
4. Product Overview – (including product perspective, summary of key
capabilities)
5. Product Features
6. Other product requirements

Suggested reviewers
-------------------
Informal: Systems Architect
Formal: Project Team Leads

Relationships with other deliverables
-------------------------------------
Input from:
- Business Requirements
Output to:
- Use Cases (high-level)
- Task Analysis
Synchronous with:
- Use Case Model
- Supplementary Specifications

I hope this helps.
Peter

[1] Rational Unified Process, see:
http://en.wikipedia.org/wiki/Rational_Unified_Process
[2] My IA Summit presentation "StUX - integrating IA deliverables in a
software development methodology"
http://www.peterboersma.com/blog/2005/03/my-ia-summit-presentation-stux_10.html(Shorter URL to prevent problems with wrapping: http://tinyurl.com/dffef )
--
Peter Boersma | Consultant User Experience | www.UserIntelligence.com
Vlaardingenlaan 9 | 1059 GL | Amsterdam | The Netherlands
p:+31(0)204084296 | f:+31(0)204084298 | m:+31(0)615072747
mailto:peter at peterboersma.com | http://www.peterboersma.com/blog/

27 Aug 2005 - 8:34am
Lada Gorlenko
2004

SVM> I am in the process of creating a document that a UI designer/information
SVM> architect would ideally extract from and record in his first few meetings
SVM> with the clients/development team.

I agree with Peter on RUP Vision-style document; it's a solid starting
point. It works, however, if you are clear what you want to document
*before* you start talking to clients and product teams (which is
what one should do, really, because then you steer your conversations
towards what you need to know, not just listen to what a client wants
to tell you). If you didn't do the homework and are now looking for
a format to suit the data available, try IBM Ease of Use site for
inspiration. It outlines different work products that capture results
of different UX activities, some of which might match your data:
http://www-306.ibm.com/ibm/easy/eou_ext.nsf/publish/2022

Lada

27 Aug 2005 - 9:20pm
dszuc
2005

We have used "Design Memos" in the past when design commences that can
include:

Design Memo Name & Version No
=============================

* Screen Name

* Screen Type - primary, secondary etc

* Screen elements

* Screen Flow

* Comment Log - Designers, management, users etc.

Backgrounders:
==============

* Business Objectives

* Users

* Tasks (specific to the screen)

Daniel Szuc
Principal Usability Consultant
Apogee Usability Asia Ltd
www.apogeehk.com
'Usability in Asia'

Ph: +852 2581-2166
Fax: +852 2833-2961

-----Original Message-----
From:
discuss-interactiondesigners.com-bounces at lists.interactiondesigners.com
[mailto:discuss-interactiondesigners.com-bounces at lists.interactiondesigners.
com] On Behalf Of Peter Boersma
Sent: Saturday, August 27, 2005 7:45 PM
To: discuss at interactiondesigners.com
Cc: TC00081 at emirates.com
Subject: Re: [ID Discuss] Design docs

[Please voluntarily trim replies to include only relevant quoted material.]

Sudhindra Venkatesha Murthy said:
> I am in the process of creating a document that a UI
> designer/information architect would ideally extract from and record
> in his first few meetings with the clients/development team.

Could it be something like the RUP's[1] "Vision" document?

Below is the description that we put together for EzGov when we created
StUX, the Standards for User Experience[2].

Goal
----
The goal of the vision is to gain agreement on what problems need to be
solved, identify stakeholders to the system, define the boundaries of the
system, and describe primary features of the system.

Description
-----------
The Vision provides a high-level, sometimes contractual, basis for the more
detailed technical requirements. It captures the "essence" of the envisaged
solution in the form of high-level requirements and design constraints that
give the reader an overview of the system to be developed from a behavioural
requirements perspective. It communicates the fundamental "why and what" for
the project and is a gauge against which all future decisions should be
validated. The Vision document can also be created during the feasibility
stage of a project and enhanced during the inception phase.

Contents
--------
1. Introduction - (including purpose, scope)
2. Positioning - (including background and problem statement) 3.
Stakeholder and user descriptions - (including market demographics, user
environment and user profile, stakeholder and user summary,
stakeholder/project contacts, key stakeholder and user needs) 4. Product
Overview - (including product perspective, summary of key
capabilities)
5. Product Features
6. Other product requirements

Suggested reviewers
-------------------
Informal: Systems Architect
Formal: Project Team Leads

Relationships with other deliverables
-------------------------------------
Input from:
- Business Requirements
Output to:
- Use Cases (high-level)
- Task Analysis
Synchronous with:
- Use Case Model
- Supplementary Specifications

I hope this helps.
Peter

[1] Rational Unified Process, see:
http://en.wikipedia.org/wiki/Rational_Unified_Process
[2] My IA Summit presentation "StUX - integrating IA deliverables in a
software development methodology"
http://www.peterboersma.com/blog/2005/03/my-ia-summit-presentation-stux_10.h
tml(Shorter URL to prevent problems with wrapping: http://tinyurl.com/dffef
)
--
Peter Boersma | Consultant User Experience | www.UserIntelligence.com
Vlaardingenlaan 9 | 1059 GL | Amsterdam | The Netherlands p:+31(0)204084296
| f:+31(0)204084298 | m:+31(0)615072747 mailto:peter at peterboersma.com |
http://www.peterboersma.com/blog/

_______________________________________________
Welcome to the Interaction Design Group!
To post to this list ....... discuss at ixdg.org
(Un)Subscription Options ... http://discuss.ixdg.org/ Announcements List
......... http://subscribe-announce.ixdg.org/
Questions .................. lists at ixdg.org
Home ....................... http://ixdg.org/

Syndicate content Get the feed