B. Roussev and J. Wu
[1] J. Ivari, Object-orientation as structural, functional and behavioral modeling: a comparison of six methods for object-orientedanalysis, Inf. and Software Technology, 37 (3), 1995. [2] R. Wieringa, A survey of structured and object-oriented software specification methods and techniques, ACM ComputingSurveys, 30 (4), Dec. 1998, 459–527. doi:10.1145/299917.299919 [3] CHAOS, CHAOS Research Report, http://www.standish-group.com, 2003. [4] I. Jacobson, Object-oriented software engineering: a use casedriven approach (Addison-Wesley Professional, 1992). [5] OMG, OMG Unified Modeling Language Specification, Version1.5, March 2003. [6] G. Engels, J. Kuster, R. Heckel, & L. Groenewegen, Amethodology for specifying and analyzing consistency of object-oriented behavioral models, ACM ESEC/FSE, Vienna, Austria, 2001, 186–195. doi:10.1145/503209.503235 [7] B. Roussev, Generating OCL specifications and class diagramsfrom use cases: a newtonian approach, Proc. 36th Hawaii Int’lConference on System and Sciences, HICSS’36, Hawaii, 2003,321–329. doi:10.1109/HICSS.2003.1174886 [8] A. Cockburn, Structuring use cases with goals, Journal ofObject-Oriented Programming, 10(5), 1997, 35–40. [9] D. Coleman, P. Arnold, S. Bodoff, C. Dollin, H. Gilchrist, F.Hayes, & P. Jeremaes, Object-oriented development: the fusionmethod (Location: Prentice-Hall, 1994). [10] J.M. Spivey, The Z notation: a reference manual. [11] C. Jones, Systematic software development using VDM. [12] D. D’Souza & A. Wills, Objects, components and frameworkswith UML: the catalysis approach. [13] S. Cook & J. Daniels, Designing object systems: object-orientedmodeling with syntropy. (Location: Prentice-Hall, 1994). [14] S. Sendall, Specifying Reactive System Behavior, Ph.D. thesis,Ecole Polytechnique Federale De Lausenne (Swiss FederalInstitute of Technology), Lausanne, 2002. [15] J. Magee & J. Kramer, Concurrency: state models and javaprograms (John Wiley & Sons, 1999). [16] W. Damm & D. Harel, LSCs: Breathing Life into MessageSequence Charts, Formal Methods in System Design, 19(1),2001. doi:10.1023/A:1011227529550 [17] S. Uchitel, J. Kramer, & J. Magee, Incremental Elaborationof Scenario-Based Specifications and Behavior Models UsingImplied Scenarios, ACM Trans. on Software Engineering andMethodology, 13 (1), 2004, 37–95. doi:10.1145/1005561.1005563 [18] J. Whittle & J. Schumann, Generating Statechart Designs fromScenarios, Proc. of 22nd Int. Conf. on Software Engineering,ICSE’00, Limerick, Ireland, 2000, 314–323.68 [19] R. Wirfs-Brock & B. Wilkerson, Object-oriented design: aresponsibility driven approach, Proc. of OOPSLA’89, Location,1989, 71–75. doi:10.1145/74877.74885 [20] L. Maciaszek, Requirements analysis and system design(Addison-Wesley, 2004). [21] J. Warmer & A. Kleppe, The object constraint language: precisemodeling with UML (Reading MA: Addison-Wesley, 1998). [22] S. Ambler, Toward executable UML, Software DevelopmentCMP Media LLC, San Francisco, CA, 2002. Available onhttp://www.sdmagazine.com/documents/s=2279/sdm0201h/0201h.htm [23] I. Jacobson, G. Booch, & J. Rumbaugh, The Unified SoftwareDevelopment Process (Addison-wesley Professional, 1999). [24] A. Borgida, J. Mylopoulos, & R. Reiter, On the Frame Problemin Procedure Specification, IEEE Trans. On Soft. Eng., 21(10),1995. doi:10.1109/32.469460 [25] A. Moreira & J. Araújo, “Generating object-Z specificationsfrom use cases, Int. Conf. on Enterprise Information Systems,Setúbal, Portugal, 1999, 43–51. [26] I. Graham, Business process re-engineering with SOMA, Proc.of Object Expo Europe, Dorking, England, 1994, 163–173. [27] B.P. Douglas, Real Time UML, 3rd Ed. (Boston, USA Addison-Wesley, 2004). [28] P. Zave & M. Jackson, Four dark corners of requirements engineering, ACM Trans. on Software Engineering and Methodology, 6(1), 1997, 1–30. doi:10.1145/237432.237434 [29] B.A. Nuseibeh & S.M. Easterbrook, Requirements engineering:a roadmap, in A.C.W. Finkelstein (Ed.), The Future of SoftwareEngineering, 22nd Int. Conf. on Software Engineering, 2000.
Important Links:
Go Back
