ebook img

Object-oriented systems analysis and design PDF

636 Pages·2014·14.277 MB·English
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview Object-oriented systems analysis and design

O b j e c t O r i e n t e d S y s t e m s A n a l y s i s & D e s i g n A s h r a f i A s h r Object Oriented Systems Analysis a f and Design i Noushin Ashrafi Hessam Ashrafi 1 e First Edition ISBN 978-1-29203-960-2 9 781292 039602 Pearson New International Edition Object Oriented Systems Analysis and Design Noushin Ashrafi Hessam Ashrafi First Edition International_PCL_TP.indd 1 7/29/13 11:23 AM ISBN 10: 1-292-03960-4 ISBN 13: 978-1-292-03960-2 Pearson Education Limited Edinburgh Gate Harlow Essex CM20 2JE England and Associated Companies throughout the world Visit us on the World Wide Web at: www.pearsoned.co.uk © Pearson Education Limited 2014 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without either the prior written permission of the publisher or a licence permitting restricted copying in the United Kingdom issued by the Copyright Licensing Agency Ltd, Saffron House, 6–10 Kirby Street, London EC1N 8TS. All trademarks used herein are the property of their respective owners. The use of any trademark in this text does not vest in the author or publisher any trademark ownership rights in such trademarks, nor does the use of such trademarks imply any affi liation with or endorsement of this book by such owners. ISBN 10: 1-292-03960-4 ISBN 10: 1-269-37450-8 ISBN 13: 978-1-292-03960-2 ISBN 13: 978-1-269-37450-7 British Library Cataloguing-in-Publication Data A catalogue record for this book is available from the British Library Printed in the United States of America Copyright_Pg_7_24.indd 1 7/29/13 11:28 AM 111223334360581504711793947358161 P E A R S O N C U S T O M L I B R AR Y Table of Contents References Noushin Ashrafi/Hessam Ashrafi 1 1. Information Systems Noushin Ashrafi/Hessam Ashrafi 7 2. The Concept of Object Orientation Noushin Ashrafi/Hessam Ashrafi 36 3. Methodology Noushin Ashrafi/Hessam Ashrafi 61 4. Gathering Requirements Noushin Ashrafi/Hessam Ashrafi 109 5. Domain Analysis Noushin Ashrafi/Hessam Ashrafi 153 6. Behavioral Modeling: Use Cases: The Basics Noushin Ashrafi/Hessam Ashrafi 189 7. Behavioral Modeling: Developing Use Cases Noushin Ashrafi/Hessam Ashrafi 214 8. Structural Modeling Noushin Ashrafi/Hessam Ashrafi 257 9. Dynamic Modeling Noushin Ashrafi/Hessam Ashrafi 303 10. The Design Challenge Noushin Ashrafi/Hessam Ashrafi 345 11. Application Design: Flow & Control Noushin Ashrafi/Hessam Ashrafi 378 12. Application Design: The User Interface Noushin Ashrafi/Hessam Ashrafi 411 I 455556502592389661 13. Application Design: Database & Persistence Noushin Ashrafi/Hessam Ashrafi 453 14. Patterns Noushin Ashrafi/Hessam Ashrafi 508 15. Components & Reuse Noushin Ashrafi/Hessam Ashrafi 529 16. Architecture Noushin Ashrafi/Hessam Ashrafi 556 17. Implementation Noushin Ashrafi/Hessam Ashrafi 596 Index 621 II R EFERENCES From References of Object-Oriented Systems Analysis and Design, First Edition. Noushin Ashrafi, Hessam Ashrafi. Copyright © 2009 by Pearson Education, Inc. Published by Pearson Prentice Hall. All rights reserved. 1 R EFERENCES [Alexander 1977] Alexander, Christopher, Sara [Beck 2000] Beck, Kent, 2000. Extreme Programming Ishikawa, and Murray Silverstein, 1977. Pattern Explained.Boston: Addison-Wesley. Language: Towns, Buildings, Construction. New York: [Bennet 2002] Bennett, Simon, Steve McRobb, and Ray Oxford University Press. Farmer, 2002. Object-Oriented Systems Analysis and [Alhir 1998] Alhir, Sinan Si, 1998. UMLin a Nutshell. Design Using UML. Englewood Cliffs, NJ: Prentice Hall. Sebastopol, CA: O’Reilly. [Bittner 2002] Bittner, Kurt, and Ian Spence, 2002. Use [American Heritage 1996] The American Heritage® Case Modeling. Boston: Addison-Wesley. Dictionary of the English Language, Third Edition, 1996. [Blum 1992] Blum, Bruce I., 1992. Software Engineering: Houghton Mifflin Company. AHolistic View. New York: Oxford University Press. [Arlow 2004] Arlow, Jim, and Ila Neustadt, 2004. [Booch 1999] Booch, Grady, James Rumbaugh, and Enterprise Patterns and MDA: Building Better Soft- Ivar Jacobson, 1999. The Unified Modeling Language ware with Archetype Patterns and UML. Boston: User Guide. Boston: Addison-Wesley. Addison-Wesley. [Booch 1994] Booch, Grady, 1994. Object-Oriented Analysis [Armour 2001] Armour, Frank, and Granville Miller, and Design with Applications, Second Edition. Red- 2001. Advanced Use Case Modeling: Software Systems. woodCity, CA: The Benjamin/Cummings Publishing Boston: Addison-Wesley. Company, Inc. [Arrington 2003] Arrington, C. T., and Sayed H. Rayhan, [Brooks 1995] Brooks, Frederick P., Jr., 1995. The Mythical 2003. Enterprise Java with UML. New York: Wiley. Man-Month: Essays on Software Engineering. Reading, [Ashrafi 1995] Ashrafi, Noushin, Hessam Ashrafi, and MA: Addison-Wesley Publishing Company. Jean-Pierre Kuilboer, “ISO-9000-3: Guidelines for [Brookshear 2003] Brookshear, J. Glenn, 2003. Computer Software Quality,” Information Systems Management, Science: An Overview: 7th Edition. Reading, MA: Summer 1995. Addison-Wesley Publishing Company. [Avison 2003] Avison, David E., and G. Fitzgerald, [Brown 2001] Brown, Kyle, Gary Craig, Greg Hester, “Where Now for Development Methodologies?” Jaime Niswonger, David Pitt, and Russell Stinehour, Communications of the ACM, Vol. 46, No. 1 (January2003). 2001. Enterprise Java Programming with IBM WebSphere. [Avison 1995] Avison, David E., and G. Fitzgerald, 1995. Upper Saddle River, NJ: Pearson Education. Information Systems Development: Methodologies, [Brown 1998] Brown, William H., Raphael C. Malveau, Techniques and Tools, 2nd Edition. London: McGraw-Hill Hays W. “Skip” McCormick III, and Thomas J. Book Company. Mowbray, 1998. Anti-Patterns: Refactoring Software, [Awalt 2004] Awalt, Don, and Rick McUmber, “Secrets Architectures, and Projects in Crisis. New York: Wiley. of Great Architects,” Microsoft Architects Journal, Vol. 3 [Campbell-Kelly 2003] Campbell-Kelly, Martin, 2003. (July 2004). From Airline Reservations to Sonic the Hedgehog: AHistory of the Software Industry. Cambridge, MA: The [Bahrami 1999] Bharami, Ali, 1999. Object-Oriented MIT Press. Systems Development: Using the Unified Modeling Language. Boston: Irwin McGraw-Hill. [Chapin 2002] Donald Chapin, “What’s the Business inBusiness Rules?” Business Rules Journal, Vol. 3, No. 10 [Basiura 2001] Basiura, Russ, Mike Batongbacal, (October 2002). URL: http://www.BRCommunity. Brandon Bphling, Mike Clark, Andreas Eide, Robert com/a2002/b119.html. Eisenberg, Brian Loesgen, Christopher L. Miller, Matthew Reynold, Bill Sempf, and Srinivasa [Chessman 2001] Chessman, John, and John Daniels, Sivakumar, 2001. Professional ASP.NET Web Services. 2001. UMLComponents: ASimple Process for Specifying Birmingham, UK: Wrox Press. Component-Based Software, 2001. Boston: Addison-Wesley. [Bass 2003] Bass, Len, Paul Clements, and Rick Kazman, [Chiera 1938] Chiera, Edward, 1938. They Wrote on 2003. Software Architecture in Practice, Second Edition. Clay. Chicago: The University of Chicago Press. Boston: Addison-Wesley. (Copyright Renewed 1966) References 2 [Chisholm 2002] Malcolm Chisholm, “The Black Frameworks with UML: The Catalysis Approach. Boston: Box Problem,” Business Rules Journal, Vol. 3, No. 3 Addison-Wesley. (March 2002). URL: http://www.BRCommunity. [Dutka 1989] Dutka, Alan F., and Howard H. Hanson, com/a2002/b100.html. 1989. Fundamentals of Data Normalization. Reading, [Chonoles 2003] Chonoles, Michael Jesse, and James MA: Addison-Wesley. A. Schardt, 2003. UML2 for Dummies. Indianapolis, IN: [Evitts 2000] Evitts, Paul, 2000. AUMLPattern Language. Wiley Publishing, Inc. Indianapolis: Macmillan Technical Publishing (MTP). [Clark 2001] Clark, Andy, 2001. Mindware: An Introduction [Faison 2002] Faison, Ted, 2002. Component-Based to the Philosophy of Cognitive Science. New York: Oxford Development with Visual C#. New York: M&T Books University Press. (Wily). [Coad 1997] Coad, Peter, Mark Mayfield, and David [Fielding 2000] Fielding, Roy Thomas, 2000. Architectural North, 1997. Object Models: Strategies, Patterns, and Styles and the Design of Network-Based Software Applications, 2nd Edition. Upper Saddle River, NJ: Architecture. Doctoral Dissertation. University of Prentice Hall. California, Irvin. URL: http://www.ics.uci.edu/ [Coad 1992] Coad, Peter, “Object-Oriented Patterns,” ~fielding/pubs/dissertation. Communications of the ACM, Vol. 35, No. 9 (September [Fowler 2003] Fowler, Martin, 2003. Patterns of Enterprise 1992). Application Architecture. Boston: Addison-Wesley. [Cockburn 2002] Cockburn, Alistair, 2002. Agile [Fowler 2000a] Fowler, Martin, with Kendall Scott, Software Development. Boston: Addison-Wesley. 2000. UMLDistilled, Second Edition: ABrief Guide to the [Cockburn 2001] Cockburn, Alistair, 2001. Writing Standard Modeling Language. Boston: Addison-Wesley. Effective Use Cases. Boston: Addison-Wesley. [Fowler 2000b] Fowler, Martin, 2000. Refactoring: [Codd 1979] Codd, E. F., “Extending the Data Base Improving the Design of Existing Code. Boston: Relational Model to Capture More Meaning,” ACM Addison-Wesley. Transactions on Database Systems,Vol. 4, No. 4 (December [Fowler 1997] Fowler, Martin, 1997. Analysis Pattern: 1979), 397–434. Reusable Object Models. Boston: Addison-Wesley. [Codd 1970] Codd, E. F., “ARelational Model of Data for Large Shared Data Banks,” Communications of [Freeman 2004] Freeman, Eric, and Elisabeth ACM,Vol. 13, No. 6 (June 1970), 377–387. Freeman with Kathy Sierra and Bert Bates, 2004. Head First Design Patterns. Sebastopol, CA: O’Reilly. [Conallen 2003] Conallen, Jim, 2003. Building Web Applications with UML, Second Edition. Boston: [Gamma 1997] Gamma, Erich, Richard Helm, Ralph Addison-Wesley. Johnson, and John Vlissides, 1997. Design Patterns: Elements of Reusable Object Oriented Software. Reading, [Cook 1996] Cook, Melissa, 1996. Building Enterprise MA: Addison-Wesley. Information Architecture: Reengineering Information Systems. Upper Saddle River, NJ: Prentice Hall. [Glass 2002] Glass, Robert L., 2002. Facts and Fallacies of Software Engineering. Boston: Addison-Wesley. [Cooper 1995] Cooper, Alan, 1995. About Face: The Essentials of User Interface Design. Foster City, CA: IDG [Goldfedder 2002] Goldfedder, Brandon, 2002. The Joy Books. of Patterns: Using Patterns for Enterprise Development. Boston: Addison-Wesley. [Cooper 2003] Cooper, James W., 2003. C# Design Patterns: ATutorial. Boston: Addison-Wesley [Graham 2001] Graham, Ian, Alan O’Callaghan, and Alan Cameron Wills, 2001. Object-Oiented Methods: Principles & [Coplien 1997] Coplien, James O., 1997. “Domain Practice, Third Edition. Boston: Addison-Wesley. Analysis and Patterns,” Bell Labs. URL: http://users. rcn.com/jcoplien/oopsla/OopslaDomainPatterns- [Groff 1999] Groff, James R., and Paul N. Weinberg, 1.html. 1999. SQL: The Complete Reference. Berkeley: Osborne/ McGraw-Hill. [Crnkovic 2002] Crnkovic, Ivica, Brahim Hnich, Torsten Jonsson, and Zeynep Kiziltan, “Specifi- [Haggerty 2000] Neville Haggerty, 2000. “Modeling cation, Implementation, and Deployment of Compo- Business Rules Using the UMLand CASE,” Business nents,” Communications of ACM, Vol. 45, No. 10 Rules Community. URL: http://www.brcommunity. (October 2002). com/cgi-bin/x.pl/features/b016.html. [D’Souza 1999] D’Souza, Desmond Francis, and [Halpin 2001] Halpin, Terry, 2001. Information Modeling Cameron Wills, 1999. Objects, Components, and and Relational Databases: From Conceptual Analysis to References 3 Logical Design, Using ORM with ER and UML. San [Leffingwell 2000] Leffingwell, Dean, and Don Widrig, Fransisco: Morgan Kaufmann Publishers. 2000. Managing Software Requirements: A Unified Approach. Boston: Addison-Wesley. [Harmon 2000] Harmon, Paul, Michael Rosen, and Michael Guttman, 2000. Developing E-Business Systems [Lin 2002] Nelson Lin, “Alternatives for Rule-based and Architectures: A Manager’s Guide. San Francisco, Application Development,” Business Rules Journal, CA: Morgan Kaufmann. Vol. 3, No. 10 (October 2002). URL: http://www. BRCommunity.com/a2002/n007.html. [Hilliard 1999] Hilliard, Rich, 1999. “Using the UML for Architectural Description,” UML 99: [MacDonald 2002] MacDonald, Mathew, 2002. User Proceedings of Second International Conference Interfaces in C#: Windows Forms and Custom Controls. on the Unified Modeling Language. New York: New York: APress (Springer-Verlag, New York, Inc.). Springer-Verlag. [Malveau 2001] Malveau, Raphel, and Thomas J. [Jackson 2001] Jackson, Michael, 2001. Problem Frames: Mowbray, 2001. Software Architect Bootcamp. Upper Analyzing and Structuring Software Development Saddle River, NJ: Prentice Hall. Problems. Harlow, England: Addison-Wesley. [Martin 1996] Martin, James, and James J. Odell, 1996. [Jackson 1995] Jackson, Michael, 1995. Software- Object-Oriented Methods: Pragmatic Considerations. Requirements and Specifications: A Lexicon of Prac- Upper Saddle River, NJ: Prentice Hall. tice, Principles and Prejudices. Harlow, England: Addison-Wesley. [Martin 1995] Martin, James and James J. Odell, 1995. Object-Oriented Methods: AFoundation. Upper Saddle [Jacobson 1999] Jacobson, Ivar, Grady Booch, and James River, NJ: Prentice Hall. Rumbaugh, 1999. The Unified Software Development Process. Boston: Addison-Wesley. [Mayhew 1992] Mayhew, Deborah, J., 1992. Principles and Guidelines in Software User Interface. Englewood [Jacobson 1995] Jacobson, Ivar, Maria Ericsson, and Cliffs, NJ: Prentice Hall. Agneta Jacobson, 1995. The Object Advantage: Business Process Reengineering With Object Technology. [McBreen 2002] McBreen, Pete, 2002. Software Wokingham, England: Addison-Wesley. Craftsmanship: The New Imperative. Boston: Addison-Wesley. [Jacobson 1992] Jacobson, Ivar, Magnus Christerson, Patrik Jonsson, and Gunnar Övergaard, 1992. Object- [McClure 1997] McClure, Carma, 1997. Software Reuse Oriented Software Engineering: A Use Case Driven Techniques: Adding Reuse to the System Development Approach. Harlow, England: Addison-Wesley. Process. Upper Saddle River, NJ: Prentice Hall. [Johnson 2000] Johnson, Jeff, 2000. GUI Bloopers: Don’ts [McConnel 1996] McConnel, Steve, 1996. Rapid and Do’s for Software Developers and Web Designers. San Development: Taming Wild Software Schedules. Redmond, Fransisco: Morgan Kaufmann Publishers. WA: Microsoft Press. [Kean 2001] Kean, Liz, 2001. “Domain Engineering and [Muller 1999] Muller, Robert J., 1999. Database Design Domain Analysis,” Carnegie Mellon University: The for Smarties: Using UML for Data Modeling. San Software Engineering Institute (SEI). URL: http:// Fransisco: Morgan Kaufmann Publishers, Inc. www.sei.cmu.edu/str/descriptions/deda_body.html. [Muller 1997] Muller, Pierre-Alain, 1997. Instant UML. [Kendall 1999] Kendall, Kenneth E., and Julie E. Birmingham, UK: Wrox Press. Kendall, 1999. Systems Analysis and Design, Fourth Edition. Upper Saddle River, NJ: Prentice Hall. [Naiburg 2001] Naiburg, Eric J., and Robert A. MaksimChuk, 2001. UMLfor Database Design.Boston: [Kleppe 2003] Kleppe, Anneke, Jos Warmer, and Wim Addison-Wesley. Bast, 2003. MDAExplained, The Model Driven Architecture: Practice and Promise. Boston: Addison-Wesley. [Neighbors 1981] J. Neighbors, 1981. Software Construction Using Components. Ph.D. Thesis. Irvine: [Kulak 2000] Kulak, Daryl, and Eamonn Guiney, Department of Information and Computer Science, 2000. Use Cases: Requirements in Context. New York: University of California. ACM Press. [Nock 2004] Nock, Clifton, 2004. Data Access Patterns: [Landay 1996] Landay, James A., and Brad A. Myers. Database Interactions in Object-Oriented Applications. “Sketching Storyboards to Illustrate Interface Boston: Addison-Wesley. Behaviors,” Electrical Engineering and Computer Sciences, University of California at Berkeley. URL: [Norman 2005] Norman, Jeremy M. 2005. From Gutenberg http://www.cs.berkeley.edu/~landay/research/publi to the Internet: ASourcebook on the History of Information cations/CHI96/short_storyboard.html. Technology. Novato, CA: Historyofscience.com. References 4 [Norman 2004] Norman, Donald A. 2004. Emotional [Shoemaker 2004] Shoemaker, Martin L., 2004. UML Design: Why We Love (or Hate) Everyday Things. Applied: A .Net Perspective. New York: APress NewYork: Basic Books. (Springer-Verlag, New York, Inc.) [Norman 2002] Norman, Donald A. 2002. The Design of [Smith 1986] Smith, Sidney L., and Jane Mosier, 1986. Everyday Things. New York: Basic Books “Guidelines for Designing User Interface Software,” Report ESD-TR-86-278, Electronic System Division, [Ommering, 2002] Ommering, Rob van, 2002. ”Building MITRE Corporation, Bedford, MA. URL: http:// Product Populations with Software Components,” hcibib.org/sam/. International Conference on Software Engineering: Proceedings of the 24th International Conference on Software [Sparks 2001] Sparks, Geoffrey, 2001. “Database Engineering. ACM, 2002. URL: http://portal.acm.org. Modelling in UML,” Methods & Tools e-newsletter. URL: http://www.martinig.ch/mt/index.html. [Orfali, 1997] Orfali, Robert, and Dan Harkey, 1997. Client/Server Programming with Java and CORBA. [Spolsky 2001] Spolsky, Joel, 2001. User Interface Design NewYork: John Wiley & Sons, Inc. for Programmers. New York: APress (Springer-Verlag, New York, Inc.). [O’Rourke 2003] O’Rourke, Carol, Neal Fishman, and Warren Selkow, 2003. Enterprise Architecture Using the [Starr 2004] Starr, Paul, 2004. The Creation of the Media: Zachman Framework. Boston: Course Technology. Political Origins of Modern Communications. New York: Basic Books. [Parnas 2001] Parnas, David L., 2001. Software Fundamentals: Collected Papers by David L. Parnas. [Stephens 2003] Stephens, Matt, and Doug Rosenberg, Boston: Addison-Wesley. 2003. Extreme Programming Refactored: The Case Against XP. New York: APress (Springer-Verlag, [Petroski 2003] Petroski, Henry, 2003. Why There Is No NewYork, Inc.). Perfect Design. New York: Vintage Books. [Strum 1999] Strum, Jake, 1999. VB6 UML: Design and [Petroski 1985] Petroski, Henry, 1985. To Engineer Is Development. Birmingham, UK: Wrox Press Ltd. Human: The Role of Failure in Successful Design. NewYork: St. Martin Press. [Szyperski 2002] Szyperski, Clemens, 2002. Component Software: Beyond Object-Oriented Programming, Second [Prieto-Diaz 1990] Prieto-Diaz, Rubén, “Domain Analysis: Edition. Boston: Addison-Wesley. An Introduction,” Software Engineering Notes, 15–2, April 1990. URL: http://www.cs.jmu.edu. [Taylor 1998] Taylor, David A., 1998. Object Technology, AManager’s Guide: Second Edition. Boston: Addison- [Ravichandran 2003] Ravichandran, T, and Marcus A. Wesley. Rothenberger, “Software Reuse Strategies And Component Markets,” Communications of the ACM, [Tenner 1996] Tenner, Edward, 1996. Why Things Bite Vol. 46, No. 8. (August 2003). Back.New York: Vintage Books. [Reeder 2001] Judi Reeder, 2001. “Templates for [Togaf 2002] Open Group Architecture Forum (TOGAF), Capturing Business Rules,” Business Rules Community. 2002. “Developing Architecture View,” The OpenGroup. URL: http://www.brcommunity.com/cgi-bin/x.pl/ URL: http://www.opengroup.org/architecture. features/b056.html. [Urman 2002] Urman, Scott, 2002. Oracle 9i PL/ [Robertson 1999] Robertson, Suzanne, and James SQL Programming. New York: Oracle Press, Robertson, 1999. Mastering the Requirements Process. McGraw-Hill/Osborne. Harlow, England: Addison-Wesley. [Van Gigch 1991] Van Gigch, John P., 1991. System [Rosenberg 1999] Rosenberg, Doug, and Kendall Scott, Design Modeling and Metamodeling (The Language of 1999. Use Case Driven Object Modeling with UML: A Science). New York: Plenum Pub Corp. Practical Approach. Boston: Addison-Wesley. [Van Slyke 2003] Van Slyke, Craig , and France [Royce 1998] Royce, Walker, 1998. Software Project Bélanger, 2003. E-Business Technologies: Supporting the Management: A Unified Framework. Boston: Net-Enhanced Organization. New York: John Wiley & Addison-Wesley. Sons, Inc. [Schneider 2001] Schneider, Geri, and Jason P. Winters, [Viera 2000] Viera, Robert, 2000. Professional SQLServer 2001. Applying Use Cases, Second Edition: A Practical Programming. Birmingham, UK: Wrox Press Ltd. Guide. Boston: Addison-Wesley. [Vitharana 2003] Vitharana, Padmal, “Risks and [Shneiderman 1986] Shneiderman, B., 1986. Designing Challenges of Component-Based Software the User Interface: Strategies for Effective Human-Computer Development,” Communications of the ACM, Vol. 46, Interaction. Reading, MA: Addison-Wesley. No. 8 (August 2003). References 5

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.