Specifiying and Validating Requirements: The VENUS System

Requirements specification and validation is recognized as a crucial part of the information systems Y development process. This paper presents the VENUS integrated environment for requirements engineering. The underlying conceptual framework of VENUS combines the entity-relationship, object-oriented and rule-based paradigms for data and behaviour modelling. VENUS tools enable systems analysts to formulate, analyse and validate requirements specifications which can be automatically mapped either to a C++ prototype or to the model of Rule-Based Nets (RBNs), a variant of Predicate-Tra nsition Nets. RBNs constitute an executable model of requirements specifications and can be studied by analytical PN algorithms, animated and validated against test cases. The VENUS environment, therefore, provides an integrated, complete and formal, yet user-friendly, framework for requirements engineering. A VENUS prototype has been implemented so far, and work is still in progress towards (i) full-scale development and (ii) mapping of executable requirements specifications to design and implementation structures.

[1]  Albert Endres,et al.  An analysis of errors and their causes in system programs , 1975, IEEE Transactions on Software Engineering.

[2]  J. van Katwijk,et al.  VDM++, a formal specification language for object-oriented designs , 1992, CompEuro 1992 Proceedings Computer Systems and Software Engineering.

[3]  William H. Sanders,et al.  Importance Sampling Simulation in UltraSAN , 1994, Simul..

[4]  Derek Coleman,et al.  Introducing Objectcharts or How to Use Statecharts in Object-Oriented Design , 1992, IEEE Trans. Software Eng..

[5]  Gill Smith,et al.  Object-oriented analysis , 1988, WADAS '88.

[6]  Chris Keen,et al.  Modeling a Door Controller Protocol in LOOPN , 1993, TOOLS.

[7]  Pericles Loucopoulos,et al.  An Object-Oriented Rule-based Approach to the Dynamic modelling of Information Systems , 1990, DMIS.

[8]  Kurt Lautenbach,et al.  System Modelling with High-Level Petri Nets , 1981, Theor. Comput. Sci..

[9]  Derek Coleman,et al.  Introducing Objectcharts or how to use Statecharts in object-oriented design , 1992 .

[10]  Jan van Katwijk,et al.  Application and benefits of formal methods in software development , 1992, Softw. Eng. J..

[11]  Cliff B. Jones,et al.  Systematic software development using VDM , 1986, Prentice Hall International Series in Computer Science.

[12]  José Meseguer,et al.  Rapid prototyping: in the OBJ executable specification language , 1982, Rapid Prototyping.

[13]  Richard A. Kemmerer,et al.  Testing Formal Specifications to Detect Design Errors , 1985, IEEE Transactions on Software Engineering.

[14]  Jose Meseguer,et al.  Rapid prototyping: in the OBJ executable specification language , 1982 .

[15]  Richard C. Waters,et al.  The Requirements Apprentice: Automated Assistance for Requirements Acquisition , 1991, IEEE Trans. Software Eng..

[16]  Bill Karakostas,et al.  Experiences with Rule-based Dynamic modelling , 1990, DMIS.

[17]  J. Dähler,et al.  A graphical tool for the design and prototyping of distributed systems , 1987, SOEN.

[18]  Sjaak Brinkkemper,et al.  The Conceptual Task Model: a Specification Technique between Requirements Engineering and Program Development (Extended abstract) , 1990, CAiSE.

[19]  Pericles Loucopoulos,et al.  Integrating database technology, rule‐based systems and temporal reasoning for effective information systems: the TEMPORA paradigm , 1991, Inf. Syst. J..

[20]  C. Rolland,et al.  Trends and Perspectives in Conceptual Modelling , 1992 .

[21]  Albert Endres An Analysis of Errors and Their Causes in System Programs , 1975, IEEE Trans. Software Eng..

[22]  Tadao Murata,et al.  Petri nets: Properties, analysis and applications , 1989, Proc. IEEE.

[23]  Michael Schrefl,et al.  USING AN OBJECT-ORIENTED DIAGRAM TECHNIQUE FOR THE DESIGN OF INFORMATION SYSTEMS , 1991 .

[24]  J. Michael Spivey,et al.  The Z notation - a reference manual , 1992, Prentice Hall International Series in Computer Science.

[25]  Pamela Zave,et al.  An Insider's Evaluation of PAISLey , 1991, IEEE Trans. Software Eng..