Dealing with performance requirements during the development of information systems

Performance goals for information systems are treated as a class of nonfunctional requirements (NFRs). A given model for representing NFRs is given to make provisions for: representing a variety of implementation alternatives; expressing performance goals (including responsiveness) in terms of performance and information system concepts; and organizing the process into layers corresponding to subsets of the language to be implemented. The application of the framework is illustrated by mapping the conceptual design of an information system to its implementation, while attempting to meet a set of goals such as 'achieve good time performance for authorizing credit card sales'. A tool is being developed to aid this process.<<ETX>>

[1]  Peter P. Chen.  The entity-relationship model: toward a unified view of data , 1975, VLDB '75.

[2]  Stephen Fox,et al.  Storage and Access Structures to Support a Semantic Data Model , 1982, VLDB.

[3]  John Mylopoulos,et al.  Capturing more world knowledge in the requirements specification , 1982, ICSE '82.

[4]  Elaine Kant.  On the efficient synthesis of efficient programs , 1983 .

[5]  Robert Balzer,et al.  A 15 Year Perspective on Automatic Programming , 1985, IEEE Transactions on Software Engineering.

[6]  John Mylopoulos,et al.  Implementation of a compiler for a semantic data model: Experiences with taxis , 1987, SIGMOD '87.

[7]  Roger King,et al.  Semantic database modeling: survey, applications, and research issues , 1987, CSUR.

[8]  John Mylopoulos,et al.  Process Management and Assertion Enforcement for a Semantic Data Model , 1988, EDBT.

[9]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[10]  John Mylopoulos,et al.  Support for Data-Intensive Applications: Conceptual Design and Software Development , 1989, DBPL.

[11]  Véronique Benzaken,et al.  An Evaluation Model for Clustering Strategies in the O2 Object-Oriented Database System , 1990, ICDT.

[12]  Stephen Fickas,et al.  Goal-directed concept acquisition in requirements elicitation , 1991, Proceedings of the Sixth International Workshop on Software Specification and Design.

[13]  Lawrence Chung,et al.  Representation and Utilization of Non-Functional Requirements for Information System Design , 1991, CAiSE.

[14]  Brian A. Nixon.  Implementation of Information System Design Specifications: A Performance Perspective , 1991, DBPL.

[15]  John Mylopoulos,et al.  From information system requirements to designs: a mapping framework , 1991, Inf. Syst..

[16]  Jintae Lee,et al.  Extending the Potts and Bruns model for recording design rationale , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[17]  Matthias Jarke,et al.  DAIDA: an environment for evolving information systems , 1992, TOIS.

[18]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[19]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[20]  Le Chesnay CedexApril.  An Evaluation Model for Clustering Strategies in the O 2 Object-Oriented Database , 1995 .