Sample Marketing Requirements Document (Page 3 of 4) in pdf

3.5 Performance / Resource Requirements

All functions in the program must be available via keyboard or pointing device.

The program must not crash itself or the machine, and must not cause Windows General Protection

Faults.

The product must not fail to release Windows System Resources, except for known behavior of the

Microsoft Foundation Classes.

The package must multitask cooperatively with other applications. No slowdown shall be

perceptible to the user.

The program shall respond appropriately to inadequate memory conditions and to inadequate disk

space. The product shall warn the user of the error condition, allow the user to rectify it, or will the

user fail to rectify the problem, the program shall refrain from proceeding.

The program will act on user requests as quickly as could be expected given the request. This will

not be an unusually slow program.

3.6 Internationalisation Requirements

The product must be released simultaneously in the United States, Canada, France, Germany and the United

Kingdom, and thus must be built for fast translation.

A double-byte enabled version will be required at least _____ days after the product’s US release.

Internationalized products will share the same code base as the US version.

3.7 Problem Fix Requirements

Before the final release of the program, all bugs marked as priority 10 through 12 in the Quality

Assurance bug-tracking database will be fixed. Bugs not fixed, (marked as deferred) must be

agreed upon by all parties.

Any problems detected during the beta test cycle that conflict with this document or with the

Functional Specification must be resolved by release time.

This resolution may include a change to

the

MRD

or the FS.

The Company shall provide problem reports immediately upon request

to all outside developers.

Developers within

The Company

will have access to the Quality Assurance Bug Tracking

System.

The Company shall assign priorities to bugs with 12 being the highest priority and 1 being the

lowest priority. All bugs with priority of 10 through 12 shall be considered “show stoppers” and

shall receive immediate attention.

Problems that are fixed in a specific beta release will be marked as “fixed” by the developers on the

bug report. That bug report will then be sent back to QA for verification at the same time the code

with the fix is sent to QA.

Sample Marketing Requirements Document Page 3