Дескриптор рабочего продукта (Артефакт): Требования полной системы

Этот артефакт фиксирует атрибуты и ограничения качества, контекстом которых является вся система. Они также охватывают функциональные требования полной системы.

На основе рабочего продукта метода: Требования полной системы

When you document system-wide requirements, ensure that the needs of all of the stakeholders are represented. In particular, include the needs of those who are responsible for maintaining or supporting the system after it is delivered.
Typically, there are some overlaps and gray areas between system-wide requirements and other requirements work products. For example, the authorization behavior of a system can be specified as use cases or as statements within system-wide requirements. The overall driving need is that no important requirements are missed or duplicated, and that there is an agreed upon approach for capturing and processing every type of requirement.
System-wide requirements originate from many places. Documenting the source of the requirement is particularly important when you separate externally mandated requirements.
Requirements are often thought of as "Qualitative" (specifying a quality or desirable characteristic) versus "Quantitative" (specifying a quantity). Qualitative requirements can sometimes be elaborated into quantitative requirements.
A good quality requirement is one that you can verify, either through testing or some other objective evaluation.
You must evaluate system-wide requirements for cost, schedule impact, and level of contribution to business goals. Based on your evaluation, the system-wide requirements should be iteratively challenged, defended, and amended.