1. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
E-Store
Project Report
Version: 2.0

2. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
Table of Contents
1. Project Overview
1.1 Purpose
1.2 Scope
1.3 Workflow
1.4 Process step
2. Project Approach
2.1 Accomplishments needed
2.1.1 E-store UI
2.1.2 Customer UI
2.1.3 Agent UI:
2.2 Business Approach
3. Project Objectives
3.1 Project Specification
4. Major Deliverables
4.1 Key Decisions and Strategies
4.2 Audience
5. Constraints
5.1 General Constraints
5.2 Global Constraints
6. Risk and Feasibility
6.1 Assumptions

3. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
1. Overview
The main purpose is to provide the detail information about the E-Store
development plan which includes, an Integrity Validation Component for
conflicting items, identify business logic area, and show the service level options,
more shipping options, marketing messages, upgrading or downgrading any
monthly service.
This project will develop an integration add-on of product data management
functionality, accounting, customer hub, data functionality, Order data integrity,
order related functionality, review accounting functionality and billing functionality.
1.1 Purpose
The main purpose of this document is to provide the group, E-Store
reporting team, web group and the related groups with the final results of
this project. This document should provide them with the detailed
explanation of the final results of this project
The following is an attempt to put together a complete, yet reasonably
flexible template for the specification of this e-store application.
Wherever possible, guidelines are provided (instead of prescribing
requirements) for the contents of various sections and subsections of the
document.
Some may prefer to require more detailed subsections of a particular
section, choosing one or more of the subsection topics from the list of
guidelines provided.
1.2 Scope
The scope of this document is to address the technical specification and
issue related to e-store requirements and needs.
Must follow all the web standards, global standard, and implement proper
error handling
Provide read only access to the repository.
Restricted party screening, identity and access management authority for
online users.

4. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
1.3 Workflow
This workflow validates the order to ensure there are one or more billable
items and also checks the customer has one or more billing profiles.
Allows the customer to choose an existing billing profile or create a new
one. Updates the order with the billing profile selected by the customer. E-
Store will need to make this call only when the shopping cart contains at
least one shippable item.
1.4 Process Step
Check that order has right shipping information no wrong zip code, city
name if so double check with customer and also check an order for
shippable items. Should E-Store generate its own unique internal order
number and pass this value in the message to store in database. E-Store
will generate its own external order number and supply as input to the
order confirmation page.
2. Project Approach
This project will be accomplished by doing the work simultaneously by different
teams at same point of time (Distributed application development). The team
refers to all the tools necessary to facilitate collaboration on an application project
between two or more groups who are basically geographically separated.
2.1 Project requirements
The scope of this document is to describe the functional specifications
associated with Account Management process which is in scope of
Release two.
2.1.1 e-store UI:
• Establish Identity and/or Account
• Present List of Offering Configurations & Properties

5. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
• Present Charge Schemes/Pricing
• Presents Existing Ship To Addresses
• Presents Shipping Levels
• Creating new account/ contact
• Editing existing account/ contact
• Querying for accounts/ contact
• Maintaining account/ contact attributes
• Associating contacts, opportunities to accounts
2.1.2 Customer UI:
• Selects Offering
• Specify Transaction Attribute Values
• Selects Charge Scheme and Pricing Plan
• Selects Shipping Level
• Selects Ship To Address for Shipping
• Initiates an interaction with e-store to place an order
2.1.3 Agent UI:
• View into Account Billing Activities
• Account Setup/Modification
• Billing Profile Setup/Modification
• Payment
Capture
by
Agent
• Check
order
contents
• Check
the
order
for
billable
items
• Check
billing
profiles
• Check
if
the
customer
has
existing
usable
billing
profiles
3. Project Objectives
A ecommerce configuration tool such as E-Store are very helpful in all web
projects, and will help the marketing department to deal with marketing offerings,
sell offerings, perform order management, manage accounts, manage customer
data and manage invoice.
This project will develop an integration add-on of product data management
functionality, accounting, customer hub, data functionality, order related
functionality, review accounting functionality and billing functionality.

6. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
3.1 Project Specifications
E-Store application is evolves to include low-level design details (although
perhaps the "Detailed Design" section may not yet be appropriate at the
high-level design phase).
Best ways to document a project's is to keep a detailed project journal,
log, or diary of issues as they are mulled over and bandied about and to
record the decisions made (and the reasons why) in the journal.
4. Major Deliverables
E-Store should be able to lookup order status as well as order details for both
anonymous and signed in users in secure and privacy compliant way. Provide
customers online details of the orders in invoice format and provide link for
customer to track order as necessary or download products for 3 year that they
might have purchased. Option to refunds their order. Link to an external page, for
tracking details. Inform customer if return has been successfully processed.
4.1 Key Decisions and Strategies
Overall new architectural will help all the seven web portal to interact and
all the product, order information, working, accounts details, and other
things will be at one place. Future plan is to make everyone’s life easy
either they are coming from web, partner channel or customer support all
the architecture will be same so no more confusion and wrong
conclusions. We merge seven databases to three and try to do everything
from these three. Also keeping in mind the error detection and recovery
pan to give better user experience.
4.2 Audience
The audience associated with this project includes Global Process
Owners, Business directors, Business Process Owners, Marketing
managers, Product Managers, Sales Operations, and IT Developers.

7. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
5. Constraints
Difficult to identify variation of Order Placement through various channels that is
web, call center or partner portal. It is critical to be able to accurately detected
when an order is in a mixes state (including web subscription process – publisher
and subscriber model, web services, products and downloadable software)
because is generally not a valid condition and such an order must be cleared or
sorted up before being processed.
5.1 General Constraints
• Standards compliance
• Data repository and distribution requirements
• Security requirements (or other such regulations)
• Performance requirements
• Verification and validation requirements (testing)
• Other means of addressing quality goals
• Other requirements described in the requirements specification
• Input must be allowed from iphone, Blackberry and other PDA’s.
• Each end-user’s profile data must be kept in sync across all application
data centers with latency no longer than 60 seconds.
• Re-authentication is required if no user input within thirty minutes.
• Each quote transaction must complete and provide feedback to the
user within fifteen seconds.
• Licenses must be fully transferable to our business partners
5.2 Global constraints
• This has a significant impact on the design of the e-store application
• Hardware or software environment.
• End-user environment.
• Standards compliance.
• Data repository and distribution requirements.
• Security requirements.
• Performance requirements.
• Other means of addressing quality goals.
• Other requirements described in the requirements specification.

8. By:
Indernain
Singh
[ESTORE
VERSION
2.0]
November
8,
2009
6. Risk and Feasibility
It is most applicable when it comes to application development. Risk is the
probability of something going wrong with application development. Schedules
are always in flux; thus creating more predictable schedules. Lack of
transparency and motivation – It would be much easier if we could meet face-to-
face.
• Unknown scope beyond the working process – may be too much
customization to meet deadlines
• Requirements that can be translated into technical design specifications
• Environments delayed
• Overlap of phases to meet schedule to meet schedule
• Overlap of Iteration phases or design overlaps.
• Overlap of test phases for integration and system and risk of compromise
on Quality, Resource and schedule
6.1 Assumptions
• Finish all Iteration as per current plan
• Performance and product testing conducted in parallel with Iterations
and completed within fifteen days of end of first iteration.
• Plans are currently at major iteration level and not at task level –
accordingly schedules
• Working, looking, or "feeling" like an existing product