Aspect-Oriented Software Development with Use Cases

Part IV. Establishing an Architecture Based on Use Cases and Aspects

Building good software is like building many other kinds of systems. You start by building a skeleton, and then you add on to that skeleton, making sure that whatever you add to the system later will not impact what you built previously. When it comes to software, you can, after some initial prototyping, design a skinny system that includes the skeleton that you can build upon. To make sure that you can grow the skinny system to become the full-fledged system, you must determine whether the features not yet included in the skinny system can be added later without redesign of the system. In fact, you need to make sure that all risks that may impact the graceful growth of the skinny ...