Software development projects seeking a high level of accuracy reach out to formal methods
as early as the requirements engineering phase. However the client perspective of the future …

Systems' requirements are usually written in a natural language since it generally means a
greater understanding among the various stakeholders. However, using an informal …

With today's increasing complexity of systems and requirements there is a need for formal
analysis of requirements. Although there exist several formal requirements description …

The formal reference model for software requirements must be useful for specification of
mappings from both functional and non-functional requirements. The topological functioning …

There is an ever-increasing need to rapidly deliver products, whilst, at the same time, also
delivering products of high quality. To improve the quality of products and increase …

Abstract [Context and motivation] Stakeholder requirements are notoriously informal, vague,
ambiguous and often unattainable. The requirements engineering problem is to formalize …

Assuring a high quality requirements specification document involves both an early
validation process and an increased level of participation. An approach and its supporting …

Realizability checking refers to the formal procedure that aims to determine whether an
implementation exists, always complying to a set of requirements, regardless of the stimuli …

It is pivotal to have well-specified requirements to eliminate errors at an early stage of the
system development life cycle. Some quality standards recommend the use of formal …

Formal specification methods are not often applied in industrial projects, despite their
advantages and the maturity of theories and tools. The scarce familiarity of practitioners with …