基于用例的面向方面软件开发——经典原版书库

    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 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.
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...
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.

软件业的生存之道	精通SOA：基于服务总线的Struts+EJB+W..	SOA权威指南：通过BEA Aqualogic Serv..	软件测试（英文版·第二版）——经典..	大师品软件——软件之痛与应对之道
软件工程：实践者的研究方法（原书第6..	开源的成功之路	40岁登上健康快车(洪昭光著）	中华人民共和国劳动合同法	从零到百亿--Facebook创业故事

    lvar Jacobson博士，是许多技术“之父”，这包括组件及基于组件的软件架构，用例，现代业务工程，以及Ratlonal统一过程。他还是统一建模语言(UML)的三位创始人之一。同时他也是关于这些方法和技术的五本畅销书籍的作者，以及两本关于UML的引领性书籍的合著者。lvar 博士是JaczoneAB公司的创始人，在该公司他与其女儿、合作者Agneta Jacobson共同开发一套开创性的新产品，它将包括支持软件开发的智能代理。同时他还是lvar Jacobson Consulting公司 (IJC)的创始人，其目标是向全世界的开发团队推广优秀的软件开发实践。 　　Pan-Wei Ng博士，在lvar Jacobson Consulting公司(1JC)扮演了多个角色。Pan-Wel博士负责针对软件架构、用例、迭代开发、方面技术等相关技术的最佳实践定义、开发相关素材。这些工作通常需要基于实践进行，才能够确保归纳的最佳实践切实、实用。Pan-Wel博士还积极地和客户一起工作，以确保这些公司和项目团队能够，快速、安全地采用这些最佳实践。

　　That you have picked up this book tells us that you are a member of the software development community: a tester, a developer, a project leader, a project manager, an architect, an analyst, or a member involved in one of the many other aspects of developing. We also know that you are someone who wants to improve the way you develop software. You want your sys tem to be more maintainable, more extensible, more reusable, and if you are a project leader, you want your team to be more productive. You know that these goals are not always easy to achieve.

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

What Is Aspect-Oriented Programming?. That you have picked up this book tells us that you are a member of the software development community: a tester, a developer, a project leader, a project manager, an architect, an analyst, or a member involved in one of the many other aspects of developing. We also know that you are someone who wants to improve the way you develop software. You want your system to be more maintainable, more extensible, more reusable, and if you are a project leader, you want your team to be more productive. You know th..