This document provides an overview of an online shop management system project. It includes 7 sections that cover: 1) basic concepts and technologies used, 2) a software project plan, 3) software requirements specification, 4) architectural design, 5) software testing, 6) QA, and 7) a table of contents. The system will provide administration, moderator, and user modules to manage online orders, products, users and more for small shops. It will be developed using .NET MVC, REST APIs, JavaScript, and deployed to Azure. Testing will follow a V-model and validate functionality, interfaces, security, and performance.

1. ONLINE SHOP MANAGEMENT
SYSTEM
Supervisor: Mr Gaurav Kumar Rastogi

2. •Introduction
1
•Basic Concepts - .Net, MVC, Rest API, JavaScript. Jquery, Git, Sql Server, Azure
2
•Software Project Plan
3
•Software Requirement Specification
4
•Software Design
5
•Software Testing
6
•QA
7
TABLE OF CONTENT

3. 1. Introduction
1.1 Basic Concepts - .Net, MVC, Rest API, JavaScript. Jquery, Git, Sql Server, Azure

4.  Idea
 There a lot of small and medium restaurants in any country.
 Almost of them don’t have management tool.
 The customer is not supported to book online.
 OSMS is developed to provide management tool for shops and help customer
easy to book any goods online.
 OSMS (Online shop management system)
o Web-based system
o Providing tool to manage shop especially for any product
o We have three module in this system
• Admin Module
• Moderator Module
• User Module
o Providing “online purchase page” for customer book online
1. INTRODUCTION
1.2 Project Introduction

5.  Propose
 Providing tool to manage shop online
 Providing online booking service
 Providing online purchased System
 Scope
 Manage Users
 Manage Moderators
 Manage products
 Selling activities management
2. SOFTWARE PROJECT PLAN
2.1 Proposed system and scope

6. Iterative Approach to Development
2. SOFTWARE PROJECT PLAN
2.3 Software Model

7. 2. SOFTWARE PROJECT PLAN
2.4 Plan
4 Week 2 Week 2 Week 2 Week
Idea
Project Plan
1
•Requirement
2
•Design
3
•Code
4
•Test
1
•Requirement
2
•Design
3
•Code
4
•Test
1
•Requirement
2
•Design
3
•Code
4
•Test
1
•Requirement
2
•Design
3
•Code
4
•Test
Admin Module
Manage Moderator
Manage Products
Manage Users
Manage Orders
Manage Moderators
User Module
Deployment
Testing
Package &
Deploy
Basic .Net
Concepts
DEV
Environment
Setup
Framework
for project

8. Jquery .NET MVC Azure
Jquery and ASP.Net MVC for Website
Rest API
Git
Deployment in Azure Web App
2.5 Technology Platform
2. SOFTWARE PROJECT PLAN

9.  Microsoft Windows 11 Ultimate x64
 SQL Server 2012 or later x32
 Microsoft Visual Studio 2019 Ultimate x32
 Visual Studio Code
 C# 4.6 or later, .Net framework 4.6.1 or later
 IIS 7
 Microsoft Internet Browser 9 Chrome
 Microsoft Office 2010 Professional Plus
 Git
 Skype
2. SOFTWARE PROJECT PLAN
2.6 Tools

10. 2. SOFTWARE PROJECT PLAN
2.7 Risk Management
Requirement
Change
Communication
Estimate

11. • User requirement
1
• Functional requirement
2
• Non_functional requirement
3
• Data Structure
4
3. SOFTWARE REQUIREMENT SPECIFICATION

12. 3. SOFTWARE REQUIREMENT SPECIFICATION
3.1 User requirement
Admin
Module
• Manage
User
• Manage
Moderator
• Manage
Order
• Manage
Product
Moderator
Module
• Manage
User
• Manage
Products
• Manage
Order
User
Module
• View
Product
• Search
Product
• Purchase
Product
• Edit Profile
Booking
• Payment
online

13. 3. SOFTWARE REQUIREMENT SPECIFICATION
3.2 Functionality
Manage User Accounts
Manage Moderators
Accounts
Manage Products
Manage Orders
Administration Module
Administrator

14. 3. SOFTWARE REQUIREMENT SPECIFICATION
3.2 Functional Requirement
Users
management Products
management
Account
management
Order
management
Moderator
Moderator Module

15. 3. SOFTWARE REQUIREMENT SPECIFICATION
3.2 Functional Requirement
Search and purchase
product
Edit Profile
User
Client System

16. • Usability
• Reliability
• Availability
• Security
• Maintainability
• Performance
Software system attribute
3. SOFTWARE REQUIREMENT SPECIFICATION
3.3 Non_functional Requirement

17. 4. ARCHITECTUAL DESIGN
4.1 Software Structure

18. 4.2 Component Diagram
Web
application
4. ARCHITECTUAL DESIGN

19. 4.2 Class Diagram
+login() : bool
#authenticate() : bool
+username : string
+password : string
+rememberMe : bool = 0
+duration : int
-_identity : AdminUserIdentity
AdminLoginForm
+login() : void
+logout() : void
+actionIndex() : void
DefaultController
+actionIndex()
+actionView()
+actionUpdate()
UserController
+actionIndex()
+actionReply()
ContactController +actionIndex()
+actionAdmin()
+actionView()
+actionCreate()
+actionUpdate()
+actionDelete()
ArticleController
+actionIndex()
+actionAdmin()
+actionView()
+actionCreate()
+actionUpdate()
+actionDelete()
CategoryController
+actionIndex()
+actionSiteAccess()
+actionUserActivities()
AnalyticController
+reply()
Contact Category
Article +pageview()
+visit()
+userActivities()
AnalyticReport
User
+authenticate() : bool
AdminUserIdentity
AdminWebUser
AdminController
4. ARCHITECTUAL DESIGN

20. 5. SOFTWARE TESTING
5.1 Test Model
V Lifecycle Model
Requirement
Analysis
Specifications
Detail
Design
Code & Unit
Test
Integration
Test
System Test
Acceptance
Testing

21.  Function Testing
 User Interface Testing
 Business Cycle Testing
 View Testing
 Security and Access Control
 Performance Testing
5. SOFTWARE TESTING
5.2 Features To Be Tested

22. 5. SOFTWARE TESTING
5.3 Test Execution
Start Submit Review
In
progress
Open
Fixed
Valid
Finish
Close
Review Valid
Yes
No
Yes
No

23. 5. SOFTWARE TESTING
5.4 Test Report
5.5 Bug Report

24. 6. Q & A

25. Thanks for listening