Translated abstract:
Requirement conflicts are very common. They can result from different stakeholders’ views, different knowledge of the operating environment, different interpretations of the same concept, etc. Requirement conflicts are harmless, as long as they are detected and
resolved directly in the requirements engineering phase. Software development practice shows, however, that the conflicts often remain unperceived until implementation. In this case conflict resolution becomes much more expensive.
In the presented these we suggest an approach to formalization of functional requirement. This allows us to model every functional requirement as a partial function and to identify conflicting functions. This results in a formally well-founded conflict detection method, applicable in the requirements engineering phase.
The presented formal framework captures and interrelates both function- and component-based models. In particular, we provide a correct-by-construction procedure, which transforms a functional specification into a component-based architecture.