Back to the 2020 paper

Module 3: Software Design & Metrics

20207m

Design the following for an 'E-commerce solution for an electronic products company' that gives choice to the users to select a/few product(s) from the available range, order them and allow to make the payments online:

(i) Design the DFDs (level-0, 1 and 2).
(ii) Prepare SRS document. List assumptions, if any.
(iii) Design an ER-diagram. List all the entities, attributes, key constraints and cordiality.
(iv) Draw a Gantt chart.
(v) Specify the s/w engineering pre-design which suits this application development.

Worked SolutionAI Assisted

Solution - E-commerce for Electronic Products

(i) DFDs

Level 0 (Context): External Entities: Customer, Admin, Payment Gateway. Process: E-commerce System. Flows: Browse/Search, Order, Payment, Confirmation, Inventory update.

Level 1: Processes: 1.0 User Management & Authentication, 2.0 Catalog & Search, 3.0 Cart & Ordering, 4.0 Payment Processing, 5.0 Order Fulfillment & Shipping. Data Stores: D1 User DB, D2 Product Catalog, D3 Cart/Orders, D4 Payments.

Level 2 (example for 3.0 Cart & Ordering): 3.1 Add to cart, 3.2 Update quantity, 3.3 Calculate total + tax + discount, 3.4 Checkout & address validation.

(ii) SRS (Outline, IEEE 830)

1. Introduction: Purpose, Scope, Definitions (SKU, Cart), References, Overview
2. Overall Description: Product perspective, User classes (Guest/Customer/Admin), Constraints (PCI-DSS), Assumptions (Internet, payment gateway available)
3. Specific Requirements:

  • Functional: Registration, login, search/filter, product details, cart, wishlist, checkout, payment (COD/Card/UPI), order tracking, admin CRUD, reports
  • Non-functional: Performance <2s, security (HTTPS, encrypted), availability 99.5%, usability, scalability
  • Interfaces: UI, hardware, software (DB, gateway API)
    Assumptions: Delivery partners available, returns within 7 days.

(iii) ER Diagram

Entities & Attributes:

  • User(user_id PK, name, email, password, address, phone)
  • Product(product_id PK, name, category, price, stock, specs, warranty)
  • Cart(cart_id PK, user_id FK)
  • Cart_Item(cart_id FK, product_id FK, qty)
  • Order(order_id PK, user_id FK, date, total, status, payment_id FK, shipping_addr)
  • Order_Item(order_id FK, product_id FK, qty, price)
  • Payment(payment_id PK, method, amount, status, transaction_no)
  • Admin(admin_id PK, ...)

Key Constraints: PK as above, FK referential integrity.
Cardinality: User 1—N Cart (1 active), Cart 1—N Cart_Item, Product 1—N Cart_Item, User 1—N Order, Order 1—N Order_Item, Order 1—1 Payment.

(iv) Gantt Chart (6 months)

Phase M1 M2 M3 M4 M5 M6
Requirements ██
Design ██
Catalog & User Module ██
Cart/Payment ██
Testing ██
Deployment ██

Milestones at end of each bar.

(v) Suitable Process Model

Agile-Iterative (Scrum) + Incremental: E-commerce needs evolving features, UI feedback, frequent releases. Alternatives: Prototyping for UI validation. Waterfall too rigid for changing product requirements. Spiral if high risk payment integration.

Similar questions

Official AppAndroid App

PYQDeck for Android

Solve BEU previous-year exam papers anywhere, anytime. Fast search, offline paper viewing, and step-by-step solutions designed specifically for your phone.