Rates DB Air (Requirements)
From UG
(Difference between revisions)
| Line 6: | Line 6: | ||
==Business Analysis and Requirements== | ==Business Analysis and Requirements== | ||
''To be written by BA. This section should cover Needs, Requirements, Background and Design Ideas. Also could include Glossary, existing business workflow, cases, etc'' | ''To be written by BA. This section should cover Needs, Requirements, Background and Design Ideas. Also could include Glossary, existing business workflow, cases, etc'' | ||
| + | |||
| + | === Business Need === | ||
| + | ''what are we trying to achieve? What are the main goals of this module? '' | ||
| + | |||
| + | |||
| + | Jaguar Global needs "Air Rates DB module". It is a Tariff and contract management system with additional functionality. | ||
| + | |||
| + | Main Features: | ||
| + | * management of tariffs and contracts (client and vendor sides) | ||
| + | ** adding, editing, deleting, listing, searching, sorting, querying | ||
| + | * "Quotations" web portal and internal (for Jag Sales, Ops, Clients, etc) | ||
| + | ** searching, sorting, querying and producing an official Jag doc (with number, etc) | ||
| + | |||
| + | Additional Acc features: | ||
| + | * Automated population of charge table in "sales invoices" | ||
| + | * Automated calculation of "estimated P&L" | ||
| + | * Auto approval of PI charges | ||
| + | * Etc | ||
| + | |||
| + | === Business Background === | ||
| + | |||
| + | ==== Terminology ===== | ||
| + | |||
| + | ==== Types and Examples of Air contracts ==== | ||
| + | |||
| + | === "FAQ" === | ||
| + | ''How Jaguar deals with Air rates (in all offices) now ?'' | ||
| + | |||
| + | ==== A Day in the life of NY Inside Sales ==== | ||
| + | |||
| + | ==== In what form existing Air contracts received and maintained ? ==== | ||
| + | |||
| + | ==== How requests for rates handled (receive, search, answer) ? ==== | ||
| + | |||
| + | ==== Classify all types of existing Air tariffs, provide examples, etc ==== | ||
| + | |||
| + | ===== What is Request format? ===== | ||
| + | |||
| + | ===== What is Output format? ===== | ||
| + | |||
| + | ==== What systems we use for these? ==== | ||
| + | |||
==Pre Implementation Architect Notes== | ==Pre Implementation Architect Notes== | ||
Revision as of 20:54, 8 April 2011
Info
- mantis#
Business Analysis and Requirements
To be written by BA. This section should cover Needs, Requirements, Background and Design Ideas. Also could include Glossary, existing business workflow, cases, etc
Business Need
what are we trying to achieve? What are the main goals of this module?
Jaguar Global needs "Air Rates DB module". It is a Tariff and contract management system with additional functionality.
Main Features:
- management of tariffs and contracts (client and vendor sides)
- adding, editing, deleting, listing, searching, sorting, querying
- "Quotations" web portal and internal (for Jag Sales, Ops, Clients, etc)
- searching, sorting, querying and producing an official Jag doc (with number, etc)
Additional Acc features:
- Automated population of charge table in "sales invoices"
- Automated calculation of "estimated P&L"
- Auto approval of PI charges
- Etc
Business Background
Terminology =
Types and Examples of Air contracts
"FAQ"
How Jaguar deals with Air rates (in all offices) now ?
A Day in the life of NY Inside Sales
In what form existing Air contracts received and maintained ?
How requests for rates handled (receive, search, answer) ?
Classify all types of existing Air tariffs, provide examples, etc
What is Request format?
What is Output format?
What systems we use for these?
Pre Implementation Architect Notes
Written by Architect after previous section is completed.
Implementation Notes
To be written by Developer or BA by the time UAT is completed. Briefly defines what was implemented and how.
Post Implementation Architect Notes
Written by Architect after previous section is completed.
