This project is read-only.

Appendix C - Glossary

Non-Functional (Attributes, Requirements and Tests)

Aliases: Para-functional, extra-functional.

Product Development Team

The team or organization that includes the people who have the technical skills to develop the product. Includes anyone involved in developing the product, not just software developers.

Product Owner

The person responsible for the business success of the product including ensuring that the product is fit for purpose.
Aliases: Customer

Sequential development

Aliases: Waterfall, plan-driven, tayloristic, staged, phased

Whole Team

The team consisting of everyone involved in defining, building and verifying the product or solution. Includes the Product Development Team, the Product Owner and anyone supporting/helping the Product Owner (including interaction designers and acceptance testers) or the Product Development Team (including documentation writers, architects, etc.)

Test Plan

A more detailed (than the Test Strategy) plan for how testing will be performed.

Test Strategy

The overall approach to how the data required to make the readiness and acceptance decisions will be gathered in a cost-effective manner. Includes the decisions around what kinds of testing to perform, what kinds of test automation will be used, where testing will be done, at what point in the project, etc.. Decisions that have large impact on the cost and duration of the acceptance process belong in the test strategy.

Acceptance Test Synonyms

Term Introduced/Used in
“acceptance tests” e.g. FDA [121]
“functional tests” Beck, Extreme Programming Explained, 1/e [11]
“user acceptance tests”|
“business acceptance tests”|
“customer tests” Jeffries [61],Beck, Extreme Programming Explained, 2/e
“customer-inspired tests” Beck, Extreme Programming Explained, 1/e [11]
“story-tests” and “story-test-driven development” Kerievsky [91]
“specification by example” Fowler [41]
“coaching tests” Marick [111]
“examples”, “business-facing example”, and “example-driven-development” Marick [101]
“conditions of satisfaction” Cohn [21]
“scenario tests” Kaner [81]
“keyword-driven test” Kaner, Bach, Pettichord [7]]
“formal qualification tests” e.g. DOD [31]
“system tests” e.g. IEEE [51]


Beck, K. Extreme Programming Explained: Embrace Change, 1/e. Addison-Wesley, Boston, MA, 1999.
Cohn, M. “Do-It-Yourself”, Better Software, 7(9): 18–22, 2005.
Department of Defense. Military Standard Defense System Software Development DOD-STD-2167, section.5.3.3. Online:
Fowler, M. “Specification by Example”. Online:
Institute of Electrical and Electronics Engineers. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990.
Jeffries, R. “What is XP?” Online:
Kaner, C., Bach., J., Pettichord, B. Lessons Learnt in Software Testing : A Context-Driven Approach. John Wiley & Sons, New York, NY, 2001.
Kaner, C. “Cem Kaner on Scenario Testing: The Power of ‘What-If…’ and Nine Ways to Fuel Your Imagination”, Better Software, 5(5):16–22, 2003.
Kerievsky, J. “Storytesting”. Online:
Marick, B. “Example-Driven Development”. Online:, and
Marick, B. Agile Acceptance Testing Workshop Report, XP/Agile Universe 2002 Conf. Online:
FDA General Principles of Software Validation

Last edited Nov 7, 2009 at 2:23 AM by rburte, version 1


No comments yet.