A complete Software Requirements Specification (SRS) and system design documentation for DeenCraft — a proposed web-based e-commerce platform for a business specializing in customized Islamic products such as Prayer Mats, Tasbeeh, Digital Counters, and Travel Mats.
DeenCraft is a business that sells Islamic and customized products, currently operating through manual, WhatsApp-based order handling. This repository contains the complete Software Requirements Specification (SRS) for a proposed e-commerce platform designed to replace that manual process with a structured, automated, and scalable online store.
The documentation covers the full requirements engineering lifecycle — from problem identification and existing-system analysis, through external entity identification, functional and non-functional requirements, requirements traceability, and detailed use case descriptions with diagrams — for Phase I of the proposed system.
This was completed as a university project, focused on requirements engineering and system analysis & design for a real-world e-commerce business scenario.
DeenCraft currently manages all business operations manually through WhatsApp: customers inquire about products, customization details, and pricing directly with the owner. This approach breaks down under scale — leading to delayed replies, missed messages, customization confusion, and no way for customers to track their orders, especially during high-demand periods like Ramadan and Eid.
A complete web-based e-commerce platform that automates:
- Customer ordering, product browsing, and product customization
- Shopping cart & checkout with Cash on Delivery (COD)
- Order tracking with automated status updates
- Inventory management with low-stock and out-of-stock alerts
- WhatsApp/SMS notifications for OTPs, confirmations, and dispatch updates
- Review and rating management with admin moderation
- A centralized admin dashboard for products, orders, promotions, and analytics
The following diagrams and analysis artifacts were produced as part of the requirements engineering process.
The prioritized product backlog breaking down all functional and non-functional requirements into ranked work items — organized by module (Authentication, Catalog & Customization, Cart & Checkout, Order Management, Inventory, Reviews, Admin Panel, and Notifications) and priority level (Highest, Medium, Lowest).
A consolidated view of the project's requirements landscape — summarizing the scope of functional requirements (FRs), non-functional requirements (NFRs), and their distribution across the eight core system departments.
Structured listings of all identified functional and non-functional requirements, each tagged with a unique requirement ID (FR-x / NFR-x) for traceability back to specific business needs and use cases.
A high-level executive summary tying together the system's purpose, scope, and the key departments — User Management, Product Management, Product Customization, Cart & Checkout, Order Management, Inventory, Notifications, Reviews, and Admin Management.
The phased delivery roadmap for the system, spanning Phase I (core e-commerce launch features), Phase II (CRM, analytics, promotions, and support tooling), and Phase III (payment gateways, mobile app, AI recommendations, and enterprise-scale integrations).
Located in /Use_Case_Diagrams, these diagrams model the detailed use case flows for each of the eight core modules:
| Module | Use Case Focus |
|---|---|
| 1. Authentication | Registration, login, password reset, session management |
| 2. Catalog & Customization | Product browsing, search, filtering, and product personalization |
| 3. Cart & Checkout | Cart management, promo codes, shipping, and order review |
| 4. Order Management | Order tracking, lifecycle status transitions, cancellation |
| 5. Inventory Management | Stock tracking, low-stock/out-of-stock alerts, manual adjustments |
| 6. Review & Rating | Review submission, moderation, and display |
| 7. Dashboard & Admin | Analytics dashboard, product/order/customer management |
| 8. Notifications | Automated WhatsApp/SMS/Email alerts with fallback retry logic |
Phase I (covered in this document) includes:
- User Management & Authentication
- Product Management & Customization
- Shopping Cart & Checkout (Cash on Delivery)
- Order Processing & Tracking
- Inventory Management
- Notification Management (WhatsApp/SMS)
- Review & Rating System
- Basic Admin Dashboard
Phase II & III (future scope) extend the platform with CRM, advanced analytics, promotional campaign tooling, online payment gateways, a mobile app, AI-based recommendations, and enterprise-scale security and infrastructure.
| Role | Capabilities |
|---|---|
| Customer | Register, browse, customize, order, track, review, cancel |
| Guest User | Browse and search products only (no cart/checkout access) |
| Admin | Manage products, inventory, orders, reviews, discounts, analytics, and system settings |
- Performance: Pages load within 3 seconds on standard 4G/Wi-Fi; supports 500+ concurrent users
- Security: HTTPS/TLS 1.2+, AES-256 encryption at rest, SQL injection & XSS protection, BCrypt password hashing
- Reliability: 99.9% uptime target, load balancing, automated daily backups with 30-day retention
- Accessibility: WCAG-compliant color contrast, responsive layouts from 320px width upward
- Notification Resilience: WhatsApp-primary with automated SMS fallback and retry logic
DeenCraft/
├── Images/ # Requirements & planning artifacts
│ ├── Backlog.png
│ ├── Dashboard.png
│ ├── Lists.png
│ ├── Summary.png
│ └── Timeline.png
├── Use_Case_Diagrams/ # Detailed use case diagrams per module
│ ├── 1000461137.jpg
│ ├── 1000461138.jpg
│ ├── 1000461139.jpg
│ └── 1000461140.jpg
└── Project.pdf # Full Software Requirements Specification (SRS)
Abdul Qadeer Sikander
A complete requirements engineering and system design document for a real-world Islamic e-commerce business, developed as a university software engineering project.