Scribd
Upload
18 views4 pages

Performance Guidelines

This document provides guidelines for ensuring performance requirements are met for applications. It outlines that: 1. Performance requirements will be determined early in the project and documented in key documents. 2. Tools will be used to test and validate that performance measures are met during development and after deployment. 3. A list of recommended tools is provided to test performance of websites, databases, and mobile applications. Ensuring performance helps reduce costs and issues.

Uploaded by

Dharm Pal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
18 views4 pages

Performance Guidelines

This document provides guidelines for ensuring performance requirements are met for applications. It outlines that: 1. Performance requirements will be determined early in the project and documented in key documents. 2. Tools will be used to test and validate that performance measures are met during development and after deployment. 3. A list of recommended tools is provided to test performance of websites, databases, and mobile applications. Ensuring performance helps reduce costs and issues.

Uploaded by

Dharm Pal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Performance Guidelines

All the information in this document is confidential and privileged information and related to
smartData Enterprise (I) Ltd. Data and Information provided only for smartData use only. Its
data and contents cannot reproduce without smartData concern and permission of smartData
authority. Any unauthorized review; use, disclosure or distribution is prohibited.

Revision History

Revised By Revised On Version Comments


Anurag Sethi 29 Oct 2016 1.0 Initial version of the
document

Table of Contents
1. OBJECTIVE ............................................................................................................................... 2

2. SCOPE .......................................................................................................................................2

3. Procedure.............................................................................................................................2

4 Performance Specification and


Implementation..........................................................................................2

1. Objective
Performance Guidelines

The objective includes the set of roles, skills, activities, practices, tools, and deliverables
applied at every phase of the systems development life cycle which ensures that a solution
will be designed, implemented, and operationally supported to meet the non-functional
requirements for performance (such as response time, throughput, latency, or memory
usage).

2. Scope
The scope of this document covers organizational level performance provided at different
level of project development lifecycle.

3. Procedure
 Performance level required in the application will be determined at time of BKO.
 Performance measures will be mentioned in PMP under NON-Functional
Requirements.
 Product owner confirms the Performance measures proposed by the Scrum
Master/Product Owner.
 Performance implementation is validated at the time of Board Review/Project
Review/SQA Audit.

4. Performance Specification and Implementation


Adherence to the non-functional requirements is also validated post-deployment by
monitoring the production systems.
 Increase business revenue by ensuring the system can process transactions within
the requisite timeframe
 Increase the usage of available frameworks/re-usable code/components not limited
to the ones developed internally to process the application in the requisite time
frame.
 Increase the usage of the various available tools to measure the application
performance
 Eliminate system failure requiring scrapping and writing off the system development
effort due to performance objective failure
 Eliminate late system deployment due to performance issues
 Eliminate avoidable system rework due to performance issues
 Eliminate avoidable system tuning efforts
 Avoid additional and unnecessary hardware acquisition costs
 Reduce increased software maintenance costs due to performance problems in
production
 Reduce increased software maintenance costs due to software impacted by ad hoc
performance fixes
Performance Guidelines

 Reduce additional operational overhead for handling system issues due to


performance problems
 Identify future bottlenecks by simulation over prototype

Tools to improve performance:


Please find the list of recommended tools for improving website, database and mobile application
performances. The tools mentioned here are in no way mandatory to be used to improve the
performance as they may vary from project to project based on client’s recommendations.

Development Type of Performance Tools Remarks


Type
Website Speed Test https://tools.keycdn.com/speed
Load Test Blaze meter Run massively scalable,
open source-based
performance tests
against all of your apps,
and validate
performance at every
software delivery stage.

Loader Load testing service


that allows you to
stress test your web-
apps & APIs with
thousands of
concurrent
connections. Free up to
10,000 clients.
Database Load Testing Tools Web Performance These tools are used to
Rad View put high usage loads on
Mercury your database, which
enables to determine
whether your system's
landscape will stand up
to your business needs.
Tools to perform Unit Testing SQL Unit These tools are used to
DB Unit perform regression
testing on your
database.
Mobile Apps Performance Blaze meter Run massively scalable,
open source-based
performance tests
against all of your apps,
and validate
performance at every
software delivery stage.
Performance Guidelines

You might also like