Using Hypertext for semiformal representation in requirements engineering practice

Abstract Requirements engineering is insufficiently supported in practice, especially the issue of appropriate formality of the requirements’ representation during their definition is yet unsolved. Since informal natural language has its disadvantages and immediate formal representation is very difficult, a mediating representation is needed. Therefore, we developed a novel approach to requirements engineering — with tool support — that is based on hypertext. We utilize hypertext primarily for semiformal representation, that can help to bridge the informality/formality gap between human and computer. We have applied our approach in real-world projects, and our experience suggests its usefulness. As a consequence, we recommend the use of hypertext for the specification of requirements in practice.

[1]  Kazuhisa Kawai,et al.  Requirement analysis by the KJ editor , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[2]  Franca Garzotto,et al.  HDM—a model for the design of hypertext applications , 1991, HYPERTEXT '91.

[3]  Norbert A. Streitz,et al.  Coexistence and transformation of informal and formal structures: requirements for more flexible hypermedia systems , 1994, ECHT '94.

[4]  Steven J. DeRose,et al.  Expanding the notion of links , 1989, Hypertext.

[5]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[6]  Janet H. Walker,et al.  Supporting document development with Concordia , 1988, Computer.

[7]  Julie A. Launhardt,et al.  Hypermedia Templates: an author's tool , 1991, HYPERTEXT '91.

[8]  Ben Shneiderman,et al.  A Spectrum of Automatic Hypertext Constructions , 1989, Hypermedia.

[9]  Catherine C. Marshall,et al.  Aquanet: a hypertext tool to hold your knowledge in place , 1991, HYPERTEXT '91.

[10]  Mary Beth Rosson,et al.  Binding objects to scenarios of use , 1994, Int. J. Hum. Comput. Stud..

[11]  Raymonde Guindon,et al.  Requirements and design of DesignVision and object-oriented graphical interface to an intelligent software design assistant , 1992, CHI.

[12]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[13]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[14]  Hermann Kaindl,et al.  Types and inheritance in hypertext , 1994, Int. J. Hum. Comput. Stud..

[15]  Hermann Kaindl,et al.  Hypertext and structured object representation: an unifying view , 1991, HYPERTEXT '91.

[16]  James E. Rumbaugh,et al.  Object-Oriented Modelling and Design , 1991 .

[17]  Peter Aiken,et al.  Hypermedia support for software development: A retrospective assessment , 1994, Hypermedia.

[18]  Janis A. Bubenko,et al.  Facilitating "fuzzy to formal" requirements modelling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[19]  Jakob Nielsen,et al.  A Similarity-Based Hypertext Browser for Reading the Unix Network News , 1989, Hypermedia.

[20]  Jacob L. Cybulski,et al.  A hypertext based software-engineering environment , 1992, IEEE Software.

[21]  David R. Harris,et al.  KBRA: A new paradigm for requirements engineering , 1988, IEEE Expert.

[22]  Vasant Dhar,et al.  Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..

[23]  Michael G. Christel,et al.  A multimedia approach to requirements capture and modeling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[24]  F. Javier Lerch,et al.  Towards a model of cognitive process in logical design: comparing object-oriented and traditional functional decomposition software methodologies , 1992, CHI.

[25]  Daniel M. Russell,et al.  Facilitating the development of representations in hypertext with IDE , 1989, Hypertext.

[26]  Catherine C. Marshall,et al.  Two years before the mist: experiences with Aquanet , 1993, ECHT '92.

[27]  David Kaufer,et al.  The role of external representation in the writing process: implications for the design of hypertext-based writing tools , 1989, Hypertext.

[28]  James Bigelow,et al.  Hypertext and CASE , 1988, IEEE Software.

[29]  Jocelyne Nanard,et al.  Using structured types to incorporate knowledge in hypertext , 1991, HYPERTEXT '91.

[30]  John J. Leggett,et al.  Using an Issue-Based Hypertext System to Capture the Software Life-Cycle Process , 1990, Hypermedia.

[31]  Thomas J. Smith.  READS: a requirements engineering tool , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[32]  Mayer D. Schwartz,et al.  The Dexter Hypertext Reference Model , 1994, CACM.

[33]  Hermann Kaindl,et al.  How to identify binary relations for domain models , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[34]  Stewart A. Higgins,et al.  Scenarios-an industrial case study and hypermedia enhancements , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[35]  David Chenho Kung,et al.  Status report: requirements engineering , 1993, IEEE Software.

[36]  Rebecca Wirfs-Brock,et al.  Designing object-oriented software , 1990 .

[37]  Kenji Takahashi,et al.  An active hypertext model for system requirements , 1993, Proceedings of 1993 IEEE 7th International Workshop on Software Specification and Design.

[38]  Walt Scacchi,et al.  A hypertext system to manage software life-cycle documents , 1990, IEEE Software.

[39]  Peter J. Brown.  Do We Need Maps to Navigate Round Hypertext Documents? , 1988, Electron. Publ..

[40]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

[41]  Hermann A. Maurer,et al.  Harmony…on an expanding net , 1994, INTR.