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. Conventional design techniques do not handle this well, and over time the integrity of most systems degrades as a result. 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. 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. 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. "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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |