LinkedIn

See our LinkedIn profile, click on this button:

APDEX

Apdex-G Section [6] References

I’m writing a series of posts about Generalizing Apdex. This is #20. To minimize confusion, section numbers in the current spec are accompanied by the section symbol, like this: §1. The corresponding section numbers in the generalized spec, Apdex-G, are enclosed in square brackets, like this: [1].

I have been working systematically through the process of generalizing the current Apdex spec. Along the way, I have been skipping over parts of the current spec to work on the paragraphs that presented challenges. I am now going back to fill in those less contentious paragraphs, posting updated drafts of each section of the Apdex-G spec. The first five are Section [1] Introduction, Section [2] Index Overview, Section [3] Calculation Inputs, Section [4] Calculating the Index, and Section [5] Reporting; today I continue with Section [6] References.


Summary

In this section, I have retained the original references from Apdex section §6, added four new ones, and introduced headings to show which sections the references relate to.

Because this material includes some drafts posted previously, some of which I have edited, everything in this series of posts is considered the second draft of Apdex-G.

Apdex, current spec:

Apdex-G, second draft:

§6. References

  1. “Defining The Application Performance Index,” by Peter Sevcik, Business Communications Review, March 2005. This is a comprehensive overview of Apdex and the formation of the Apdex Alliance.
  2. “Understanding How Users View Application Performance,” by Peter Sevcik, Business Communications Review, July 2002. Describes the three zones of performance.
  3. “This Is Your Father’s Performance After All!,” by Peter Christy, published in Business Communications Review, November 2002. This is a rebuttal from Peter Christy on reference 2.
  4. “How Fast is Fast Enough?,” by Peter Sevcik, Business Communications Review, March 2003. This article continues the discussion in references 2 and 3 above of user perception of application response time.

[6] References

Section 1

[6.1] “Defining The Application Performance Index,” by Peter Sevcik, Business Communications Review, March 2005. This is a comprehensive overview of Apdex and the formation of the Apdex Alliance.
[Download: pdf at netforecast.com]

[6.2] “Understanding How Users View Application Performance,” by Peter Sevcik, Business Communications Review, July 2002. Describes the three zones of performance.
[Download: pdf at netforecast.com]

[6.3] “This Is Your Father’s Performance After All!,” by Peter Christy, published in Business Communications Review, November 2002. This is a rebuttal from Peter Christy on reference 2.
[Download: article at allbusiness.com]

[6.4] “How Fast is Fast Enough?,” by Peter Sevcik, Business Communications Review, March 2003. This article continues the discussion in references 2 and 3 above of user perception of application response time.
[Download: article at allbusiness.com (but without images)]

Section 2

[6.5] “The Zone of Tolerance,” by Robert Johnston, International Journal of Service Industry Management, Vol 6, No 2 1995. This paper reviews literature on service quality and in particular the zone of tolerance, the zone of acceptable or expected outcomes in a service experience. “The importance of the zone of tolerance is that customers may accept variation within a range of performance and any increase in performance within this area will only have a marginal effect on perceptions. It is only when performance moves outside of this range that it will have any real effect on perceived service quality.”
[Download: pdf ]

Section 4

[6.6] “The Apdex Index Revealed,” by Neil J. Gunther, CMG MeasureIT, February 2009. This paper reviews the Apdex metric in detail, explaining the basis for the formula, discussing some criticisms, and possible enhancements.
[Download: paper at www.cmg.org]

Section 5

[6.7] “RFC 4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files,” by Y. Shafranovich, The Internet Society, October 2005. The Apdex Uniform Output format incorporates the IETF specification of CSV published in RFC 4180.
[Download: tools.ietf.org]

[6.8] “Interval Notation,” by Y. Shafranovich, Zonaland Education. Interval notation is a method of writing down a set of numbers. The Apdex Uniform Output format employs a scheme based on interval notation to describe performance intervals, ranges of input values that correspond to common satisfaction levels.
[Download: article at zonalandeducation.com]

Next Steps …

This completes my second draft. I will begin work on Apdex-R, the addendum addressing measurements of response times. Apdex-R will cover all the domain-specific content of the current spec that has been excised from Apdex-G. I am postponing work on Section [7] Glossary until I have completed a draft of Apdex-R. If I want to record any new terminology, or edit previous definitions, I will amend my previous post, An Extensible Apdex Glossary.

As usual, all these proposals are open for public discussion. Please use the comment form below to contribute any comments, suggestions, or questions.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

  

  

  


*