Department or Program Name

[SYSTEM/APPLICATION NAME]
Single Report
Design
Specifcation
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
Report Design Spei!iation
Temp"ate G#i$e"ine
To aid in the completion of a Report Design Specification please adhere to the following guidelines. For
specific information regarding project deliverables, please refer to the University Services rogram
!anagement "ffice. Remo%e t&ese g#i$e"ines !rom t&e omp"ete$ $o#ment'
De!inition # Report Design Specification defines the definition needed to satisfy a re$uested
business report, including data re$uired. %t should be part of a larger Technical
Specification document pac&age that describes the detailed technical solution for the
report methodology.
P#rpose The Report Design Specification forms the basis for technical design, technical
development, wor&flows, and procedures for using the report and all testing plans. They
describe how the business re$uirements will be translated into the system and application
components. %ts goal is to help ensure a clear understanding of what the developers are
supposed to build in satisfying overall business intelligence needs, and to ensure internal
standards and best practices are met.
O(ners&ip The project development team is responsible for preparing Report Design Specification
documents. Prior to proee$ing) the Report Design Specification $o#ment*s+ m#st
in"#$e appro%a"s !rom t&e ,e- Sta,e&o"$ers'
.&en Report Design Specification documents are completed during the Design phase of the
Solution Delivery 'ife (ycle. %t is started once the )usiness Re$uirements Definition
document is more finali*ed, since business re$uirements supply core information needed
to begin a Report Design Specification, and in conjunction with any system architecture
and data specifications to ensure alignment between the documents. %t is important to
note that the Report Design Specification serves a different purpose than the general
Technical Design Specification documents.
# Report Design Specification is a re$uired deliverable for all business intelligence and
management information reports.
Temp"ate
F"e/i0i"it-
This Report Design Specification template includes data input fields that support internal
controls and processes, policies and ris& mitigation principles, governance drivers, and+or
project management control standards and proven best practices. %t provides the
minimum basic fields re$uired to successfully complete a Report Design Specification
document deliverable in meeting !" re$uirements for all system development projects
re$uiring reporting. The amount of detail included in the template will depend on the si*e,
comple,ity and type of project, as well as the &inds of systems involved and information
re$uired.
The project development leads+teams are empowered to utili*e this template as necessary
to best serve the needs of the project and business owner. -ach data input field provided
in this template should be considered for applicability and relevance to the project at hand.
!ultiple Report Design Specification documents may need to be created for the entire
library of reports.
Temp"ate
Comp"etion
.. This Template /uidelines section is for reference purposes only. %t should be printed
and deleted prior to completing the final document.
0. To input te,t within a te,t field 1 2, place the cursor inside the field and just start
typing.
3. -nter the re$uired information on the Title age and add additional fields as needed.
4. (omplete the document utili*ing suggested te,t where applicable and entering
te,t+fields where shown within 5blue te,t6 brac&ets. 7ote that the blue te,t is 7"T to
be included in your final document. %ts purpose is to either provide guidance for
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
completing re$uested information, or to show where te,t is to be input.
Temp"ate
Comp"etion
8. #s changes are made to the document, ensure that the Document (ontributors,
Document Revision 9istory and Table of (ontents 1T"(2 sections are updated
accordingly.
:. The development team needs to ensure that the Report Design Specification
documents 1and all design solutions2 traces back to and addresses the re$uirements
as defined in the )usiness Re$uirements Document and traces forward to the Test
lans and Test (ases.
;. rior to finali*ing the Report Design Specification documents, the roject !anager
should schedule and facilitate a design wal&<thru meeting with all appropriate parties.
The developers should use their specific &nowledge and judgment to ma&e the final
determination as to who should be reviewers and+or approvers of this design
document.
=. (omplete the Design Review > #pproval 1see !" website2 per the provided
instructions, listing all necessary final reviewers, approvers and others who only
re$uire ac&nowledgement. Route accordingly.
?. Upon receipt of the Review > #pproval, notify the reviewers and approvers of any
critical design recommendations that will 7"T be incorporated and the rationale.
.@. "nce Report Design Specification is completed and after the project has been
closed, this document is to be retained with other project documentation in
accordance with the records management policy and the business lineAs records
schedule, storage and destruction re$uirements.
Important
Notie
#s this template may change, it is &ig&"- reommen$e$ that you access a blan&
template from the rogram !anagement "ffice website
1httpB++www.uservices.umn.edu+pmo+2 each time you need one for a new project and not
merely use one from a previous project by changing the old te,t.
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
DOC1MENT INFORMATION AND APPRO2ALS
VERSION HISTORY
2ersion 3 Date Re%ise$ 4- Reason !or &ange
5'6 7/58/67 Aaron Demenge PMO Re%ie(
DOCUMENT APPROVALS
Appro%er Name Pro9et Ro"e Signat#re/E"etroni Appro%a" Date
SYSTEM/APPLICATION NAME REPORT DESIGN SPECIFICATION
TA4LE OF CONTENTS
5'6 O%er%ie(''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''5
... Chat business $uestion will this report answerD..................................................................................... .
..0 Cho are the report usersD....................................................................................................................... .
..3 Chat are the &ey parameters or business rulesD..................................................................................... .
..4 Chat is the report layoutD........................................................................................................................ .
:'6 So#re De!inition''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''5
0.. Definition Table........................................................................................................................................ .
0.0 !etrics..................................................................................................................................................... 0
0.3 Totals....................................................................................................................................................... 0
0.4 Drill<Downs.............................................................................................................................................. 0
;'6 Report Data De!initions/G"ossar-'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''':
<'6 C&e,"ist Items'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''';
='6 Appen$i/''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''<
SYSTEM /APPLICATION NAME REPORT DESIGN SPECIFICATION
5'6 O2ER2IE.
rovide an overview of the re$uested report. %nclude e,amples of e,isting reports if appropriate.
5'5 .&at 0#siness >#estion (i"" t&is report ans(er?
<Define business question to be answered.>
5': .&o are t&e report #sers?
<Define any users.>
5'; .&at are t&e ,e- parameters or 0#siness r#"es?
<Define any parameters.>
5'< .&at is t&e report "a-o#t?
<Define report layout.>
:'6 SO1RCE DEFINITION
:'5 De!inition Ta0"e
S#09et Area Ta0"e Co"#mn Desription
Product TBL_PROD Prod_D Product dentiifier
TBL_PROD Prod_Desc Product Description

!eo"rap#y TBL_!$O! !eo"_D !eo"rap#ic dentifier
TBL_!$O! !eo"_Le%el
!eo"rap#ic Le%el &Re"ion' District'
Territory(
TBL_!$O! !eo"_Desc !eo"rap#ic Description

Prod ) !eo" ) *ales TBL_+R$+_*+L$* Prod_D Product dentiifier
TBL_+R$+_*+L$* !eo"_D !eo"rap#ic dentifier
TBL_+R$+_*+L$* ,ty_*old ,uantity *old
TBL_+R$+_*+L$* Re%enue Re%enue





:': Metris
Metri So#re Gro#p Metri Name Metri Desription Ca"#"ation
-eader Day
Date
Time
E 0@.0 Regents of the University of !innesota. #ll rights reserved. Revised Fuly 00, 0@.4 age .
SYSTEM /APPLICATION NAME REPORT DESIGN SPECIFICATION
.et Plan
.et +ctual
/ariance
Details
*equence
*01 *tyle
Description
Prices 2*RP
List Price
*ale Price
:'; Tota"s
<Define any totals calculations to be displayed.>
:'< Dri""@Do(ns
<Define any drill)down lin3a"es to be displayed.>
;'6 REPORT DATA DEFINITIONS/GLOSSARY
<Define "lossary items.>
<'6 CAECBLIST ITEMS
Define the single overarching business $uestion the report is suppose to answer
/ather e,amples or create moc& ups of e,pected report information
-nsure -T' designs document are in the overall project Technical Specification Design document
Galidate metric definitions
Document universe of related reports to view individual reports+re$uests in conte,t
(reate the report specific design document
Review and get business user sign off
E 0@.0 Regents of the University of !innesota. #ll rights reserved. Revised Fuly 00, 0@.4 age 0
SYSTEM /APPLICATION NAME REPORT DESIGN SPECIFICATION
='6 APPENDIC
-,isting Reports -,amples or !oc&<ups
E 0@.0 Regents of the University of !innesota. #ll rights reserved. Revised Fuly 00, 0@.4 age 3