MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

SHRI H. H. J. B POLYTECHNIC,
CHANDWAD-423101 (Nashik)

MICRO PROJECT
Academic year 2024-25

TITLE OF PROJECT
Mobile Shop Management System

Program: Computer Technology Program Code:CM

Course: Software Testing Course code

 Teacher Evaluation Sheet
Name of Student: Jamdhade Neha Anil
Enrolment No: 2200790153
Name of Program: Computer Technology Semester:-5I
Course Title: Software Testing Code: -22518
Title of the Micro Project: Mobile Shop Management System

Course Outcomes Achieved:-

CO-a Apply various software testing methods.

CO-b Prepare test cases for different types and levels of testing.
CO-c Prepare test plan for an application.
CO-d Identify bugs to create defect report of given application.
CO-e Test software for performance measures using automated testing tools.
Evaluation as per Suggested Rubric for Assessment of Micro-Project:
Sr. No.
Characteristic to be Poor Average Good (Marks Excellent (Marks 9-
assessed (Marks 1-3) (Marks 4-5) 6 - 8) 10)
(A) Process and Product Assessment (Convert above total marks out of 6 marks)

1 Relevance to the Course

Literature Survey /
2
Information Collection
Completion of the Target as per
3
project proposal
Analysis of data and
4
representation
5 Quality of Prototype / Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 marks)

8 Presentation
9 Viva
Micro – Project Evaluation Sheet:
Process Assessment Product Assessment
Part A Project Part B – Individual Total
– project Methodology Project Presentation / Marks 10
Name of Student Proposal (2 marks) Report / Working Viva (4 marks)
(2 marks) Model(2 marks)
Jamdhade Neha Anil
Any Other Comment

Name and designation of faculty member: Mr.G.M.Lodha Signature

 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Sr.No. Name of Student Roll No Enrollment No Seat No

1. Jamdhade Neha Anil 29 2200790153 390753

CERTIFICATE
This is to certify
1)Jamdhade Neha Anil of 5th Semester of Diploma in Computer Technology
of Institute, SHHJB POLYTECHNIC, CHANDWAD (Code: 0079) has
completed the Micro-Project
satisfactorily in Subject Software Testing (22518) for the academic year 2024-
2025 as prescribed in the curriculum.

Place: CHANDWAD
Date:

Subject Teacher Head of the Department Principal

(Mr.G.M.Lodha) (Mr.P.R.Sali) (Dr. V.A.Wankhede)

3
 INDEX

SR_NO. CONTENT PAGE NO.

Part A

1.0 Brief Introduction 5

2.0 Aim of Micro Project 5

3.0 Action Plan 6

4.0 Resources Required 6

Part B

1.0 Brief Description 7

2.0 Aim of Micro Project 7

3.0 Course Outcome Integrated 7

4.0 Actual Procedure Followed 7

5.0 Actual Resource Used 14

6.0 Skill Developed 14

7.0 Applications of this Microproject 14

4
 PART A-Plan

Title of micro-project: Mobile Shop Management system

1.0Aim/Benefits of the Micro-Project-

The primary aim of the Mobile Shop Management System is to create a user-friendly mobile
application that streamlines the management of retail operations for small businesses.
This system is designed to facilitate better inventory management, sales tracking, customer
relationship management, and overall operational efficiency

2.0 Course Outcomes Addressed-

a)Apply various software testing methods.
b)Prepare test cases for different types and levels of testing.
c)Prepare test plan for an application.
d)Identify bugs to create defect report of given application.
e)Test software for performance measures using automated testing tools.

3.0 Action Plan-

Sr no. Details of activity Planned Start Planned Finish
Date Date
1. Finalization of topic 25-07-2024 01-08-2024

2. Preparation of Abstract 01-08-2024 08-08-2024

3. Collection of data 20-08-2024 25-08-2024

4. Preparation of concept 05-09-2024 29-09-2024

5. Submission of Micro Project -11-2024 -11-2024

4.0 Resources Required:

Sr.No Name of Resource/Material Specification Quantity Remarks

1. Computer (Desktop/Laptop) i3,RAM 2GB 1 Available
2. Microsoft office word 2010 1 Available
3. Books - -
4. Websites - - -

PART B-Plan
5
 Title of micro-project: Mobile Shop Management System

1.0 Brief Description:

The Mobile Shop Management System is an innovative platform designed to streamline
the shopping experience for both customers and retailers. It integrates features like
product browsing, inventory management, order processing, and customer feedback, all
accessible via a user-friendly mobile interface. This system enhances efficiency by
automating tasks, allowing retailers to manage their stock in real time while providing
customers with a seamless shopping journey. With secure payment options and
personalized recommendations, it aims to boost sales and customer satisfaction in the
competitive e-commerce landscape.

2.0 Aims/Benefits of Micro Project:

The Mobile Shop Management System aims to enhance the shopping experience for
customers while streamlining retail operations. Its intuitive interface simplifies product
browsing and purchasing, while real-time inventory management helps retailers
monitor stock levels effectively. The system boosts sales efficiency with streamlined
order processing and secure transactions, and it offers data-driven insights for informed
decision-making. Personalized recommendations engage customers, while its cost-
effective automation reduces manual tasks. Scalable and accessible on multiple
devices, the system allows for growth and flexibility. Additionally, it facilitates
customer feedback collection, enabling retailers to refine their offerings and improve
satisfaction.

3.0 Course Outcomes Achieved:

a)Apply various software testing methods.
b)Prepare test cases for different types and levels of testing.
c)Prepare test plan for an application.
d)Identify bugs to create defect report of given application.

4.0Actual Methodology/Procedure Followed:

4.1 Unit Testing

 Objective: Verify that individual components function correctly in isolation.
 Key Areas:
1. Product Management:
 Test functions for adding, updating, deleting, and retrieving products.
2. User Management:
 Test user registration, profile updates, and login validation.

6
 3. Order Management:
Verify functions for placing, updating, and cancelling orders.

4. Cart Management:
 Test adding/removing items from the cart and calculating totals.
 Integration Testing
 Objective: Validate interactions between modules.
 Focus Areas:
Test interactions between user management, product management, and order management
modules.
Ensure smooth data flow between payment gateways and the order system.
4.2 System Testing
 Objective: Validate the complete application as a cohesive unit against specified requirements.
 Key Focus Areas:
1. End-to-End Functionality:
Test workflows like user registration, product browsing, placing orders, and payment
processing.
2. Integration:
 Verify that all integrated modules (e.g., payment systems, notifications) work seamlessly
together.
3. Usability:
 Evaluate the user interface for intuitiveness, navigation, and accessibility.
4. Security:
 Conduct tests for vulnerabilities, ensuring secure user authentication and data protection.
4.3 Performance Testing:
 Objective: Assess responsiveness, stability, and scalability under various load conditions.
 Key Focus Areas:
1. Load Testing:
Simulate multiple concurrent users to evaluate system performance during peak usage
(e.g., product searches, order placements).
2. Stress Testing:
Push the system beyond normal limits to identify breaking points and recovery
mechanisms.

7
 3. Response Time Measurement:
Measure the time taken for key operations.
4. Scalability Testing:
 Assess how well the system accommodates increasing numbers of users or transactions.
4.4 White Box Testing:
 Objective: Test the internal structures or workings of the application.
 Key Aspects:
1. Code Coverage:
 Evaluate how much of the code is executed during testing, ensuring all paths, branches,
and conditions are tested.
2. Functionality Testing:
 Examine internal functions and algorithms, such as payment processing and inventory
management.
3. Data Flow Testing:
 Assess how data moves through the system to identify any potential bottlenecks.
4. Control Flow Testing:
 Analyze control structures (e.g., loops, conditionals) to ensure they perform correctly
under various conditions.
4.5 Black Box Testing
 Objective: Evaluate the system's functionality without knowledge of its internal code structure.
 Key Aspects:
1. Functional Testing:
 Verify user-facing features, such as browsing products, adding to cart, and completing
purchases.
2. User Interface Testing:
 Assess usability and accessibility of the app interface, ensuring intuitive navigation.
3. Boundary Testing:
 Test system behavior at input value limits, such as the maximum number of items in a
cart.
4. Error Handling:
 Validate system responses to invalid inputs or unexpected actions, ensuring appropriate
error messages are displayed
5. Test cases:-

8
 5. Test cases:-
Test Case ID Test Case Name Actual Result Expected Result Status
TC001 User Registration User registered User registered Passed
with Valid Details successfully successfully
TC002 User Registration Error message Error for Passed
with Duplicate displayed duplicate email
Email should be shown
TC003 User Login with User logged in User should be Passed
Valid Credential successfully logged in
TC004 User Login with Error message Error for invalid Passed
Invalid Password displayed password should be
show
TC005 Product Search Search results Relevant products Passed
Functionality displayed should be displayed
TC006 View Product Detail Product details Details should Passed
displayed match the selected
produc
TC007 Add Product to Car Product added to Product should be in Passed
cart successfully the car
TC008 Remove Product Product removed Cart should not Passed
from Car from car show the removed
produc
TC009 Proceed to Checkout page Checkout page Passed
Checkout displayed should ope
TC010 Place an Orde Order confirmation Order should be Passed
displayed confirme
TC011 View Order Histor Order history Past orders should Passed
displaye be visible
TC012 Update Account Account details Changes should be Passed
Detail update saved successfull
TC013 Reset Password Reset link sent to Confirmation Passed
email message for reset
link should show
TC014 Payment Processing Payment processed Payment should be Passed
with Valid Details successfully confirmed
TC015 Payment with Error message Payment failure Passed
Invalid Details displayed error should be
shown
TC016 User Logout User logged out User should be Passed
successfully logged out
TC017 App Response to Warning message Warning for low Passed
Low Battery displayed battery should be
shown
TC018 Notifications for Notifications User should receive Passed
Orders received notifications for
updates
TC019 Filter Products by Products filtered Only selected Passed
Category successfully category products
should display
TC020 View App Settings Settings displayed App settings should Passed
be visible

9
 6.0 TEST SUMMARY PLAN:
Test Summary Plan for Mobile Shop Management System
1. Introduction
This test summary plan outlines the objectives, scope, methodologies, and deliverables for testing the
Mobile Shop Management System. The primary goal is to ensure that the application provides a
seamless, efficient, and secure shopping experience for users on mobile devices.
2. Objectives
 Validate all functionalities, including user registration, product search, and checkout.
 Ensure performance meets user expectations during peak loads.
 Confirm that the user interface is intuitive and user-friendly.
 Identify and resolve defects to enhance user satisfaction and system reliability.
3. Scope
 In-Scope:
o User Registration and Login: Test the process for creating and managing user accounts.
o Product Search and Display: Verify the effectiveness of product searches and accurate display of
product details.
o Shopping Cart: Validate adding, updating, and removing products from the cart.
o Checkout Process: Test the complete flow from cart to order confirmation, including payment
processing.
o Order Management: Check the functionalities related to viewing order history and notifications.
o User Account Management: Test profile updates, password resets, and security features.
 Out of Scope:
o Desktop or web versions of the application.
o Integration with external marketing tools and analytics beyond essential functionalities.
4. Testing Methodologies
 Unit Testing: Validate individual modules like user registration and product management.
 Integration Testing: Ensure seamless interaction between components such as the payment gateway
and inventory database.
 System Testing: Conduct end-to-end testing of the entire application to verify compliance with
requirements.
 User Acceptance Testing (UAT): Involve real users to confirm that the system meets their shopping
needs and preferences.
 Performance Testing: Assess the app’s responsiveness under varying loads, especially during peak
shopping times (e.g., sales events).
 Security Testing: Test for vulnerabilities, ensuring user data is secure and protected during transactions.
5. Test Deliverables
 Test Cases Document: Detailed test cases covering all functionalities of the Mobile Shopee
Management System.
 Test Data: Sample data for executing test cases, including user profiles and product listings.
 Test Execution Reports: Reports documenting the results of executed test cases, including pass/fail
status.
 Defect Reports: Documentation of identified defects with severity levels and status updates.
 Test Summary Report: A comprehensive report summarizing testing results, overall quality metrics,
and readiness for deployment.

6.Resources
 Testing Team: List of QA engineers and their roles (e.g., Test Lead, Test Engineer).
10
 Tools: Automation tools (e.g., Selenium, Appium), defect tracking tools (e.g., JIRA), and performance
testing tools (e.g., JMeter).
8. Risks
 Potential delays in development impacting the testing timeline.
 High volume of user traffic leading to performance bottlenecks.
 Unanticipated defects that may extend the testing phase.
9. Conclusion
This Test Summary Plan serves as a strategic guide for ensuring the quality and functionality of the
Mobile Shopee Management System. By following this plan, the team aims to deliver a high-quality
application that meets user needs and enhances the overall shopping experience.

7.0 Defect Report:-

Defect report

Defect id

Title Payment Gateway Failure

Description Payment processing fails for valid credit card

Steps to Replicate 1. Add item to cart

2. Proceed to checkout
3. Enter valid credit card details
4. Click 'Pay'
5. Observe failure message

Expected Payment should be processed successfully

Result

Actual Result

Severity Critical

Priority High

Reported by

Assigned to

Status Open

8.0 Actual Resources Used:

11
 Sr.No Name of Resource/Material Specification Quantity Remarks
1. Computer (Desktop/Laptop) i3,RAM 2GB 1 Available
2. Microsoft office word 2010 1 Available
3. Books - -
4. Websites - - -
5. Software’s Notepad 1 Available

6.0 Skill Developed:

1. Problem-Solving Skills
2. Software Development
3. Database Management
4. User Interface (UI) and User Experience (UX) Design
5. Testing and Debugging
6. Project Management

7.0 Applications of this Micro project:

 User Account Management:
The system includes features for user registration, profile management, and order history tracking,
enhancing user engagement and personalized shopping experiences.
 Product Management:
Enables efficient management of product listings, including adding, updating, and removing products,
ensuring that users have access to the latest inventory.
 Payment Processing:
Integrates secure payment gateways for processing transactions, ensuring a safe and reliable payment
experience for users.
 Order Fulfillment:
Streamlines the order fulfillment process, allowing users to receive real-time updates on order status,
shipping, and delivery.

12