Market Requirements Document

MARKET REQUIREMENTS DOCUMENT

FOR [PROJECT NAME]

[DATE]

[Company name]

REVISION HISTORY
Rev # / Rev Date / Modified By / History/Comments
0.1 / Initial Draft
APPROVALS
Your signature on this document indicates that you or your designated representative has reviewed, understands, and provided feedback on the contents of the document, and you authorize work to proceed. You agree to notify the other signers of the document if the requirements as stated need to change.
Title / Signature
VP, Marketing
VP, Development
Product Manager
Program Manager

1EXECUTIVE SUMMARY

1.1OBJECTIVES

1.2DOCUMENT SCOPE

1.3KEY FEATURES

1.4POSITIONING, STRATEGY & TARGET CUSTOMERS

1.5KEY MESSAGES & BENEFITS

2PROBLEM DEFINITION

3PRODUCT DESCRIPTION & POSITIONING

3.1PRODUCT OVERVIEW

3.2OBJECTIVES & REQUIRED DATE

3.3POSITIONING, KEY MESSAGES, & MAIN BENEFITS

4STAKEHOLDERS ANALYSIS

5ACTORS

5.1CUSTOMER CARE AGENT

5.2SOFTWARE ENGINEERS

6USE CASE LIST/DIAGRAM

7USE CASES & REQUIREMENTS

7.1REQUIREMENTS NOT INCLUDED IN TARGET/CURRENT RELEASE

8NON-FUNCTIONAL REQUIREMENTS

8.1CONSTRAINTS

8.2PLATFORMS & CONFIGURATIONS MATRIX

8.3PRODUCT PACKAGING

9GLOSSARY

10OPEN ISSUES

/ CORPORATE LIBRARY
Status: DRAFT
Distribution: INTERNAL USE ONLY
Last Revised: mm/dd/yy
Page 1 of 8

1EXECUTIVE SUMMARY

[Introduction, from Product Plan; Why are we doing this product? Explain strategic fit with company and product line objectives.]

1.1OBJECTIVES

[One to three Specific objectives for this product and version.Measurable, and with target dates]

1.2DOCUMENT SCOPE

[This document focuses on defining requirements for version X deliverables, and collects longer term requirements for future iterations.]

1.3KEY FEATURES

[Three to five key features being delivered in this product and version]

1.4POSITIONING, STRATEGY & TARGET CUSTOMERS

[From the Positioning Template]

1.5KEY MESSAGES & BENEFITS

[Three benefit-focused messages that support the positioning]

2PROBLEM DEFINITION

[From Product Plan/Concept Document]

3PRODUCT DESCRIPTION & POSITIONING

3.1PRODUCT OVERVIEW

[Summary of what this product will do. Product Strategy Statement. Is this a date driven release, or feature-driven?]

Main Product Components

[Highest level of scope definition]

Component #1
Component #2
…Component n

3.2OBJECTIVES & REQUIRED DATE

[From above, with elaboration if necessary]

3.3POSITIONING, KEY MESSAGES, & MAIN BENEFITS

[More description on the key benefit with examples that sales and marketing can use for positioning in the marketplace and competition.]

4STAKEHOLDERS ANALYSIS

ROLE / STAKEHOLDER INTEREST / PRIMARY USER / SECONDARY USER / REPRESENTATIVE
Organization 1
Executive Team / Revenue / [Names of Individuals]
VP Media Sales / Revenue
Client Activation Team / Cost / •
Client Satisfaction Team / Cost / •
Professional Services / Cost / • / •
Technical Support Team / Cost / •
Network Operations / Security, Scalability / •
Engineering Team / Maintainability / •
Business Development Team / Revenue
CTO / Security, Scalability, Maintainability
VP, Products / Profitability
Billing / Data Export
Accounting / Taxation
Organization 2
Executives / Revenue
Sales team / Revenue
Organization 3
Regulators
Auditors

5ACTORS

[List of all actors/personas]

Example:

5.1CUSTOMER CARE AGENT

XYZ customer service representatives.The employees who set up and maintain the client accounts on applications.May be earlier in their careers, perhaps without a college degree or possessing an AA degree.Personable on phones.Not necessarily PC or Internet experts.

5.2SOFTWARE ENGINEERS

Developers who are responsible for creating and maintaining the applications and responsible for integrating the application’s functionality.

6USE CASE LIST/DIAGRAM

Required Use Cases to be addressed in this release include the following:

Example:

USE CASE # / ACTOR / SUMMARY DESCRIPTION
Client Management
1 / Customer Care Agent / Adds new client
2 / Customer Care Agent / Adds/changes client packages purchased
3 / Customer Care Agent / Updates client data
4 / Customer Care Agent / Views client information
Campaign Management
5 / Customer Care Agent / Creates campaign
6 / Customer Care Agent / Updates campaign data
7 / Customer Care Agent / Change TFN redirect
8 / Customer Care Agent / View campaign
User Management
9 / Customer Care Agent / Adds client users
10 / Customer Care Agent / Updates client user data
11 / Customer Care Agent / Maintains passwords
Application Integration
12 / Software Engineer / Integrates services with own applications via web services API

7USE CASES & REQUIREMENTS

1.0 / DRAFT mm/dd/yy / AUTHOR
USE CASE / Add.client account / PRIORITY / 1
ACTOR/ROLE / Customer Care Agent
GOAL / Establish service for a new client
PRE-CONDITIONS / Signed contract received from new client
POST-CONDITIONS / Client account established; user accounts can be set up
STEPS

Customer Care Agent logs in as administrator.

Chooses “Set up new client” from admin options presented.

Enters new client data (refer to Properties list below) from contract, including service package selection.

Agent saves setup information.

System assigns client ID to new client and stores setup information.

System exports data to billing system for nightly update.

EXTENSIONS / 3.1Activate in the future
3.2Deactivate in the future
EXCEPTIONS/ERRORS / Required Fields:
Company Name
Company Street Address
Company City
Company State
Company Zip
Company Phone
Company Fax
Billing Street Address
Billing City
Billing State
Billing Zip
Initial Sales Date
Billing Cycle
Time Zone
NOTES

7.1REQUIREMENTS NOT INCLUDED IN TARGET/CURRENT RELEASE

[Feature list; could also be a list of use cases not addressed in this version.]

Below are the features of the product not included in the target/current release. These features are important for the product lifecycle and will be re-considered in future planning. Generally each feature has a related function, benefit, and priority rating. The priority ratings are 1 = Critical; 2 = Important; 3 = Nice to Have.

ITEM / FEATURE / FUNCTION / BENEFIT / PRIORITY
1. / Report enhancements / Select a range of client accounts to report on within a branded account; Select ranges by business type, UDAC, directory/publication/edition, market (locale)
2. / Additional user security roles / Enable additional permission levels within and across client accounts and within branded account groups

8NON-FUNCTIONAL REQUIREMENTS

[List provided as a checklist only; determine which non-functional requirements apply and define appropriate targets and measures.]

ITEM / FEATURE / FUNCTION / MEASURE / PRIORITY
1. / Scalability / Ability to handle large volumes of data / Ability to handle up to tracking 50,000 numbers per client account / 1
2. / Security / Ability to allow or restrict access to data and functions by user or role / 1
3. / Availability / Rate of hardware and software component failures (mean time between failures) / Service up-time (not including planned maintenance) 99.99%. / 1
4. / Cost of ownership / Overall operating cost to the organization after the system is in production / 2
5. / Maintainability / Ability to keep the system in a steady running state, including enhancements / 1
6. / Flexibility / Ability to handle requirements changes / 1
7. / Installability / Ease of system installation on all necessary platforms / 2
8. / Performance / Ability to meet response time requirements / 1
9. / Portability / Ability to move the application to different platforms or operating systems / 3
10. / Quality / System performs accurately as defined in the specification / No Pri 1 or Pri 2 issues at time of deployment / 1
11. / Robustness / Ability to handle error and boundary conditions while running / 1
12. / Data integrity / Tolerance for loss, corruption, or duplication of data / 1
13. / Extensibility / Ability to accommodate increased functionality / 1
14. / Reuse / Ability to leverage common components across multiple products / 1
15. / Operability / Ease of everyday operation; Level of support requirements / 1

8.1CONSTRAINTS

Examples:

Use existing sprocs and tables. No new data elements or stored procedures.
UI must integrate with new brand framing without duplication of elements or omission of elements.

8.2PLATFORMS & CONFIGURATIONS MATRIX

[What technical environments will be supported?]

PRIORITY / TYPE / O/S & VERSION / PRODUCT & VERSION / DATABASE & VERSION
1 / Server
1 / Browsers
1 / Mobile
1 / Desktop

8.3PRODUCT PACKAGING

[What will the customer get when they buy? Are multiple configurations available?]

Box
Media
User Guide
Installation Guide
Training Package
Support Product
Professional Services

9GLOSSARY

UDAC (Universal Directory Advertising Code)

Abbreviations used to represent the various sizes of advertising units available in a directory.

10OPEN ISSUES

Description / Date Opened / Responsible / Status/Resolution
1.
2.

Pivotal Product Management provides award-winning product management training, consulting, coaching, and skills assessment. Please contact us if you have questions about using this tool. Visit our website for more Product Management best practices, free tools, and templates.