FUNCTIONAL REQUIREMENTS DOCUMENT CONTENTS Document Purpose Intended audience Project background Purpose of functio

1. FUNCTIONAL REQUIREMENTS DOCUMENT CONTENTS Document Purpose Intended audience Project background Purpose of functional requirements Business goals to be achieved Stakeholders Benefits Assumptions Project scope Functional requirements Use case diagram Activity diagrams and detailed use cases Budget Approvals

2. Document Purpose • The purpose of this document is to describe functional requirements of the proposed web based e-commerce solution in a very clear manner in order to avoid any ambiguity. This document will later be used to suggest functional specifications and the technical design of the proposed project. • Intended audience • The main intended audience of this document is the owners and sponsors of the proposed project. • Also various entities like the business groups, technical groups and the sales and marketing groups will also find this information helpful in designing and developing the project. It will also aid in future decision making process. • Project Background • Amazon.com company founded to provide users with a fresh and an easy way to shop in a convenient manner. Users will be able to browse, search and shop a huge collection of products of all categories in a single place and a matter of few clicks. They can also opt for our Prime service to enjoy some really cool features, free services and many more. We also are aware of the provisions and work well within the boundaries of E-commerce.

3. Purpose of functional requirements • This functionalrequirements document has been created for developing a new application. • Business goals to be achieved • Launch the new service by the end of August 2014 and perform extensive advertisement to create a significant customer base. • Stakeholders • Sponsor • Amazon.com top level management • Business development team • IT team • End users • Benefits • Customer Benefits • Browse the products from a huge collection of products. • All the information of the product will be available . • Customer reviews of the product. • Shop by department • Related products • Influenced/Influenced by list • Shopping cart feature • Wish list feature.

4. Other features • Special showcase- In-house products • Platform for upcoming products and companies. •  Assumptions • We have assumed that the major brands will be interested in being a part the proposed project and major products will be featured on the online store. • Project scope • In scope • Build the system possessing the intended features. • Invite the sellers to the company. • Build a database complete with products of all categories. • Extensive marketing of service after launch • Out of scope • No social networking site integration

5. Detailed Use Case Use case name: Sign In Use case ID: 1101 Actor1: User Actor2: System Description: The user navigate to Sign In page and try to sign in using his credentials. Priority: High Frequency: High Pre-Condition: User has account with the system. Post-Condition: User will be navigated to homepage with member access. Trigger: User open the Sign In page. Happy Path: User enter the URL or click the link for Sign In page. System open the Sign In page. User enter his email address. User enter his password User click the Sign In button System verify the information System opens the homepage with member access Alternate Path 4a) User choose new password and click Sign In 4b) System redirect to Sign Up page. Exception: If wrong password is provided with correct email ID three times, the user ID will be blocked.

6. Detailed Use case Use case name: Sign Up Use case ID: 1102 Actor1: User Actor2: System Description: User open the Sign-up page and input the information to Sign Up. Priority: High Frequency: Medium to High Pre-Condition: User has an e-mail address to sign up with. Post-Condition: User will be navigated to homepage with member access Trigger: User open the sign up page or click the link for sign up. Happy Path: User enter the URL or click the link for Sign up page. System open the Sign up page. User input his name. User input his e-mail address. User input his e-mail address again. User input his password. User input his password again. User click the create account button. System verify the information provided. System accept the information and open the homepage with member access. Alternate Path:** Exception: If email address or password does not match, system reload the sign up page with an error message.

7. Detailed Use case Use case name: Browse Use case ID: 1103 Actor1: User Actor2: System Description: User open the homepage, start browsing the products and choose from the options. Priority: High Frequency: High Pre-Condition: ** Post-condition: User add the product to his cart or his wish list. Trigger: User open the homepage. Happy path: User enter the URL. System open the homepage. System provide the options of ‘Top picks’, ‘What customers are looking’ and ‘Best seller’. User choose from any option. System open the product information page. System provide the options of ‘Choose color/size/variant’, ‘Similar products’ and ‘Also bought togather’. User choose any option. System provide the options of ‘Add to cart’ and ‘Wish list’. User choose any option. System proceed to the respective webpage. Alternate path:** Exception:**

8. Detailed Use Case Use case name: Cart Use case ID: 1102 Actor 1: User Actor 2: System Description: User choose a product, add it to the cart and proceed to checkout. Priority: High Frequency: Medium to High Pre-Condition: User has an account with the system Post-Condition: User choose shipping address and make payment. Trigger: User choose the product. Happy Path: User choose the product System provide the buying options. User choose the buying option. System give option to choose quantity and add to cart. User select the quantity User click add to cart. System add the product to the cart. The default number of items are selected if quantity not selected by the user. System shows the net price and ask to view the cart or edit the cart. After making selection user click proceed to checkout. System open the checkout page. Alternate path: 6a) Use select ‘Edit the cart’. 6b) User change the products or quantity and proceed to step 7. Exception: If verify inventory is returned less than the order Or zero, the user is notified and the item is not added to the cart.

9. Detailed Use Case • Use case name: Payment • Use case ID: 1105 • Actor1: User • Actor2: System • Description: The user input his shipping address and choose the shipping speed. • Priority: High • Frequency: Medium to High • Pre-Condition: The user already has items in his cart. • Post-condition: Confirmation number is provided to the user. • Trigger: User already has items in his cart and he clicked proceed to checkout. • Happy path: • User already has items in his cart and he click proceed to checkout. • System open the shipping address webpage. • System provide the options of choosing his address from the stored information or to input new address. • User choose the address from his stored information. • System provide the option of choosing the shipping speed. • User choose any shipping speed. • User click the continue button. • System add the charges of shipping accordingly. • User click the continue button. • System ask the user to provide information of payment. • User input the name on card. • User input card number • User input expiration date. • User click the continue button • System process the payment. • System generate the confirmation number and show on user’s screen. • Alternate path: • 3a) User choose to input new shipping address. • 3b) User input all the information. • 3c) User click continue and proceed to step 5. • 14a) System does not find the payment. • 14b) Show error message and return to step 10. • Exception: **

10. Detailed Use Case • Use case name: Search • Use case ID: 1106 • Actor 1: User • Actor 2: System • Description: User open the homepage, input his search text and click search button. • Priority: High • Frequency: High • Pre-Condition: ** • Post-Condition: User choose from the products. • Trigger: User enter the URL. • Happy path: • User enter the website URL. • System open the homepage. • System provide the option to input the search text. • User input his text. • User click the Search button. • System show the relevant product. • Alternate path: • 3a) User choose the department from dropdown menu and proceed to step 4. • Exception: • User did not use the search functionality.

11. Budget • The estimated budget for this project is $10,00,000. • Approvals