Representing and Using Nonfunctional Requirements: A Process-Oriented Approach

A comprehensive framework for representing and using nonfunctional requirements during the development process is proposed. The framework consists of five basic components which provide the representation of nonfunctional requirements in terms of interrelated goals. Such goals can be refined through refinement methods and can be evaluated in order to determine the degree to which a set of nonfunctional requirements is supported by a particular design. Evidence for the power of the framework is provided through the study of accuracy and performance requirements for information systems. >

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

[2]  John Mylopoulos,et al.  A language facility for designing database-intensive applications , 1989 .

[3]  Richard H. Thayer,et al.  System and Software Requirements Engineering , 1994 .

[4]  Matthias Jarke,et al.  Telos: representing knowledge about information systems , 1990, TOIS.

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

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

[7]  児玉 文雄.  Harvard Business Review : 抄録雑誌の概要 , 1987 .

[8]  Victor R. Basili,et al.  The Future Engineering of Software: A Management Perspective , 1991, Computer.

[9]  Graeme Hirst,et al.  Computational stylistics for natural language translation , 1990 .

[10]  Barry Boehm,et al.  Characteristics of software quality , 1978 .

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

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

[13]  Johan de Kleer,et al.  An Assumption-Based TMS , 1987, Artif. Intell..

[14]  Jack Mostow,et al.  Toward Better Models of the Design Process , 1985, AI Mag..

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

[16]  William N. Robinson,et al.  Negotiation behavior during requirement specification , 1990, [1990] Proceedings. 12th International Conference on Software Engineering.

[17]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

[18]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[19]  Howard B. Reubenstein,et al.  Automated Acquisition of Evolving Informal Descriptions , 1990 .

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

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

[22]  Edward D. Lazowska,et al.  Quantitative system performance - computer system analysis using queueing network models , 1983, Int. CMG Conference.

[23]  Matthias Jarke,et al.  Teamwork Support in a Knowledge-Based Information Systems Environment , 1991, IEEE Trans. Software Eng..

[24]  David K. Hsiao,et al.  Full protection specifications in the semantic model for database protection languages , 1976, ACM '76.

[25]  William Francis Hyslop,et al.  Performance prediction of relational database management systems , 1991 .

[26]  R BasiliVictor,et al.  The Future Engineering of Software , 1991 .

[27]  Edward D. Lazowska,et al.  Quantitative System Performance , 1985, Int. CMG Conference.

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

[29]  W. W. Bledsoe,et al.  Review of "Problem-Solving Methods in Artificial Intelligence by Nils J. Nilsson", McGraw-Hill Pub. , 1971, SGAR.

[30]  Connie U. Smith,et al.  Performance Engineering of Software Systems , 1990, SIGMETRICS Perform. Evaluation Rev..

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

[32]  Grant E. Weddell,et al.  Selection of Indexes to Memory-Resident Entities for Semantic Data Models , 1989, IEEE Trans. Knowl. Data Eng..

[33]  Michael Stonebraker,et al.  Triggers and inference in data base systems , 1985, ACM '85.

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

[35]  Stephen Fickas,et al.  Automating the Transformational Development of Software , 1985, IEEE Transactions on Software Engineering.

[36]  Martin S. Feather,et al.  Representation and Presentation of Requirements Knowledge , 1992, IEEE Trans. Software Eng..

[37]  Jennifer Widom,et al.  Deriving Production Rules for Constraint Maintainance , 1990, VLDB.

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

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

[40]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[41]  Jon Doyle,et al.  A Truth Maintenance System , 1979, Artif. Intell..

[42]  Nils J. Nilsson,et al.  Problem-solving methods in artificial intelligence , 1971, McGraw-Hill computer science series.

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

[44]  Charles P. Pfleeger,et al.  Security in computing , 1988 .

[45]  Johan de Kleer,et al.  Problem Solving with the ATMS , 1986, Artif. Intell..

[46]  James Marting,et al.  Security, Accuracy, and Privacy in Computer Systems , 1973 .

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