Developing Enterprise Java Applications with J2EE™ and UML

Problem Analysis

Requirements come in all shapes and forms and from a variety of sources. For example, they may be presented in the form of written documents by an end user, via meetings with visionaries in the company, or via direct customer interaction and face-to-face visits.

Projects often fail because the requirements were not accurately understood. This is not too surprising in light of the fact that language, whether written or oral, is imprecise by nature and open to multiple interpretations. So, the first thing to do is to make sure the basic requirements are understood; that is, go beyond what is obvious and stated in the requirements document. It is only through such an approach that you can really identify the essential usage patterns ...