MRD Database

20
Proj Number Proj Name Proj Approach Date Proj Inititaion Date

Transcript of MRD Database

Page 1: MRD Database

Proj Number Proj Name Proj Approach Date Proj Inititaion Date

Page 2: MRD Database

Marketing Requirement Document

What product is about Who Target customers are Competitors Why customers are likely to want this product

Executive Summary Purpose Goals Delivery Date Target Market CustomersOver all Position Competition Use Model Customer Corrs. Features Systems and Technical Requirements Quality Assurance and testing Appendices

Page 3: MRD Database

Why customers are likely to want this product

Page 4: MRD Database

Production Requirement Document

What product is about Who Target customers are Competitors Why customers are likely to want this product

Executive Summary Purpose Goals Delivery Date Target Market CustomersOver all Position Competition Use Model Customer Corrs. Features Systems and Technical Requirements Quality Assurance and testing Appendices

Page 5: MRD Database

Why customers are likely to want this product

Page 6: MRD Database

As soon as the product is ready and exe is prepared then

Check and list down the transmission channels

Check for configuration Demands of the Client

Client's Infrastructire check and/or constraint

License Check and issuance of License Number

Final distributionDelivery Deployment Reporting

Send to repository

Update CRM and Configuration Management

Page 7: MRD Database

Check and list down the transmission channels

Check for configuration Demands of the Client

Client's Infrastructire check and/or constraint

License Check and issuance of License Number

Update CRM and Configuration Management

Page 8: MRD Database

Management of security features control of changes to

H/WS/W defines functional and physical attributes of a S/W at various points in time Documentation perform systematic control of changes for maintaining integrity Testing / test reports etc.

Essential Processes Identification

Control

Status Accounting

Audits

Components Client-Server Product /Component Name Version O/SS/W H/W Tech. Archi. Prod sets Networking

Page 9: MRD Database

defines functional and physical attributes of a S/W at various points in time perform systematic control of changes for maintaining integrity

Identification

Status Accounting

Page 10: MRD Database

Introduction Growth Phase

Product Quality is maintained

Pricing

Distribution

Promotion

branding and quality leel is established alon with getting patents, intellectual prioperty right and or licenses

Low to gain market share

Pricing is maintained to ensure the regular sales

High to make up for high investments

selective until demand is shown by the customers

channels are added,as the demand increase to ensure smooth supply of goods

Through Innovators,Marketing channels/Firms

promotion at a broader customers

educate potential customers about the product

Page 11: MRD Database

Maturity Decline

features enhancement Rjuvenation of product

prices are declined to avoid competition

reduce the price further

become more intensive and offer incentives for promotion of product

How the product is differentiated

Page 12: MRD Database

liquidating the inventory or selling to the person interested in selling.continuing the product

Page 13: MRD Database

Requirement Managemnt Feedback Investigation Users Business Goals Constraints

This Process leads to MRD Feasibility

Budget Schedule for the project

Design

current tools or processes in place

costs of requirement are determined

costs being incurred due to present processes

what is the budget of department for overcoming this cost

expected rate of return on the new product in the market

Internal rate of return in reducing the costs of training and support, if we make a new, easier to use system

costs are accurately determined and benefits gained are sufficinetly large , design stage begins

Page 14: MRD Database

Construction and test

Release Data about the application's acceptability is gathered and fed into investigation phase if the next generation or releasr functional requirements

compare the scope of work with the design

work and cost stay with-in budget and schedule

prototype construction and iterative testing

Page 15: MRD Database

Developers

software development cosDo we have right people to create this tool

hardware costs do we need new equipment to support extended software roles

the document helps the team to stick with th requirements and original scope of work

Page 16: MRD Database

helps the team analyse the change in the market trend or other demographic factors on which the requirement was made, and change the design of the system accordingly

Data about the application's acceptability is gathered and fed into investigation phase if the next generation or releasr

Page 17: MRD Database

helps the team analyse the change in the market trend or other demographic factors on which the requirement was made, and change the design of the system accordingly