The role of formalism in system requirements
share
A major determinant of the quality of software systems is the quality of their requirements, which should be both understandable and precise. Most requirements are written in natural language, which is good for understandability but lacks precision. To make requirements precise, researchers have for many years advocated the use of “formal” approaches. Many such approaches exist, differing in their style, scope and applicability. The present survey discusses some of the principal approaches and compare them to informal ones. The analysis uses a set of complementary criteria, such as level of abstraction, availability of tools, support for traceability. It classifies the approaches into five categories: general-purpose, natural-language, graph/automata, other mathematical notations, programming-language-based. The review includes examples from all of these categories, altogether 22 different methods, including for example SysML, Relax, Eiffel, Event-B, Alloy. The review discusses a number of open questions, including seamlessness, the role of tools and education, and how to make industrial applications benefit more from the contributions of formal approaches.
READ FULL TEXT
