Performance Acceptance Criteria
Performance Acceptance Criteria
based on the perspectives of system users, business owners of the system, and the
project team, in addition to compliance expectations and technological
considerations.
complementary performance acceptance criteria.
project as more information becomes available.
the perspectives of the system users, business owners of the system, and the project team,
as well as compliance expectations and technological considerations. This chapter
demonstrates how to blend and consolidate the information collected from these sources
into a single set of verifiable, complementary performance requirements and testing
objectives.
Determining the desired performance characteristics for a system from particular
perspectives is only the first part of determining the overall performance acceptance
criteria for that system. After examining the desired performance characteristics from
limited perspectives, you must resolve those characteristics against one another. For
example, end users may desire sub-second response time for every transaction; business
stakeholders may want the system to support millions of users; and compliance criteria
may mandate strict security policies.
Individually, any of these characteristics may be achievable, but collectively they may
not be possible due to time, technology, and/or budget constraints. Finding a way to
achieve these desired characteristics presents team-wide challenges that should be
addressed proactively, not reactively after conflicts become apparent through testing.
acceptance criteria based on the perspectives of system users, business owners of the
system, and the project team, and on compliance expectations and the technologies
involved. To get the most from this chapter:
·
performance-testing requirements and acceptance criteria that will facilitate
articulating terms correctly in the context of your project.