Use Case Realizations
Thus far, our focus has been on capturing the requirements and making sure we understand what we need to build. Everything we have done is generic in that no consideration has been given to how we will actually design or implement our solution.
The same set of functional requirements can lead to vastly different systems that are functionally equivalent but are totally different in the way they solve specific problems. For example, the online banking system could be offered to the customer base as two different products: an application that actually dials into the banking system or a Web-based application that uses the Internet (perhaps the bank wants to market the direct dial version as a more upscale and secure version). ...
Get Developing Enterprise Java Applications with J2EE™ and UML now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
