Requirements, Models, and Properties: Their Relationship and Validation

242 views
Download
  • Share
#REQUIREMENTS #MODELS #PROPERTIES

Over 20 years of research (and many case studies and development efforts), we have accumulated a wealth of experiences in model-based development and requirements engineering that provide the foundation for the research covered in this talk.

Getting the system requirements right in a development project is crucial for success. One highly promising approach to rigorous requirements capture and definition is modeling of the requirements in formal notations. In such Model-Based Requirements Engineering, an initial set of natural language requirements forms the basis for an initial behavioral model of the intended system behavior and an initial formalization of the natural language requirements into formal requirements properties. Recent breakthroughs in formal verification now allow formal verification techniques to be used to analyze the set of requirements properties as well as the behavioral models. For example, the set of requirements properties can be checked for consistency and the behavioral model can be verified against the formalized requirements properties. The results from this analysis can then be used in an iterative requirements validation process where the analysis results serve as a basis for the modification, refinement, and extension of the set of requirements and/or the behavioral models to bring them in conformance with the truly desired (or notional) system requirements. Over 20 years of research (and many case studies and development efforts), we have accumulated a wealth of experiences in model-based development and requirements engineering that provide the foundation for the research covered in this talk. The goal of the presentation is threefold. First, we aim to clarify the often confused relationships between natural language requirements, formal behavioral models, and formally captured requirements. Second, we will describe a requirements and model verification and validation process intended to ensure that (1) the model indeed behaves as stated in the requirements and (2) that the requirements are the "true" requirements needed to meet the system objectives. Finally, we want to spend time discussing how the "traditional" notion of requirements mesh with the "new" way of using use-cases or user-stories.

Over 20 years of research (and many case studies and development efforts), we have accumulated a wealth of experiences in model-based development and requirements engineering that provide the foundation for the research covered in this talk.

Advertisment

Advertisment