Атрибутыкачества (quality attributes
77
) расширяют собой нефункциональ-
ные требования и на уровне пользовательских требований могут быть представ-
лены в виде описания ключевых для проекта показателей качества (свойств про-
дукта, не связанных с функциональностью, но являющихся важными для достиже-
ния целей создания продукта — производительность, масштабируемость, восста-
навливаемость). Атрибутов качества очень много
78
, но для любого проекта реально
важными является лишь некоторое их подмножество.
72
User requirement. User requirements are general statements of user goals or business tasks that users need to perform. [
«Soft-
ware Requirements (3
rd
edition)
», Karl Wiegers and Joy Beatty]
73
Use case. A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an
actor can be a user or anything that can exchange information with the system. [ISTQB Glossary]
74
User story. A high-level user or business requirement commonly used in agile software development, typically consisting of one
or more sentences in the everyday or business language capturing what functionality a user needs, any non-functional criteria,
and also includes acceptance criteria. [ISTQB Glossary]
75
A scenario is a hypothetical story, used to help a person think through a complex problem or system.
«An Introduction to Scenario
Testing
», Cem Kaner. [
http://kaner.com/pdfs/ScenarioIntroVer4.pdf
]
76
Business rule. A business rule is a statement that defines or constrains some aspect of the business. It is intended to assert
business structure or to control or influence the behavior of the business. A business rule expresses specific constraints on the
creation, updating, and removal of persistent data in an information system. [
«Defining Business Rules — What Are They Really»,
David Hay
и др.]
77