[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ Skip to main content
Log in

Elements underlying the specification of requirements

  • Published:
Annals of Software Engineering

Abstract

As more and more complex computer‐based systems are built, it becomes increasingly more difficult to specify or visualize the system prior to its construction. One way of simplifying these tasks is to view the requirements from multiple viewpoints. However, if these viewpoints examine the requirements using different notations, how can we know if they are consistent? This paper describes the elemental concepts that underlie all requirements. By reducing each view of requirements to networks of these elemental concepts, it becomes possible to better understand the relationships among the views.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+ Basic
£29.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price includes VAT (United Kingdom)

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Barroca, L. and J. McDermid (1993), “Specification of Real-Time Systems — A View-Oriented Approach,” unknown.

  • Berdon, J. and A. Davis (1994), “Multiple Viewpoint Based Method for Requirements Engineering,” Technical Report UCCS-CSSE-TR-94-5, Center for Software Systems Engineering, University of Colorado, Colorado Springs, CO.

    Google Scholar 

  • Brackett, J. (1991), private conversation with A. Davis, Pittsburgh, PA, October 3, 1991.

  • Coad, P. and E. Yourdon (1990), Object-Oriented Analysis, Prentice Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Davis, A. (1988a), “A Taxonomy of the Early Stages of the Software Development Life Cycle,” Journal of Systems and Software 8,4, 297–311.

    Article  Google Scholar 

  • Davis, A. (1988b), “A Comparison of Techniques for the Specification of External System Behavior,” Communications of the ACM 31,9, 1098–1115.

    Article  Google Scholar 

  • Davis, A. (1993), Software Requirements: Objects, Functions and States, Prentice Hall, Englewood Cliffs, NJ.

    MATH  Google Scholar 

  • Davis, A. and K. Jordan (1991), “Some Ideas for a Method-Independent Requirements Environment,” In Proceedings of 24th Hawaii International Conference of Systems Sciences, IEEE Computer Society Press, Los Alamitos, CA, pp. 36–42.

    Google Scholar 

  • Davis, A., K. Jordan, and T. Nakajima (1993), “A Canonical Representation for Requirements,” Technical Report EAS-CS-93-5, Department of Computer Science, University of Colorado, Colorado Springs, CO.

    Google Scholar 

  • Delugash, H. (1992), “Specifying Multiple-Viewed Software Requirements with Conceptual Graphs,” Journal of Systems and Software 19,3, 207–224.

    Article  Google Scholar 

  • DeMarco, T. (1979), Structured Analysis and System Specification, Prentice Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Easterbrook, S. (1993), “Domain Modeling with Hierarchies of Alternative Viewpoints,” In Proceedings of International Symposium on Requirements Engineering, IEEE Computer Society Press, Los Alamitos, CA, pp. 65–72.

    Google Scholar 

  • Finkelstein, A. and H. Fuks (1989), “Multi-Party Specification,” ACM Software Engineering Notes 14,3, 185–195.

    Article  Google Scholar 

  • Harel, D. (1987), “Statecharts: A Visual Formalism for Complex Systems,” Science of Computer Programming 8,3, 231–274.

    Article  MATH  MathSciNet  Google Scholar 

  • Hatley, D. (1984), “The Use of Structured Methods in the Development of Large Software-Based Avionics Systems,” In Proceedings of AIAA/IEEE 6th Digital Avionics Systems Conference, American Institute of Aeronautics and Astronautics, Reston, VA, pp. 6–15.

    Google Scholar 

  • Hatley, D. and I. Pirbhai (1987), Strategies for Real-Time System Specification, Dorset House, New York, NY.

    Google Scholar 

  • Hibbitts-Kramer, D. (1997), “Requirements Language Definition Generator for the TINA System,” MS Project, Department of Computer Science, University of Colorado, Colorado Springs, CO.

    Google Scholar 

  • Jackson, M. (1983), Systems Development, Prentice Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Jahanian, F. and A. Mok (1986), “Safety Analysis of Timing Properties in Real-Time Systems,” IEEE Transactions on Software Engineering 12,9, 890–904.

    Google Scholar 

  • Jordan, K. (1991), “A Requirements Engineering Metamodel: Integrating Multiple Views of Requirements,” MS Thesis, Department of Computer Science, George Mason University, Fairfax, VA.

    Google Scholar 

  • Jordan, K. and A. Davis (1991), “An Integrated View of Requirements,” In Proceedings of Fifteenth IEEE International Conference on Computer Software and Applications, IEEE Computer Society Press, Los Alamitos, CA, pp. 472–478.

    Chapter  Google Scholar 

  • Leffingwell, D. and A. Davis (1996), “Requirements Management in Medical Device Development,” Medical Device and Diagnostic Industry Magazine 18,3, 100–116.

    Google Scholar 

  • Maler, O., Z. Manna, and J. Power (1991), “From Timed to Hybrid,” Real-Time: Theory in Practice, Springer, Berlin, Germany.

    Google Scholar 

  • Manna, Z. and A. Pnueli (1992), The Temporal Logic of Reactive and Concurrent Systems, Springer, Berlin, Germany.

    Google Scholar 

  • McMenamin, S. and J. Palmer (1984), Essential Systems Analysis, Prentice Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Moret, B. (1982), “Decision Trees and Diagrams,” ACM Computing Surveys 14,4, 543–623.

    Article  Google Scholar 

  • Nuseibeh, B., J. Kramer, and A. Finkelstein (1993), “Expressing the Relationship Between Multiple Views in Requirements Specification,” In Proceedings of 15th IEEE International Conference on Software Engineering, IEEE Computer Society Press, Los Alamitos, CA, pp. 187–197.

    Chapter  Google Scholar 

  • Petri, C.A. (1962), “Kammunikation mit Automaten, Schriften des Reinsch,” West Falischen Inst. Instrumentelle math und der Universität Bonn, Bonn, West Germany.

    Google Scholar 

  • Peterson, J. (1977), “Petri Nets,” ACM Computing Surveys 9,3, 223–252.

    Article  MATH  Google Scholar 

  • Rumbaugh, J. (1991), Object-Oriented Modeling and Design, Prentice Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Sanden, B. (1989), “An Entity-Life Modeling Approach to the Design of Concurrent Software,” Communications of the ACM 32,3, 330–343.

    Article  Google Scholar 

  • Soli, J. (1996), “An Editor for an Integrated Requirements Engineering Environment,” Technical Report UCCS-CSSE-TR-96-4, MS Project, Department of Computer Science, University of Colorado, Colorado Springs, CO.

    Google Scholar 

  • Song, X. and L. Osterweil (1992), “Toward Objective, Systematic Design-Method Comparisons,” IEEE Software 9,3, 43–53.

    Article  Google Scholar 

  • Ward, P. (1986), “The Transformation Schema: An Extension of The Data Flow Diagram to Represent Control and Timing,” IEEE Transactions on Software Engineering 12,2, 198–210.

    Google Scholar 

  • Ward, P. and S. Mellor (1985), Structured Development for Real-Time Systems, Prentice Hall, Englewood Cliffs, NJ.

    Google Scholar 

  • Zweig, A. (1997), “A Displayer for Multiple Requirements Views,” MS Thesis, Department of Computer Science, University of Colorado, Colorado Springs, CO.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Davis, A.M., Jordan, K. & Nakajima, T. Elements underlying the specification of requirements. Annals of Software Engineering 3, 63–100 (1997). https://doi.org/10.1023/A:1018902408324

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1018902408324

Keywords

Navigation