This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello, I am now working on the part II design project for the exam and wondering if it is necessary to take system extensibility into account. Although it is not specified in the requirements, I find designing an extensible architecture very different than one that just fulfills the initial requirements. There are some catalogued architectural design patterns which enhanced extensibility: e.g, event-centric design and state machine. I've seen them used in several J2EE applications mentioned in magazine, along with the Sun's pet store program and IBM's San Francisco framework. Can someone comment on this, especially if you have finished or even passed the test? Thanks, Harry
Yes, tyically an architect is concerned with extensibility. But also scalability, latencey, capacity, performance, managability, reliablity, availability, testability, and security. The others aside, extensibility can be handled by a clean OO design. Your OO model is key to adding funcitionality later. dan'l