Introduction of customer reservation in AATP report

Functional Specification

Introduction of customer reservation in AATP report

Author: Akanksha Jain

Version: 1.0

Date: 4th Jan, 2011

Document History

Version Date Modifications Prepared by / Revised by

1.0 nd
22 Dec, 2010 Draft Akanksha Jain

Contents
1 Introduction.........................................................................................................................................3
2 Major Components of Project Solution...............................................................................................3
2.1 Critical Success Criteria................................................................................................................3
 Consolidated Report

2.2 Assumptions................................................................................................................................3
2.3 Dependencies..............................................................................................................................3
2.4 Constraints...................................................................................................................................3
2.5 Out-of-Scope................................................................................................................................3
3 Relevant Stakeholders.........................................................................................................................4

Page | 2
 Consolidated Report

1 Introduction

In order promising the capacity is being reserved at customer level. This logic needs to be incorporated
in the AATP report.

2 Major Components of Project Solution

This development will automate the below mentioned processes:

Major Deliverable Description of Deliverable

AATP Report It will show the capacity reserved at customer level along
with the other allocations.

2.1 Critical Success Criteria

The following has been defined as the success criteria for the project:

1. Capacity reserved at customer level along with other ATP’s at different sellers.

2.2 Assumptions
1. No assumptions

2.3 Dependencies
1. Proper export from the order promise into the data base table.

2.4 Constraints
1. N/A

2.5 Out-of-Scope
The following items have been defined as “Out of Scope” and not part of the project:

# Out of Scope Item Reasoning Identified By

1 N/A

Page | 3
 Consolidated Report

3 Relevant Stakeholders
The Stakeholder Matrix identifies stakeholders and their stake in this project.

# Type Name(s) Impact

1. Support Team Akanksha Jain Functional consultant

2. Support Team Akanksha Jain Technical Consultant

 Stakeholder Type: This column is used to identify general categories of Stakeholders. Examples
of Stakeholder Type include:
 MHP Sponsor
 End User
 Interfacing Group
 Project Team
 Name: The name or names of stakeholders are provided here.
 Impact: Summarize how the identified stakeholder(s) will be impacted by the project

Page | 4