The process activities are:
1. Requirements discovery: This is the process of interacting with stakeholders of the system to discover their requirements. Domain requirements from stakeholders and documentation are also discovered during this activity. There are several complementary techniques that can be used for requirements discovery, which I discuss later in this section.
2. Requirements classification and organization: This activity takes the unstructured collection of requirements, groups related requirements, and organizes them into coherent clusters. The most common way of grouping requirements is to use a model of the system architecture to identify sub-systems and to associate requirements with each sub-system. In practice, requirements engineering and architectural design cannot be completely separate activities.
3. Requirements prioritization and negotiation: Inevitably, when multiple stake-holders are involved, requirements will conflict. This activity is concerned with prioritizing requirements and finding and resolving requirements conflicts through negotiation. Usually, stakeholders have to meet to resolve differences and agree on a compromise requirements.
4. Requirements specification: The requirements are documented and input into the next round of the spiral.
Somatic coherence techniques When your website or blog goes live for the first time, it is exciting. That is until you realize no one but you and your.
ReplyDelete