Software engineering with UML

Software Engineering with UML

Volumn , Issue , 2017, Pages 1-390

  Unhelkar, Bhuvan ^a  

^a UNIVERSITY OF SOUTH FLORIDA SARASOTA MANATEE   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

SOFTWARE ENGINEERING;

ACTIVITY DIAGRAM; AGILE DEVELOPMENT ENVIRONMENTS; ARCHITECTURAL SPACE; INTERACTION DIAGRAM; QUALITY OF SOFTWARES; SOLUTION SPACE; STATE MACHINE DIAGRAMS; USE CASE DIAGRAM;

GRAPHIC METHODS;

EID: 85052488010     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1201/9781351235181     Document Type: Book

References (115)

1. Ambler, S. (2004), “The Object Primer,” in Agile Model Driven Development with UML 2.0 3rd ed., New York: Cambridge University Press. ISBN#: 0-521-54018-6.
2. Armour, F. and Miller, G. (2001), Advanced Use Case Modeling, Reading, MA: Addison-Wesley.
3. Bandwagon. Sloan Management Review, 35(1), 73-86.
4. Basili, V., Briand, L., Condon, S., Kim, Y.-M., Melo, W. L., and Valett, J. D. (1996), Understanding and predicting the process of software maintenance releases. Proc 18 Intl Conf on Software Engineering, Berlin, Germany.
5. Beck, K. (2000), EXtremeProgramming Explained: Embrace Change, Reading, MA: Addison-Wesley.
6. Beizer, B. (1984), System Testing and Quality Assurance, New York, NY: Van Nostrand Reinhold.
7. Bennett, K.H. and Rajlich, V.T. (2000), Software Maintenance and Evolution: A Roadmap. Published in the ACM Press, “The Future of Software Engineering,” ACM Press 2000, ISBN-1-58113-253-0.
8. Binder, R.V. (1999), Testing Object-Oriented Systems, Reading, MA: Addison-Wesley.
9. Boehm, B.W. (1986), “A Spiral Model of Software Development and Enhancement,” ACS Software Engineering Notes, 11(4), 14-24.
10. Booch, G. (1994), Object-oriented Analysis and Design, 3rd Edition. Upper Saddle River, NJ: The Addison-Wesley Object Technology Series.
11. Booch, G., Rumbaugh, J., and Jacobson, I. (1999), The Unified Modelling Language User Guide, Reading, MA: Addison-Wesley.
12. Canosa, J., Introduction to Web Services, Embedded Systems Programming. Retrieved from https://www.embedded.com/design/connectivity/4023907/Introduction-to-Web-Services; accessed October 19, 2017.
13. Cantor, M. (1998), Object Oriented Project Management with UML, Wiley, USA. Also see the companion site for this book: http://www.wiley.com/legacy/compbooks/cantor/; accessed October 15, 2017.
14. Card D. and Comer E. (1994), “Why Do So Many Reuse Programs Fail?,” IEEE Software, 11(5), 114-115.
15. Caudwell, P. (2001), Professional XML Web Services, Birmingham: Wrox Press
16. Cho, J. (2008), Issues and Challenges of Agile Software Development with Scrum, Colorado State University-Pueblo, Issues in Information Systems, vol. IX, no. 2.
17. Cockburn, A. (1997), “Goals and Use Cases,” Journal of Object-Oriented Programming, 10(5), 35-40.
18. Cockburn, A. (2000), Writing Effective Use cases, Reading, MA: Addison-Wesley.
19. Coffin, R. and Lane, D. (2007), A Practical Guide to Seven Agile Methodologies, Part 1, Jupitermedia Corporation. Retrieved from http://www.devx.com/architect/Article/32761/1954
20. Constantine, L. (1995), Constantine on Peopleware, Yourdon Press Computing Series, Upper Saddle River, NJ: Prentice Hall.
21. Constantine, L. (2001), The Peopleware Papers: Notes on the Human Side of Programming (Yourdon Press computing series). Upper Saddle River, NJ: Prentice Hall. ISBN-13: 978-0130601230.
22. Constantine, L. and Lockwood, L. (1997), Software for Use: A Practical Guide to the Models and Methods of Usage-centered Design, Reading, MA: Addison-Wesley. (see also www.foruse.com).
23. Constantine, L.L. (1997), “The Case for Essential Use Cases,” Object Magazine, 7(3), 72-80.
24. Constantine, L.L. and Lockwood, L.A.D. (2001), “Structure and Styles in Use Cases for User Interface Design,” in Object Modelling and User Interface Design, M. V. Harmelen (ed.), Reading, MA: Addison-Wesley.
25. DeMarco, T. and Lister, T. (1987), Peopleware: Productive Projects and Teams, USA: Dorset House Publishing Company.
26. Douglass, B. P. (1999), Doing Hard Time Developing Real-Time Systems With UML, Objects, Frameworks, and Patterns, Object Technology Series. Reading, MA: Addison-Wesley.
27. Fowler, M. (1996), “A Survey of Object-oriented Analysis and Design Methods,” OOPSLA’96 Tutorial No. 45, 6-10.
28. Fowler, M. (1997), Analysis Patterns: Reusable Object Models, Reading, MA: Addison-Wesley.
29. Fowler, M. (2003), UML Distilled, 3rd ed., Reading, MA: Addison-Wesley.
30. Frakes, W.B. and Isoda, S. (1994), “Success Factors of Systematic Reuse,” IEEE Software, 11(5), 14-19.
31. Gabriel, R. (1993), “The Quality Without a Name,” Jrnl of Obj Or Prog, 6(5), 86-89.
32. Gamma, E., Helm, R., Johnson, R., and Vlissides, J. (1995), Design Patterns: Elements of Reusable Object-Oriented Software, Reading, MA: Addison-Wesley.
33. Glass, R. (1997), Software Runaways: Monumental Software Disasters, Upper Saddle River, NJ: Prentice Hall.
34. Glenford, M. G., Badgett, T., and Sandler, C. (1979), The Art of Software Testing, Hoboken, NJ: John Wiley & Sons, Inc.
35. Goldberg, A. and Robson, D. (1983), The Interactive Programming Environment, Reading, MA: Addison-Wesley. ISBN: (978-)0201113716.
36. Goldberg, A. and Rubin, K. (1995), Succeeding with Object: Decision Frameworks for Project Management, Reading, MA: Addison-Wesley.
37. Graham, I. (1994), Migrating to Object Technology, Reading, MA: Addison-Wesley.
38. Graham, S. (2001), Building Web Services with Java: Making Sense of XML, SOAP, WSDL, and UDDI, Indiana: SAMS Press.
39. Greatrex, C., (KPMG Director) (1996) “Achieving Excellence through Effective Management of your IT project,” Proceedings of ITProject Management by AIC Conferences.
40. Hammer, M. and Champy, J. (1994), Reengineering the Corporation, St Leonards, NSW: Allen and Unwin.
41. Hans-Erik, E. and Penkar, M. (2000), Business Modelling with UML; Business Patterns at Work, OMG Press.
42. Henderson-Sellers, B. (1997), Book of Object-oriented Knowledge, 2nd ed., Upper Saddle River, NJ: Prentice Hall.
43. Henderson-Sellers, B. and Bulthuis, A. (1997), Object-oriented Metamethods, New York: Springer.
44. Henderson-Sellers, B. and Edwards, J. M. (1994), Book Two of Object-oriented Knowledge: The Working Object, Upper Saddle River, NJ: Prentice-Hall.
45. Henderson-Sellers, B. and Serour, M. (2001), “Creating a Process for Transitioning to Object Technology,” IEEE 2000, 436-440, 00896731; Also presented at TOOLS USA 2001.
46. Henderson-Sellers, B. and Unhelkar, B. (2000), OPEN Modelling with the UML, Reading, MA: Addison-Wesley.
47. Henninger S. (1994), “Using Iterative Refinement to Find Reusable Software,” IEEE Software, 11(5), 48-59.
48. Hudson, William (2001), “A User-centered UML Method,” in Object Modeling and User Interface Design: Designing Interactive Systems, Mark Van Harmelen (ed.), Reading, MA: Addison-Wesley.
49. Humphrey, Watts (1995), A Discipline for Software Engineering, Reading, MA: Addison-Wesley.
50. Hutt, A. (1994), Object Analysis and Design, Description of Methods, OMG/Wiley.
51. Jaaksi, A. (1997), “Our Cases with Use Cases,” Jrnl. Of Obj Or Prog, 10(9), 58-65.
52. Jacobson, I. (1993), “Time for a Cease-Fire in the Methods War,” Jrnl of Obj Or Prog, 6(3), 20-25.
53. Jacobson, I., Booch, G., and Rumbaugh, J. (1999), The Unified Software Development Process, Reading, MA: Addison-Wesley.
54. Jacobson, I., Christerson, M., Jonsson, P., and Overgaard, G. (1992), Object-Oriented Software Engineering: A Use Case Driven Approach, Reading, MA: Addison-Wesley.
55. Jacobson, I., Griss, M., Jonsson, P. (1997), Software Reuse, Reading, MA: Addison-Wesley.
56. Jalote, P. (2000), CMM in Practice: Process for Executing Software Projects at Infosys, Reading, MA: Addison-Wesley.
57. Kriendler, J. (1993), “Cultural Change and Object-oriented technology,” Jrnl of Obj Or Prog, 5(9), 6-8.
58. Kruchten, P., Ahlqvist, S., and Bylund, S. (2001), “User Interface Design in the Rational Unified Process,” in Object Modelling and User Interface Design, M. V. Harmelen (ed.), Reading, MA: Addison-Wesley.
59. Lacity, M. and Hirschheim, R. (1993), The Information systems Outsourcing
60. Lan, Y. and Unhelkar, B. (2005), Global Enterprise Transitions, Hershey, PA, USA: IDEAS Group Inc.
61. Lanier, J. (1997), “The Frontier between Us,” Special Anniversary issue on 50 years of computing, Communications of the ACM, 40(2), 55-56.
62. Lauder, A. and Kent, S. (1999), “Two-Level Modelling,” in Technology of OO Languages and Systems, (TOOLS 31), Jian Chen, Jian Lu, Bertrand Meyer (eds.), Nanjing, China: IEEE Computer Society, 108-117.
63. Lewis, J. and Neher, K. (2007), “Over the Waterfall in a Barrel - MSIT Adventures in Scrum,” IEEE Computer Society, Washington, DC.
64. Lim, W. C., “Effects of Reuse on Quality, Productivity, and Economics,” IEEE Software, 11(5), 23-30.
65. Lorenz, M. and Kidd, J. (1994), Object-oriented Software Metrics, Upper Saddle River, NJ: Prentice-Hall.
66. McGregor, J. and Sykes, D. (2001), A Practical Guide to Testing Object-Oriented Software, Reading, MA: Addison-Wesley.
67. Meyer, B. (1991), “Object-Oriented Software Construction,” In The Importance of Being Humble, 2nd ed., Upper Saddle River, NJ: Prentice Hall, PTR, Section 19.4.
68. Meyer, B. (1995), Object Success, Upper Saddle River, NJ: Prentice Hall.
69. Meyers, G. (1979), The Art of Software Testing, USA: John-Wiley and Sons.
70. Miller, R. B. (1968). “Response Time in Man-Computer Conversational Transactions.” Proc. AFIPS Fall Joint Computer Conference, 33, 267-277.
71. Nygaard, K. (1999), Keynote Address, Technology of OO Languages and Systems, (TOOLS 31), J. Chen, J. Lu, B. Meyer (eds.), Nanjing, China: IEEE Computer Society, 108-117.
72. OMG White Paper on Security (1994) OMG Security Working Group, Issue 1.0 April 1994.
73. Perry, W. (1991), Quality Assurance for Information Systems, MA: QED Information Sciences.
74. Rosenberg, D. and Scott, K. (1999), Use Case Driven Object Modelling with the UML. Reading, MA: Addision-Wesley.
75. Rosenberg, D. and Scott, K. (2001), Applying Use Case Driven Object Modelling with the UML. Reading, MA: Addision-Wesley.
76. Rumbaugh, J. “Modeling & Design: Designing bugs and dueling methodologies,” JOOP Jan’92, pp. 50-56.
77. Rumbaugh, J., Jacobson, I., and Booch, G. (1999), The Unified Modelling Language Reference Manual, Reading, MA: Addison-Wesley.
78. Schneider, G. and Winters, J. P. (2001), Applying Use Cases, Second Edition a Practical Guide, Object Technology Series, Reading, MA: Addision-Wesley.
79. Schwaber, K. and Beedle, M. (2001), Agile Software Development with Scrum, Upper Saddle River, NJ: Prentice Hall.
80. Scott, K. (2004), Fast Track UML 2.0, Apress.
81. Shaw, M. and Garlan, D. (1996), Software Architecture: Perspectives on an Emerging Discipline, Upper Saddle River, NJ: Prentice Hall.
82. Sommerville, I. (1989), Software Engineering, Reading, MA: Addison-Wesley. p. 352.
83. Thomas, D. and Jacobson, I. (1989), Managing Object-oriented Software Engineering Tutorial, TOOLS '89, Paris, 13-15 November 1989.
84. This has been further developed by Henderson-Sellers, B. (1993), “The Economics of Reusing Library Classes,” Jrnl of OO Prog, 6(4), 43-50.
85. Torres, R. J. (2002), Practitioner’s Handbook for User Interface Design & Development, Upper Saddle River, NJ: Prentice-Hall.
86. Unhelkar, B. (1995), “The MOSES Experience,” Object Magazine, p. 51.
87. Unhelkar, B. (1997), “Developing a Financial Market Analysis Product: A MOSES Case Study,” in Developing Business Objects, A. Carmichael (ed.), SIGS, pp. 113-140.
88. Unhelkar, B. (1997-98), Effect of Granularity of Object-oriented Design on Modelling an Enterprise and its Application to Financial Risk Management, Ph.D. Thesis, University of Technology, Sydney: 1997-1998.
89. Unhelkar, B. (1998), “Effect of Granularity of Object-oriented Design on Modelling an Enterprise and its Application to Financial Markets,” Doctoral thesis, Univ. of Technology, Sydney.
90. Unhelkar, B. (1999), After the Y2K Fireworks: Business and Technology Strategies, Boca Raton, FL: CRC Press.
91. Unhelkar, B. (2001), “DeMystifying the UML” Information Age, publication of the Australian Computer Society, pp. 56-61.
92. Unhelkar, B. (2003), Process Quality Assurance for UML-based Projects, Reading, MA: Addison-Wesley.
93. Unhelkar, B. (2005), “Practical Object Oriented Analysis,” Cengage (first published by Thomson Publishing), Australia, March, 2005. Pages 221; ISBN 0-17-012298-0.
94. Unhelkar, B. (2005), “Practical Object Oriented Design,” Cengage (first published by Thomson Publishing), Australia, July, 2005. Pages 220+. ISBN 0-17-012299-9.
95. Unhelkar, B. (2010), Agile in Practice: A Composite Approach, (16,000 words), Cutter Executive Report, Jan 2010, USA. Vol 11, No 1, Agile Product and Project Management Practice.
96. Unhelkar, B. (2013), The Art of Agile Practice: A Composite Approach for Projects and Organizations, Boca Raton, FL: Taylor and Francis, ISBN 9781439851180.
97. Unhelkar, B. and Henderson-Sellers, B. (1993a), “Evaluating the Role of Reuse in Object-Oriented Systems,” Proceedings of the First Australian Conference on Software Metrics, ACOSM’93, J. Verner (ed.).
98. Unhelkar, B. and Henderson-Sellers, B. (1993b), “The Role of Granularity in the Reuse of Object-oriented Systems,” Proceedings of ACOSM’93 First Australian Conference on Software Metrics, Sydney, Australia, June Verner (ed.), Australian Software Metrics Association, November 18-19 1993, pp. 51-66.
99. Unhelkar, B. and Mamdapur, G. (1995), “Practical Aspects of Using a Methodology: A Road Map Approach,” Report on Object Analysis and Design (ROAD), 2(2), 34-36, 54.
100. Van Harmelen, M. (ed.). (2001), Object Modelling and User Interface Design: Designing Interactive Systems, Reading, MA: Addison-Wesley.
101. Winblad A., Edwards S., and King D. (1990), Object-Oriented Software, Reading, MA: Addison-Wesley, pp. vi.
102. Wohlin, C. and Ahlgren, M. (1995), “Soft Factors and Their Impact on Time to Market,” Software Quality Journal, 4(3), 189-205.
103. Younessi, H. (2002), Object-Oriented Defect Management of Software, USA: Prentice Hall PTR.
104. Younessi, H. and Henderson-Sellers, B. (1997), “Cooking Up Quality Software: Object-oriented Software Development Process,” Object Magazine, 7(8), 38-42.
105. http://www.uml-diagrams.org/
106. http://www.agilemanifesto.org/
107. http://www.omg.org/spec/UML/2.5/
108. https://www.ibm.com/software/rational earlier Rational.com - www.rational.com Rational company’s website containing details of Rational’s Object Software Engineering (ROSE) CASE tool for UML. Rational is now owned by IBM and known as IBM Rational.
109. https://www.researchgate.net/publication/229001868_The_future_of_UML [accessed Jul 6, 2017].
110. ISO/IEC 19505-1: 2012 (UML 2.4.1 Infrastructure) http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32624
111. ISO/IEC 19505-2: 2012 (UML 2.4.1 Superstructure) http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=52854
112. www.MethodScience.com. Practical experiences in using and training with UML.
113. www.omg.org: Contains details of standard UML are available. Site also contains details on CORBA, and the Unified Process Model, which is the upcoming effort by OMG to standardize processes.
114. www.sei.cmu.edu: The Carnegie-Mellon University’s Software Engineering Institute’s site. This is the Institute responsible for the five levels of CMM - Capability Maturity Models.
115. www.BPMN.org