MAHARASHTRA STATE BOARD OF TECHNICAL

EDUCATION
NAVJEEVAN EDUCATION SOCIETY’S
POLYTECHNIC BHANDUP(W)

MICRO PROJECT

ACADEMIC YEAR 2024-2025

Subject: Emerging Trends In Computer(22618)

3
 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

CERTIFICATE
This is to certify that Ms. Siddhi Pashte(1355), Mr. Aditya Sakpal (1356), Mrs.
sudhanshu Muneshwar (1357) of Fourth semester of diploma in Computer
Engineering , of institute NAVJEEVAN EDUCATION SOCIETY’S POLYTECHNIC
(Code : 0144) has completed the project work satisfactorily inEmerging Trend computer
22618)for the academic year 2024 to 2025 as prescribed in theComputer
curriculum.

Place : Bhandup Enrolment number: 23111050056

23111050057
23111050059
Date :
Subject Teacher Principal Head of department

Seal of Institute

5
 Micro Project Report

Title:- Performance Testing

1.0 Retionale:

Performance Testing is a software testing process used for testing the speed, response
time, stability, reliability, scalability and resource usage of a software application under
particular workload. The main purpose of performance testing is to identify and eliminate
the performance bottlenecks in the software application. It is a subset of performance
engineering and also known as “Perf Testing”.

2.0 Aims/Benefits of the Micro-Project:

The goal of Performance Testing is not to find bugs but to eliminate performance
bottlenecks.

3.0 Course Outcomes Achieved :

• List a range of different software testing techniques and statergies and be able to
apply
• Distinguish characteristics of structural testing methods
• Demonstrate the integration testing which aims to uncover interaction and
compatibility problems as early as possible.
• Discuss about the functional and system testing methods
• Demonstrate various issues for object oriented testing.

4.0Literature review:

1. Test reporting in the mean of communicating the result of testing.

2. the test reports are designed to document the result of testing as defined in the test
plan.

3.without a well- developed test plan it is difficult to developed a meaningful test report.

4.A test report is designed to accomplish three objectives .

• define the scope of testing.

• . Present the result of testing.

• .Draw Conclusion and make recommendation based on those result.

5.0 Actual Methodology Followed:

Purpose of the document

The main purpose of performance testing is to identify and eliminate the performance
bottlenecks in the software application.
Application overview
Better development process beings with a better testing process. To advance in software
development and design, enterprises need to improve their testing capabilities. The testing
needs of an app changes throughout it's development cycle.

About Performance Testing

Features and Functionality supported by a software system is not the only concern. A
software application’s performance like its response time, reliability, resource usage and
scalability do matter. The goal of Performance Testing is not to find bugs but to eliminate
performance bottlenecks.

Performance Testing is done to provide stakeholders with information about their

application regarding speed, stability, and scalability. More importantly, Performance
Testing uncovers what needs to be improved before the product goes to market. Without
Performance Testing, software is likely to suffer from issues such as: running slow while
several users use it simultaneously, inconsistencies across different operating systems and
poor usability.
Performance Testing Process:
The methodology adopted for performance testing can vary widely but the objective for
performance tests remain the same. It can help demonstrate that your software system
meets certain pre-defined performance criteria. Or it can help compare the performance
of two software systems. It can also help identify parts of your software system which
degrade its performance.

Below is a generic process on how to perform performance testing

Identify your testing environment – Know your physical test environment, production
environment and what testing tools are available. Understand details of the hardware,
software and network configurations used during testing before you begin the testing
process. It will help testers create more efficient tests. It will also help identify possible
challenges that testers may encounter during the performance testing procedures.

Identify the performance acceptance criteria – This includes goals and constraints for
throughput, response times and resource allocation. It is also necessary to identify project
success criteria outside of these goals and constraints. Testers should be empowered to set
performance criteria and goals because often the project specifications will not include a
wide enough variety of performance benchmarks. Sometimes there may be none at all.
When possible finding a similar application to compare to is a good way to set
performance goals.

Plan & design performance tests – Determine how usage is likely to vary amongst end
users and identify key scenarios to test for all possible use cases. It is necessary to simulate
a variety of end users, plan performance test data and outline what metrics will be
gathered.

Configuring the test environment – Prepare the testing environment before execution.
Also, arrange tools and other resources.

Implement test design – Create the performance tests according to your test design.

Run the tests – Execute and monitor the tests.

Analyze, tune and retest – Consolidate, analyze and share test results. Then fine tune and
test again to see if there is an improvement or decrease in performance. Since
improvements generally grow smaller with each retest, stop when bottlenecking is caused
by the CPU. Then you may have the consider option of increasing CPU power.
Types of Performance Testing:
Load Testing:

Load testing helps developers understand the behavior of a system under a specific load
value. In the load testing process, an organization simulates the expected number of
concurrent users and transactions over a duration of time to verify expected response
times and locate bottlenecks. This type of test helps developers determine how many
users an application or system can handle before that app or system goes live. Additionally,
a developer can load test specific functionalities of an application, such as a checkout cart
on a webpage. A team can include load testing as part of a continuous integration (CI)
process, in which they immediately test changes to a code base through the use of
automation tools, such as Jenkins.
Stress Testing:

Stress testing places a system under higher-than-expected traffic loads so developers can
see how well the system works above its expected capacity limits. Stress tests have two
subcategories: soak testing and spike testing. Stress tests enable software teams to
understand a workload's scalability. Stress tests put a strain on hardware resources in
order to determine the potential breaking point of an application based on resource usage.
Resources could include CPUs, memory and hard disks, as well as solid-state drives. System
strain can also lead to slow data exchanges, memory shortages, data corruption and
security issues. Stress tests can also show how long KPIs take to return to normal
operational levels after an event. Stress tests can occur before or after a system goes live.
A kind of production-environment stress test is called chaos engineering and there are
specialized tools for it. An organization might also perform a stress test before a
predictable major event, such as Black Friday on an e-commerce application,
approximating the expected load using the same tools as load tests.
Security Testing:
Security Testing is a type of Software Testing that uncovers vulnerabilities, threats, risks in
a software application and prevents malicious attacks from intruders. The purpose of
Security Tests is to identify all possible loopholes and weaknesses of the software system
which might result in a loss of information, revenue, repute at the hands of the employees
or outsiders of the Organization.
Client-Server Testing:
In Client-server testing there are several clients communicating with the server.

1. Multiple users can access the system at a time and they can communicate with the
server.
2. Configuration of client is known to the server with certainty.
3. Client and server are connected by real connection.
4. Testing approaches of client server system:

• Component Testing: One need to define the approach and test plan for testing
client and server individually. When server is tested there is need of a client
simulator, whereas testing client a server simulator, and to test network both
simulators are used at a time.
• Integration testing: After successful testing of server, client and network, they are
brought together to form system testing.
• Performance testing: System performance is tested when number of clients is
communicating with server at a time. Volume testing and stress testing may be
used
for testing, to test under maximum load as well as normal load expected. Various
interactions may be used for stress testing.
• Concurrency Testing: It is very important testing for client-server architecture. It
may be possible that multiple users may be accessing same record at a time, and
concurrency testing is required to understand the behavior of a system in this
situation.
• Disaster Recovery Business continuity testing: When the client server are
communicating with each other , there exit a possibility of breaking of the
communication due to various reasons or failure of either client or server or link
connecting them. The requirement specifications must describe the possible
expectations in case of any failure.
• Testing for extended periods: In case of client server applications generally server is
never shutdown unless there is some agreed Service Level Agreement (SLA) where
server may be shut down for maintenance. It may be expected that server is
running 24X7 for extended period. One needs to conduct testing over an extended
period to understand if service level of network and server deteriorates over time
due to some reasons like memory leakage.
• Compatibility Testing: Client server may be put in different environments when the
users are using them in production. Servers may be in different hardware, software,
or operating system environment than the recommended. Other testing such as
security testing and compliance testing may be involved if needed, as per testing
and type of system.
6.0Actual Resources Used:

Sr Name of Resource/ Material Specification QTY Remark

No
1)
Computer i3 processor windows 1
10 RAM 8GB
2)
Operating system Windows 7/linux 1
Version 5 or later

8.0 Skill Develop/ Learning outcome of this micro Project:

1. Planning and documentation.

2. Think analytically and logically.

3. Defect tracking and reported the bugs.

4. Creating test cases and test scenarios.

5. Applying testing tools and technologies.

6. Time management.

7. Team work.

8. Problem solving

9.0 Application of this Micro Project:

It is used to study the testing and it's process of different software.
 Evaluation Sheet for the Micro Project
Name of Program: - TY.COM Semester: - CO6I
Course Title: - Emerging Trends in Computer Code: - 22618
Title of Micro Project: - Mobile Phones and Cloud Computing

Course Outcomes Achieved:

• Understanding Mobile Technologies – Gained knowledge of mobile phone

architectures, operating systems, and communication protocols.
• Cloud Computing Concepts – Understood the fundamentals of cloud
computing, including SaaS, PaaS, and IaaS models.

• Integration of Mobile and Cloud Computing – Explored how mobile

applications leverage cloud computing for storage, processing, and scalability.

• Security and Privacy in Mobile-Cloud Systems – Analyzed security challenges

and best practices in mobile cloud environments.

Identify box to create defect report of given application.

Poor Average Good Excellent

Sr
Characteristics to be assessed (Marks 1- (Marks4- (Marks 6- (Marks 9-
No
3) 5) 8) 10)
1 Relevance to the course
2 Literature survey / Information collection
Completion of the target as per project
3
proposal
4 Analysis of data and representation
5 Quality of prototype / Model
6 Report Presentation
(A) Process and Product Assessment (Convert above total marks out of 6 marks)
8 Presentation
9 Viva
(B) Individual Presentation /Viva (Convert above total marks out of 4 marks)
 (A)
(B) Individual Presentation / Viva Total
Process and Product Assessment
(4 marks) marks 10
(6 marks)

Comments/Suggestions above team work/leadership/inter-personal communication (if any)

Name and designation of the Teacher:-

Date Signature:-