Elaboration
So you have the go-ahead to start a project. At this stage, typically, you have only a vague idea of the requirements. For instance, you might be able to say:
We are going to build the next-generation customer support system for the Watts Galore Utility Company. We intend to use object-oriented technology to build a more flexible system that is more customer-oriented—specifically, one that will support consolidated customer bills.
Of course, your requirements document will likely be more expansive than that, but it may not actually say very much more.
At this point, you want to get a better understanding of the problem.
What is it you are actually going to build?
How are you going to build it?
In deciding what issues to look into ...
Get UML Distilled: A Brief Guide to the Standard Object Modeling Language, Second Edition 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.
