Many development projects are facing a growing challenge these days: how to handle variability. The ability to create variants of a system or a software product by using variable components is in high demand in businesses today and no longer only limited to software product line development and the automotive sector.
At the beginning of requirements analysis, you should specify the variability properties that the solution should have. To do this, you must answer questions like “What changes?” and “How?”objectiF RM helps you to record the answers: for properties that can vary, variation points can be created. In what way a property varies, is described with values, i.e., variations of a variation point.
Creating variations and variation points provides a foundation for dealing with variability. When developing requirements, you have to answer the question “Does a requirement apply to one or more variants?” If so, allocate the requirement its corresponding variations. “Or does a requirement not apply to the requirement, but to the test cases of the corresponding variation?” In this case, don’t allocate a requirement, instead allocate the test cases of the relevant variation.