├── README.md ├── doc ├── 1-PBIs (Text) │ ├── Detailed PBIs (Text) │ │ ├── 01-161-Display special offer products in a slider.txt │ │ ├── 02-138-Display top featured products in a slider.txt │ │ ├── 03-28-Display top new arrival products in a slider.txt │ │ ├── 04-120-Display top hot sale products in a slider.txt │ │ ├── 05-119-Display top best selling products in a slider.txt │ │ ├── 06-121-Display random products in a slider.txt │ │ ├── 07-145-Display all main and sub categories of products.txt │ │ ├── 08-139-Display products of a selected category.txt │ │ ├── 09-2116-Provide paging for product lists.txt │ │ ├── 10-37-Access shopping cart from the home page.txt │ │ ├── 11-41-Display product detailed information.txt │ │ ├── 12-75-Add product to the shopping cart.txt │ │ ├── 13-141-Remove product from shopping cart.txt │ │ ├── 14-57-Review products in shopping cart.txt │ │ ├── 15-58-Add delivery address for the order.txt │ │ ├── 16-59-Review order before checkout.txt │ │ ├── 17-147-Place order after review as member.txt │ │ ├── 18-155-Place order after review as guest.txt │ │ ├── 19-142-Display all order made by visitors and members.txt │ │ ├── 20-143-Update completed order.txt │ │ ├── 21-63-Display orders history for members.txt │ │ ├── 22-5-Provide membership for visitors.txt │ │ ├── 23-146-Login to the member site.txt │ │ ├── 24-271-Login to the vendor panel.txt │ │ ├── 25-89-Login to the admin panel.txt │ │ ├── 26-96-Add product to the store.txt │ │ ├── 27-92-Display all added products.txt │ │ ├── 28-93-Update product data.txt │ │ ├── 29-2071-Display all orders made by all users for all vendors.txt │ │ ├── 30-2119-Update order status.txt │ │ ├── 31-2118-Display order detailed information.txt │ │ ├── 32-90-Recover forgotten password.txt │ │ └── 33-18-Change password.txt │ └── Initial PBIs (Text) │ │ ├── 01-161-Display special offer products in a slider.txt │ │ ├── 02-138-Display featured products in a slider.txt │ │ ├── 03-28-View top new arrival products in a slider.txt │ │ ├── 04-120-View hot sale products in a slider.txt │ │ ├── 05-119-Display best selling products in a slider.txt │ │ ├── 06-121-Display random products in a slider.txt │ │ ├── 07-145-Display all main and sub categories of products.txt │ │ ├── 08-139-Display products of a selected category.txt │ │ ├── 09-2116-Provide paging for products listing.txt │ │ ├── 10-37-Access the shopping cart from the home page.txt │ │ ├── 11-41-View a detailed product information.txt │ │ ├── 12-75-Add selected product to the shopping cart.txt │ │ ├── 13-141-Remove a product from shopping cart.txt │ │ ├── 14-57-Review products in shopping cart.txt │ │ ├── 15-58-Add delivery address for the order.txt │ │ ├── 16-59-Review order before checkout.txt │ │ ├── 17-147-Place order after review as member.txt │ │ ├── 18-155-Place order after review as guest.txt │ │ ├── 19-142-List all order made by users.txt │ │ ├── 20-143-Update completed order.txt │ │ ├── 21-63-Display placed orders.txt │ │ ├── 22-5-Provide a membership for user.txt │ │ ├── 23-146-Login to the member site.txt │ │ ├── 24-271-Login to the vendor panel.txt │ │ ├── 25-89-Login to the admin panel.txt │ │ ├── 26-96-Add a product to the store.txt │ │ ├── 27-92-List all added products.txt │ │ ├── 28-93-Update product data.txt │ │ ├── 29-2071-Display all orders made by all users for all vendors.txt │ │ ├── 30-2119- Update order status.txt │ │ ├── 31-2118-View order details.txt │ │ ├── 32-90-Recover forgotten password.txt │ │ ├── 33-18-Change password.txt │ │ └── README.md ├── 2-Test Cases (Text) │ ├── Conceptual Test Cases (Text) │ │ └── README.md │ ├── Functional Test Cases (Text) │ │ └── README.md │ └── Functional and Usability Test Cases (Text) │ │ └── README.md ├── 3-Use Case Scenarios (Text) │ ├── Detailed Use Case Scenarios (Text) │ │ ├── 01- Use Case 161-Display special offer products in a slider.txt │ │ ├── 02- Use Case 138-Display top featured products in a slider.txt │ │ ├── 03- Use Case 28-Display top new arrival products in a slider.txt │ │ ├── 04- Use Case 120-Display top hot sale products in a slider.txt │ │ ├── 05- Use Case 119-Display top best selling products in a slider.txt │ │ ├── 06- Use Case 121-Display random products in a slider.txt │ │ ├── 07- Use Case 145-Display all main and sub categories of products.txt │ │ ├── 08- Use Case 139-Display products of a selected category.txt │ │ ├── 09- Use Case 2116-Provide paging for product lists.txt │ │ ├── 10- Use Case 37-Access shopping cart from the home page.txt │ │ ├── 11- Use Case 41-Display product detailed information.txt │ │ ├── 12- Use Case 75-Add product to the shopping cart.txt │ │ ├── 13- Use Case 141-Remove product from shopping cart.txt │ │ ├── 14- Use Case 57-Review products in shopping cart.txt │ │ ├── 15- Use Case 58-Add delivery address for the order.txt │ │ ├── 16- Use Case 59-Review order before checkout.txt │ │ ├── 17- Use Case 147-Place order after review as member.txt │ │ ├── 18- Use Case 155-Place order after review as guest.txt │ │ ├── 19- Use Case 142-Display all order made by visitors and members.txt │ │ ├── 20- Use Case 143-Update completed order.txt │ │ ├── 21- Use Case 63-Display orders history for members.txt │ │ ├── 22- Use Case 5-Provide membership for visitors.txt │ │ ├── 23- Use Case 146-Login to the member site.txt │ │ ├── 24- Use Case 271-Login to the vendor panel.txt │ │ ├── 25- Use Case 89-Login to the admin panel.txt │ │ ├── 26- Use Case 96-Add product to the store.txt │ │ ├── 27- Use Case 92-Display all added products.txt │ │ ├── 28- Use Case 93-Update product data.txt │ │ ├── 29- Use Case 2071-Display all orders made by all users for all vendors.txt │ │ ├── 30- Use Case 2119-Update order status.txt │ │ ├── 31- Use Case 2118-Display order detailed information.txt │ │ ├── 32- Use Case 90-Recover forgotten password.txt │ │ ├── 33- Use Case 18-Change password.txt │ │ └── README.md │ └── Initial Use Case Scenarios (Text) │ │ ├── 01- Use Case 161-Display special offer products in a slider.txt │ │ ├── 02- Use Case 138-Display top featured products in a slider.txt │ │ ├── 03- Use Case 28-Display top new arrival products in a slider.txt │ │ ├── 04- Use Case 120-Display top hot sale products in a slider.txt │ │ ├── 05- Use Case 119-Display top best selling products in a slider.txt │ │ ├── 06- Use Case 121-Display random products in a slider.txt │ │ ├── 07- Use Case 145-Display all main and sub categories of products.txt │ │ ├── 08- Use Case 139-Display products of a selected category.txt │ │ ├── 09- Use Case 2116-Provide paging for product lists.txt │ │ ├── 10- Use Case 37-Access shopping cart from the home page.txt │ │ ├── 11- Use Case 41-Display product detailed information.txt │ │ ├── 12- Use Case 75-Add product to the shopping cart.txt │ │ ├── 13- Use Case 141-Remove product from shopping cart.txt │ │ ├── 14- Use Case 57-Review products in shopping cart.txt │ │ ├── 15- Use Case 58-Add delivery address for the order.txt │ │ ├── 16- Use Case 59-Review order before checkout.txt │ │ ├── 17- Use Case 147-Place order after review as member.txt │ │ ├── 18- Use Case 155-Place order after review as guest.txt │ │ ├── 19- Use Case 142-Display all order made by visitors and members.txt │ │ ├── 20- Use Case 143-Update completed order.txt │ │ ├── 21- Use Case 63-Display orders history for members.txt │ │ ├── 22- Use Case 5-Provide membership for visitors.txt │ │ ├── 23- Use Case 146-Login to the member site.txt │ │ ├── 24- Use Case 271-Login to the vendor panel.txt │ │ ├── 25- Use Case 89-Login to the admin panel.txt │ │ ├── 26- Use Case 96-Add product to the store.txt │ │ ├── 27- Use Case 92-Display all added products.txt │ │ ├── 28- Use Case 93-Update product data.txt │ │ ├── 29- Use Case 2071-Display all orders made by all users for all vendors.txt │ │ ├── 30- Use Case 2119-Update order status.txt │ │ ├── 31- Use Case 2118-Display order detailed information.txt │ │ ├── 32- Use Case 90-Recover forgotten password.txt │ │ ├── 33- Use Case 18-Change password.txt │ │ └── README.md ├── 4-Basic Mockups (Pictures) │ └── README.md ├── 5-Photoshop Design (PSD and Pictures) │ └── README.md ├── 6-Website Components (HTML-CSS-JS) │ └── HTML │ │ └── README.md ├── 7-Storyboard (PPTX) │ ├── Conceptual Storyboard (PPTX) │ │ └── README.md │ └── Detailed Storyboard (PPTX) │ │ └── README.md └── 8-E-Commerce Products data (Pictures-Data Txt) │ └── README.md └── src ├── Code └── README.md ├── Infrastructure └── README.md ├── Packages └── README.md └── README.md /README.md: -------------------------------------------------------------------------------- 1 |

2 |
3 | DevOpsThoughts Logo 4 |
5 |

6 | 7 | # DevOpsThoughts 8 | DevOpsThoughts is a community initiative aims to teach the best practices in DevOps through a multi-platform application which targets variety of technologies. 9 | DevOps is one of the most emerging topics of software development today as it improves the whole software development process, but unfortunately, there is no clear, detailed and explicit model to teach the best DevOps & Software Engineering practices on real world projects, this was the main problem that lead to DevOpsThoughts community establishment. 10 | 11 | DevOpsThoughts teaches the best practices on a series of real world e-commerce projects, each of which is 12 | 17 | 18 | ### DevOpsThoughts Architecture 19 | Visualization is the best way to understand DevOpsThoughts architecture, below is a list of useful diagrams to explain this. 20 | 21 | 26 | 27 | ### Quick Start 28 | 29 | Run the following commands and replace the BranchName with the name of the branch you want to clone. 30 | 31 | ``` 32 | git clone https://github.com/DevOpsThoughts/E-Commerce.git -b BranchName 33 | cd E-Commerce 34 | ``` 35 | 36 | 37 | 38 | 39 | 40 | # DevOpsThoughts Rabbit 41 | 42 | DevOpsThoughts Rabbit is the first project in DevOpsThoughts Series. It's an e-commerce website built with the following technologies: 43 | 48 | 49 | Below is the homepage for DevOpsThoughts Rabbit 50 |

51 |
52 | Homepage Design 53 |
54 |

55 | 56 | 57 | # Development Steps 58 | As we're developing a model for learning, we had to make a precise plan for the whole development process, using Scrum, user stories and behavior driven development (BDD) we can simply but the plan into this list: 59 | 60 | ## User Stories & Product Backlog Items (PBIs) 61 | 62 | 66 | For each user story, we develop a Product Backlog Item (PBI), assign proper tags to it based on publicity (Public/Private), main actor (Visitor/Member/Vendor/Admin) and work flow type (Basic/Advanced), then we add its Acceptance Criteria. 67 | Each Acceptance Criteria Consists of two main parts: 68 | 72 | All PBIs are made on two levels 73 | 77 | All BWF PBIs are added to the source control in plain text format, so we can quickly trace any changes to it. 78 | 79 | Below is the sample for Vendor's login Initial PBI. 80 | 81 |

82 |
83 | Vendor Login Initial 84 |
85 |

86 | 87 | Another sample for Vendor's login Detailed PBI. 88 | 89 |

90 |
91 | Vendor Login Detailed 92 |
93 |

94 | 95 | 96 | You can click here to view the complete list of all Basic Work Flow PBIs 97 | 98 | ---- 99 | ## Test Cases 100 | Test Cases are very important for Behavior driven development, In DevOpsThoughts, we have test cases written on three levels 101 | 106 | 107 | ### Conceptual Test Cases 108 | Conceptual Test Cases are the most abstract form of test cases made with conceptual input only for purpose of conceptualizing the flow itself. 109 | ### Functional Test Cases 110 | Functional Test Cases made for testing the application functionality without discussing UI elements or UX, just making sure the application outputs the suitable output when some input is provided. 111 | ### Usability & Functional Test Cases 112 | Usability & Functional Test Cases are the most detailed test cases, it cares not only for functionality as functional test cases, but also for the way application responds to user actions from user experience (UX) and user interface (UI) perspective. 113 | 114 | ---- 115 | ## Use Case Scenarios 116 | Use Case Scenario is a list of user actions and system response to it. In DevOpsThoughts, we map each PBI to a single use case scenario. Each scenario has the following: 117 | 125 | Also as in PBIs, use case scenarios are divided into Initial and Detailed use case scenarios. 126 | 130 | 131 | 132 | Below is the sample for Display Products List Initial Use Case Scenario. 133 | 134 |

135 |
136 | Use Case Initial 137 |
138 |

139 | 140 | Another sample for Display Products List Detailed Use Case Scenario. 141 |

142 |
143 | Use Case Detailed 144 |
145 |

146 | 147 | ---- 148 | 149 | ## Basic Mockups 150 | Mockups are very basic UI representation used to deliver an abstract format of the expected to UI design to a UI developer from end-user or product owner perspective. 151 | ### Making Mockups 152 | Mockups are usually made using a basic photo edition application like MS Paint or Paint.NET. 153 | ### Level of Details 154 | Mockups usually represents only an abstract view of a webpage, Only spaces occupied and by which elements, doesn't include icons, content nor colors. 155 | 156 | ---- 157 | ## PhotoShop Designs (PSDs) 158 | Based on Test Cases, Basic Mockups and PBIs, the final PSDs are made for the Project, A PSD file is a Photoshop Design file which can be edited later, PSD files are kept up-to-date with any modifications made to the UI. 159 | ### Level of Details 160 | PSD Designs are made while keeping attention to details. We can - from logical point of view - look to the Basic Mockups as initial designs, while the PSDs are the detailed designs. 161 | 162 | Below is a sample for the Final PSD Design for the homepage, and it's identical with the screenshot for the homepage at the very beginning of this readme file. 163 | 164 |

165 |
166 | PSD 167 |
168 |

169 | 170 | 171 | ---- 172 | ## Website Components (HTML, CSS and JavaScript) 173 | Website components are simply the source code for UI, alongside with any elements used in the UI such as images, icons and libraries. 174 | The Website components isn't only used for Rabbit, but the same are used for other versions of the project which is using web as a presentation layer. 175 | Developing the website components uses PSDs as an input, each PSD is converted - as it is - to be a separate web page. 176 | We gave much importance to utilize and minify all of UI source files. 177 | After each PSD is converted, it is reviewed on two levels 178 |
    179 |
  1. External: Which is making sure that the web page matches 100% the provided PSD.
    2. 180 |
  2. Internal: Which is checking for source code quality, readability and if the code is minified.
    3. 181 |
182 | 183 | 184 | 185 | ---- 186 | ## Storyboarding 187 | A Storyboarding is an illustration for a user interaction with application story, not to be confused with user stories, in storyboarding we use visual images arrayed together for user interaction with the application to represent. 188 | Storyboards are easier to be remembered than other written Test Cases, as it shows the real UX, not just some text about it. 189 | In DevOpsThoughts we use Microsoft Office's PowerPoint, which allows develops to make an animated representation of User interaction with application UI quickly with higher quality. 190 | If we look to the PSDs and Basic Mockups as a User Interface representation, we should consider Storyboarding to be the User Experience Representation. 191 | 192 | ---- 193 | ## Products Data 194 | 195 | To give the application some reality, we have added more than 400 Products, and we're still adding more frequently. 196 | For each product, the following information is added 197 | 212 | 213 | 214 | ---- 215 | ## Pages List Grouped By User Roles 216 | 262 | 263 | 264 | 265 | ---- 266 | 267 | ## Architecture Diagram 268 | Architecture diagram is a graphical representation of System components and how thery're (components) are groupped together. The UML Architecture Diagram gives use a general overview of how the system works and its principles. 269 | 270 |

271 |
272 | Architecture Diagram 273 |
274 |

275 | 276 |

277 | 278 | ---- 279 | 280 | ## Use Case Diagram 281 | Use Case Diagram is UML Diagram used to represent different interactions with the system. The Use Case Diagram also acts as an input for making PBIs and User Stories. 282 | 283 | Below is the Use Case Diagram we have in DevOpsThoughts. 284 | 285 |

286 |
287 | Use Case Diagram 288 |
289 |

290 | 291 |

292 | 293 | ---- 294 | 295 | ## Project Layers 296 | Below a screenshot from Microsoft Visual Studio's Solution Explorer for the different layers used in DevOpsThoughts. 297 | 298 |

299 |
300 | Use Case Diagram 301 |
302 |

303 | 304 | 305 | 306 | ---- 307 |
308 | 309 | ## List of Basic Work Flow Product Backlog Items (PBIs) 310 | 311 | This is the complete list of BWF PBIs: 312 | 313 |
    314 |
  1. Display special offer products in a slider
    2. 315 |
  2. Display top featured products in a slider
    3. 316 |
  3. Display top new arrival products in a slider
    4. 317 |
  4. Display top hot sale products in a slider
    5. 318 |
  5. Display top best selling products in a slider
    6. 319 |
  6. Display random products in a slider
    7. 320 |
  7. Display all main and sub categories of products
    8. 321 |
  8. Display products of a selected category
    9. 322 |
  9. Provide paging for product lists
    10. 323 |
  10. Access shopping cart from the home page
    11. 324 |
  11. Display product detailed information
    12. 325 |
  12. Add product to the shopping cart
    13. 326 |
  13. Remove product from shopping cart
    14. 327 |
  14. Review products in shopping cart
    15. 328 |
  15. Add delivery address for the order
    16. 329 |
  16. Review order before checkout
    17. 330 |
  17. Place order after review as member
    18. 331 |
  18. Place order after review as guest
    19. 332 |
  19. Display all order made by visitors and members
    20. 333 |
  20. Update completed order
    21. 334 |
  21. Display orders history for members
    22. 335 |
  22. Provide membership for visitors
    23. 336 |
  23. Login to the member site
    24. 337 |
  24. Login to the vendor panel
    25. 338 |
  25. Login to the admin panel
    26. 339 |
  26. Add product to the store
    27. 340 |
  27. Display all added products
    28. 341 |
  28. Update product data
    29. 342 |
  29. Display all orders made by all users for all vendors
    30. 343 |
  30. Update order status
    31. 344 |
  31. Display order detailed information
    32. 345 |
  32. Recover forgotten password
    33. 346 |
  33. Change password
    34. 347 |
348 | 349 | 350 | ### About The Founder 351 | 352 | Mohamed Radwan is Visual Studio MVP (Microsoft Most Valuable Professional) for 5 consecutive years and a DevOps Practice Lead. He focuses on providing solutions for the various roles involved in software development and delivery process to enable them to build better software through Agile Methodologies and utilization of Microsoft Visual Studio ALM/DevOps Tools and Technologies.
353 | Mohamed has been working in software development industry for more than 17 years, starting as a classic ASP developer in the year 2000 them moving to different roles as a senior developer, team leader, lead architect. For the last 7 years he has been passionate and focused about DevOps practices and automation.
354 | Mohamed also worked in several countries in different regions, including United Kingdom, Sweden, Denmark, Egypt, Saudi Arabia, Kuwait, Oman, Libya.
355 | Through his journey, he got the opportunity to work and help hundreds of companies to improve their software delivery practices. 356 | He also issued a lot of guides for TFS (Team Foundation Server), developed many extensions for Visual Studio, made many open source libraries and projects on GitHub and authored many tutorials on YouTube, his blog and other communities. 357 | He is also a regular speaker and participated in many local and regional conferences and events in all countries where He worked in.
358 | 362 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/01-161-Display special offer products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 1 2 | 3 | Id : 161 4 | 5 | Title : Display special offer products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view special offers for products in a slider that exists on the home page as a banner so that 11 | I can view the special offers and buy from them. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Three products in a slider should be displayed. 17 | * Buttons for moving between products should be Displayed. 18 | * All three products should be loaded at once. 19 | * A detailed view for a product should be displayed when clicked from slider 20 | 21 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/02-138-Display top featured products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 2 2 | 3 | Id : 138 4 | 5 | Title : Display top featured products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to see featured products in a slider that exist on the home page below special offer product's 11 | slider so that I can view the featured products and buy from them. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Three product at a time in slider's page should be displayed. 17 | * buttons for moving to next three and previous three products in slider should be included. 18 | * Three products should be loaded in advance from current one (next to current page and previous to current page). 19 | * A detailed view for a product should be displayed when clicked from slider 20 | * Limit number of pages in slider to be maximum 5 (it could be only one page if database does not have enough featured products), 21 | last item of 5th page should be a link titled "View All". 22 | * Last item of last page of slider ("View All") should open all featured products on a separate view/page. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/03-28-Display top new arrival products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 3 2 | 3 | Id : 28 4 | 5 | Title : Display top new arrival products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view top new arrival products in a slider on the home page so that I can 11 | view the new arrival products and buy from them. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Three product at a time in slider's page should be displayed. 17 | * buttons for moving to next three and previous three products in slider should be included. 18 | * Three products should be loaded in advance from current one (next to current page and previous to current page). 19 | * A detailed view for a product should be displayed when clicked from slider 20 | * Limit number of pages in slider to be maximum 5 (it could be only one page if database does not have enough featured products), 21 | last item of 5th page should be a link titled "View All". 22 | * Last item of last page of slider ("View All") should open all featured products on a separate view/page. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/04-120-Display top hot sale products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 4 2 | 3 | Id : 120 4 | 5 | Title : Display top hot sale products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view hot sale products in a slider on the home page so that I can 11 | view the hot sale products and buy from them. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * One product at a time in slider's page should be displayed. 17 | * Buttons for moving to next one and previous one product in slider should be included. 18 | * One product should be loaded in advance from current one (next to current page and previous to current page). 19 | * A detailed view for a product should be displayed when clicked from slider. 20 | * Limit number of pages in slider to be maximum 5 (it could be only one page if database does not have enough featured products), last item of 5th page should be a link titled "View All". 21 | * Last item of last page of slider ("View All") should display a link to open all hot sale products on a separate 22 | view/page where products will be displayed in descending order of their discount amount. 23 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/05-119-Display top best selling products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 5 2 | 3 | Id : 119 4 | 5 | Title : Display top best selling products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view best selling products in a slider on the home page so that 11 | I can view the best selling products and buy from them. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * One product at a time in slider's page should be displayed. 17 | * Buttons for moving to next one and previous one product in slider should be included. 18 | * One product should be loaded in advance from current one (next to current page and previous to current page). 19 | * A detailed view for a product should be displayed when clicked from slider. 20 | * Limit number of pages in slider to be maximum 5 (it could be only one page if database does not have enough featured products), last item of 5th page should be a link titled "View All". 21 | * Last item of last page of slider ("View All") should display a link to open all hot sale products on a separate 22 | view/page where products will be displayed in descending order of their discount amount. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/06-121-Display random products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 6 2 | 3 | Id : 121 4 | 5 | Title : Display random products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view random products in a slider on the home page so that 11 | I can view random products and buy from them. 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * One product at a time in slider's page should be displayed. 16 | * Buttons for moving to next one and previous one product in slider should be included. 17 | * One product should be loaded in advance from current one (next to current page and previous to current page). 18 | * A detailed view for a product should be displayed when clicked from slider. 19 | * Limit number of pages in slider to be maximum 5 (it could be only one page if database does not have enough featured products), last item of 5th page should be a link titled "View All". 20 | * Last item of last page of slider ("View All") should display a link to open all hot sale products on a separate 21 | view/page where products will be displayed in descending order of their discount amount. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/07-145-Display all main and sub categories of products.txt: -------------------------------------------------------------------------------- 1 | Order : 7 2 | 3 | Id : 145 4 | 5 | Title : Display all main and sub categories of products 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view all main and sub categories of products on the home page so that I can 11 | easily navigate and select the required category. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * All categories should be displayed in a list. 17 | * All subcategories of a list should be displayed in the same list. 18 | * All displayed categories should be dynamically fetched. 19 | * A detailed view/page of a category/subcategory should be displayed when clicked. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/08-139-Display products of a selected category.txt: -------------------------------------------------------------------------------- 1 | Order : 8 2 | 3 | Id : 139 4 | 5 | Title : Display products of a selected category 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to navigate and select a main or a sub category from categories so that I can 11 | view all products in that category. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * All related products of selected category should be displayed in a list. 17 | * 20 products/page should be displayed by default. 18 | * A paging buttons should be displayed for navigation between other products pages. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/09-2116-Provide paging for product lists.txt: -------------------------------------------------------------------------------- 1 | Order : 9 2 | 3 | Id : 2116 4 | 5 | Title : Provide paging for product lists 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to navigate between different pages which displays the products I'm looking for. 11 | 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * 20 items should be displayed per page by default, but this number can be changed from settings. 16 | * Two navigation buttons for navigation between next and previous page should be displayed. 17 | * Two navigation buttons for navigation to first and last page should be displayed 18 | * Buttons for page numbers including the current page should be displayed. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/10-37-Access shopping cart from the home page.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/CloudDevOpsVisions/E-Commerce/16727613efaedd4a065b97099098f7b669a937d3/doc/1-PBIs (Text)/Detailed PBIs (Text)/10-37-Access shopping cart from the home page.txt -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/11-41-Display product detailed information.txt: -------------------------------------------------------------------------------- 1 | Order : 11 2 | 3 | Id : 41 4 | 5 | Title : Display product detailed information 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view a detailed product information in a separate view so that 11 | I can view more about the selected product. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Title, description, image, price, discount, stock availability of product should be displayed. 17 | * Key features of product should be displayed. 18 | * Full specifications with all details of product should be displayed. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/12-75-Add product to the shopping cart.txt: -------------------------------------------------------------------------------- 1 | Order : 12 2 | 3 | Id : 75 4 | 5 | Title : Add product to the shopping cart 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to add a product to my cart with a single click when viewing 11 | products so that I can quickly put the product I want to purchase into my cart. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * A click on "Add to cart" button for a product should add it to the shopping cart. 17 | * Multiple clicks on "Add to cart" should increase the quantity of the added product. 18 | * A popup window indicating that the selected product was added to the shopping cart should 19 | smoothly appears and after 3 seconds smoothly disappears when a product is added. 20 | 21 | 22 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/13-141-Remove product from shopping cart.txt: -------------------------------------------------------------------------------- 1 | Order : 13 2 | 3 | Id : 141 4 | 5 | Title : Remove product from shopping cart 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to remove a product from shopping cart by a button/link so that 11 | I can remove unwanted products from my shopping cart. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * A Remove button should be displayed for each product in shopping cart. 17 | * A Product should be removed from shopping cart by clicking on remove button. 18 | * Shopping cart price, quantity and total should be updated when a product is removed 19 | from the shopping cart. 20 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/14-57-Review products in shopping cart.txt: -------------------------------------------------------------------------------- 1 | Order : 14 2 | 3 | Id : 57 4 | 5 | Title : Display special offer products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to review the details for the shopping cart at anytime so that 11 | I can correct any mistake that might exist. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Title, Price, Quantity, Image, Discount and Shipping details should be displayed for 17 | each added product. 18 | * Buttons to add/remove products from shopping cart should be displayed. 19 | * Checkout button should be displayed. 20 | * Continue shopping button should be displayed. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/15-58-Add delivery address for the order.txt: -------------------------------------------------------------------------------- 1 | Order : 15 2 | 3 | Id : 58 4 | 5 | Title : Add delivery address for the order 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to add addresses during my shopping checkout so that I can specify address 11 | for delivery. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * A full detailed address which includes City, Postal Code, State, Country, Street Address should be saved. 17 | * All the above information is required. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/16-59-Review order before checkout.txt: -------------------------------------------------------------------------------- 1 | Order : 16 2 | 3 | Id : 59 4 | 5 | Title : Review order before checkout 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to review the shopping cart details along with delivery address 11 | before proceeding to checkout so that I can correct any mistake that might exist. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Image, Title, Quantity, Price, Discount, Total amount and Gift Wrap option for each added product 17 | should be displayed. 18 | * First Name, Last Name, Email, Phone, City, State, Postal Code, Country, Address of shipping details 19 | (delivery address) should be saved. 20 | * Shipping details and adding/removing products from shopping cart should be updateable. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/17-147-Place order after review as member.txt: -------------------------------------------------------------------------------- 1 | Order : 17 2 | 3 | Id : 147 4 | 5 | Title : Place order after review as member 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want to place an order after reviewing its details so that I can get those products in email. 11 | 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * An email should be sent to the email provided for the shipping details containing information about the 16 | order details. 17 | * An email should be sent to email of logged in member containing information about purchased products. 18 | * If the email provided for the shipping details and email of logged in user are same, A single email should be 19 | sent. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/18-155-Place order after review as guest.txt: -------------------------------------------------------------------------------- 1 | Order : 18 2 | 3 | Id : 155 4 | 5 | Title : Place order after review as guest 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to place an order after reviewing so that I can get those products in email. 11 | 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * A confirmation email should be sent to the email provided for shipping details containing information 16 | about the order details. 17 | * Order information should be stored in database. 18 | * Register guest as a member without password. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/19-142-Display all order made by visitors and members.txt: -------------------------------------------------------------------------------- 1 | Order : 19 2 | 3 | Id : 142 4 | 5 | Title : Display all order made by visitors and members 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to view a list of all orders made by visitors and members in vendor 11 | panel so that I can find and manage desired order. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Order Id, Order Date, Order Status, Total Product in order, Total Price, Username of user who made 17 | order should be displayed. 18 | * There should be link to update order with each order. 19 | * 20 orders per page should be displayed. 20 | * number of displayed orders per page should be updateable from settings. 21 | * There should be paging buttons to move to other pages. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/20-143-Update completed order.txt: -------------------------------------------------------------------------------- 1 | Order : 20 2 | 3 | Id : 143 4 | 5 | Title : Update completed order 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to update an order in vendor panel so that I can correct any mistake that might exist. 11 | 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * Quantity of products in order, Price of each product in order, Discount on each product in order, Total price on 16 | each product in order, Order Status and Gift wrap option of order should be updatable. 17 | * First name, Last name, Email, Phone, City, State, Postal code, Country and Address of shipping details should be 18 | updatable. 19 | 20 | Input Validation Criteria : 21 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 22 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 23 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 24 | |Quantity |Text |N |N |Y |6 |20 |A-Z or a-z or 0-9 or space | 25 | ------------------------------------------------------------------------------------------------------------------ 26 | |Discount |Text |N |N |Y |3 |50 |A-Z or a-z or 0-9 or any special character | 27 | ------------------------------------------------------------------------------------------------------------------ 28 | |Price |Text |N |N |Y |6 |100 |A-Z or a-z or 0-9 or any special character | 29 | ------------------------------------------------------------------------------------------------------------------ 30 | |Total |Integer |N |N |Y |1 |1000 |0-9 | 31 | ------------------------------------------------------------------------------------------------------------------ 32 | |Status |Text |N |N |Y |3 |20 |A-Z or a-z or 0-9 or space | 33 | ------------------------------------------------------------------------------------------------------------------ 34 | |First Name |Text |N |N |Y |3 |20 |A-Z or a-z or blank | 35 | ------------------------------------------------------------------------------------------------------------------ 36 | |Last Name |Text |N |N |Y |3 |20 |A-Z or a-z or blank | 37 | ------------------------------------------------------------------------------------------------------------------ 38 | |Email |Text |N |Y |Y |6 |20 |A-Z or a-z or 0-9 or @, dot, minus/underscore | 39 | ------------------------------------------------------------------------------------------------------------------ 40 | |Phone |Integer |N |N |Y |5 |15 |0-9 | 41 | ------------------------------------------------------------------------------------------------------------------ 42 | |City |Text |N |N |Y |3 |20 |A-Z or a-z or space | 43 | ------------------------------------------------------------------------------------------------------------------ 44 | |State Id |Integer |Y |N |Y |1 |10000 |0-9 | 45 | ------------------------------------------------------------------------------------------------------------------ 46 | |State Name |Text |N |N |Y |3 |50 |A-Z or a-z or 0-9 or space | 47 | ------------------------------------------------------------------------------------------------------------------ 48 | |Postal Code |Integer |N |N |Y |5 |10 |0-9 | 49 | ------------------------------------------------------------------------------------------------------------------ 50 | |Country Id |Integer |Y |N |Y |1 |500 |0-9 | 51 | ------------------------------------------------------------------------------------------------------------------ 52 | |Country Name |Text |N |N |Y |6 |50 |A-Z or a-z or 0-9 or space | 53 | ------------------------------------------------------------------------------------------------------------------ 54 | |Address |Text |N |N |Y |5 |100 |A-Z or a-z or space | 55 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/21-63-Display orders history for members.txt: -------------------------------------------------------------------------------- 1 | Order : 21 2 | 3 | Id : 63 4 | 5 | Title : Display orders history for members 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want to view my previous orders after login, so that I can view any order 11 | details from my orders. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Order Id, Order Date, Each product in order with image and title, Status of order should be displayed. 17 | * 20 orders/page should be displayed. 18 | * number of displayed orders per page should be updateable from settings 19 | * There should be paging buttons to move to other pages. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/22-5-Provide membership for visitors.txt: -------------------------------------------------------------------------------- 1 | Order : 22 2 | 3 | Id : 5 4 | 5 | Title : Provide membership for visitors 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to have a membership in the application as a member, I want to 11 | create an account by using my email so that I can track my orders, wishlist, etc. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * A welcome email should be sent to provided email address upon successful registration. 17 | * Upon successful registration, redirection to account page should happen 18 | 19 | Input Validation Criteria : 20 | +----------------+----------+------+------+--------+---+-------+---------------------------------------------------+ 21 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 22 | +----------------+----------+------+------+--------+---+-------+---------------------------------------------------+ 23 | |First Name |Text |N |N |Y |3 |20 |A-Z or a-z or space | 24 | -------------------------------------------------------------------------------------------------------------------- 25 | |Last Name |Text |N |N |Y |3 |20 |A-Z or a-z or space | 26 | -------------------------------------------------------------------------------------------------------------------- 27 | |Email |Text |N |Y |Y |6 |20 |A-Z or a-z or 0-9 or @, dot, minus/underscore | 28 | -------------------------------------------------------------------------------------------------------------------- 29 | |Phone |Integer |N |N |Y |5 |15 |0-9 | 30 | -------------------------------------------------------------------------------------------------------------------- 31 | |Username |Text |N |Y |Y |3 |20 |A-Z or a-z or 0-9 | 32 | -------------------------------------------------------------------------------------------------------------------- 33 | |Age |Integer |N |N |Y |2 |2 |0-9 | 34 | -------------------------------------------------------------------------------------------------------------------- 35 | |Sex/Gender |Integer |N |N |Y |1 |1 |0-1 | 36 | -------------------------------------------------------------------------------------------------------------------- 37 | |Password |Text |N |N |Y |6 |20 |A-Z or a-z or 0-9 or any special character | 38 | -------------------------------------------------------------------------------------------------------------------- 39 | |Confirm Password|Text |N |Y |N |6 |20 |A-Z or a-z or 0-9 or any special character | 40 | -------------------------------------------------------------------------------------------------------------------- 41 | |City |Text |N |N |Y |3 |20 |A-Z or a-z or space | 42 | ------------------------------------------------------------------------------------------------------------------- 43 | |State Id |Integer |Y |N |Y |1 |10000 |0-9 | 44 | ------------------------------------------------------------------------------------------------------------------- 45 | |State Name |Text |N |N |Y |3 |50 |A-Z or a-z or 0-9 or space | 46 | ------------------------------------------------------------------------------------------------------------------- 47 | |Postal Code |Integer |N |N |Y |5 |10 |0-9 | 48 | ------------------------------------------------------------------------------------------------------------------- 49 | |Country Id |Integer |Y |N |Y |1 |500 |0-9 | 50 | ------------------------------------------------------------------------------------------------------------------- 51 | |Country Name |Text |N |N |Y |6 |50 |A-Z or a-z or 0-9 or space | 52 | ------------------------------------------------------------------------------------------------------------------- 53 | |Address |Text |N |N |Y |5 |100 |A-Z or a-z or space | 54 | +----------------+----------+------+------+--------+---+-------+---------------------------------------------------+ -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/23-146-Login to the member site.txt: -------------------------------------------------------------------------------- 1 | Order : 23 2 | 3 | Id : 146 4 | 5 | Title : Login to the member site 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want to login into the application so that I can manage my membership like reviewing 11 | my previous orders or shipping/delivery address etc, also an option to remember my credentials should 12 | be there so that when I visit the application next time, it doesn't require me to re-enter credentials 13 | again for login. 14 | 15 | Acceptance Criteria : 16 | 17 | Action Criteria : 18 | * Option to remember credentials should be included. 19 | * Link for registration should be included. 20 | * Link to recover password should be included. 21 | * On login failure, a failure message should be shown. 22 | * On login success, member should be redirected to his account. 23 | 24 | Input Validation Criteria : 25 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 26 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 27 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 28 | |Username |Text |N |Y |Y |3 |20 |A-Z or a-z or 0-9 or space | 29 | ------------------------------------------------------------------------------------------------------------------ 30 | |Password |Text |N |N |Y |6 |20 |A-Z or a-z or 0-9 or any special character | 31 | +----------------------------------------------------------------------------------------------------------------+ 32 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/24-271-Login to the vendor panel.txt: -------------------------------------------------------------------------------- 1 | Order : 24 2 | 3 | Id : 271 4 | 5 | Title : Login to the vendor panel 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to login to the vendor panel so that I can manage the application for 11 | different areas, also an option to remember my credentials should be there so that when I visit 12 | the vendor panel next time, it doesn't require me to re-enter credentials again for login. 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Option to remember credentials should be included. 17 | * Link for registration should be included. 18 | * Link to recover password should be included. 19 | * On login failure, a failure message should be shown. 20 | * On login success, vendor should be redirected to the vendor panel. 21 | 22 | Input Validation Criteria : 23 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 24 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 25 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 26 | |Username |Text |N |Y |Y |3 |20 |A-Z or a-z or 0-9 or space | 27 | ------------------------------------------------------------------------------------------------------------------ 28 | |Password |Text |N |N |Y |6 |20 |A-Z or a-z or 0-9 or any special character | 29 | +----------------------------------------------------------------------------------------------------------------+ 30 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/25-89-Login to the admin panel.txt: -------------------------------------------------------------------------------- 1 | Order : 25 2 | 3 | Id : 89 4 | 5 | Title : Login to the admin panel 6 | 7 | Tags : BWF, Private, Admin, Web 8 | 9 | Description : 10 | As an admin, I want to login to the admin panel so that I can manage the application for 11 | different areas, also an option to remember my credentials should be there so that when I 12 | visit the admin panel next time, it doesn't require me to re-enter credentials again for login. 13 | 14 | Acceptance Criteria : 15 | 16 | Action Criteria : 17 | * Option to remember credentials should be included. 18 | * Link for registration should be included. 19 | * Link to recover password should be included. 20 | * On login failure, a failure message should be shown. 21 | * On login success, user redirects to admin panel. 22 | 23 | Input Validation Criteria : 24 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 25 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 26 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 27 | |Username |Text |N |Y |Y |3 |20 |A-Z or a-z or 0-9 or space | 28 | ------------------------------------------------------------------------------------------------------------------ 29 | |Password |Text |N |N |Y |6 |20 |A-Z or a-z or 0-9 or any special character | 30 | +----------------------------------------------------------------------------------------------------------------+ 31 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/26-96-Add product to the store.txt: -------------------------------------------------------------------------------- 1 | Order : 26 2 | 3 | Id : 96 4 | 5 | Title : Add product to the store 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to add a new product to the store to be displayed on the site so 11 | that I can sell my products. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * It should include some other optional data like, sub category, discount, reward 17 | points, key features, specifications and flag for featured product. 18 | * Product should be visible on user end upon successful addition of product. 19 | 20 | Input Validation Criteria : 21 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 22 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 23 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 24 | |Code |Text |N |Y |Y |6 |20 |A-Z or a-z or 0-9 or space | 25 | ------------------------------------------------------------------------------------------------------------------ 26 | |Title |Text |N |N |Y |3 |50 |A-Z or a-z or 0-9 or any special character | 27 | ------------------------------------------------------------------------------------------------------------------ 28 | |Description |Text |N |N |Y |6 |100 |A-Z or a-z or 0-9 or any special character | 29 | ------------------------------------------------------------------------------------------------------------------ 30 | |Category Id |Integer |Y |Y |Y |1 |1000 |0-9 | 31 | ------------------------------------------------------------------------------------------------------------------ 32 | |Category Name |Text |N |Y |Y |3 |50 |A-Z or a-z or 0-9 or or any special character | 33 | ------------------------------------------------------------------------------------------------------------------ 34 | |Brand |Text |N |N |Y |3 |20 |A-Z or a-z or space | 35 | ------------------------------------------------------------------------------------------------------------------ 36 | |Reward Points |Integer |N |N |Y |1 |1000 |0-9 | 37 | ------------------------------------------------------------------------------------------------------------------ 38 | |Price |Integer |N |Y |Y |1 |100000 |0-9 | 39 | ------------------------------------------------------------------------------------------------------------------ 40 | |Discount |Integer |N |N |Y |1 |100000 |0-9 | 41 | ------------------------------------------------------------------------------------------------------------------ 42 | |Specification |Text,Text |N |N |Y |3 |1000 |A-Z or a-z or 0-9 or or any special character | 43 | ------------------------------------------------------------------------------------------------------------------ 44 | |Key features |Text |Y |N |Y |10 |10000 |A-Z or a-z or 0-9 or or any special character | 45 | ------------------------------------------------------------------------------------------------------------------ 46 | |Image |Text |N |N |Y |3 |100 |Image URL | 47 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/27-92-Display all added products.txt: -------------------------------------------------------------------------------- 1 | Order : 27 2 | 3 | Id : 92 4 | 5 | Title : Display all added products 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to view my added products as list in vendor panel so that I can manage them. 11 | 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * Product Id, Title and Price of products should be displayed. 16 | * There should be link to update product with each product. 17 | * There should be link to delete product with each product. 18 | * 20 products/page can be displayed. 19 | * I could change the number of the displayed product from the settings. 20 | * There should be paging buttons to move to other pages. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/28-93-Update product data.txt: -------------------------------------------------------------------------------- 1 | Order : 28 2 | 3 | Id : 92 4 | 5 | Title : Update product data 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to update previously added products, so that I can change old data for any product. 11 | 12 | Acceptance Criteria : 13 | 14 | Action Criteria : 15 | * It should include some other optional data like, sub category, discount, reward points, 16 | key features, specifications and flag for featured product. 17 | 18 | Input Validation Criteria : 19 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 20 | |Field |Data |Hidden|Unique|Required|Min|Max |Format | 21 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ 22 | |Code |Text |N |Y |Y |6 |20 |A-Z or a-z or 0-9 or space | 23 | ------------------------------------------------------------------------------------------------------------------ 24 | |Title |Text |N |N |Y |3 |50 |A-Z or a-z or 0-9 or any special character | 25 | ------------------------------------------------------------------------------------------------------------------ 26 | |Description |Text |N |N |Y |6 |100 |A-Z or a-z or 0-9 or any special character | 27 | ------------------------------------------------------------------------------------------------------------------ 28 | |Category Id |Integer |Y |Y |Y |1 |1000 |0-9 | 29 | ------------------------------------------------------------------------------------------------------------------ 30 | |Category Name |Text |N |Y |Y |3 |50 |A-Z or a-z or 0-9 or or any special character | 31 | ------------------------------------------------------------------------------------------------------------------ 32 | |Brand |Text |N |N |Y |3 |20 |A-Z or a-z or space | 33 | ------------------------------------------------------------------------------------------------------------------ 34 | |Reward Points |Integer |N |N |Y |1 |1000 |0-9 | 35 | ------------------------------------------------------------------------------------------------------------------ 36 | |Price |Integer |N |Y |Y |1 |100000 |0-9 | 37 | ------------------------------------------------------------------------------------------------------------------ 38 | |Discount |Integer |N |N |Y |1 |100000 |0-9 | 39 | ------------------------------------------------------------------------------------------------------------------ 40 | |Specification |Text,Text |N |N |Y |3 |1000 |A-Z or a-z or 0-9 or or any special character | 41 | ------------------------------------------------------------------------------------------------------------------ 42 | |Key features |Text |Y |N |Y |10 |10000 |A-Z or a-z or 0-9 or or any special character | 43 | ------------------------------------------------------------------------------------------------------------------ 44 | |Image |Text |N |N |Y |3 |100 |Image URL | 45 | +---------------+----------+------+------+--------+---+-------+--------------------------------------------------+ -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/29-2071-Display all orders made by all users for all vendors.txt: -------------------------------------------------------------------------------- 1 | Order : 29 2 | 3 | Id : 2071 4 | 5 | Title : Display all orders made by all users for all vendors 6 | 7 | Tags : BWF, Private, Admin, Web 8 | 9 | Description : 10 | As an admin, I want to see list of all orders made by all users to all vendors in 11 | admin panel so that I can find and manage desired order. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * Order Id, Order Date, Order Status, Total Product in order, Total Price, Username of 17 | user who made the order, vendor name who will provide the order, should be displayed. 18 | * There should be link to update order with each order. 19 | * 20 orders/page should be displayed. 20 | * The number of the displayed orders can be changed from the settings. 21 | * We can filter the order list by Username or Vendor name 22 | * There should be paging buttons to move to other pages. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/30-2119-Update order status.txt: -------------------------------------------------------------------------------- 1 | Order : 30 2 | 3 | Id : 2119 4 | 5 | Title : Update order status 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to change order status from within list all orders page with no need 11 | to edit the whole order. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * The order status can be changed with no need to navigate to view/update order page. 17 | * Status change is reflected immediately. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/31-2118-Display order detailed information.txt: -------------------------------------------------------------------------------- 1 | Order : 31 2 | 3 | Id : 2118 4 | 5 | Title : Display order detailed information 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to view a detailed order information in a separate view so that I can 11 | view more about the selected order. 12 | 13 | Acceptance Criteria : 14 | 15 | Action Criteria : 16 | * First Name, Last Name, Email, Phone, City, State, Postal Code, Country, Address of shipping 17 | details (delivery address) of the order maker should be included. 18 | * Image, Title, Quantity, Price, Discount, Total amount and Gift Wrap option of added products 19 | should be included. 20 | * Each of displayed details can be changed by clicking on it. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/32-90-Recover forgotten password.txt: -------------------------------------------------------------------------------- 1 | Order : 32 2 | 3 | Id : 90 4 | 5 | Title : Recover forgotten password 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As an member, I want an option to recover my password to solve my problem if I forgot my password. 11 | 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Detailed PBIs (Text)/33-18-Change password.txt: -------------------------------------------------------------------------------- 1 | Order : 33 2 | 3 | Id : 18 4 | 5 | Title : Change password 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want to change my password at any time so that I can keep my account safe. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/01-161-Display special offer products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 1 2 | 3 | Id : 161 4 | 5 | Title : Display special offer products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to see special offers for products in a slider that exist on the home page above featured 11 | product's slider and on the right side to categories so that I can know about special offers. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/02-138-Display featured products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 2 2 | 3 | Id : 138 4 | 5 | Title : Display featured products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to see featured products in a slider that exist on the home page below special offer 11 | product's slider so that I can know about featured products. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/03-28-View top new arrival products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 3 2 | 3 | Id : 28 4 | 5 | Title : View top new arrival products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view top new arrival products in a slider on the home page so that I can buy popular 11 | products that were unavailable for purchase for a long time. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/04-120-View hot sale products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 4 2 | 3 | Id : 120 4 | 5 | Title : View hot sale products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to view hot sale products on the home page so that I can buy products that are in fashion at 11 | the moment. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/05-119-Display best selling products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 5 2 | 3 | Id : 119 4 | 5 | Title : Display best selling products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to see best selling products in a slider that exist on the home page so that I can know about 11 | best selling products. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/06-121-Display random products in a slider.txt: -------------------------------------------------------------------------------- 1 | Order : 6 2 | 3 | Id : 121 4 | 5 | Title : Display random products in a slider 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to see random products in a slider that exist on the home page so that I can know about 11 | random products. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/07-145-Display all main and sub categories of products.txt: -------------------------------------------------------------------------------- 1 | Order : 7 2 | 3 | Id : 145 4 | 5 | Title : Display all main and sub categories of products 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to see all main and sub categories of products in the home page so that I can quickly select 11 | the required category. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/08-139-Display products of a selected category.txt: -------------------------------------------------------------------------------- 1 | Order : 8 2 | 3 | Id : 139 4 | 5 | Title : Display products of a selected category 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to select a main or sub category from category list so that I can see what are the products 11 | in that category. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/09-2116-Provide paging for products listing.txt: -------------------------------------------------------------------------------- 1 | Order : 9 2 | 3 | Id : 2116 4 | 5 | Title : Provide paging for products listing 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to have a paging method to navigate between different pages which displays the products 11 | which I'm looking for. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/10-37-Access the shopping cart from the home page.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/CloudDevOpsVisions/E-Commerce/16727613efaedd4a065b97099098f7b669a937d3/doc/1-PBIs (Text)/Initial PBIs (Text)/10-37-Access the shopping cart from the home page.txt -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/11-41-View a detailed product information.txt: -------------------------------------------------------------------------------- 1 | Order : 11 2 | 3 | Id : 41 4 | 5 | Title : View a detailed product information 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to be able to view a detailed product information in a separate view so that I can explore 11 | more about the selected product. 12 | 13 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/12-75-Add selected product to the shopping cart.txt: -------------------------------------------------------------------------------- 1 | Order : 12 2 | 3 | Id : 75 4 | 5 | Title : Add selected product to the shopping cart 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to be able to add a product to my cart with a single click when viewing products so that I 11 | can quickly put the product I want to purchase into my cart. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/13-141-Remove a product from shopping cart.txt: -------------------------------------------------------------------------------- 1 | Order : 13 2 | 3 | Id : 141 4 | 5 | Title : Remove a product from shopping cart 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want an option to remove a product from shopping cart by a button/link so that 11 | I can remove unwanted products from shopping cart. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/14-57-Review products in shopping cart.txt: -------------------------------------------------------------------------------- 1 | Order : 14 2 | 3 | Id : 57 4 | 5 | Title : Review products in shopping cart 6 | 7 | Tags : BWF, Public, Vistor, Web 8 | 9 | Description : 10 | As a visitor, I want to review the details of the content for the shopping cart at anytime so that I 11 | can correct any mistake. -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/15-58-Add delivery address for the order.txt: -------------------------------------------------------------------------------- 1 | Order : 15 2 | 3 | Id : 58 4 | 5 | Title : Update completed order 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want an option to add addresses after clicking "Place Order" on shopping 11 | cart page for delivery so that I can specify address for delivery. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/16-59-Review order before checkout.txt: -------------------------------------------------------------------------------- 1 | Order : 16 2 | 3 | Id : 59 4 | 5 | Title : Review order before checkout 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to review content of shopping cart along with delivery address before proceeding to 11 | checkout so that I can correct any mistake that might be there. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/17-147-Place order after review as member.txt: -------------------------------------------------------------------------------- 1 | Order : 17 2 | 3 | Id : 147 4 | 5 | Title : Place order after review as member 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want an option to place an order after review so that I can get those products. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/18-155-Place order after review as guest.txt: -------------------------------------------------------------------------------- 1 | Order : 18 2 | 3 | Id : 155 4 | 5 | Title : Place order after review as guest 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want an option to place an order after review so that I can get those products. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/19-142-List all order made by users.txt: -------------------------------------------------------------------------------- 1 | Order : 19 2 | 3 | Id : 142 4 | 5 | Title : List all order made by users 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to see list of all orders made by users in vendor panel so that I can find and manage desired 11 | order. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/20-143-Update completed order.txt: -------------------------------------------------------------------------------- 1 | Order : 20 2 | 3 | Id : 143 4 | 5 | Title : Update completed order 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want an option to update an order in vendor panel so that I can correct any mistake that might 11 | exist in any order. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/21-63-Display placed orders.txt: -------------------------------------------------------------------------------- 1 | Order : 21 2 | 3 | Id : 63 4 | 5 | Title : Display placed orders 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want to see my placed orders after login, so that I can view any order details 11 | or ordered products from this place. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/22-5-Provide a membership for user.txt: -------------------------------------------------------------------------------- 1 | Order : 22 2 | 3 | Id : 5 4 | 5 | Title : Provide a membership for user 6 | 7 | Tags : BWF, Public, Visitor, Web 8 | 9 | Description : 10 | As a visitor, I want to have membership in application as user, I want to create an account by using my 11 | email address so that I can track transactions, wishlist, etc. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/23-146-Login to the member site.txt: -------------------------------------------------------------------------------- 1 | Order : 23 2 | 3 | Id : 146 4 | 5 | Title : Login to the member site 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I want to login into the application so that I can mange my membership like review my 11 | previous orders or shipping/delivery address etc. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/24-271-Login to the vendor panel.txt: -------------------------------------------------------------------------------- 1 | Order : 24 2 | 3 | Id : 271 4 | 5 | Title : Login to the vendor panel 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want an option to login to the vendor panel so that I can manage the application for 11 | different areas, also an option to remember my credentials should be there so that when I visit the 12 | vendor panel next time it do not require me to re-enter credentials again for login. 13 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/25-89-Login to the admin panel.txt: -------------------------------------------------------------------------------- 1 | Order : 25 2 | 3 | Id : 89 4 | 5 | Title : Login to the admin panel 6 | 7 | Tags : BWF, Private, Admin, Web 8 | 9 | Description : 10 | As an admin, I want an option to login to the admin panel so that I can manage the application for 11 | different areas, also an option to remember my credentials should be there so that when I visit the 12 | admin panel next time it do not require me to re-enter credentials again for login. 13 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/26-96-Add a product to the store.txt: -------------------------------------------------------------------------------- 1 | Order : 26 2 | 3 | Id : 96 4 | 5 | Title : Add a product to the store 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want an option to add new products to be displayed on the app so that I can sell my products. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/27-92-List all added products.txt: -------------------------------------------------------------------------------- 1 | Order : 27 2 | 3 | Id : 92 4 | 5 | Title : List all added products 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to see my added product list in vendor panel so that I can manage them. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/28-93-Update product data.txt: -------------------------------------------------------------------------------- 1 | Order : 28 2 | 3 | Id : 93 4 | 5 | Title : Update product data 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want an option to update added products, this option can be given in product list 11 | so that I can update product data. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/29-2071-Display all orders made by all users for all vendors.txt: -------------------------------------------------------------------------------- 1 | Order : 29 2 | 3 | Id : 2071 4 | 5 | Title : Display all orders made by all users for all vendors 6 | 7 | Tags : BWF, Private, Admin, Web 8 | 9 | Description : 10 | As an admin, I want to see list of all orders made by all users to all vendors in admin panel so that I can 11 | find and manage desired order. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/30-2119- Update order status.txt: -------------------------------------------------------------------------------- 1 | Order : 30 2 | 3 | Id : 2119 4 | 5 | Title : Update order status 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want an option to change order status from within list all orders page with no 11 | need to edit the whole order. 12 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/31-2118-View order details.txt: -------------------------------------------------------------------------------- 1 | Order : 31 2 | 3 | Id : 2118 4 | 5 | Title : View order details 6 | 7 | Tags : BWF, Private, Vendor, Web 8 | 9 | Description : 10 | As a vendor, I want to have a page to view a single order details so I can check any order information. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/32-90-Recover forgotten password.txt: -------------------------------------------------------------------------------- 1 | Order : 32 2 | 3 | Id : 90 4 | 5 | Title : Recover forgotten password 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As an member, I want an option to recover my password to solve my problem and if I forgot my password. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/33-18-Change password.txt: -------------------------------------------------------------------------------- 1 | Order : 33 2 | 3 | Id : 18 4 | 5 | Title : Change password 6 | 7 | Tags : BWF, Public, Member, Web 8 | 9 | Description : 10 | As a member, I may want change my password at any time so that I can keep my account safe. 11 | -------------------------------------------------------------------------------- /doc/1-PBIs (Text)/Initial PBIs (Text)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/2-Test Cases (Text)/Conceptual Test Cases (Text)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/2-Test Cases (Text)/Functional Test Cases (Text)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/2-Test Cases (Text)/Functional and Usability Test Cases (Text)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/01- Use Case 161-Display special offer products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 161 2 | 3 | PBI Title : Display special offer products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Three products was chosen by an admin to be displayed in the slider. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider shows the first offer with buttons for navigation is displayed. 14 | 3. Visitor clicks on a button for the second special offer. 15 | 4. The second offer is displayed to the visitor. 16 | 5. Visitor clicks on a button for the third special offer. 17 | 6. The third offer is displayed to the visitor. 18 | 19 | 20 | Postconditions : 21 | None 22 | 23 | Alternative Flow: 24 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/02- Use Case 138-Display top featured products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 138 2 | 3 | PBI Title : Display top featured products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already chosen at least 14 featured products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with three featured products and buttons for navigation between next and previous 14 | featured products is displayed. 15 | 3. Visitor clicks on the next button. 16 | 4. Another three featured products are displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. Visitor clicks on the next button. 19 | 7. Another two featured products and a link to view all featured products is displayed. 20 | 21 | 22 | Postconditions : 23 | None 24 | 25 | Alternative Flow: 26 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/03- Use Case 28-Display top new arrival products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 28 2 | 3 | PBI Title : Display top new arrival products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added at least 14 products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with three new arrival products and buttons for navigation between next and previous 14 | new arrival products is displayed. 15 | 3. Visitor clicks on the next button. 16 | 4. Another three new arrival products are displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. Visitor clicks on the next button. 19 | 7. Another two new arrival products and a link to view all new arrival products is displayed. 20 | 21 | 22 | Postconditions : 23 | None 24 | 25 | Alternative Flow: 26 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/04- Use Case 120-Display top hot sale products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 120 2 | 3 | PBI Title : Display top hot sale products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added at least four products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with one hot sale product and buttons for navigation between 14 | next and previous hot sale products is displayed. 15 | 3. Visitor clicks on the next button. 16 | 4. Another hot sale product is displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. A link to view all hot sale products is displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/05- Use Case 119-Display top best selling products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 119 2 | 3 | PBI Title : Display top best selling products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added at least four products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with one best selling product and buttons for navigation between 14 | next and previous best selling products is displayed. 15 | 3. Visitor clicks on the next button. 16 | 4. Another best selling product is displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. A link to view all best selling products is displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/06- Use Case 121-Display random products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 121 2 | 3 | PBI Title : Display random products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added at least four products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with one random product and buttons for navigation between 14 | next and previous random products is displayed. 15 | 3. Visitor clicks on the next button. 16 | 4. Another random product is displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. A link to view all products is displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/07- Use Case 145-Display all main and sub categories of products.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 145 2 | 3 | PBI Title : Display all main and sub categories of products 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one main category and at least one sub category are added by an admin. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A navigation panel shows the list of main categories is displayed. 14 | 3. Each main category has an icon and an arrow to expand it. 15 | 4. Visitor clicks on a specific main category. 16 | 5. The sub categories list for the selected main category expands under its main category. 17 | 18 | 19 | Postconditions : 20 | None 21 | 22 | Alternative Flow: 23 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/08- Use Case 139-Display products of a selected category.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 139 2 | 3 | PBI Title : Display products of a selected category 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one product is added and assigned to a specific category 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page and clicks on a specific sub category. 13 | 2. A page with products under the specified sub category is displayed. 14 | 3. The page shows first 20 product from the selected sub category. 15 | 4. There is also a paging area where visitor can navigate between 16 | different pages which displays the rest of the products. 17 | 18 | 19 | Postconditions : 20 | None 21 | 22 | Alternative Flow: 23 | 3.1 The number of products per page is set to 30 24 | if the settings were modified to show 30 products per page, then 25 | 3.1.1 The page will show 30 products instead of 20. 26 | 3.1.2 The use case resumes at step 4. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/09- Use Case 2116-Provide paging for product lists.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2116 2 | 3 | PBI Title : Provide paging for product lists 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. At least 81 products was added by vendors. 10 | 11 | 12 | Basic Flow (Happy Path): 13 | 1. Visitor navigates to the home page and clicks on view all link from the new arrivals slider. 14 | 2. A page shows first 20 new arrivals products is displayed. 15 | 3. The page has a paging area where visitor can navigate between different pages which shows 16 | the rest of the products. 17 | 4. The paging area shows buttons to navigate to the previous and next pages. 18 | 5. The current page button is disabled. 19 | 6. The visitor clicks on the second page button. 20 | 7. The list is updated with other products. 21 | 8. The previous page button is now enabled. 22 | 9. The current page button is disabled. 23 | 24 | 25 | Postconditions : 26 | None. 27 | 28 | 29 | Alternative Flow: 30 | 2.1 The number of products per page is set to 30 31 | if the settings were modified to show 30 products per page, then 32 | 2.1.1 The page will show 30 products instead of 20. 33 | 2.1.2 The use case resumes at step 4. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/10- Use Case 37-Access shopping cart from the home page.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 37 2 | 3 | PBI Title : Access shopping cart from the home page 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one product was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. Visitor hovers on the shopping cart icon. 14 | 3. A floating dialog shows a summary of the shopping cart is displayed. 15 | 4. The dialog shows for each product its price, image and link to remove it, also 16 | it shows the total price, a link to view the shopping cart in details and a link to checkout. 17 | 5. User hovers out of the dialog to hide it. 18 | 6. The dialog disappears. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/11- Use Case 41-Display product detailed information.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 41 2 | 3 | PBI Title : Display product detailed information 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one product was added by a vendor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. Visitor clicks on a specific product from featured products slider. 14 | 3. Another page for viewing the product is displayed. 15 | 4. The page shows all information for the specified product, which are price, image, 16 | title, description, discount, stock availability, key features, and a fully detailed 17 | specifications. 18 | 5. An add to cart button is also displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/12- Use Case 75-Add product to the shopping cart.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 75 2 | 3 | PBI Title : Add selected product to the shopping cart 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one product was added by a vendor. 10 | 11 | 12 | Basic Flow (Happy Path): 13 | 1. Visitor navigates to the home page. 14 | 2. Visitor clicks on "Add to cart" button for a specific product from featured products slider. 15 | 3. The product is added to the visitor's shopping cart. 16 | 4. A notification pane shows that the specified product was added is displayed for three seconds. 17 | 5. Visitor clicks again on the "Add to cart" button for the specified product. 18 | 6. One more item of the product is added to the shopping cart. 19 | 7. A notification pane shows that the specified product was added is displayed for three seconds. 20 | 21 | 22 | Postconditions : 23 | 1. Two items of the same product are added to the shopping cart. 24 | 25 | 26 | Alternative Flow: 27 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/13- Use Case 141-Remove product from shopping cart.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 141 2 | 3 | PBI Title : Remove product from shopping cart 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one item was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page and hovers on his shopping cart. 13 | 2. A product is displayed in the shopping cart with one item of it. 14 | 2. Visitor clicks on the remove icon next to the specified product. 15 | 3. The product is removed from the shopping cart. 16 | 17 | 18 | Postconditions : 19 | 1. The shopping cart total price and quantity are updated. 20 | 21 | 22 | Alternative Flow: 23 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/14- Use Case 57-Review products in shopping cart.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 57 2 | 3 | PBI Title : Review products in shopping cart 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one item was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor hovers on the shopping cart and clicks on a button to view the shopping cart. 13 | 2. The shopping cart page is displayed, showing the first 20 items in rows. 14 | 3. Each row shows a Product Image, Product Name, Quantity, Total Price and a link to remove it. 15 | 4. The page also has a checkout and continue shopping buttons. 16 | 5. There is a paging area where visitor can navigate between different pages which displays 17 | the rest of the items. 18 | 6. Visitor clicks on the continue shopping button. 19 | 7. The visitor is returned to the previous page. 20 | 21 | 22 | Postconditions : 23 | None 24 | 25 | Alternative Flow: 26 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/15- Use Case 58-Add delivery address for the order.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 58 2 | 3 | PBI Title : Add delivery address for the order 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one item was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to his shopping cart and clicks on the checkout button. 13 | 2. A page shows input fields for visitor's info, which is First name, Last name, 14 | Email, Phone, City, State name, Postal code, Country name and address is displayed. 15 | 3. The page also shows buttons to get back to the shopping cart and to checkout. 16 | 4. The visitor adds the details and clicks on the checkout button. 17 | 5. The visitor details are validated. 18 | 6. The visitor is navigated to review order page. 19 | 20 | 21 | Postconditions : 22 | 1. The visitor's information is now saved with the order information. 23 | 24 | 25 | Alternative Flow: 26 | 5.1 Invalide postal code 27 | if the postal code is invalid, then 28 | 5.1.1 An error message will show to the visitor indicating that the postal code is invalid. 29 | 5.1.2 The use case resumes at step 2. 30 | 31 | 5.2 Invalid address 32 | if the address provided is invalid, then 33 | 5.2.1 An error message will show to the visitor indicating that the address is invalid. 34 | 5.2.2 The use case resumes at step 2. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/16- Use Case 59-Review order before checkout.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 59 2 | 3 | PBI Title : Review order before checkout 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one item was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to his shopping cart, confirms his information and clicks on review order. 13 | 2. The order review page shows the total price, gift wrap information, and a list of all 14 | ordered items into rows. 15 | 3. Each row shows a Product Image, Title, Quantity, Price and an icon to remove it. 16 | 4. The visitor's personal information is shown, which is First Name, Last Name, Email, Phone, 17 | City, State, Postal Code, Country and Address. 18 | 5. The page shows a button to edit the address and other personal information, a button to 19 | continue shopping and a button to continue the checkout. 20 | 21 | 22 | 23 | Postconditions : 24 | None 25 | 26 | Alternative Flow: 27 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/17- Use Case 147-Place order after review as member.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 147 2 | 3 | PBI Title : Place order after review as member 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member has been logged successfully to his account. 10 | 2. Member has already added at least one item into his shopping cart. 11 | 12 | 13 | Basic Flow (Happy Path): 14 | 1. Member clicks on "Checkout" button after reviewing his order. 15 | 2. The address confirmation page shows Default address and two buttons for Use 16 | Default Address and Use Another Address is displayed. 17 | 3. The Member clicks on the Use Default Address option. 18 | 4. The checkout page shows the current payment information as hiddent text and 19 | buttons for Use Default Payment Method and Use Another Payment Method is displayed. 20 | 5. Member clicks on Use Default Payment Method option. 21 | 6. A confirmation email is sent to the member with shipping details and order details. 22 | 23 | 24 | Postconditions : 25 | 1. The Application is updated with the order information. 26 | 27 | Alternative Flow: 28 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/18- Use Case 155-Place order after review as guest.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 155 2 | 3 | PBI Title : Place order after review as guest 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At least one item was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor clicks on "Checkout" button after reviewing the order and adding his address. 13 | 2. The checkout page shows input fields for payment information and a button place order 14 | button is displayed. 15 | 3. The visitor adds the required details. 16 | 4. The visitor clicks on the place order button. 17 | 5. The payment information is validated. 18 | 6. An email is sent to the visitor with shipping details and order details. 19 | 7. The visitor is registered as a member without a password. 20 | 21 | 22 | Postconditions : 23 | 1. The Application is updated with the order information. 24 | 2. The Application is updated with member information. 25 | 26 | Alternative Flow: 27 | 28 | 5.1 Invalid payment details 29 | if the payment information is invalid, then 30 | 5.1.1. An error message will show to the visitor indicating that the 31 | payment information is invalid. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/19- Use Case 142-Display all order made by visitors and members.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 142 2 | 3 | PBI Title : Display all order made by visitors and memebrs 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. At least one order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to the vendor panel. 14 | 2. Vendor clicks on list all orders link. 15 | 3. The list all orders page is displayed, showing the first 20 offers in rows ordered by recent order date. 16 | 4. Each row shows an Order Id, Order Date, Order Status, Total Product in order, Total Price and Username 17 | which made the order. 18 | 5. The Order Id is also a link to view order details, the Order Status is a list with possible order status 19 | and the username is also a link to view member profile. 20 | 6. There is a paging area where vendor can navigate between different pages which displayes the rest of the 21 | orders. 22 | 7. The list can be filtered by date range or username using a date range selectors, a search box and a search 23 | button repectively. 24 | 8. Vendor clicks on the date range selectors. 25 | 9. Two Date selectors are displayed, the feature dates are disabled. 26 | 10. Vendor enters two specific dates. 27 | 11. Vendor clicks on the search button. 28 | 12. The vendor input is being validated. 29 | 13. The list is updated with orders made in the selected date range. 30 | 31 | 32 | Postconditions : 33 | None 34 | 35 | Alternative Flow: 36 | 37 | 3.1 The number of orders per page is set to 30 38 | if the settings were modified to show 30 order per page, then 39 | 3.1.1. The list will show 30 order, and the use case continue. 40 | 3.1.2 The use case resumes at step 4. 41 | 42 | 12.1 No orders for the selected dates 43 | if the selected dates doesn't contain any orders, then 44 | 12.1.1. The list content is replaced with a message indicating that no items were found. 45 | 12.1.2 The use case ends. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/20- Use Case 143-Update completed order.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 143 2 | 3 | PBI Title : Update completed order 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. At least one order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor clicks on a specific order from list all orders page. 14 | 2. A page shows order details which is the Quantity of products in order, Price of each 15 | product in order, Total price for products in order, Order Status and Gift wrap option 16 | for order is displayed. 17 | 3. The member's personal information which is First name, Last name, Email, Phone, City, 18 | State, Postal code, Country and Address of shipping details is also displayed. 19 | 4. The vendor clicks on the member's personal information area. 20 | 5. A dialog shows the member's personal information into input fields and a save button 21 | is displayed. 22 | 6. The vendor corrects a spelling mistake in the member's first name field. 23 | 7. The vendor clicks on the save button. 24 | 8. The member information is validated. 25 | 9. The dialog disappears. 26 | 27 | 28 | Postconditions : 29 | 1. The order information is updated. 30 | 31 | Alternative Flow: 32 | 8.1 Invalid first name 33 | if vendor provides an invalid first name, then 34 | 8.1.1. An error message shows to indicate that the first name provided 35 | is invalid. 36 | 8.1.2 The use case resumes at step 5. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/21- Use Case 63-Display orders history for members.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 63 2 | 3 | PBI Title : Display orders history for members 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member has been logged in to his account. 10 | 2. At least one order was made by the member. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Member navigates to the home page. 14 | 2. Member clicks on order history link under his account list. 15 | 3. The orders list page shows the first 20 orders in rows ordered by recent order date is displayed. 16 | 4. Each row shows an Order Id, Order Date Total Price and a details link. 17 | 5. There is also a paging area where member can navigate between different pages which displays the rest of the orders. 18 | 6. Member clicks on the details link for a specific order. 19 | 7. The row for the specified order expands and displays a list of all items in the order in rows. 20 | 8. Each row shows item quantity, total price and an image. 21 | 22 | 23 | Postconditions : 24 | None 25 | 26 | Alternative Flow: 27 | 3.1 The number of orders per page is set to 30 28 | if the settings were modified to show 30 orders per page, then 29 | 3.1.1. The list will show 30 orders instead of 20. 30 | 3.1.2 The use case resumes at step 4. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/22- Use Case 5-Provide membership for visitors.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 5 2 | 3 | PBI Title : Provide membership for visitors 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | None 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. Visitor clicks on the Sign In link. 14 | 3. Visitor is redirected to the login page. 15 | 4. Visitor clicks on Create Account link from the login page. 16 | 5. The registeration page shows input fields for First name, Last name, Email, Phone, Username, 17 | Age, Gender, Password, Password confirmation, City, State name, Postal code, Country name and 18 | Address is displayed. 19 | 6. The page has a Sign Up button. 20 | 7. The visitor enters the required information. 21 | 8. The visitor clicks on the Sign Up button. 22 | 9. The visitor details is validated. 23 | 10. The system sends a welcome email to the user. 24 | 11. Member is redirected to account page. 25 | 26 | 27 | Postconditions : 28 | 1. The member account is created. 29 | 2. The member is automatically logged in after registeration. 30 | 31 | Alternative Flow: 32 | 9.1 Invalid Email address 33 | if the email provided is invalid, then 34 | 9.1.1. An error message will show to the visitor indicating that the email is 35 | invalid. 36 | 9.1.2. The use case resumes at step 5. 37 | 9.2 Invallid phone number 38 | if the phone number provided is invalid, then 39 | 9.2.1. An error message will show to the visitor indicating that the phone number 40 | is invalid. 41 | 9.2.2 The use case resumes at step 5. 42 | 9.3 Password is too short 43 | if the phone number provided is invalid, then 44 | 9.3.1. An error message will show to the visitor indicating that the password 45 | is too short and the the minimum length is 6 characters. 46 | 9.3.2 The use case resumes at step 5. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/23- Use Case 146-Login to the member site.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 146 2 | 3 | PBI Title : Login to the member site 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member account already exists. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Member navigates to the home page. 13 | 2. Member clicks on the Sign In link. 14 | 3. The login page shows username and password input fields, a Remember Me checkbox, 15 | a Reset Password link and a Create Account link is displayed. 16 | 4. Member enters his username and his password. 17 | 5. Member checks the Remember me button. 18 | 6. Member clicks on the login button. 19 | 7. The member credentials are validated. 20 | 8. Member is redirected to his profile. 21 | 22 | 23 | Postconditions : 24 | 1. The member has been logged in successfully. 25 | 2. Member is kept logged in, so for his next visit to the site he won't need to re-enter 26 | his username and password. 27 | 28 | 29 | Alternative Flow: 30 | 7.1 Invalid Username or Password 31 | if the username or password provided by the member is invalid, then 32 | 7.1.1. An error message will show indicating that the username or 33 | password is invalid. 34 | 7.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/24- Use Case 271-Login to the vendor panel.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 271 2 | 3 | PBI Title : Login to the vendor panel 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor account already exists. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Vendor navigates to the home page. 13 | 2. Vendor clicks on the Sign In link. 14 | 3. The login page shows username and password input fields, a Remember Me checkbox, 15 | a Reset Password link and a Create Account link is displayed. 16 | 4. Vendor enters his username and his password. 17 | 5. Vendor checks the Remember me button. 18 | 6. Vendor clicks on the login button. 19 | 7. The Vendor credentials are validated. 20 | 8. Vendor is redirected to vendor panel. 21 | 22 | 23 | Postconditions : 24 | 1. The Vendor has been logged in successfully. 25 | 2. Vendor is kept logged in, so for his next visit to the site he won't need to re-enter 26 | his username and password. 27 | 28 | 29 | Alternative Flow: 30 | 7.1 Invalid Username or Password 31 | if the username or password provided by the Vendor is invalid, then 32 | 7.1.1. An error message will show indicating that the username or 33 | password is invalid. 34 | 7.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/25- Use Case 89-Login to the admin panel.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 89 2 | 3 | PBI Title : Login to the admin panel 4 | 5 | Primary Actors : 6 | 1. Admin 7 | 8 | Preconditions : 9 | 1. Admin account already exists. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Admin navigates to the home page. 13 | 2. Admin clicks on the Sign In link. 14 | 3. The login page shows username and password input fields, a Remember Me checkbox, 15 | a Reset Password link and a Create Account link is displayed. 16 | 4. Admin enters his username and his password. 17 | 5. Admin checks the Remember me button. 18 | 6. Admin clicks on the login button. 19 | 7. The Admin credentials are validated. 20 | 8. Admin is redirected to Admin panel. 21 | 22 | 23 | Postconditions : 24 | 1. The Admin has been logged in successfully. 25 | 2. Admin is kept logged in, so for his next visit to the site he won't need to re-enter 26 | his username and password. 27 | 28 | 29 | Alternative Flow: 30 | 7.1 Invalid Username or Password 31 | if the username or password provided by the Admin is invalid, then 32 | 7.1.1. An error message will show indicating that the username or 33 | password is invalid. 34 | 7.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/26- Use Case 96-Add product to the store.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 96 2 | 3 | PBI Title : Add product to the store 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Vendor navigates to the vendor panel. 13 | 2. Vendor clicks on the add product link. 14 | 3. The add product page shows input for product details which is Code, Title, Description, 15 | Category Name, Brand, Price, Specifications, Key features, Image, also some optional 16 | information such as sub category, discount and flag for featured product is displayed. 17 | 4. The page has a disabled save button. 18 | 5. Vendor enters the product information. 19 | 6. The save button is enabled. 20 | 7. Vendor clicks on the save button. 21 | 8. The product details are validated. 22 | 9. The button is disabled again, indicating that the product was saved. 23 | 24 | 25 | Postconditions : 26 | 1. The product is visible to members and visitors. 27 | 28 | Alternative Flow: 29 | 8.1 Price contains a currency symbol 30 | if vendor provides a price with a currency sybmol, then 31 | 8.1.1. An error message shows to indicate that the price 32 | provided is invalid. 33 | 8.1.2 The use case resumes at step 3. 34 | 8.2 No category assigned 35 | if vendor doesn't provide a specific product category, then 36 | 8.2.1. An error message will show indicating that the 37 | category is required for the product. 38 | 8.2.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/27- Use Case 92-Display all added products.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 92 2 | 3 | PBI Title : Display all added products 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. At least one product was already added by the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to vendor panel. 14 | 2. Vendor clicks on list all products link. 15 | 3. The product list page is displayed, showing the first 20 products in rows ordered 16 | by product title. 17 | 4. Each row shows a single product details, which is Product Id, Title, Price and a 18 | delete icon. 19 | 5. The product title is also a link to view and update product details. 20 | 6. There is a paging area where vendor can navigate between different pages which 21 | displayes the rest of the products. 22 | 23 | 24 | Postconditions : 25 | None 26 | 27 | Alternative Flow: 28 | 3.1 The number of products per page is set to 30 29 | if the settings were modified to show 30 products per page, then 30 | 3.1.1. The list will show 30 products instead of 20. 31 | 3.1.2 The use case resumes at step 4. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/28- Use Case 93-Update product data.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 93 2 | 3 | PBI Title : Update product data 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. At least one product was already added by the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to vendor panel. 14 | 2. Vendor clicks on a specific product title from list all products page. 15 | 3. The page shows input fields for product details which is Code, Title, 16 | Description, Category Name, Brand, Price, Specifications, Key features, 17 | Image, sub category and a flag for featured product is displayed. 18 | 4. All of the input fields are filled with the current product details. 19 | 5. The page has a disabled update button. 20 | 6. Vendor updates product title and price. 21 | 7. The update button is active. 22 | 8. Vendor clicks on the update button. 23 | 9. The product details are validated. 24 | 10. The update button is disabled again, indicating that 25 | the product details were updated. 26 | 27 | Postconditions : 28 | 1. The product details are updated. 29 | 2. The update is reflected to members and visitors. 30 | 31 | Alternative Flow: 32 | 9.1 New price contains a currency symbol 33 | if vendor provides a new price with a currency sybmol, then 34 | 9.1.1 An error message shows to indicate that the price provided is invalid. 35 | 9.1.2 The use case resumes at step 3. 36 | 37 | 9.2 Empty title 38 | if vendor removed the product title, then 39 | 9.2.1 An error message will show indicating that the title is required for the product. 40 | 9.2.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/29- Use Case 2071-Display all orders made by all users for all vendors.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2071 2 | 3 | PBI Title : Display all orders made by all users for all vendors 4 | 5 | Primary Actors : 6 | 1. Admin 7 | 8 | Preconditions : 9 | 1. Admin has been logged in to his account. 10 | 2. Admin has been authorized to list all orders. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Admin navigates to admin panel. 14 | 2. Admin clicks on list all orders link. 15 | 3. The list all orders page is displayed, showing the first 20 offers in rows ordered 16 | by recent order date. 17 | 4. Each row shows an Order Id, Order Date, Order Status, Total Products in order, 18 | Total Price, Username of the member who made the order and vendor name who will 19 | provide the order. 20 | 5. The Order Id is also a link to view order details, the Order Status is a list with 21 | possible order status, the vendor name and member username is also links to view vendor 22 | profile and member profile respectively. 23 | 6. There is a paging area where admin can navigate between different pages which displayes 24 | the rest of the orders. 25 | 7. The list can be filtered by date range, vendor name or username using a date range 26 | selectors, two search boxes and a search button respectively. 27 | 8. Admin enters few letters of a specific vendor name in the filter by vendor name field. 28 | 9. A list of vendor names that contains letters entered by admin shows in the filter by vendor name field. 29 | 10. Admin clicks on a specific vendor name from the list. 30 | 11. The filter by vendor name field is filled with the selected vendor. 31 | 12. Admin clicks on the search box. 32 | 13. The list is updated with only orders made for the specified vendor. 33 | 34 | 35 | Postconditions : 36 | None 37 | 38 | Alternative Flow: 39 | 3.1 The number of orders per page is set to 30 40 | if the settings were modified to show 30 order per page, then 41 | 3.1.1. The list will show 30 order. 42 | 3.1.2. The use case resumes at step 4. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/30- Use Case 2119-Update order status.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2119 2 | 3 | PBI Title : Update order status 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. At least one order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to list all orders page. 14 | 2. The list all orders page is displayed. 15 | 3. The page has a disabled save button. 16 | 4. The vendor clicks on the Order status for a specific order, and changes it to completed. 17 | 5. The save buttons is available indicating that there changes to be saved. 18 | 6. The vendor clicks on the save button. 19 | 7. The save button is disabled again. 20 | 21 | 22 | Postconditions : 23 | 1. The order status is updated in the application. 24 | 25 | Alternative Flow: 26 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/31- Use Case 2118-Display order detailed information.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2118 2 | 3 | PBI Title : Display order detailed information 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. At least one order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to vendor panel. 14 | 2. Vendor clicks on a specific order Id from list all orders page. 15 | 3. Another page for viewing order details is displayed. 16 | 4. The page shows Member's personal information, which is First Name, Last Name, 17 | Email, Phone, City, State, Postal Code, Country and Delivery Address. 18 | 5. The page also shows the order infromation, which is Order Id, Order Date, Order 19 | Status, Total Product in order, Total Price, Username of user who made the order. 20 | 6. The page also displayes each ordered product details, which is Image, Title, 21 | Quantity, Price, Total amount and Gift Wrap option. 22 | 7. Vendor clicks on the quantity for a specific product. 23 | 8. The quanitity value becomes an input field, filled with the current quantity, but 24 | can be changed. 25 | 26 | 27 | Postconditions : 28 | None 29 | 30 | Alternative Flow: 31 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/32- Use Case 90-Recover forgotten password.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 90 2 | 3 | PBI Title : Recover forgotten password 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | None 10 | 11 | Basic Flow (Happy Path): 12 | 1. Member navigates to the sign in page. 13 | 2. Member clicks on the forgot password option. 14 | 3. A page is displayed with input field for member's email account and button for submission. 15 | 4. Member enters his email account and clicks on the submit button. 16 | 5. Email account is being validated. 17 | 6. An email is sent to the provided email with a link to reset password. 18 | 7. Member clicks on the link in his email. 19 | 8. Another page for the new password is displayed, with input fields for the new password and 20 | password confirmation and a submit button. 21 | 9. Member enters the new password and its confirmation and clicks on the submit button. 22 | 10.The new password is validated. 23 | 11.Member is logged in automatically to his account using the new password. 24 | 25 | 26 | Postconditions : 27 | 1. Password is updated in the application. 28 | 2. Member is logged in using his new password automatically. 29 | 30 | Alternative Flow: 31 | 5.1 Email doesn't exist. 32 | if member provides an email which doesn't exist in the application, then 33 | 5.1.1 An error message will show to indicate that the email doesn't exist. 34 | 5.1.2 The use case resumes at step 3. 35 | 36 | 10.1 Short password 37 | if Member provides a short password, then 38 | 10.1.1 An error message will show to indicate that the password is too short. 39 | 10.1.2 The use case resumes at step 8. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/33- Use Case 18-Change password.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 33 2 | 3 | PBI Title : Change password 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member has been logged in to his account. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Member navigates to his account page. 13 | 2. Member clicks on the Change Password option. 14 | 3. Another page is displayed, with input fields for the current password, new password 15 | and new password confirmation. 16 | 4. Member enters the required his old password, his new password and his new password confirmation. 17 | 5. Member's input is validated. 18 | 6. A confirmation message is displayed to indicate password has been changed successfully. 19 | 20 | Postconditions : 21 | 1. The Member password is updated in the application. 22 | 23 | Alternative Flow: 24 | 5.1 Old password is incorrect 25 | if Member provides an incorrect old password, then 26 | 5.1.1 An error message will show to indicate that the old password is incorrect. 27 | 5.1.2 The use case resumes at step 3. 28 | 29 | 5.2 New password is too short. 30 | if Member provides a short new password, then 31 | 5.2.1 An error message will show to indicate that the new password is too short. 32 | 5.2.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Detailed Use Case Scenarios (Text)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/01- Use Case 161-Display special offer products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 161 2 | 3 | PBI Title : Display special offer products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Products was chosen by an admin to be displayed in the slider. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider shows the first offer with navigation support is displayed. 14 | 3. Visitor navigates to the second offer. 15 | 4. The second offer is displayed to the visitor. 16 | 5. Visitor navigates to the third offer. 17 | 6. The third offer is displayed to the visitor. 18 | 19 | 20 | Postconditions : 21 | None 22 | 23 | Alternative Flow: 24 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/02- Use Case 138-Display top featured products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 138 2 | 3 | PBI Title : Display top featured products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already chosen some featured products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with featured products and navigation support between featured products is 14 | displayed. 15 | 3. Visitor navigates to the next featured products. 16 | 4. Other featured products are displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. Visitor clicks on the next button. 19 | 7. Other featured products and a link to view all featured products is displayed. 20 | 21 | 22 | Postconditions : 23 | None 24 | 25 | Alternative Flow: 26 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/03- Use Case 28-Display top new arrival products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 28 2 | 3 | PBI Title : Display top new arrival products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added some products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with new arrival products and navigation support between new arrival products is 14 | displayed. 15 | 3. Visitor navigates to the next new arrival products. 16 | 4. Other new arrival products are displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. Visitor clicks on the next button. 19 | 7. Other new arrival products and a link to view all new arrival products is displayed. 20 | 21 | 22 | Postconditions : 23 | None 24 | 25 | Alternative Flow: 26 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/04- Use Case 120-Display top hot sale products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 120 2 | 3 | PBI Title : Display top hot sale products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added some products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with a hot sale product and navigation support between hot sale products 14 | is displayed. 15 | 3. Visitor navigates to the next hot sale product. 16 | 4. Another hot sale product is displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. A link to view all hot sale products is displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/05- Use Case 119-Display top best selling products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 119 2 | 3 | PBI Title : Display top best selling products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added some products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with a best selling product and navigation support between best selling products 14 | is displayed. 15 | 3. Visitor navigates to the next best selling product. 16 | 4. Another best selling product is displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. A link to view all best selling products is displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/06- Use Case 121-Display random products in a slider.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 121 2 | 3 | PBI Title : Display random products in a slider 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Vendors have already added some products. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. A slider with a random product and navigation support between random products is 14 | displayed. 15 | 3. Visitor navigates to the next random product. 16 | 4. Another random product is displayed. 17 | 5. Repeat step 3 and step 4 for three times. 18 | 6. A link to view all products is displayed. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/07- Use Case 145-Display all main and sub categories of products.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 145 2 | 3 | PBI Title : Display all main and sub categories of products 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. Categories was added by an admin. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. The list of main categories is displayed. 14 | 3. Visitor clicks on a specific main category. 15 | 4. The sub categories list for the selected main category is displayed. 16 | 17 | 18 | Postconditions : 19 | None 20 | 21 | Alternative Flow: 22 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/08- Use Case 139-Display products of a selected category.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 139 2 | 3 | PBI Title : Display products of a selected category 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A category was assigned to an existing product. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page and clicks on a specific sub category. 13 | 2. A page with products under the specified sub category is displayed. 14 | 3. The page shows product from the selected sub category. 15 | 4. There is a paging support to navigate between different pages of products. 16 | 17 | 18 | Postconditions : 19 | None 20 | 21 | Alternative Flow: 22 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/09- Use Case 2116-Provide paging for product lists.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2116 2 | 3 | PBI Title : Provide paging for product lists 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Some products was added by vendors. 10 | 11 | 12 | Basic Flow (Happy Path): 13 | 1. Visitor navigates to the home page and clicks on view all link from the new arrivals slider. 14 | 2. A page shows new arrivals products is displayed. 15 | 3. There is a paging support to navigate between different pages of products. 16 | 4. The paging area shows options to navigate to the previous and next pages. 17 | 5. The current page option is disabled. 18 | 6. The visitor clicks on the second page option. 19 | 7. The list is updated with other products. 20 | 8. The previous page option is now enabled. 21 | 9. The current page option is disabled. 22 | 23 | 24 | Postconditions : 25 | None 26 | 27 | 28 | Alternative Flow: 29 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/10- Use Case 37-Access shopping cart from the home page.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 37 2 | 3 | PBI Title : Access shopping cart from the home page 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. Visitor hovers on the shopping cart icon. 14 | 3. A dialog shows a summary of the shopping cart is displayed. 15 | 4. The dialog shows each product information and controls also 16 | it shows the total price, a link to view the shopping cart in details and a link to checkout. 17 | 5. User hovers out of the dialog to hide it. 18 | 6. The dialog disappears. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/11- Use Case 41-Display product detailed information.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 41 2 | 3 | PBI Title : Display product detailed information 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added by a vendor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. Visitor clicks on a specific product. 14 | 3. Another page for viewing the product is displayed. 15 | 4. The page shows all information for the specified product. 16 | 5. An add to cart option is also displayed. 17 | 18 | 19 | Postconditions : 20 | None 21 | 22 | Alternative Flow: 23 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/12- Use Case 75-Add product to the shopping cart.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 75 2 | 3 | PBI Title : Add selected product to the shopping cart 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added by a vendor. 10 | 11 | 12 | Basic Flow (Happy Path): 13 | 1. Visitor navigates to the home page. 14 | 2. Visitor clicks on "Add to cart" option for a specific product. 15 | 3. The product is added to the visitor's shopping cart. 16 | 4. A notification shows that the specified product was added is displayed. 17 | 18 | 19 | Postconditions : 20 | 1. Product is added to the shopping cart. 21 | 22 | 23 | Alternative Flow: 24 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/13- Use Case 141-Remove product from shopping cart.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 141 2 | 3 | PBI Title : Remove product from shopping cart 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page and hovers on his shopping cart. 13 | 2. A product is displayed in the shopping cart. 14 | 2. Visitor clicks on the remove icon next to the specified product. 15 | 3. The product is removed from the shopping cart. 16 | 17 | 18 | Postconditions : 19 | 1. The Shopping cart is updated. 20 | 21 | 22 | Alternative Flow: 23 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/14- Use Case 57-Review products in shopping cart.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 57 2 | 3 | PBI Title : Review products in shopping cart 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor hovers on the shopping cart and clicks on the option to view the shopping cart. 13 | 2. The shopping cart page is displayed, showing the added items in rows. 14 | 3. Each row shows a Product information, Total Price and an option to remove it. 15 | 4. The page also has a checkout and continue shopping options. 16 | 5. There is a paging support to navigate between different pages of items. 17 | 6. Visitor clicks on the continue shopping option. 18 | 7. The visitor is returned to the previous page. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/15- Use Case 58-Add delivery address for the order.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 58 2 | 3 | PBI Title : Add delivery address for the order 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to his shopping cart and clicks on the checkout option. 13 | 2. A page shows input fields for visitor's address and information is displayed. 14 | 3. The page also shows options to get back to the shopping cart and to checkout. 15 | 4. The visitor adds the details and clicks on the checkout option. 16 | 5. The visitor details are validated. 17 | 6. The visitor is navigated to review order page. 18 | 19 | 20 | Postconditions : 21 | 1. The visitor's information is updated. 22 | 23 | 24 | Alternative Flow: 25 | 5.1 Invalide postal code 26 | if the postal code is invalid, then 27 | 5.1.1 An error message will show to the visitor indicating that the postal code is invalid. 28 | 5.1.2 The use case resumes at step 2. 29 | 30 | 5.2 Invalid address 31 | if the address provided is invalid, then 32 | 5.2.1 An error message will show to the visitor indicating that the address is invalid. 33 | 5.2.2 The use case resumes at step 2. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/16- Use Case 59-Review order before checkout.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 59 2 | 3 | PBI Title : Review order before checkout 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. A product was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to his shopping cart, confirms his information and clicks on review order option. 13 | 2. The order review page shows the items ordered in rows and shopping cart information is displayed. 14 | 3. Each row shows a Product information and controls. 15 | 4. The visitor's personal information is also displayed. 16 | 5. The page shows an option to edit the address and other personal information, an option to 17 | continue shopping and an option to continue the checkout. 18 | 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/17- Use Case 147-Place order after review as member.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 147 2 | 3 | PBI Title : Place order after review as member 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member has been logged successfully to his account. 10 | 2. Member has already added an item to his shopping cart. 11 | 12 | 13 | Basic Flow (Happy Path): 14 | 1. Member clicks on the checkout option after reviewing his order. 15 | 2. The address confirmation page shows Default address and options for Use 16 | Default Address and Use Another Address is displayed. 17 | 3. The Member clicks on the Use Default Address option. 18 | 4. The checkout page shows the current payment information and options 19 | for Use Default Payment Method and Use Another Payment Method is displayed. 20 | 5. Member clicks on Use Default Payment Method option. 21 | 6. A confirmation email is sent to the member with shipping details and order details. 22 | 23 | 24 | Postconditions : 25 | 1. The Application is updated with the order information. 26 | 27 | Alternative Flow: 28 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/18- Use Case 155-Place order after review as guest.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 155 2 | 3 | PBI Title : Place order after review as guest 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | 1. At product was added to the shopping cart by the visitor. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor clicks on the checkout option after reviewing the order and adding his address. 13 | 2. The checkout page shows input fields for payment information and an option to place order 14 | is displayed. 15 | 3. The visitor adds the required details. 16 | 4. The visitor clicks on the place order option. 17 | 5. The payment information is validated. 18 | 6. An email is sent to the visitor with shipping details and order details. 19 | 7. The visitor is registered as a member without a password. 20 | 21 | 22 | Postconditions : 23 | 1. The Application is updated with the order information. 24 | 2. The Application is updated with member information. 25 | 26 | Alternative Flow: 27 | 28 | 5.1 Invalid payment details 29 | if the payment information is invalid, then 30 | 5.1.1. An error message will show to the visitor indicating that the 31 | payment information is invalid. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/19- Use Case 142-Display all order made by visitors and members.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 142 2 | 3 | PBI Title : Display all order made by visitors and memebrs 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. An order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to the vendor panel. 14 | 2. Vendor clicks on list all orders link. 15 | 3. The list all orders page is displayed, showing offers in rows. 16 | 4. Each row shows an Order Information. 17 | 5. There is a paging support to navigate between different pages of orders. 18 | 6. The list can be filtered using some order information. 19 | 7. Vendor filters the list using order dates range. 20 | 8. The vendor input is being validated. 21 | 9. The list is updated with orders made in the selected date range. 22 | 23 | 24 | Postconditions : 25 | None 26 | 27 | Alternative Flow: 28 | 29 | 8.1 No orders for the selected dates 30 | if the selected dates doesn't contain any orders, then 31 | 8.1.1. The list content is replaced with a message indicating that no items were found. 32 | 8.1.2 The use case ends. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/20- Use Case 143-Update completed order.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 143 2 | 3 | PBI Title : Update completed order 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. An order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor clicks on a specific order from list all orders page. 14 | 2. A page shows order details is displayed. 15 | 3. The member's personal information which is also displayed. 16 | 4. The vendor clicks on the member's personal information area. 17 | 5. A dialog shows the member's personal information into input fields and a save option 18 | is displayed. 19 | 6. The vendor corrects a spelling mistake in the member's first name field. 20 | 7. The vendor clicks on the save option. 21 | 8. The member information is validated. 22 | 9. The dialog disappears. 23 | 24 | 25 | Postconditions : 26 | 1. The order information is updated. 27 | 28 | Alternative Flow: 29 | 8.1 Invalid first name 30 | if vendor provides an invalid first name, then 31 | 8.1.1. An error message shows to indicate that the first name provided 32 | is invalid. 33 | 8.1.2 The use case resumes at step 5. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/21- Use Case 63-Display orders history for members.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 63 2 | 3 | PBI Title : Display orders history for members 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member has been logged in to his account. 10 | 2. An order was made by the member. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Member navigates to the home page. 14 | 2. Member clicks on order history link under his account list. 15 | 3. The orders list page shows orders in rows ordered is displayed. 16 | 4. Each row shows an Order information. 17 | 5. There is a paging support to navigate between different pages of orders. 18 | 6. Member clicks on the link for a specific order. 19 | 7. The row for the specified order expands and displays a list of all items in the order in rows. 20 | 8. Each row shows a specific item information. 21 | 22 | 23 | Postconditions : 24 | None 25 | 26 | Alternative Flow: 27 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/22- Use Case 5-Provide membership for visitors.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 5 2 | 3 | PBI Title : Provide membership for visitors 4 | 5 | Primary Actors : 6 | 1. Visitor 7 | 8 | Preconditions : 9 | None 10 | 11 | Basic Flow (Happy Path): 12 | 1. Visitor navigates to the home page. 13 | 2. Visitor clicks on the Sign In link. 14 | 3. Visitor is redirected to the login page. 15 | 4. Visitor clicks on Create Account link from the login page. 16 | 5. The registeration page shows input fields for Member information. 17 | 6. The page has a Sign Up option. 18 | 7. The visitor enters the required information. 19 | 8. The visitor clicks on the Sign Up option. 20 | 9. The visitor details is validated. 21 | 10. The system sends a welcome email to the user. 22 | 11. Member is redirected to account page. 23 | 24 | 25 | Postconditions : 26 | 1. The member account is created. 27 | 2. The member is logged in. 28 | 29 | Alternative Flow: 30 | 9.1 Invalid Member information 31 | if the information provided is invalid, then 32 | 9.1.1. An error message will show to the visitor indicating that information 33 | provided are invalid. 34 | 9.1.2 The use case resumes at step 5. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/23- Use Case 146-Login to the member site.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 146 2 | 3 | PBI Title : Login to the member site 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member account already exists. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Member navigates to the home page. 13 | 2. Member clicks on the Sign In option. 14 | 3. The login page shows input fields for member credentials and remember me option. 15 | 4. Member enters his username and his password. 16 | 5. Member checks the Remember me option. 17 | 6. Member clicks on the login option. 18 | 7. The member credentials are validated. 19 | 8. Member is redirected to his profile. 20 | 21 | 22 | Postconditions : 23 | 1. The member has been logged in successfully. 24 | 2. Member is kept logged in. 25 | 26 | 27 | Alternative Flow: 28 | 7.1 Invalid credentials 29 | if the credentials provided by the member are invalid, then 30 | 7.1.1. An error message will show indicating that the credentials are 31 | invalid. 32 | 7.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/24- Use Case 271-Login to the vendor panel.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 146 2 | 3 | PBI Title : Login to the Vendor site 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor account already exists. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Vendor navigates to the home page. 13 | 2. Vendor clicks on the Sign In option. 14 | 3. The login page shows input fields for Vendor credentials and remember me option. 15 | 4. Vendor enters his username and his password. 16 | 5. Vendor checks the Remember me option. 17 | 6. Vendor clicks on the login option. 18 | 7. The Vendor credentials are validated. 19 | 8. Vendor is redirected to his profile. 20 | 21 | 22 | Postconditions : 23 | 1. The Vendor has been logged in successfully. 24 | 2. Vendor is kept logged in. 25 | 26 | 27 | Alternative Flow: 28 | 7.1 Invalid credentials 29 | if the credentials provided by the Vendor are invalid, then 30 | 7.1.1. An error message will show indicating that the credentials are 31 | invalid. 32 | 7.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/25- Use Case 89-Login to the admin panel.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 146 2 | 3 | PBI Title : Login to the Admin site 4 | 5 | Primary Actors : 6 | 1. Admin 7 | 8 | Preconditions : 9 | 1. Admin account already exists. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Admin navigates to the home page. 13 | 2. Admin clicks on the Sign In option. 14 | 3. The login page shows input fields for Admin credentials and remember me option. 15 | 4. Admin enters his username and his password. 16 | 5. Admin checks the Remember me option. 17 | 6. Admin clicks on the login option. 18 | 7. The Admin credentials are validated. 19 | 8. Admin is redirected to his profile. 20 | 21 | 22 | Postconditions : 23 | 1. The Admin has been logged in successfully. 24 | 2. Admin is kept logged in. 25 | 26 | 27 | Alternative Flow: 28 | 7.1 Invalid credentials 29 | if the credentials provided by the Admin are invalid, then 30 | 7.1.1. An error message will show indicating that the credentials are 31 | invalid. 32 | 7.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/26- Use Case 96-Add product to the store.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 96 2 | 3 | PBI Title : Add product to the store 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Vendor navigates to the vendor panel. 13 | 2. Vendor clicks on the add product option. 14 | 3. The add product page shows input fields for product information is displayed. 15 | 4. The page has a save option. 16 | 5. Vendor enters the product information. 17 | 7. Vendor clicks on the save button. 18 | 8. The product details are validated. 19 | 9. The product is saved into the application. 20 | 21 | 22 | Postconditions : 23 | 1. The product is visible to members and visitors. 24 | 25 | Alternative Flow: 26 | 8.1 Product information is invalid 27 | if vendor provides invalid product information, then 28 | 8.1.1. An error message shows to indicate that the product information 29 | is invalid. 30 | 8.1.2 The use case resumes at step 3. 31 | -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/27- Use Case 92-Display all added products.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 92 2 | 3 | PBI Title : Display all added products 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. A product was added by the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to vendor panel. 14 | 2. Vendor clicks on list all products option. 15 | 3. The product list page is displayed, showing added products in rows. 16 | 4. Each row shows a single product information. 17 | 6. There is a paging support to navigate between different pages of products. 18 | 19 | 20 | Postconditions : 21 | None 22 | 23 | Alternative Flow: 24 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/28- Use Case 93-Update product data.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 93 2 | 3 | PBI Title : Update product data 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. A product was added by the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to vendor panel. 14 | 2. Vendor clicks on a specific product from list all products page. 15 | 3. The page shows input fields for product information is displayed. 16 | 4. All of the input fields are filled with the current product information. 17 | 5. The page has an update option. 18 | 6. Vendor updates product information 19 | 7. Vendor clicks on the update option. 20 | 8. The product information is validated. 21 | 9. The product information is updated. 22 | 23 | Postconditions : 24 | 1. The product information is updated. 25 | 2. The update is reflected to members and visitors. 26 | 27 | Alternative Flow: 28 | 8.1 Product information is invalid 29 | if vendor provides invalid product information, then 30 | 8.1.1. An error message shows to indicate that the product information 31 | is invalid. 32 | 8.1.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/29- Use Case 2071-Display all orders made by all users for all vendors.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2071 2 | 3 | PBI Title : Display all orders made by all users for all vendors 4 | 5 | Primary Actors : 6 | 1. Admin 7 | 8 | Preconditions : 9 | 1. Admin has been logged in to his account. 10 | 2. Admin has been authorized to list all orders. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Admin navigates to admin panel. 14 | 2. Admin clicks on list all orders option. 15 | 3. The list all orders page is displayed, showing offers in rows. 16 | 4. Each row shows an Order Information. 17 | 5. There is a paging support to navigate between different pages of orders. 18 | 6. The list can be filtered using some order information. 19 | 7. Admin filters the list by vendor name using a specific vendor name. 20 | 8. Admin clicks on the search option. 21 | 9. The list is updated with only orders made for the specified vendor. 22 | 23 | 24 | Postconditions : 25 | None 26 | 27 | Alternative Flow: 28 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/30- Use Case 2119-Update order status.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2119 2 | 3 | PBI Title : Update order status 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. An order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to list all orders page. 14 | 2. The list all orders page is displayed. 15 | 3. The page has a save option. 16 | 4. The vendor changes the order status for a specific order to be completed. 17 | 6. The vendor clicks on the save button. 18 | 7. The order is updated. 19 | 20 | 21 | Postconditions : 22 | 1. The order status is updated in the application. 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/31- Use Case 2118-Display order detailed information.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 2118 2 | 3 | PBI Title : Display order detailed information 4 | 5 | Primary Actors : 6 | 1. Vendor 7 | 8 | Preconditions : 9 | 1. Vendor has been logged in to his account. 10 | 2. An order was made to the vendor. 11 | 12 | Basic Flow (Happy Path): 13 | 1. Vendor navigates to vendor panel. 14 | 2. Vendor clicks on a specific order from list all orders page. 15 | 3. Another page for viewing order information is displayed. 16 | 4. The page shows Member's personal information. 17 | 5. The page also shows the order infromation. 18 | 6. The page also displayes each ordered product information. 19 | 20 | 21 | Postconditions : 22 | None 23 | 24 | Alternative Flow: 25 | None -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/32- Use Case 90-Recover forgotten password.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 90 2 | 3 | PBI Title : Recover forgotten password 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | None 10 | 11 | Basic Flow (Happy Path): 12 | 1. Member navigates to the sign in page. 13 | 2. Member clicks on the forgot password option. 14 | 3. A page is displayed with input field for member's email account and 15 | an option to recover password. 16 | 4. Member enters his email account and clicks on the recover password option. 17 | 5. Email account is being validated. 18 | 6. An email is sent to the provided email with a link to reset password. 19 | 7. Member clicks on the link in his email. 20 | 8. Another page for the new password is displayed. 21 | 9. Member enters the new password clicks on the submit option. 22 | 10.The new password is validated. 23 | 11.Member is logged in to his account. 24 | 25 | 26 | Postconditions : 27 | 1. Password is updated in the application. 28 | 2. Member is logged in using his new password automatically. 29 | 30 | Alternative Flow: 31 | 5.1 Email doesn't exist. 32 | if member provides an email which doesn't exist in the application, then 33 | 5.1.1 An error message will show to indicate that the email doesn't exist. 34 | 5.1.2 The use case resumes at step 3. 35 | 36 | 10.1 Short password 37 | if Member provides a short password, then 38 | 10.1.1 An error message will show to indicate that the password is too short. 39 | 10.1.2 The use case resumes at step 8. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/33- Use Case 18-Change password.txt: -------------------------------------------------------------------------------- 1 | PBI Number : 33 2 | 3 | PBI Title : Change password 4 | 5 | Primary Actors : 6 | 1. Member 7 | 8 | Preconditions : 9 | 1. Member has been logged in to his account. 10 | 11 | Basic Flow (Happy Path): 12 | 1. Member navigates to his account page. 13 | 2. Member clicks on the Change Password option. 14 | 3. Another page is displayed, with input fields current and new password. 15 | 4. Member enters the required information. 16 | 5. Member's input is validated. 17 | 6. Password is updated in the application. 18 | 19 | Postconditions : 20 | 1. The Member password is updated in the application. 21 | 22 | Alternative Flow: 23 | 5.1 Old password is incorrect 24 | if Member provides an incorrect old password, then 25 | 5.1.1 An error message will show to indicate that the old password is incorrect. 26 | 5.1.2 The use case resumes at step 3. 27 | 28 | 5.2 New password is too short. 29 | if Member provides a short new password, then 30 | 5.2.1 An error message will show to indicate that the new password is too short. 31 | 5.2.2 The use case resumes at step 3. -------------------------------------------------------------------------------- /doc/3-Use Case Scenarios (Text)/Initial Use Case Scenarios (Text)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/4-Basic Mockups (Pictures)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/5-Photoshop Design (PSD and Pictures)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/6-Website Components (HTML-CSS-JS)/HTML/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/7-Storyboard (PPTX)/Conceptual Storyboard (PPTX)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/7-Storyboard (PPTX)/Detailed Storyboard (PPTX)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /doc/8-E-Commerce Products data (Pictures-Data Txt)/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /src/Code/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /src/Infrastructure/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /src/Packages/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | -------------------------------------------------------------------------------- /src/README.md: -------------------------------------------------------------------------------- 1 | "# E-Commerce" 2 | --------------------------------------------------------------------------------