Abstract
As software technologies advance, the software community uses the newest and most powerful technology and associated notations. However, mapping software with a set of notations that would survive the test of time is becoming increasingly difficult. A survey of current methodologies indicates that half‐lives of various software notations are short. The dependence of software notations on programming languages and environment specific methodologies often makes these notations obsolete. In this paper, development of a standard set of software notations that is independent of programming paradigms, yet extensible enough to accommodate programming needs, is proposed.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Chan, W. (1998), "Model Checking Large Software Specifications," IEEE Transactions on Software Engineering 28, 7, 498–518.
Edwards, S., L. Lavagno, E. Lee, and S. Vincentelli (1997), "Design of Embedded Systems: Formal Models, Validation, and Synthesis," Proceedings of the IEEE 85, 3, 366–390.
Ellsberger, J. et al.(1997), Formal Object-oriented Language for Communicating Systems, Prentice-Hall, Europe.
Eriksson, H. and M. Penker (1998), UML Toolkit, Wiley, New York, NY.
Finney, K. (1996), "Mathematical Notation in Formal Specification: Too Difficult for the Masses?" IEEE Transactions on Software Engineering 22, 2, 158–159.
Ganssle, J.G. (1998), "Changes in Embedded Design Methodology," Embedded Systems Programming 11, 10, 35–40.
Gerhart, S., D. Craigen, and T. Ralston (1994), "Experience with Formal Methods in Critical Systems," IEEE Software 11, 1, 21–28.
Gomma, H. (1993), Software Design Methods for Concurrent and Real-time Systems, Addison-Wesley, Reading, MA.
Hall, A. (1990), "Seven Myths of Formal Methods," IEEE Software 7, 6, 11–19.
Hall, A. (1996), "Using Formal Methods to Develop an ATC Information System," IEEE Software 13, 2, 66–76.
Harel, D. (1987), "Statecharts: A Visual formalism for Complex Systems," Science of Computer Programming 8, 231–274.
Harel, D. and E. Gery (1997), "Executable Object Modeling with Statecharts," Computer 30, 7, 31–42.
Islam, N. (1997), "Customizing System Software using OO Frameworks," Computer 30, 2, 69–78.
Larsen, P.G., J. Fitzgerald, and T. Brookes (1996), "Applying Formal Specification in Industry," IEEE Software 13, 7, 48–56.
Leveson, N., M. Heimdahl, H. Hildreth, and J. Reese (1994), "Requirements Specification for Process-Control Systems," IEEE Transactions on Software Engineering 20, 9, 684–707.
Perkusich, A. and J. de Figueiredo (1997), "G-Nets: A Petri Net Based Approach for Logical and Timing Analysis of Complex Software Systems," Journal of Systems and Software 39, 1, 39–59.
Rumbaugh, J. et al.(1991), Object-oriented Modeling and Design, Prentice-Hall, New York.
Shlaer, S. and S. Mellor (1997), "Recursive Design of an Application-independent Architecture," IEEE Software 14, 1, 61–72.
Spivey, J.M. (1989), The Z Notation: A Reference Manual, Prentice-Hall, New York.
Voas, J. (1998), "The Challenges of Using COTS Software in Component-based Development," Computer 31, 6, 44–45.
Wing, J.M. and M. Vaziri Farahani (1997), "A Case Study in Model Checking Software Systems," Science of Computer Programming 28, 2–3, 273–299.
Yourdon, E. and L. Constantine (1979), Structure Design: Fundamentals of a Discipline of Computer Program and System Design, Prentice-Hall, Englewood Cliffs, NJ.
Rights and permissions
About this article
Cite this article
Banerjee, B. Mapping software: Are we nearing standardization?. Annals of Software Engineering 10, 373–387 (2000). https://doi.org/10.1023/A:1018908320986
Issue Date:
DOI: https://doi.org/10.1023/A:1018908320986