5. Detailed Functional Requirements
5.1 UI Navigation & Screen Flow
<<Frequently, software engineers can‘t visualize the UI (User Interface),
since they are deft in left-brain logical reasoning, and not in right-brained
activities like UI design. To create the UIs, the product manager in software
firms should have graphic designers reporting to him, or resource allocated
to him. These designers, who are skilled in everything from Microsoft
Frontrage to Coffeecup / Evrsoft HTML editors to Macromedia/Adobe
DreamWeaver / Photoshop will be able to come up with user frieldly screen
shots and HTML mockups.
The HTML mockups will serve a dual purpose in product management.
While the product is being built, the product manager can take the mockups
to customers / prospects to show an upcoming product build. At the same
time, the HTML mockups can be ASP or JSP fed by application logic to
build the product, depending on whether the underlying architecture is dot-
net or J2EE.
>>
<< Once the HTML mockups are ready, the Use Cases can reference those
mockups in the appropriate section as described in the Use Case templates in
the previous section.
.
.
.
However, describing the difficult to understand screen flows can be made
easier and save time for the product manager, if crafted upfront. The
descriptions below describe how to do that. Appropriated fields should be
circled, highlighted, etc.>>
