Our project is about e-commerce system.So we are trying to complete all the necessary need for the e-commerce site.

2. 1.Introduction
1.1 Definition
1.2 Advantages Of E-COMMERCE
1.3 Disadvantages Of E-COMMERCE
2. Information Gathering &
System Study
2.1 Get Information From Internet
2.2 Goal of our project
2.3 Benchmark Analysis
2.4 Our proposed Features
3. Moqups & Templates
Moqups:
3.1 Home page
3.2 Second page
3.3 Detail Page
3.4 Cart Page
3.5 Login & Signup page
Templates:
3.1 Signup & Login Page
3.2 Home Page
3.3 Shop & Cart Page
3.4 User Account Information
4. System Design & Show Design
4.1 Context Diagram
4.2 Activity Diagram
4.3 Data Flow Diagram
4.4 Use Case Diagram
4.5 Use Case Descriptive Form
4.6 Entity Relationship Diagram
5. Screenshots Of Project & Visual Guide
5.1 Signup & Login
5.2 Home Page
5.3 Search & Select Product
5.4 Product Delivery Information
6. Conclusion & Future Direction
6.1 Conclusion
6.2 Future Direction
7. References

3.  Introduction
 Advantage of E-Commerce
 Disadvantage of E-Commerce
 Goal of your project
 Information Gathering
 Benchmark Analysis
 Proposed Features List
 Context Diagram
 Activity Diagram
 Data Flow Diagram
 Use Case Diagram
 ER Diagram

4. 1.1 Definition
1.2 Advantages Of E-COMMERCE
1.3 Disadvantages Of E-COMMERCE

5.  It is commonly known as electronic marketing.
 It consist of buying and selling goods and services over an
electronic system such as the internet.
 E-commerce is the purchasing , selling & exchanging goods
and services over computer network or internet through which
transactions or terms of sale are performed electronically

7.  Faster buying/selling procedure, as well as easy to find
products.
 Buying/selling 24/7.
 More reach to customers, there is no theoretical geographic
limitations.
 Low operational costs and better quality of services.
 No need of physical company set-ups.
 Easy to start and manage a business.
 Customers can easily select products from different providers
without moving around physically.

8.  Unable to examine products personally
 Not everyone is connected to the Internet
 There is the possibility of credit card number theft
 Mechanical failures can cause unpredictable effects on the total
processes.

9. 2.1 Get Information From Internet
2.2 Goal of our project
2.3 Benchmark Analysis
2.4 Our proposed Features

10. Home Page Of Amazon.com

11. Home Page Of Walmart.com

12. Sign in/login features comparison between Walmart.com vs amazon.com

13. Sign up features comparison between daraz.com vs AliExpress.com

14. Search features comparison between Walmart.com vs amazon.com

15. Category Of Walmart.com

16.  The main goals of this project are:
1.User friendly navigations to provide ease.
2.Maximize search options
2.1. by category's name
2. 2. by Product’s title
3. Help user by providing specification of products.
4. Full Security System.
5. Sell and Buy online Any product At Home Fastly.

17. Comparison Amazon Walmart Daraz AliExpress Our
Project
Sitemap No No No No Yes
Search Yes Yes Yes Yes Yes
Home Yes Yes Yes Yes Yes
Advertisement Yes Yes Yes Yes Yes
Help Yes Yes Yes Yes Yes
Sign in & up Yes Yes Yes Yes Yes
Language No No Yes Yes Yes
Logo Yes Yes Yes Yes Yes
Animation Yes Yes Yes Yes Yes
Track Order Yes Yes Yes No Yes
Categories Yes Yes Yes Yes Yes
Gift Card Yes Yes Yes No Yes
Survey No No No Yes Yes
Product Video Yes No No No Yes
Prime Member Yes No No No Yes
Compare to similar item Yes No No No Yes
User Review Yes Yes Yes No Yes
Blog No No Yes No Yes
Benchmark Analysis

18. 1.Home
2.Search
3.Categorise
3.1.Sub-Categories
4.Help
5.Logo
6.Sign in & up
7.Advartisement
8.Product Video
9.Compare to smiler
item
10.User review
11. Blog
12. Gift card/coupon
13. Track order
14. Sitemap
15. Animation
16. Survey
17.Language Support
18. Subscribe
19.Chat
20. Social Links
21. Cart
22. Latest Product

19. Moqups:
3.1 Home page
3.2 Second page
3.3 Detail Page
3.4 Cart Page
3.5 Login & Signup page
Templates:
3.1 Signup & Login Page
3.2 Home Page
3.3 Shop & Cart Page
3.4 User Account Information

29. 4.1 Context Diagram
4.2 Activity Diagram
4.3 Data Flow Diagram
4.4 Use Case Diagram
4.5 Use Case Descriptive Form
4.6 Entity Relationship Diagram

30. Context Diagram
A system context diagram (SCD) in software engineering &
systems engineering is a diagram that defines the boundary
between the system, or part of a system, and its environment,
showing the entities that interact with it. This diagram is a high
level view of a system.
*Symbol of context Diagram
Connections
Process
External Entity

31. Context Diagram
0
Online Shopping
System
CUSTOMER
ADMINISTRATOR
SHIPPING AGENT
PAYMENT
OPTION
VISITOR
Search
Product
Information
Order Accept/Reject
Notice
Order
Product
Details
Add/Update
Catalog
Payment
Confirm
Payment
Request
Shipping
Request
Request
Confirmation

32. Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system. So the
control flow is drawn from one operation to another.
*Symbol of Activity Diagram.
Starting point
Activity
Decisions
Signals (input and output)
Concurrent activity
Final activity

33. Activity Diagram

34. Data Flow Diagram
A data flow diagram (DFD) is a graphical representation of the
"flow" of data through an information system, modelling its
process aspects. A DFD is often used as a preliminary step to
create an overview of the system, which can later be
elaborated.
*Symbols of DFD
Connections
Process
External Entity
Database

35. DFD Level - 0

36. DFD Level – 1 for Process - 3

37. DFD Level – 1 for Process - 4

38. DFD Level – 1 for Process - 5

39. Use Case Diagram Symbols
<<include>> <<extend>>
adding (not reusing)
functionality
reuse of functionality
As a whole
use case
Individual
Use case
Connections
Primary
Actor

40. Use Case Analysis
Stakeholder/Actors:
Customer
Browse
Search
Purchase
System Admin
Manages Products
Verifies Customer
Facilitates Transaction

41. Use Case Diagram

42. Use Case 01: Login
Primary actor: Customer
Stakeholders and Interests:
 Customer: Wants to a simple login feature in order to access full features of site.
 System Admin: Wants the login process to complete smoothly.
Pre-conditions: User must first reach the website.
Success Scenario:
1. The use case starts when the user accesses a protected page. the system displays a
login form.
2. The user enters correct id and password. User is authenticated by system and login
process is completed.
Alternative Scenario:
1. The user enters invalid id or password. The system displays an error message and
requests for login again.
Post-conditions: User can now access all features of service available and will search,
buy products desired.

43. Use Case 02: Registration
Primary actor: Customer
Stakeholders and Interests:
 Customer: Wants to search and buy products quickly so they want no hassle in
registration process.
 System Admin: Wants so streamline the process of registration so it doesn’t become
annoyance to user.
Pre-conditions: User must click on the register button on the website.
Success Scenario:
1. The customer clicks registration button.
2. Customer fills in the required information.
3. System admin verifies the information and creates a new database entry for the user.
Alternative flow:
1. The user enters invalid information and the page redirects user to new instance of that
page.
Post-conditions: User can proceed to buy, order the items or, continue browsing.

44. Use Case 03: Payment
Primary actor: Customer
Stakeholders and Interests:
 Customer: Wants purchase and fast service with minimal effort and order
confirmation.
 Admin: Will save login information. Provide customers need and update
information.
Pre-conditions: Customer needs to be identified and authenticated.
Success Scenario
1.Customer login to the page for purchasing.
2.System provides a confirmation page with given orders.
3.System authenticates users payment information.
4.System records sale item and presents item description, price and running total.
Alternative flow:
At any time, System fails:
1. System Admin restarts System, logs in and request recovery of prior state.
2. System re-constructs prior state.
3. If invalid identifier detected, signals system error and rejects entry.
Post-conditions: Sale is saved. All the information is updated. Order confirmation is
generated.

45. Use Case 04: Order
Primary actor: Customer
Stakeholders and Interests:
 Customer: Wants to order the the chosen products with no hassle.
 System Admin: Wants the simplify ordering system for customer.
Pre-conditions: User must have at least one item on cart and passes previous payment
step.
Success Scenario:
1. The customer search the items they wish to purchase.
2. Customer can also search products order by their range.
3. System admin will create new items and update the items as customer can get more
products by search.
Alternative Scenario:
1. The user cancels the order.
2. Clear the order information and delete entry for the order.
Post-conditions: User can proceed to order other items or, continue browsing.

46. Use Case 05: System Update
Primary actor: System Admin
Stakeholders and Interests:
 Customer: Wants to find new and latest product in the online shop.
 System Admin: Wants to make new products available for the customer to buy.
Pre-conditions: The product must be available in the warehouse with given quantity.
Success Scenario:
1. The system admin creates a new entry for the product.
2. The system admin enter product quantity and information.
3. System admin updates the system to reflect newly inserted data.
Alternative Scenario:
1. The admin is unable to perform database update and checks database integrity.
Post-conditions: User now can buy new types of products in greater quantity.

47.  An entity-relationship diagram (ERD) is a data modeling technique
that graphically illustrates an information system's entities and the
relationships between those entities. An entity-relationship
diagram is a conceptual and representational model of data used to
represent the entity framework infrastructure.
 Symbols Of ERD:

48. ER Diagram

49. 5.1 Signup & Login
5.2 Home Page
5.3 Search & Select Product
5.4 Product Delivery Information

54. 6.1 Conclusion
6.2 Future Direction

55.  In conclusion we can say that there is no end to product
improvement. Even when there seems to room for
improvement there always is. Just like google was once
just a search engine, but provided additional related
features; similarly our goal is other features to our
ecommerce system.
 The objective from this course was to learn to build a
product using formal methods such as information
gathering, benchmarking, various diagrams DFD, use
case, activity etc. We applied these tools we learned into
our own project. These formal methods has given a
structure to our project and necessary documentation for
future upgrade.

56. We want to continue build our project as we learn more formal methods. These
below are some of the future directions that we want to see in our product.
1. AI based chatting system with customer for statistically similar questions.
2. Personalized product suggestion based on customer purchase and browsing
record.
3. Using sslcommerz api to provide online transations.
4. Creating an algorithms to provide delivary routine to minimize cost. If
multiple products are being delivered to same area in close time slot then cost
can be minimized.
5. A product request system for customers to add new products to inventory.
6. Doing sentimental analysis on product review to get true customer
satisfaction of product.
7. An admin panel with complete customization and control over website.

57.  https://www.amazon.com/
 https://www.walmart.com/
 https://www.aliexpress.com/
 https://www.daraz.com.bd/
 https://www.bagdoom.com/