Software engineering: The trend

Informatica (Ljubljana)

Volumn 28, Issue 2, 2004, Pages 129-137

  Isazadeh, Ayaz ^a  

^a UNIVERSITY OF TABRIZ   (Iran)

Author keywords

Formal methods; Requirements engineering; Software engineering

Indexed keywords

COMPUTER SOFTWARE; GRAPH THEORY; INFORMATION USE; PROCESS ENGINEERING; REQUIREMENTS ENGINEERING;

FORMAL METHODS; SOFTWARE ENGINEERING TOOLS; STATE TRANSITION DIAGRAMS (STD);

SOFTWARE ENGINEERING;

EID: 9144273830     PISSN: 03505596     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (54)

1. Aho A. V., Hopcroft J. E., and Ullman J. D. (1975). The Design and Analysis of Computer Algorithms. Addison Wesley, Reading, MA.
2. Berry G. and Cosserat L. (1984). The ESTEREL synchronous programming language and its mathematical semantics. In Seminar on Concurrency, Springer-Verlag, Vol. 197 of Lecture Notes in Computer Science, pp. 389-448.
3. Björkander M. (2000). Graphical programming using UML and SDL. IEEE Computer, 33(12):30-35.
4. Breu R., Grosu R., Huber F., Rumpe B., and Schwerin W. (1998). Systems, views and models of UML. In Schader M. and Korthaus A., editors, The Unified Modeling Language, Technical Aspects and Applications, Physica Verlag, Heidelberg, pp. 93-109.
5. Breu R., Hinkel U., Hofmann C., Klein C., Paech B., Rumpe B., and Thurner V. (1997). Towards a formalization of the unified modeling language. In Proceedings of ECOOP'97, Springer Verlag, LNCS, pp. 344-366.
6. Broy M. (2001). Toward a mathematical foundation of software engineering methods. IEEE Transactions on Software Engineering, 27(1):42-57.
7. Carr D. A. (1997). Interaction object graphs: An executable graphical notation for specifying user interface. In Palanque P. and Pterno F., editors, Formal Method for Computer Human Interaction. Springer-Verlag, pp. 141-156.
8. Coleman D., Hayes F., and Bear S. (1992). Introducing Objectcharts or how to use Statecharts in object oriented design. IEEE Transactions on Software Engineering, 18(1):9-18.
9. Collins B. P., Nicholls J. E., and Sorensen I. H. (1987). Introducing formal methods: The CICS experience with Z. Technical Report TR12.260, IBM Hursley Park.
10. Davies J. (1993). Specification and Proof in Real-Time CSP. Distinguished Dissertations in Computer Science. University of Cambridge Press, Cambridge.
11. Drusinsky D. and Harel D. (1988). On the power of cooperative concurrency. In Proceedings of International Conference on Concurrency (CONCURRENCY'88), Springer-Verlag, Vol. 335 of Lecture Notes in Computer Science, pp. 74-103.
12. Drusinsky D. and Harel D. (1994). On the power of bounded concurrency I: Finite automata. Journal of the Association for Computing Machine (ACM), 41(3):517-539.
13. Fernández J. and Toval A. (2000). Can intuition become rigorous? foundations for UML model verification tools. In Titsworth F. M., editor, Proceedings of the International Symposium on Software Reliability Engineering, IEEE Press, pp. 344-355.
14. France R. (1999). A problem-oriented analysis of basic UML static requirements modeling concepts. In Proceedings of the 1999 ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, ACM Press, pp. 57-69.
15. Glinz M. (2000). Problems and deficiencies of UML as a requirements specification language. In Proceedings of Tenth International Workshop on Software Specification and Design (IWSSD'00), pp. 11-22.
16. Grosu R., Broy M., Selic B., and Stefanescu G. (1998). Towards a calculus for UML-RT specifications. In Kilov H., Rumpe B., and Simmonds I., editors, Proceedings of the Seventh OOPSLA Workshop on Behavioral Semantics of OO Business and System Specifications, pp. 135-152.
17. Guttag J., Horning J., and Wing J. (1982). Some notes on putting formal specifications to productive use. Science of Computer Programming, 2(1):53-68.
18. Harel D. (1987). Statecharts: A visual formalism for complex systems. Science of Computer Programming, 8:231-274.
19. Harel D. (1988). On visual formalisms. Communications of ACM, 31(5):514-530.
20. Harel D. (1995). Private communication. Weizmann Institute of Science, Rehovot, Israel.
21. Harel D., Lachover H., Naamad A., Pnueli A., Politi M., Sherman R., Shtull-Trauring A., and Trakhtenbrot M. (1990). STATEMATE: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, 16(4):403-414.
22. Harel D. and Naamad A. (1995). The STATEMATE semantics of Statecharts. Technical report, i-Logix, Inc., 22 Third Avenue, Burlington, Mass.
23. Harel D. and Pnueli A. (1985). On the development of reactive systems. In Apt K. R., editor, Logics and Models of Concurrent Systems. Springer-Verlag, New York, pp. 477-498.
24. Hendricksen C. S. (1989). Augmented state-transition diagrams for reactive software. ACM SIGSOFT Software Engineering Notes, 14(6):61-67.
25. Heninger K. L., Kallander J. W., Shore J. E., and Parnas D. L. (1978). Requirements for the A-7E aircraft. Technical Report NRL 3876, Naval Research Laboratory, Washington, DC.
26. Hoare C. (1978). Communicating sequential processes. Communications of ACM, 8(21):666-677.
27. Hoare C. (1985). Communicating Sequential Processes. Prentice Hall, Englewood Cliffs, NJ.
28. Hopcroft J. E., Motwani R., and Ullman J. D. (2001). Introduction to Automata Theory, Languages and Computation. Addison Wesley, Boston, MA.
29. Isazadeh A., Lamb D. A., and Shepard T. (1999). Behavioural views for software requirements engineering. Requirements Engineering Journal, 4(1):19-37.
30. Jahanian F. and Mok A. K. (1986). Safety analysis of timing properties in real-time systems. IEEE Transactions on Software Engineering, 12(9):890-904.
31. Jahanian F. and Mok A. K. (1994). Modechart: A specification language for real-time systems. IEEE Transactions on Software Engineering, 20(12):933-947.
32. Jones C. B. (1990). Systematic Software Development using VDM. Prentice Hall International Series in Computer Science. Prentice Hall.
33. Kaplan A. and Wileden J. C. (1995). Formalization and application of a unifying model for name management. In Proceedings of ACM SIGSOFT'95, pp. 161-172.
34. Lann G. L. (1997). An analysis of the Ariane 5 Flight 501 failure - a system engineering perspective. In Proceedings of the IEEE Workshop on Engineering of Computer-Based Systems (ECBS'97), IEEE Computer Society Press, pp. 339-346.
35. Leveson N. G., Heimdahl M. P. E., Hildreth H., and Reese J. D. (1994). Requirements specification for process control systems. IEEE Transactions on Software Engineering, 20(9):684-707.
36. Lions J. L. (1996). ARIANE 5; Flight 501 Failure. Report by the Inquiry Board available online at: http://www.esrin.esa.it/htdocs/tidc/Press/Press96/ ariane5rep.html.
37. OMG (1999). UML Notation Guide, Version 1.3. Object Management Group, available online at http://www.rational.com/uml.
38. OMG (1999). UML Semantics, Version 1.3. Object Management Group, available online at http://www.rational.com/uml.
39. OMG (1999). Unified Modeling Language, Version 1.3. Object Management Group, available online at http://www.omg.org.
40. Parnas D. (1972). On the criteria to be used in decomposing systems into modules. Communications of ACM, 15(2):1053-1058.
41. Peterson J. L. (1977). Petri Net. Computing Surveys, 9(3):223-252.
42. Phillips M. (1989). CICS/ESA 3.1 experiences. In Nicholls J. E., editor, Z User Workshop, pp. 179-185.
43. Rouff C. and Horowitz E. (1991). A system for specifying and rapidly prototyping user interfaces. In Karat J., editor, Taking Software Design Seriously. Academic Press, pp. 257-272.
44. Rumbaugh J., Blaha M., Premerlani W., Eddy F., and Lorensen W. (1991). Object-Oriented Modeling and Design. Prentice Hall, Englewood Cliffs, NJ.
45. Selic B., Gullekson G., and Ward P. T. (1994). Real-Time Object-Oriented Modeling. Wiley, New York.
46. Shaw A. C. (1992). Communicating real-time state machines. IEEE Transactions on Software Engineering, 18(9):805-816.
47. Tague-Sutcliffe J. (1995). Measuring Information: An Information Services Perspective. Academic Press, San Diego.
48. van Schouwen A. J. (1990). The A-7 requirements model: Re-examination for real-time systems and an application to monitoring systems. Technical Report 90-276, Telecommunications Research Institute of Ontario (TRIO), Department of Computing and Information Science, Queen's University, Kingston, Canada.
49. Walters N. (1992). Using Harel's Statecharts to model object-oriented behavior. ACM SIGSOFT Software Engineering Notes, 17(4):28-31.
50. White M. S. (1994). Requirements: A quick and inexpensive way to improve testing. Testing Techniques Newsletter (TTN), On-Line Edition, ttn@soft.com, http://www.cs.ucl.ac.uk/research/renoir/newsletter/backissues/renl34.
51. Wilson E. O. (1999). Consilience: The Unity of Knowledge. Random House, New York.
52. Wolf A. L., Clarke L. A., and Wileden J. C. (1988). A model of visibility control. IEEE Transactions on Software Engineering, 14(4):512-520.
53. Wordsworth J. B. (1992). Software Development with Z. International Computer Science Series. Addison-Wesley.
54. Zelkowits M. V., Shaw A. C., and Gannon J. D. (1979). Principles of Software Engineering. Prentice-Hall, Englewood Cliffs, NJ.