Validating JSD specifications by executing them

Abstract Users prefer to validate system prototypes rather than specification documents. The paper describes a specification presentation tool, which is founded on the specification execution approach. The tool gives automated assistance to the systems analyst in the presentation of specifications to the user for validation. That is, the user can check that the specification meets the requirements by interacting with an actual system. The software can present specifications developed by the JSD (Jackson System Development) method. The approach taken was to derive executable Lisp code and default screens from Art representations of JSD specifications.

[1]  Pamela Zave,et al.  An experiment in technology transfer: PAISLey specification of requirements for an undersea lightwave cable system , 1987, ICSE '87.

[2]  C. Floyd.  A Systematic Look at Prototyping , 1984 .

[3]  Amnon Naamad,et al.  Statemate: a working environment for the development of complex reactive systems , 1988, ICSE '88.

[4]  Nan C. Shu.  Formal: A Forms-Oriented, Visual-Directed Application Development System , 1985, Computer.

[5]  Alex A. Verrijn-Stuart,et al.  Themes and Trends in Information Systems: TC8, 1975-1985 , 1986, Comput. J..

[6]  Suzanne Sluizer,et al.  Applying Entity-Relationship Concepts to Executable Specifications , 1986, ER.

[7]  Maryam Alavi,et al.  An assessment of the prototyping approach to information systems development , 1984, CACM.

[8]  Juha Heinanen.  A language for specifying functionality of data intensive applications , 1986, 1986 IEEE Second International Conference on Data Engineering.

[9]  A. Pnueli,et al.  STATEMATE: a working environment for the development of complex reactive systems , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[10]  José Meseguer,et al.  Parameterized programming in OBJ2 , 1987, ICSE '87.

[11]  Thomas S. Tullis,et al.  Designing a menu-based interface to an operating system , 1985, CHI '85.

[12]  A. Jörgensen.  On the Psychology of Prototyping , 1984 .

[13]  Heinrich C. Mayr,et al.  Prototyping Interactive Application Systems , 1984 .

[14]  Dennis Wixon,et al.  User performance with command, menu, and iconic interfaces , 1985, CHI '85.

[15]  Finn Parbst.  Experience with Prototyping in an IBM-Based Installation , 1984 .

[16]  Thorsten Spitta,et al.  Concept and Experiences of Prototyping in a Software-Engineering-Environment with Natural , 1984 .

[17]  Ferdi Put.  The ER Approach Extended with the Action Concept as a Conceptual Modelling Tool , 1988, ER.

[18]  Gail E. Kaiser,et al.  Models of software development environments , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[19]  Brad A. Myers,et al.  The importance of percent-done progress indicators for computer-human interfaces , 1985, CHI '85.

[20]  Otthein Herzog,et al.  SLAN-4-A software specification and design language , 1980, IEEE Transactions on Software Engineering.

[21]  W. Lewis Johnson.  Deriving specification from requirements , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[22]  D. Bjorner,et al.  On the use of formal methods in software development , 1987, ICSE '87.

[23]  Paul J. Layzell,et al.  Assisting the Analyst - The aims and objectives of the Analyst Assist project , 1986 .