Requirements Management

Tracking of Relationship Between Requirements

An important aspect of requirements management is the ability to trace the relationships between requirements and other artifacts (including other requirements). The ability to track relationships supports the process of software development in the following aspects: Verity: Tracking the relationship between requirements and other artifacts allows you to verify whether the requirements have been implemented. …

Tracking of Relationship Between Requirements Read More »

Requirements Management – Best Practices

Ian Sommerville and Pete Sawyer in “Requirements Engineering: A Good Practice Guide” described, over 15 years ago, the method of assessing and improving requirements engineering processes. It is based on the identification of good practices, activities that are desirable elements of the model process of requirements engineering. The authors tried to cover the entirety of …

Requirements Management – Best Practices Read More »

User Stories vs Requirements

When writing any specification of requirements and the product register and sprint register, non-functional requirements should be included in this specification. While the user’s story itself usually represents functional requirements, in my opinion a small problem is with non-functional requirements that represent system-level expectations. Lack of non-functional requirements or their insufficient quantity are often a …

User Stories vs Requirements Read More »

Categorization of Requirements According to the Kano Model

Defining the requirements that will increase the satisfaction of stakeholders from the system being created is crucial for the process of acquiring requirements. Implementation of too many functionalities will make the application less intuitive and more difficult to use. During the process of acquiring requirements, you should choose those requirements that will be crucial for …

Categorization of Requirements According to the Kano Model Read More »

Requirements Documentation Based on Use Cases

Use cases are used to document the functionality of the system and are based on two commonly used concepts: Use case diagrams Specifications of use cases Objects Use case: The use case represents a system function that represents the achievement of a goal in the system. The name of the use case should reflect the …

Requirements Documentation Based on Use Cases Read More »

Requirement Prioritization Techniques

Today, it is time to describe the requirement prioritization techniques. We can transmit them using a number of techniques. Those are as follows: Ranking This technique consists in a selected group of stakeholders determining the available priorities for the requirements according to the adopted criteria. Top-Ten This technique consists in stakeholders selecting the most important …

Requirement Prioritization Techniques Read More »

Scroll to Top