<<Project Name>>

User Requirements
Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
3453+5+3(-
2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO WARRANTIES E!PRESS OR
IMP"IE# IN T$IS #OCUMENT%
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
3453+5+3(-
Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title 8ser Re9uirements
Author
6reation 1ate
:ast 8pdated
3453+5+3(-
Table of Contents
$ummar"..........................................................................................................................
8ser ;perience...............................................................................................................
;ase of 8se......................................................................................................................
Reliabilit"........................................................................................................................
0erformance....................................................................................................................-
<ulti=language Re9uirements........................................................................................-
Accessibilit"...................................................................................................................-
;nd=8ser Training Re9uirements...................................................................................-
3453+5+3(-
%Intro&uction to t'e Tem()ate
#escri(tion* The "ser &e'uirements document defines the non(functional aspect of
the user)s interaction with the solution. *t provides guidance on the user interface,
e+pectations of the solution)s performance, reliabilit, and accessibilit, and defines
what must be done in order to properl train the users on the solution.
+usti,ication* A successful solution satisfies both the organi,ation)s need for
technolog and the user)s e+pectations for emploing that technolog. #trong, e+plicit
user re'uirements facilitate the development and deliver of a solution that users
consider an asset to their organi,ational activities.
-Team Ro)e Primar-* Pro.ram Mana.ement is responsible for ensuring that the
user re'uirements document is completed in a timel manner. #e/e)o(ment has the
primar responsibilit for creating the content of the user re'uirements document.
User E0(erience is responsible for ensuring that all relevant user roles and user
perspectives and needs are identified.
Team Ro)e Secon&ar-* Pro&uct Mana.ement will review and understand the user
re'uirements document in order to conve those to parties e+ternal to the team and
to ensure that user re'uirements are represented according to initial pro.ect sponsor
re'uirements. Test will review the user re'uirements to ensure test plans are in place
to validate the re'uirements. Re)ease Mana.ement will review the document to
ensure operational, deploment, migration, interoperabilit and support needs are
addressed./0
3453+5+3(- (
Summar-
%#escri(tion* 1rovide an overall summar of the contents of this document. This
should include the criteria b which the user re'uirements were established and how
the were validated.
+usti,ication* #ome pro.ect participants ma need to know onl the document)s
highlights, and summari,ing creates that user view. *t also enables the full reader to
know the essence of the document before the e+amine the details.0
<<Begin tet here!!
User E0(erience
%#escri(tion* The "ser 2+perience section lists and defines the user e+perience
re'uirements. This includes a description of the elements of the current user
e+perience that are acceptable for the new solution and what elements need to
change to surpass the current user e+perience. This section ma also define the
processes that will collect feedback from the user communit regarding how well the
re'uirements were implemented.
+usti,ication* This information supports the approach that puts the user, rather than
the technolog, at the center of the process. 3athering user concerns and
e+pectations promotes the principle that the users) needs should be foremost in an
design decisions.0
<<Begin tet here!!
Ease o, Use
%#escri(tion* The 2nd of "se section defines the users) abilit to emplo the solution
without an negative impact on their primar work responsibilities. 2ase of use
re'uirements ma include a definition of the solution)s flow$navigation and interface
design 4simplicit, alignment with other solutions alread in place, intuitive, etc5. This
section ma also define the processes that will collect feedback from the user
communit regarding how well the re'uirements were implemented.
+usti,ication* This information supports the approach that puts the user, rather than
the technolog, at the center of the process. 3athering user concerns and
e+pectations promotes the principle that the users) needs should be foremost in an
design decisions.0
<<Begin tet here!!
Re)ia1i)it-
%#escri(tion* The &eliabilit section describes the users) e+pectations on how
reliable the solution must be. This information ma be stated at both the solution level
as well as the feature level. This section ma also define the processes that will
collect feedback from the user communit regarding how well the re'uirements were
implemented.
3453+5+3(- +
+usti,ication6 &eliabilit e+pectations from the users are from their business
perspective ( what the solution must deliver to ensure their productivit. This is
important information that will lead to designing a solution that is stable and
trustworth in its operational environment.0
<<Begin tet here!!
Per,ormance
%#escri(tion* The 1erformance section describes the users) e+pectations on the
solution)s performance, usuall described as application response time. This
information ma be stated at both the solution level as well as the feature level. This
section ma also define the processes that will collect feedback from the user
communit regarding how well the re'uirements were implemented.
+usti,ication6 1erformance e+pectations from the users are from their business
perspective ( what the solution must deliver to ensure their productivit. This is
important information that will lead to designing a solution that is stable and
trustworth in its operational environment.0
<<Begin tet here!!
Mu)ti2)an.ua.e Requirements
%#escri(tion* The Multi(7anguage &e'uirements section identifies an international
support that the solution must address.
+usti,ication* "nderstanding these re'uirements earl will enable the development
team to design all international support features into the solution and ensure that the
entire scope of users is accommodated.0
<<Begin tet here!!
Accessi1i)it-
%#escri(tion* The Accessibilit section identifies the handicap$accessibilit
re'uirements that the solution must meet. 2+amples of these are support for multiple
hardware input tpes, support for e+isting operating sstem accessibilit features,
etc.
+usti,ication* "nderstanding these re'uirements earl will enable the development
team to design all support features into the solution and ensure that the entire scope
of users is accommodated.0
<<Begin tet here!!
En&2User Trainin. Requirements
%#escri(tion* The 2nd("ser Training &e'uirements section defines the training
re'uirements that must be met prior to the solution)s production deploment. This
information does not identif specific training events or mediums 4that information is
3453+5+3(- .
in the Training 1lan5. Training re'uirements define the competencies that the users
must have in order to emplo the solution successfull and identifies where users do
not currentl have those competencies. The gap between the needed competenc
and the e+isting competenc becomes the training re'uirements.
+usti,ication* The Training 1lan is created based on the training re'uirements.0
<<Begin tet here!!
3453+5+3(- -