Aspect-Oriented Software Development with Use Cases PDF
Preview Aspect-Oriented Software Development with Use Cases
This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Aspect-Oriented Software Development with Use Cases By Ivar Jacobson, Pan-Wei Ng Publisher: Addison Wesley Professional Pub Date: December 30, 2004 ISBN: 0-321-26888-1 Pages: 464 Table of • Contents • Index Aspect-oriented programming (AOP) is a revolutionary new way to think about software engineering. AOP was introduced to address crosscutting concerns such as security, logging, persistence, debugging, tracing, distribution, performance monitoring, and exception handling in a more effective manner. Unlike conventional development techniques, which scatter the implementation of each concern into multiple classes, aspect-oriented programming localizes them. Aspect-oriented software development (AOSD) uses this approach to create a better modularity for functional and nonfunctional requirements, platform specifics, and more, allowing you to build more understandable systems that are easier to configure and extend to meet the evolving needs of stakeholders. In this highly anticipated new book, Ivar Jacobson and Pan-Wei Ng demonstrate how to apply use casesa mature and systematic approach to focusing on stakeholder concernsand aspect-orientation in building robust and extensible systems. Throughout the book, the authors employ a single, real-world example of a hotel management information system to make the described theories and practices concrete and understandable. The authors show how to identify, design, implement, test, and refactor use-case modules, as well as extend them. They also demonstrate how to design use-case modules with the Unified Modeling Language (UML)emphasizing enhancements made in UML 2.0and how to achieve use-case modularity using aspect technologies, notably AspectJ. Key topics include Making the case for use cases and aspects Capturing and modeling concerns with use cases Keeping concerns separate with use-case modules Modeling use-cases slices and aspects using the newest extensions to the UML notation Applying use cases and aspects in projects Whatever your level of experience with aspect-oriented programming, Aspect-Oriented Software Development with Use Cases will teach you how to develop better software by embracing the paradigm shift to AOSD. This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Aspect-Oriented Software Development with Use Cases By Ivar Jacobson, Pan-Wei Ng Publisher: Addison Wesley Professional Pub Date: December 30, 2004 ISBN: 0-321-26888-1 Pages: 464 Table of • Contents • Index Copyright Praise for Aspect-Oriented Software Development with Use Cases The Addison-Wesley Object Technology Series The Component Software Series Preface What Is Aspect-Oriented Programming? What Is Aspect-Oriented Software Development? AOSD with Use Cases What This Book Is What This Book Is Not What You Need Before Reading This Book How to Read This Book How This Book Came About Acknowledgments Part I: The Case for Use Cases and Aspects Chapter 1. Problem to Attack Section 1.1. The Use of Components Today Section 1.2. Limitation of Components Section 1.3. Approaching a Solution Section 1.4. Keeping Concerns Separate Chapter 2. Attacking the Problem with Aspects Section 2.1. Approaching a Solution with Aspects Section 2.2. Keeping Peers Separate with Aspects Section 2.3. Keeping Extensions Separate with Aspects Section 2.4. Need for Methodological Guidance Chapter 3. Today with Use Cases Section 3.1. Use Cases in Brief Section 3.2. Use-Case-Driven Development Section 3.3. Roles and Benefits of Use Cases Section 3.4. Gaps in the Use-Case Technique Section 3.5. Bridging the Gaps with Aspects Chapter 4. Tomorrow with Use-Case Modules Section 4.1. Building Systems in Overlays with Use-Case Slices Section 4.2. Keeping Peer Use Cases Separate Section 4.3. Keeping Extension Use Cases Separate Section 4.4. Developing with Use-Case Modules Part II: Modeling and Capturing Concerns with Use Cases This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Chapter 5. Modeling Concerns with Use Cases Section 5.1. Use-Case Modeling Section 5.2. Use-Case Instances and Flows of Events Section 5.3. Describing Use Cases Section 5.4. Visualizing Use-Case Flows Section 5.5. Summary and Highlights Chapter 6. Structuring Use Cases Section 6.1. Use-Case Relationships Section 6.2. Use-Case Extend Relationship Section 6.3. Use-Case Include Relationship Section 6.4. Use-Case Generalization Section 6.5. Utility Use Cases Section 6.6. Summary and Highlights Chapter 7. Capturing Concerns with Use Cases Section 7.1. Understanding Stakeholder Concerns Section 7.2. Capturing Application Use Cases Section 7.3. Capturing Infrastructure Use Cases Section 7.4. Summary and Highlights Part III: Keeping Concerns Separate with Use-Case Modules Chapter 8. Keeping Peer Use-Case Realizations Separate with Aspects Section 8.1. Realizing Peer Use Cases Section 8.2. Keeping Use-Case Specifics Separate Section 8.3. Dealing with Overlap Section 8.4. Summary and Highlights Chapter 9. Keeping Extensions Separate with Pointcuts Section 9.1. Realizing Extension Use Cases Section 9.2. Keeping Modularity of Extension Use-Case Realizations Section 9.3. Parameterizing Pointcuts Section 9.4. Generalizing Extension Use-Case Realizations Section 9.5. Templating Use-Case Slices Section 9.6. Summary and Highlights Chapter 10. Building Systems with Use-Case Modules Section 10.1. A System Comprises Models Section 10.2. Use-Case Model Section 10.3. Analysis Model Section 10.4. Design and Implementation Models Section 10.5. Use-Case Modules Cut Across Models Section 10.6. Composing and Configuring Use-Case Modules Section 10.7. Summary and Highlights Part IV: Establishing an Architecture Based on Use Cases and Aspects Chapter 11. Road to a Resilient Architecture Section 11.1. What Is Architecture? Section 11.2. What Is a Good Architecture? Section 11.3. Steps to Establish an Architecture Baseline Section 11.4. Begin with a Platform-Independent Structure Section 11.5. Overlay Platform Specifics on Top Section 11.6. Summary and Highlights Chapter 12. Separating Functional Requirements with Application Peer Use Cases Section 12.1. Analyzing Application Use Cases Section 12.2. Keeping Application Use Cases Separate Section 12.3. Designing Application Use Cases This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Section 12.4. Refining Design Elements Section 12.5. Summary and Highlights Chapter 13. Separating Functional Requirements with Application-Extension Use Cases Section 13.1. Analyzing Application-Extension Use Cases Section 13.2. Keeping Application-Extension Use Cases Separate Section 13.3. Designing Application-Extension Use Cases Section 13.4. Dealing with Changes in the Base Section 13.5. Summary and Highlights Chapter 14. Separating Nonfunctional Requirements with Infrastructure Use Cases Section 14.1. Analyzing an Infrastructure Use Case Section 14.2. Keeping Infrastructure Use Cases Separate Section 14.3. Designing Infrastructure Use Cases Section 14.4. Dealing with Multiple Infrastructure Use Cases Section 14.5. Summary and Highlights Chapter 15. Separating Platform Specifics with Platform-Specific Use-Case Slices Section 15.1. Keeping Platform Specifics Separate Section 15.2. Overlaying User Interfaces Section 15.3. Overlaying Distribution Section 15.4. Overlaying Persistency Section 15.5. Preserving the Use-Case Structure Section 15.6. Summary and Highlights Chapter 16. Separating Tests with Use-Case Test Slices Section 16.1. Test-First Approach Section 16.2. Identifying Test Cases from Use Cases Section 16.3. Identifying Elements to Be Tested Section 16.4. Designing and Implementing Tests Section 16.5. Summary and Highlights Chapter 17. Evaluating the Architecture Section 17.1. Putting It Together Section 17.2. Evaluating Separation of Concerns Section 17.3. Evaluating and Achieving Systemwide Concerns Section 17.4. Summary and Highlights Chapter 18. Describing the Architecture Section 18.1. Architecture Description Comprises Architectural Views Section 18.2. Architectural View of the Use-Case Model Section 18.3. Architectural View of the Analysis Model Section 18.4. Architectural View of the Design Model Section 18.5. Summary and Highlights Part V: Applying Use Cases and Aspects in a Project Chapter 19. Running a Project Section 19.1. Iterative Development Section 19.2. Estimating Development Effort Section 19.3. Planning and Controlling the Project Section 19.4. Productivity Gains by Keeping Concerns Separate Section 19.5. Summary and Highlights Chapter 20. Tailoring the Approach Section 20.1. Achieving the Right Balance Section 20.2. Selecting Disciplines to Apply Section 20.3. Adopting at Different Phases of a Project Section 20.4. Summary and Highlights Chapter 21. Aspects and Beyond This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Section 21.1. Building a System in Extensions Section 21.2. Balancing Best Practices Section 21.3. The Road Ahead Appendix A. Modeling Aspects and Use-Case Slices in UML Section A.1. Modeling Intertype Declarations with Class Extensions Section A.2. Modeling Advices with Operation Extensions Section A.3. Modeling Pointcuts Section A.4. Modeling Use-Case Slices Appendix B. Notation Guide Section B.1. Package Section B.2. Actors and Use Cases Section B.3. Classes and Instances Section B.4. Components and Interfaces B.5 Processes and Nodes References Glossary Index This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to regis.ter it. Thanks Copyright The authors and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The publisher offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales, which may include electronic versions and/or custom covers and content particular to your business, training goals, marketing focus, and branding interests. For more information, please contact: U. S. Corporate and Government Sales (800) 382-3419 [email protected] For sales outside the U. S., please contact: International Sales [email protected] Visit us on the Web: www.awprofessional.com Library of Congress Cataloging-in-Publication Data Jacobson, Ivar. Aspect-oriented software development with use cases / Ivar Jacobson, Pan- Wei Ng. p. cm. Includes bibliographical references and index. ISBN 0-321-26888-1 (pbk. : alk. paper) 1. Computer softwareDevelopment. 2. Object-oriented programming (Computer science) I. Ng, Pan-Wei, 1969- II. Title. QA76.76.D47J343 2004 005.1dc22 2004023750 Copyright © 2005 Pearson Education, Inc. All rights reserved. Printed in the United States of America. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. For information regarding permissions, write to: Pearson Education, Inc. Rights and Contracts Department One Lake Street This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. Upper Saddle River, NJ 07458 Text printed in the United States on recycled paper at Courier in Stoughton, Massachusetts. First printing, December 2004 This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to regis.ter it. Thanks Praise for Aspect-Oriented Software Development with Use Cases "A refreshingly new approach toward improving use-case modeling by fortifying it with aspect orientation." RAMNIVAS LADDAD author of AspectJ in Action "Since the 1980s, use cases have been a way to bring users into software design, but translating use cases into software has been an art, at best, because user goods often don't respect code boundaries. Now that aspect-oriented programming (AOP) can express crosscutting concerns directly in code, the man who developed use cases has proposed step-by-step methods for recognizing crosscutting concerns in use cases and writing the code in separate modules. If these methods are at all fruitful in your design and development practice, they will make a big difference in software quality for developers and users alike." WES ISBERG AspectJ team member "This book not only provides ideas and examples of what aspect-oriented software development is but how it can be utilized in a real development project." MICHAEL WARD ThoughtWorks, Inc. "No system has ever been designed from scratch perfectly; every system is composed of features layered in top of features that accumulate over time. Conventional design techniques do not handle this well, and over time the integrity of most systems degrades as a result. For the first time, here is a set of techniques that facilitates composition of behavior that not only allows systems to be defined in terms of layered functionality but composition is at the very heart of the approach. This book is an important advance in modern methodology and is certain to influence the direction of software engineering in the next decade, just as Object-Oriented Software Engineering influenced the last." KURT BITTNER IBM Corporation "Use cases are an excellent means to capture system requirements and drive a user-centric view of system development and testing. This book offers a comprehensive guide on explicit use-case-driven development from early requirements modeling to design and implementation. It provides a simple yet rich set of guidelines to realize use-case models using aspect-oriented design and programming. It is a valuable resource to researchers and practitioners alike." DR. AWAIS RASHID Lancaster University, U.K., and author of Aspect-Oriented Database Systems "AOSD is important technology that will help developers produce better systems. Unfortunately, it has not been obvious how to integrate AOSD across a project's lifecycle. This book shatters that barrier, providing concrete examples on how to use AOSD from requirements analysis through testing." This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks. CHARLES B. HALEY research fellow, The Open University, U.K. . This document was created by an unregistered ChmMagic, please go to http://www.bisenter.com to register it. Thanks
Description:The list of books you might like
