基于用例的面向方面软件开发——经典原版书库 (2008 年度畅销榜NO.14280 )

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..\r\n 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.\r\n In this highly anticipated new book, Ivar Jacobson and Pan-Wei Ng demonstrate how to apply use cases--a mature and systematic approach to focusing on stakeholder concerns--and 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.\r\n 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.0--and how to achieve use-case modularity using aspect technologies, notably AspectJ...\r\nKey topics include\r\n ·Making the case for use cases and aspects\r\n ·Capturing and modeling concerns with use cases\r\n ·Keeping concerns separate with use-case modules\r\n ·Modeling use-cases slices and aspects using the newest extensions to the UML notation\r\n ·Applying use cases and aspects in projects...\r\n 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.\r\n

Table of Contents \r\nPreface. \r\nAcknowledgments. \r\nList of Sidebars. \r\nI. THE CASE FOR USE CASES AND ASPECTS. \r\n 1. Problem to Attack. \r\n 2. Attacking the Problem with Aspects. \r\n 3. Today with Use Cases. \r\n 4. Tomorrow with Use Case Modules. \r\nII. MODELING AND CAPTURING CONCERNS WITH USE CASES. \r\n 5. Modeling Concerns with Use Cases. \r\n 6. Structuring Use Cases. \r\n 7. Capturing Concerns with Use Cases. \r\nIII. KEEPING CONCERNS SEPARATE WITH USE CASE MODULES. \r\n 8. Keeping Peer Use Case Realizations Separate with Aspects. \r\n 9. Keeping Extensions Separate with Pointcuts. \r\n 10. Building Systems with Use Case Modules. \r\nIV. ESTABLISHING AN ARCHITECTURE BASED ON USE CASES AND ASPECTS. \r\n 11. Road to a Resilient Architecture. \r\n 12. Separating Functional Requirements with Peer Application Use Cases. \r\n 13. Separating Functional Requirements with Application Extensions Use Cases. \r\n 14. Separating Non-Functional Requirements with Infrastructure Use Cases. \r\n 15. Separating Platform Specifics with Platform Specific Use Case Slices. \r\n 16. Separating Tests with Use Case Test Slices. \r\n 17. Evaluating the Architecture. \r\n 18. Describing the Architecture. \r\nV. APPLYING USE CASES AND ASPECTS IN A PROJECT. \r\n 19. Running a Project. \r\n 20. Tailoring the Approach. \r\n 21. Aspects and Beyond.\r\n

无封面