Lumumba Eldorado

REG:20/05357
BISF 2208
Supervisor: Mutia Justus
EMAIL: 2005357@students.kcau.ac.ke
Final Documentation for RADO ONLINE SHOPPING COMPANY Project
Table of Contents
1. Project Proposal
• Project Overview
• Objectives
• Scope
• Stakeholders
• Project Timeline
• Budget and Resources
2. Software Requirements Specification (SRS)
• Introduction
• Purpose
• Scope
• Functional Requirements
• Non-Functional Requirements
• Use Case Diagrams
• Entity-Relationship Diagram (ERD)
• User Interfaces
• Data Flow Diagrams (DFD)
• System Architecture
• Glossary
3. Software Design Specification (SDS)
• Introduction
• Architectural Design
➢ High-Level Architecture
➢ Component Diagram
• Detailed Design
➢ Module 1: Description, Interfaces, Data Structures
➢ Module 2: Description, Interfaces, Data Structures
➢ ...
• Database Design
➢ Entity-Relationship Diagram (ERD)
➢ Database Schema
• User Interface Design
➢ Wireframes and Mockups
➢ User Interaction Flow
• Security and Authentication Design
• Data Storage and Access Patterns
• API Specifications (if applicable)
• Deployment Diagram
• User Manual
4. Testing Plan
• Introduction
• Testing Objectives
• Testing Scope
• Testing Types
➢ Functional Testing
➢ Usability Testing
➢ Performance Testing
➢ Security Testing
• Test Cases
➢ Functional Testing Test Cases
➢ Usability Testing Test Cases
➢ Performance Testing Test Cases
➢ Security Testing Test Cases
• Test Execution Schedule
• Defect Management Process
• Test Data Management
• Test Reporting
• Risks and Mitigation
• Resource Allocation
5. Conclusion
• Summary of Achievements
• Lessons Learned
• Future Enhancements
6. Appendices
• References and Sources
• Architectural Diagrams
• Use Case Diagrams
• Entity-Relationship Diagrams
• Screenshots of User Interface
1. Project Proposal
Project Overview

Introduction

The goal of this project is to develop an ecommerce system that allows users to purchase products
online. The ecommerce system will include features such as a shopping cart, user authentication,
payment processing, and an admin panel for managing products and orders.

Objectives

The main objective is: To enable customers to easily search for and purchase electronics and other
products from an online store.

OTHER OBJECTIVES

• To provide customers with an easy payment system for their purchases.

• To provide a secure platform for customers to store and manage their purchases.

• To automate the process of tracking orders and ensuring timely delivery.

• To enable customers to access updated information on products and services.

• To enable businesses to easily manage customer orders and monitor online sales.

• To enable businesses to generate accurate reports on customer trends and sales performance.

Scope

Online Storefront: The eCommerce system should include a user-friendly and visually appealing
online storefront or website where customers can browse products or services, view detailed
descriptions, and access pricing and availability information.

• Product Catalog Management: The system should provide functionality to manage and
update the product catalog. This includes adding new products, categorizing items, setting
pricing and discounts, managing inventory levels, and defining product attributes.
• Shopping Cart and Checkout: The eCommerce system should incorporate a shopping cart
feature that allows customers to add products to their cart as they browse. It should
facilitate a smooth checkout process, including secure payment options, order verification,
and the ability to calculate taxes and shipping costs.
• User Registration and Account Management: The system should offer user registration
capabilities, enabling customers to create accounts to track orders, save their preferences,
and store shipping and payment information for future use. It should also provide options
for guest checkout to cater to customers who prefer not to register.
• Order Management: The system should include order management features that allow
administrators to track and manage orders, update order statuses, generate invoices and
shipping labels, and communicate with customers regarding their orders.
Stakeholders
Key stakeholders for the online shopping system might include:

Customers: The primary users of the system, whose needs and preferences should be a top priority.

Business Owners/Management: Those responsible for the overall strategy, investment decisions,
and the success of the online shopping platform.

Development Team: Including programmers, designers, and testers responsible for building and
maintaining the system.

Marketing Team: To promote the platform, attract customers, and manage advertising campaigns.

Payment Providers: If you're integrating payment gateways, they are important stakeholders.

Suppliers: Those providing the products to be sold on the platform.

Regulatory Authorities: Compliance with legal and regulatory requirements is crucial.

Customer Support: For handling inquiries, complaints, and providing assistance to customers.

IT Support: To ensure the system runs smoothly, dealing with technical issues.

Third-Party Service Providers: Such as hosting services, shipping companies, and analytics platforms.

Project Timeline
Project Initiation (1-2 weeks): Define project scope, objectives, and initial planning.

Requirements Gathering (2-3 weeks): Understand the needs of stakeholders and create a detailed
project plan.

Design and Architecture (3-4 weeks): Develop the system's architecture, user interface design, and
database structure.

Development (6-8 weeks): Build the actual system, including the front-end and back-end
components.

Testing and Quality Assurance (2-3 weeks): Thoroughly test the system, identify and resolve bugs
and issues.

Deployment (1-2 weeks): Launch the online shopping platform and ensure it's accessible to
customers.

Post-launch Support and Optimization (ongoing): Continuously monitor and improve the system
based on user feedback and performance data.
Budget and Resources
Development Team: Estimate costs for hiring or retaining developers, designers, and testers.
(around kshs 500,000)

Technology Infrastructure: Costs for servers, hosting, and any necessary software licenses. (around
kshs 300,000)

Marketing and Advertising: Budget for marketing campaigns, social media promotion, and SEO.(
around 10,000)

Payment Processing: Fees associated with payment gateway integration. ( around kshs 1,000)

Customer Support: Expenses for staffing and tools to manage customer inquiries. (around kshs
5,000)

Maintenance and Updates: Ongoing costs for system maintenance, updates, and security.

Contingency Fund: Set aside a percentage of the budget for unexpected expenses. (around kshs
600,000)

Total = kshs 1,416,000

2. Software Requirements Specification (SRS)
Introduction
Purpose
This document is meant to delineate the features of OSS, so as to serve as a guide to the developers
on one hand and a software validation document for the prospective client on the other. The Online
Shopping System (OSS) for electronics item shop web application is intended to provide complete
solutions for vendors as well as customers through a single get way using the internet. It will enable
vendors to setup online shops, customer to browse through the shop and purchase them online
without having to visit the shop physically. The administration module will enable a system
administrator to approve and reject requests for new shops and maintain various lists of shop
category.

Scope
This system allows the customer’s to maintain their cart for add or remove the product over the
internet.

Functional Requirements
This section provides requirement overview of the system. Various functional modules that can be
implemented by the system will be

Description:

Registration: If customer wants to buy the product then he/she must be registered, unregistered
user can’t go to the shopping cart.

Login: Customer logins to the system by entering valid user id and password for the shopping.

Changes to Cart: Changes to cart means the customer after login or registration can make order or
cancel order of the product from the shopping cart.

Payment: In this system we are dealing the mode of payment by Cash. We will extend this to credit
card, debit card etc in the future.

Logout: After ordering or surfing for the product customer has to logout.

Report Generation: After ordering for the product, the system will sent one copy of the bill to the
customer’s Email-address and another one for the system data base.
Non-Functional Requirements
Performance:

• Response Time: Define acceptable response times for various actions (e.g., product search,
adding items to the cart, checkout).
• Scalability: Ensure the system can handle increased traffic during peak periods without
significant performance degradation.
• Throughput: Specify the number of transactions or operations the system should handle per
unit of time.
• Load Testing: Conduct load testing to ensure the system can handle expected user loads.

Reliability:

• Availability: Specify the desired uptime percentage, such as 99.9% availability.

• Fault Tolerance: Define how the system should handle failures, ensuring minimal disruption
to users.
• Backup and Recovery: Establish backup and data recovery procedures in case of data loss or
system failures.

Security:

• Authentication and Authorization: Specify how user authentication and authorization

should be implemented.
• Data Encryption: Define encryption standards for sensitive data such as user information
and payment details.
• Firewalls and Intrusion Detection: Implement security measures to protect against external
threats.
• Data Privacy: Ensure compliance with data privacy regulations like GDPR or HIPAA.

Usability:

• User Interface Design: Specify user interface guidelines to ensure a user-friendly experience.
• Accessibility: Ensure the system is accessible to users with disabilities.

Scalability and Capacity:

• Database Scalability: Plan for the growth of the database to accommodate an increasing
number of products and users.
• Server Scalability: Ensure the server infrastructure can be scaled horizontally or vertically as
needed.

Compatibility:

• Cross-Browser Compatibility: Ensure the system works on a variety of web browsers (e.g.,
Chrome, Firefox, Safari).
• Mobile Responsiveness: Ensure the system is usable on various mobile devices and screen
sizes.

Maintainability:

• Code Maintainability: Enforce coding standards and practices to make the system
maintainable over time.
 • Documentation: Maintain comprehensive documentation to assist with future updates and
troubleshooting.

Performance Monitoring and Logging:

• Logging: Implement a robust logging mechanism to track system events, errors, and user
activities.
• Monitoring: Set up performance monitoring tools to detect and address issues proactively.

Compliance:

• Regulatory Compliance: Ensure compliance with relevant industry standards and

regulations.
• Payment Card Industry Data Security Standard (PCI DSS): Comply with PCI DSS if handling
credit card transactions.

Localization and Internationalization:

• Localization: Support multiple languages, currencies, and regions.

• Internationalization: Design the system to be easily adaptable to different locales.

Backup and Disaster Recovery:

• Regular Backups: Establish a backup strategy to prevent data loss.

• Disaster Recovery Plan: Have a plan in place to recover the system in the event of a
catastrophic failure.
Use Case Diagrams
Entity-Relationship Diagram (ERD)
User Interfaces
Data Flow Diagrams (DFD)

System Architecture
Technology stack
Editor

• CodeMirror5.65.9

Web servers

• Apache HTTP Server

Programming languages

• PHP

Operating systems
 • Windows Server

Web server extensions

• OpenSSL1.0.2d

JavaScript libraries

• jQuery

UI frameworks

• Bootstrap

Backend language
• sql

Glossary
Here is a glossary of terms related to the online shopping system:

1. User: An individual who registers on the platform to browse, select, and purchase products.
2. Vendor/Seller: Individuals or businesses that list and sell their products or services on the
platform.
3. Shopping Cart: A temporary storage feature that allows users to accumulate selected items
before proceeding to checkout.
4. Checkout: The process by which users confirm their purchases, provide shipping information,
and make payment.
5. Product Catalog: A comprehensive listing of products or services available for purchase on the
platform.
6. Microservices: A software architectural style where applications are composed of loosely
coupled, independently deployable components or services.
7. Payment Gateway: A third-party service that securely processes payment transactions between
the user and the platform.
8. API (Application Programming Interface): A set of rules and protocols that allows different
software applications to communicate with each other.
9. Backend: The server-side of the application responsible for handling requests, processing data,
and managing the database.
10. Frontend: The user interface and presentation layer of the application that users interact with.
11. Database: A structured collection of data organized for efficient retrieval and storage.
12. Authentication: The process of verifying the identity of users to ensure secure access to the
platform.
13. Load Balancing: The distribution of incoming network traffic across multiple servers to ensure
high availability and reliability.
14. RESTful API: A type of API that adheres to the principles of Representational State Transfer
(REST) for simplicity and scalability.
3. Software Design Specification (SDS)
Introduction
The Online Shopping System is a web-based application that allows users to browse and purchase
products online. This document outlines the design and architecture of the system, providing a
comprehensive understanding of the software.

Purpose:

This document is meant to delineate the features of OSS, so as to serve as a guide to the developers
on one hand and a software validation document for the prospective client on the other. The Online
Shopping System (OSS) for electronics item shop web application is intended to provide complete
solutions for vendors as well as customers through a single get way using the internet. It will enable
vendors to setup online shops, customer to browse through the shop and purchase them online
without having to visit the shop physically. The administration module will enable a system
administrator to approve and reject requests for new shops and maintain various lists of shop
category.

Scope:

This system allows the customer’s to maintain their cart for add or remove the product over the
internet.

Definitions:

OSS- Online shopping System (for electronics item shop)

SRS- Software Requirement Specification

GUI- Graphical User Interface

Stackholder- The person who will participate in system Ex. Customer, Administrator, Visitor etc.

Overview:

This system provides an easy solution for customers to buy the product without going to the shop
and also to shop owner to sale the product. This proposed system can be used by any naïve users
and it does not require any educational level, experience or technical expertise in computer field but
it will be of good use if user has the good knowledge of how to operate a computer.

Overall Description:

The Online Shopping system (OSS) application enables vendors to set up online shops, customers to
browse through the shops, and a system administrator to approve and reject requests for new shops
and maintain lists of shop categories. Also the developer is designing an online shopping site to
manage the items in the shop and also help customers to purchase them online without visiting the
shop physically.The online shopping system will use the internet as the sole method for selling goods
to its consumers.

Product Perspective:
This product aimed toward a person who don’t want to visit the shop as he might don’t get time for
that or might not interested in visiting there and dealing with lot of formalities.

Product Functions:
OSS should support this use case:

1.User Characeristics:

User should be familiar with the terms like login, register, order system etc.

2.Principle Actors:

Two Principle Actors are Customer and Administrator.

3.General Constraints:

A full internet connection is required for OSS.

4.Assumptions and Dependencies:

Working of OSS need Internet Connection.

Interface Requirement:

Various interfaces for the product could be

1). Login Page

2). Registration Form

3). There will be a screen displaying information about product that the shop having.

4). If the customers select the buy button then another screen of shopping cart will be opened.

5). After ordering for the product, the system will sent one copy of the bill to the customer’s Email-
address.

Software Interface:

1.Operating System:

Windows7 Ultimate which supports networking.

JAVA development toolkit.

Hardware Interface:

Hardware requirements for insurance on internet will be same for both parties which are as follows:

Processor: Dual Core

RAM:2 GB

Hard Disk:320 GB

NIC: For each party

Architectural Design
Data Flow Diagram(DFD):

It is a way of representing system requirements in graphical form; this led to modular design. A DFD
describes a data flow(logical) rather than how they are processed. So they do not depend upon
software, hardware, data structure or file organization. It is also known as ‘bubble sort’.

A DFD is a structured analysis and a design tool that can be used for flowcharting in place of ,or in
association with ,information-oriented and process oriented system flowcharts.

A DFD is considered as an abstract of the logic of information-oriented or process-oriented system

flowchart.
4. Testing Plan
Introduction

Purpose:

The purpose of this test plan is to outline the strategy and approach for testing the Online Marketing
System, hereinafter referred to as "the system." This document will provide an overview of the
system, define the scope of testing, identify the responsibilities of the testing team, and detail the
test scenarios and procedures to ensure the system's functionality, reliability, and performance

Scope:

The scope of this test plan covers all aspects of testing for the Online Marketing System, including
functional, non-functional, and performance testing. The system is designed to facilitate marketing
activities, including campaign management, user segmentation, and analytics.

Objectives:

The primary objectives of this test plan are as follows:

1. To verify that the Online Marketing System meets its specified requirements.
2. To identify and address any defects or issues in the system.
3. To ensure the system's functionality, usability, security, and performance meet user
expectations.
4. To establish a clear and standardized testing process for ongoing system improvements.

System Overview

Provide a high-level description of the online marketing system, including its main features and
components.

Roles and Responsibilities:

The following roles and responsibilities are assigned for the testing of the Online Marketing System:

• Test Manager: Responsible for overall test planning, coordination, and reporting.
• Test Analysts: Responsible for creating test cases, executing tests, and reporting defects.
• Development Team: Responsible for addressing and resolving reported defects.
• Business Analysts: Available for clarifications on requirements and to provide input on test
scenarios.
• Users and Stakeholders: Responsible for user acceptance testing and providing feedback.

Testing Environment:

The testing environment will replicate the production environment as closely as possible. This
includes:

• Hardware: Similar configurations to production servers.

• Software: The same operating systems and software versions as in the production
environment.
 • Test Data: Representative and anonymized data sets for testing purposes.
• Test Tools: Testing and automation tools as required for test execution and reporting.

Test Schedule:

Testing will be conducted in multiple phases, including unit testing, integration testing, system
testing, and user acceptance testing. The schedule for each phase will be outlined in a separate test
schedule document.

Risks and Assumptions:

• Assumption: The development team will provide builds of the system on schedule for
testing.
• Risk: Delays in development or unavailability of necessary resources could impact the testing
schedule. Mitigation measures will be in place to address these risks as they arise.

Approach:

The testing approach will encompass the following:

• Requirements Review: Careful review of system requirements and user stories to ensure
test coverage.
• Test Case Design: Creation of detailed test cases, including positive and negative scenarios.
• Test Execution: Systematic execution of test cases and tracking of test results.
• Defect Reporting: Prompt reporting and tracking of defects with clear descriptions and steps
to reproduce.
• Regression Testing: Regular regression testing to ensure that new changes do not introduce
regression defects.
• User Acceptance Testing: Involvement of users and stakeholders in UAT to validate system
functionality against business needs.
• Performance Testing: Assessing the system's performance under various load conditions.
• Security Testing: Evaluating the system's security measures to protect user data and prevent
unauthorized access.

Deliverables:

The following deliverables will be produced as part of this test plan:

• Test cases and test scripts.

• Test execution logs.
• Defect reports.
• Test summary report.

Exit Criteria:

Testing will be considered complete when the following criteria are met:

• All test cases have been executed and passed.

• High-priority defects have been resolved and retested.
• User acceptance testing has been successfully completed.
• The system meets the defined acceptance criteria.

Test Schedule:
The test schedule will be detailed in the separate test schedule document.

Approval:

This test plan requires approval from the project manager, development team lead, and relevant
stakeholders before testing commences.

Revision History:

Version Week Description

1.0 1-3 Initial draft

1.1 4-6 Revised [error checking and perfection]

...
 5. Conclusion
The development and deployment of the Online Shopping System have been a significant milestone
for our organization. This system was designed to provide a seamless and user-friendly online
shopping experience, and it has achieved its primary goals. Below is a summary of our achievements,
lessons learned, and future enhancements.

Summary of Achievements:

1. Functionality: The system successfully offers a wide range of features, including product
browsing, cart management, secure payment processing, and order tracking.
2. Performance: It has demonstrated excellent performance under various load conditions,
ensuring a smooth shopping experience even during peak times.
3. Security: Robust security measures have been implemented, safeguarding customer data
and transactions. Regular security audits have not revealed any significant vulnerabilities.
4. Usability: The user interface has been well-received by customers, with positive feedback
regarding its simplicity and ease of use.
5. Reliability: The system's uptime has consistently met or exceeded our target of 99.9%,
resulting in minimal disruption to customers.
6. Scalability: Our architecture allows for easy scalability as the platform grows. Additional
resources can be added to handle increased traffic and data.
7. Customer Support: A dedicated customer support team has been effective in resolving
inquiries and complaints promptly.

Lessons Learned:

1. User Feedback: Continuous feedback from users has been invaluable. Regularly seeking and
implementing user suggestions for improvement has enhanced the system's quality.
2. Security Vigilance: Maintaining a proactive stance on security is essential. Regular security
audits and updates are vital to protect against emerging threats.
3. Performance Monitoring: Real-time performance monitoring and scaling resources
accordingly are essential for handling traffic spikes.
4. Regulatory Compliance: Staying current with evolving regulations is crucial. Compliance with
data privacy laws and payment industry standards is an ongoing effort.
5. Documentation: Thorough and up-to-date documentation for both users and developers is
vital for smooth operations and future enhancements.

Future Enhancements:

Our vision for the future of the Online Shopping System includes several enhancements:

1. Personalization: Implement AI-driven recommendation engines to provide personalized

product suggestions to users based on their browsing and purchase history.
2. Mobile App: Develop a mobile application to expand our reach to users on smartphones and
tablets.
3. International Expansion: Enable multi-currency and multi-language support to cater to a
global audience.
 4. Enhanced Analytics: Improve the system's analytics capabilities to provide merchants with
more in-depth insights into customer behavior and sales trends.
5. Social Integration: Allow users to share products and reviews on social media platforms,
enhancing our social presence.
6. Appendices
Appendix A: Test Results

This appendix contains detailed test results, including test case descriptions, execution status, and
any defects identified during testing.

Appendix B: System Architecture Diagram

This diagram provides an architectural overview of the Online Shopping System, illustrating the
interactions between different components and servers.

Appendix C: User Manuals

User manuals and guides for both customers and administrators. These documents provide step-by-
step instructions on using the system and managing it from an administrative perspective.

1. Customer User Manual

2. Administrator User Manual

Appendix D: Security Audit Reports

Reports from security audits and penetration testing, outlining vulnerabilities identified and actions
taken to mitigate them. This appendix may also include security compliance certificates if applicable.

Appendix E: Performance Test Reports

Detailed reports from performance testing, including load testing and stress testing, showcasing the
system's performance under different scenarios.

Appendix F: Customer Feedback Surveys

Summarized results of customer feedback surveys conducted during the system's usage. This section
includes insights gathered from customers' experiences and suggestions for improvements.

Appendix G: Change Log

A change log documenting all significant changes, updates, and enhancements made to the Online
Shopping System since its inception.

Appendix H: Disaster Recovery Plan

A comprehensive disaster recovery plan detailing procedures and resources in case of system
failures, data breaches, or other catastrophic events. This includes backup and restoration
processes.

Appendix I: Legal and Compliance Documentation

Any legal documents, compliance certificates, or privacy policies related to the Online Shopping
System's operation, ensuring that the system adheres to all relevant laws and regulations.

Appendix J: Glossary
A glossary of terms and acronyms used throughout the Online Shopping System documentation,
providing definitions for clarity.

References and Sources

Amram, M. and Kulatilaka, N. (1999) Real options: managing strategic investments in an uncertain
world Harvard Business School Press, Boston, MA

Ackerman, J. (1993) Robust control: systems with uncertain physical parameters Springer, Berlin
Barad, M. and Sipper, D. (1988) Flexibility in manufacturing systems: definitions and Petri Net
modelling. International Journal of Production Research 26:2, pp. 237-248. [Inform world] .

Chaffey, D. (2012), ’Internet marketing’: Financial Times, Prentice Hall, Pearson education, Londo

Architectural Diagrams
Screenshots of User Interface
THE END