| Overview
"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."
—MichaelWard, 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."
—Charles B. Haley, research fellow, The Open
University, U.K.
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.
Editorial ReviewsProduct Description"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." --MichaelWard, 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." --Charles B. Haley, research fellow, The Open University, U.K. 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. |
Other Readers Also Read | Top Sellers in This Category | Browse Similar Topics | | | Top Level Categories:Sub-Categories: | | | | |
Reader Reviews From Amazon (Ranked by 'Helpfulness') Average Customer Rating: based on 5 reviews. why is everything a use case ;), 2009-03-19 Reviewer rating: Despite the title of my review I would like to say that first up great book.
The only criticism I would offer is that the Requirements Engineering world has unified around i* approaches [...]which are especially good at capturing and expressing non-functional requirements. I think pushing use cases at non-functional requirements is a little nieve given the semantics.
What appears to be happening in places is a merging of i* and Use Case approaches (especially at System Engineering leves)[...].
i* doesn't break the intent of what Jacobson and Ng attempt with so-called "Infrastructure Use Cases". i* is simply designed for functional and non-functional modelling - rather than trying to use a screw-driver as a hammer.
Why bother? Use case have come from the C++ world where software developers would scratch a quick "requirement" model before diving into coding. Agile methods have diluted this to "User Stories" which look remarkably like "features" as expressed by Jacobson/Ng. (In i* "features" whould be variously hard or soft goals.)
So what would be ideal? The next edition moulds Aspects, Goals (i*) and Use Cases together. | Too Abstract And Not backed by AOP implementation!, 2009-01-21 Reviewer rating: The new ideas (use case slices and use case modules) that the authors try to get across is not backed by a practical (implementable) project that show how one can model, analyze, design, implement, deploy and test. Considering Aspect Oriented Programming (AOP) implementation is real and easy using AspectJ, this book just songs and dances and repeats use case modeling concepts over and over again without actually showing a concrete AOP based software development. It would have been nice if the authors provided the complete model from start to finish for the Hotel Management backed up by AOP code. But the book doesn't deliver. It's just too theoretical. | Finally I know what Aspect Programming is for, 2007-03-25 Reviewer rating: Nothing more to say. Clear explanation that Aspect Programming fills the gap in software engineering, and that this it is more than just fancy logging mechanism. But this book makes also clear that Aspect Programming must be used from very early stages of software design process, but not simply as add-on to object oriented design. Worth to read, despite whether you will use Aspect Programming or not. If not, you will know the limitation of Object Oriented paradigm. If yes, you will know how to use Aspect programming right | how use cases can lead to aspect oriented coding, 2006-04-28 Reviewer rating: Jacobson and Ng present a detailed exposition of what aspect oriented programming means. As implemented in the AspectJ language, an extension to Java for expressly this purpose. They explain that object oriented programming has a conceptual limitation. Indeed, it is good to separate code into components using OO. But in general you have M concerns and N components, where M>N. Sometimes, M>>N. So if you imagine an M x N matrix, then you can easily see how entanglement arises. A given component may have code from multiple concerns. Which makes it harder to implement and maintain.
The authors describe how if you start at the design level, with use cases, that these can effectively be considered concerns. Then, taking these use cases and using AspectJ, you can design and write code that keeps the use cases/concerns separate as much as possible. While being able to compose code for several concerns when necessary. Use cases are of course widely used in many design processes. An attraction of this book is in showing how starting with the familiarity of use cases, you can logically understand and implement an aspect oriented coding.
The book is primarily written at the design level. While some small code fragments are offered as examples, you should have some earlier knowledge of AspectJ. The book is not, per se, a syntax manual on the latter. | In Absentia: Unfortunate Sign of the Times, 2005-11-28 Reviewer rating: No one has reviewed this?? This is a great book. Jacobson describes it as the result of a kind of epiphanal realization that AOP could solve an inherent problem in use case design. This is how the book hooked me: rather than just showing AOP as a series of stunts, or explaining it w/the usual little examples (logging, exceptions, etc.), this book starts w/the strategic implications and then works down to the tactical. The basic premise is that the so called separation of concerns is always followed by a required recomposition of said concerns and that aspects provide a means of recomposing w/out introducing 'leaks' and the like.
It's pathetic that no one is reading this book. Ballmer was mooning last week about how he's going to erase Rational (and with it the UML). Jacobson and use cases are the best part of the UML and one of the great things about this book is it opens the door to a conception of a different design approach that short circuits some of the flab from the RUP req/spec cycle (which, when trying to be iterative, tends instead toward rapid repeat waterfall).
Despite the apparent dearth of readership, I predict this book will be seen as one of the most important of this decade.
|
Some information above was provided using data from Amazon.com. View at Amazon > |
| |
|
|
