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.
Hi again ! About the Quality of Service required in the part II (5 seconds in peak time), is it necessary to make assumptions about how this is achieved ? For example should I state that I'll use a feature of the application server xxxxx ? By way is it necessary to state on the assumptions on which application server the platform will run ? Thanks Francesco
The QoS requirements related to your application should be defined at your techical architecture. For example, you could use redudance or caching features to meet the performance needs.
Try to use some patterns that could improve the application performance, the Fast Lane Reader is a good example of pattern that could improve performance, and the persistence mechanism should be carefully verified.
Let the assumptions for the business decisions of your solution
Ricardo, thanks for your reply. Yes I actually included the fast lane reader pattern to improve the access of data. Last question: should I include the application server name in the Component diagram ? This choice could have implications with the QoS since some application servers provide different QoS features...... thanks Francesco
Joined: Feb 13, 2006
well, I don't think a good idea mention the application server name in the component diagram, since the component diagram emphasis is much more related to logical components, subsystems design and component dependency.
But, mention it in some deployment diagram could make more sense, because infrastructure is the point of the diagram, and sometimes is more related to the production environment instead of development enviroment.
Remember that: J2EE is a good approach to distributed application because the architect can focus only in the main businessd requirements of the application. Non functional requiements could be gained with application server features. So, the solution can be, in terms of design, technologic neutral.