A template to use is provided. Please note, emphasis should be placed in section 3. User Interface Walkthrough. Create mock ups of how your UI should look like and how it should function.
The user interface should be designed on,
Storm water is collected in three different locations in a school, 1.playground, 2. parking, 3. classrooms.
All the water which is collected in a tank, should show the volume of the water collected in the tank, and the temperature of the water in that tank, using a sensor, which is placed in that tank.
2.User Interface Standards
Give the reader an overview of the design standards that you will use to maintain consistency in the user interface throughout your system. Use illustrations as necessary. Discuss general screen layouts, common components (e.g., buttons, menus), general error handling, and navigation. You do not need to go into details such as colors and fonts. [Length will vary, but I would expect at least one overall screen layout illustration with explanations of the different screen areas, common components that will be used, and how the user will generally navigate through the system.]
3.User Interface Walkthrough
Provide a diagram that illustrates how the user will navigate from one screen to another (I call this a “navigation diagram”).Label each symbol that represents a screen so that you can reference the screens, if necessary, later in the document. Give a brief description of what the diagram as a whole represents.
Next, guide the reader through a series of screen shots of all system screens. (You do not need to include error and confirmation messages/pop-ups.) Give the screen shots figure numbers and labels that match those in the navigation diagram. Refer to the figure numbers in the text of the walkthrough. Explain what the reader is seeing in each screen shot: the major screen areas, menus, what each button does, how to navigate to the next screen or return to the previous, etc. Note that if a feature has been standardized (e.g., how to return to the previous screen) and explained in Section 2, you do not need to repeat it here.
Screen shots should not be hand written, but may be drawn using any tool you wish (e.g., Visual Basic, PowerPoint, a drawing program, etc.). At this point in the process, they are a best approximation as to what the user interface will look like in both layout and annotation.
Include a full description of all data items that can be entered into the system by the user. The description should include the item’s basic data type (e.g., integer, string), its limits, and its allowable format(s). Be sure to uniquely identify each data item. For example, if you are using a GUI, a data item can be identified by screen name and data item label. A tabular format works well for the data validation information.
If your product generates any hard copy reports that cannot be previewed on screen (i.e., are not described in Section 3), show their formats here. Otherwise, omit this section.
Appendix A – Agreement Between Customer and Contractor
Place on a separate page. Describe what the customer and your team are agreeing to when all sign off on this document. [One paragraph] Include a statement that explains the procedure to be used in case there are future changes to the document. [One paragraph] Provide lines for typed names, signatures, and dates for each team member and the customer. Provide space for customer comments.
Appendix B – Team Review Sign-off
Place on a separate page. Provide a brief paragraph stating that all members of the team have reviewed the document and agree on its content and format. Provide lines for typed names, signatures, dates, and comments for each team member. The comment areas are to be used to state any minor points regarding the document that members may not agree with. Note that there cannot be any major points of contention.
Appendix C – Document Contributions
Identify how each member contributed to the creation of this document. Include what sections each member worked on and an estimate of the percentage of work they contributed. Remember that each team member must contribute to the writing (includes diagrams) for each document produced.