JSPM’s

JAYWANTRAO SAWANT POLYTECHNIC

DEPARTMENT OF COMPUTER ENGINEERING

MICRO PROJECT
Academic year: 2024-25

TITLE OF PROJECT

Design Test Cases for Amazon Purchase Order

Management

Program: CO Program code: CO5I

Course: Software Testing Course code: 22518
Class: TYCO-2

Submitted By:
1.
2.
3.
Guided By:
Mrs.K.M.Shirole
 DEPARTMENT OF COMPUTER
ENGINEERING

MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
Certificate
This is to certify that

Mr/Ms . , Roll No: of Semester Fifth of Diploma in

Computer Engineering of Institute, JS POLYTECHNIC (Code:0711) has completed the
Micro Project satisfactorily in Subject- Software Testing (22518) for the academic year
2024- 2025 as prescribed in the curriculum.

Place: Hadapsar, Pune Enrollment No:

Date: Exam Seat No:

Subject Teacher Head of the Department Principal

 JSPM’s
JAYAWANTRAO SAWANT POLYTECHNIC,
Handewadi Road, Hadapsar, Pune-28
Department of Computer Engineering
Academic Year 2024-25
Teacher Evaluation Sheet
Name of student: Enrollment No:

Name of program: Computer Engineering Semester: Fifth

CourseTitle: Software Testing Code: 22518

Title of Micro Project: Design Test Cases for Amazon Purchase Order
Management

Brief Description:
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
……………

Aims/Benefits of the Micro-Project:

…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
………………
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.
 e. Test software for performance measures using automated testing tools.

Action Plan:
Sr. Details of activity Planned Planned Name of
No start date Finish date Responsible
Team
members
1 Introduction
2 Test Cases
3 Outputs of the Micro
Projects
4 Advantages /
Disadvantages
5 References
6 Conclusion

Actual Resources Used:

Sr. Name of resource / material Specification Quantity Remarks

No
.

Evaluation as per suggested Rubric for Assessment of Micro Project

Sr. Characteristic to be Poor Average Good Excellent
No assessed (Marks1- 3) (Marks 4 -5) (Marks 6 - (Marks 9 -
8) 10)
1 Relevance to the course
2 Literature Survey /
Information collection
3 Project Proposal
4 Completion of the Target as
per Project Proposal
5 Analysis of data and
representation
6 Quality of Prototype/
Model
7 Report preparation
8 Presentation
 9 Defense

Micro Project Evaluation Sheet

Process Assessment Product Assessment Total
Marks
Part A - Project Par B - Project Individual
Project Methodology Report/ working Presentation/ 10
Proposal Model Viva
(2 Marks)
(2 Marks) (2 Marks) (4 Marks)

Note: Every course teacher is expected to assign marks for group evaluation in first 3
columns and individual evaluation 4th column
Comment/ suggestion about team work/leadership/ interpersonal communication (If
any)
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
………………………………………
…………………………………………………………………………………………………………………………………………
……………
Any other comment:
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
…………………………………………………………………………………………………………………………………………
………
Name of the Faculty Member: Mrs.K.M.Shirole

Signature: ………………………….

Install operating system and

configure it.
b) Use operating system tools
to perform various functions.
c) Execute process commands
for performing process
management technique.
d) Apply scheduling algorithm
to calculate turnaround time
and average waiting time.
e) Calculate efficiency of
different memory
management technique.
f) Apply file management
technique.
Install operating system and
configure it.
b) Use operating system tools
to perform various functions.
c) Execute process commands
for performing process
management technique.
d) Apply scheduling algorithm
to calculate turnaround time
and average waiting time.
e) Calculate efficiency of
different memory
management technique.
f) Apply file management
technique.
Install operating system and
configure it.
b) Use operating system tools
to perform various functions.
c) Execute process commands
for performing process
management technique.
d) Apply scheduling algorithm
to calculate turnaround time
and average waiting time.
e) Calculate efficiency of
different memory
management technique.
f) Apply file management
technique.
 Acknowledgment

We would like to express our special thanks of gratitude to our subject teacher
Mrs. K.M.Shirole as well as our principal sir and HOD sir who gave us the golden
opportunity to do this wonderful Report on the topic of Design Test Cases for
Amazon Purchase Order Management which also helped us doing lot of
Research and we came to know about so many new things related to software
testing we are really thankful to them.
 JAYAWANTRAO SAWANT POLYTECHNIC,
Handewadi Road, Hadapsar, Pune-28
Academic Year 2024-2025

INDEX

Sr.No Title Page No.

1 Introduction

2 Diagram

3 Test Cases

4 Outputs of the Micro Projects

5 Advantages / Disadvantages

6 References

7 Conclusion

INTRODUCTION
Diagram
Test Cases
Outputs of the Micro Projects
 Advantages / Disadvantages
Advantages:

1. Saves Money

First and foremost, software testing saves money. Software development and implementation
involve several stages. Each stage demands coordination and communication between multiple
teams and every stage has a laundry list of ways that things could go wrong.
Catching those problems once the software is already live is a nightmare. You have to handle
PR while retasking employees to scramble and fix the problem. And in the meantime, your
would-be customers can’t use your software.
 So you’re not just losing money on the direct cost of fixing the software. You’re also losing
money through lost potential transactions. Software testing allows you to catch problems early
and fix them before they become PR disasters.

2. Inspires Customer Confidence and Satisfaction

Let’s say you’re a customer who’s just downloaded a new software program. But when you try
to launch the program or log in, you get an error message. Not only have you wasted money on
a program that doesn’t work, but now you also have to decide whether to hedge your bets and
see if the software is worth waiting for or take your business elsewhere. Chances are, most
customers aren’t willing to forgive that sour taste in their mouth.
By investing in quality assurance early, you’re sending a message to your customers that you
care about their experience. You want them to get everything they hoped for and more. And
that message is critical in forming long-term customer relationships.

3. Improves Security

You see, when your software fails, you’re not just sacrificing your customer experience.
You’re also sacrificing software security. That means that every customer who uses your
software has now put their data and systems at risk. And with all the major data privacy
scandals last year (Cambridge Analytica, anyone?) customers aren’t willing to risk their data
twice.
With software testing, you can deliver a safe, trustworthy product to your customers from Day
One. It protects their critical information, cements their trust, and reduces the risk of expensive
embarrassments later on.

4. Improves Product Quality

Finally, in case you hadn’t guessed yet, software testing improves your overall product quality.
Companies may know the benefits of Software-as-a-Service (SaaS), but they won’t invest in
SaaS if the product is subpar. After all, they have customers to keep happy just as much as you
do.

Disadvantages:

Black Box Testing:

Only limited coverage of application as the tester cannot target specific code segment
Test cases are difficult to design as the tester doesn’t have prior knowledge on specifications
and coding Some possible inputs will only be tested.

White Box Testing:

Requires highly skilled testers and debugging tools
Results will be more efficient but according to resources it may become expensive
Even though all paths of the source code will be covered there may be a chance of missing to
find out hidden errors.

Grey Box Testing:

As there is no full access of source code, the tester can able to cover a limited area of the
software application There may be a chance of occurring redundant if the designer already
starts the test case
The major disadvantage is that software product cannot be tested fully as there are limitations

Reference
Conclusion