How to write "complete" UI Design Manual

Most of us have gone through the UI design specification (or UI specification), and there is often a similar discussion in the forum. I will not explain the framework and structure of the UI design specification too much. Why does someone write hundreds of pages of UI design manuals that others still don't understand, or ignore the details? Today, we will focus on some of our experiences on detailed elaboration and presentation, so as not to write a UI design manual that only you can understand.
Let me talk about some of my experiences. I hope you can actively discuss them:
Our goal is: (no tooth decay, ^ _ ^ joke !)
It is necessary to clearly describe the details and interaction methods in the user interface prototype, and to facilitate the communication and inspection of other developers, demanders, and testers of the project team.
The main content includes:
1. Product goals and success criteria (for example, a brand new prediction project cannot require a user satisfaction rate of more than 90%, and the requirements for product upgrades will be higher .)
2. End User Group and purpose of the product (it is necessary to know the age, occupation, and use environment of the product)
3. satisfy basic functions first. (For example, the basic function of a DVD server is to play a video or CD)
4. main functions (use user verification and Project Group filtering among dozens of features of the product, select the most commonly used features of the user, optimize them, and display them on the interface at different levels .)
5. User interface features. (Each interface has its own features. For example, even if the touch screen operation interface is the same as the mobile phone operation interface, the structure, layout, and other features will not be the same .)
Notes
1. You must closely follow the requirements and focus on functions.
2. The description language is short and accurate (so that others will not bother reading it)
3. Keep the text easy to maintain. We recommend that you use the Outline View of word for easy modification and search.
4. You must have version management in the manual to provide detailed description of each update.
5. The icon must be submitted with the name and type, such as the desktop icon, icon in the list, toolbar icon, button icon, attribute box, or icon in the prompt information box.
6. Pay attention to the record, including the project team, users, and partners. If two or more people are confused during a specific period, this part should be elaborated more clearly.
7. Design and Implementation synchronization are the most difficult. Program They cannot be implemented, and early programs cannot determine whether they can be implemented!
8. Do not forget to maintain the prototype when maintaining the UI design manual. It is important to supplement the prototype as the UI design manual.
Easy to ignore in uidesign
1. Support error message and undo operations
2. Easy installation and uninstallation.
3. Necessary settings and help.
4. Exception Handling, Error Message description, and problem response prompt.
5. In addition to icons and buttons on the interface, you can also describe the shortcut key, Menu access key, right-click menu, and whether to support copying files from other software interfaces.
6. The domain, menu, and button cannot be clicked.
7. Status area, which is used to describe the area of the interface status, usually at the bottom of the page. (The progress bar is displayed in the state zone during PS storage)
8. Clipboard behavior: whether the text or image copied by the user in our product can be pasted into other programs.
9. pointer behavior, indicating how long the wait time should be, the hourglass status should appear, the cursor should change in the text input area, and the link may change to a small hand.
10. Sound behavior, alarm sound, button trigger pronunciation, etc.
11. unified the pop-up position, background color, size, layout and features of the message window
12. The menu bar, drop-down options, and other program action descriptions are displayed down or right.
13. Description of the dynamic state. If the window needs to be gradually hidden or gradually displayed, it indicates the time and method (translucent or mosaic) of the gradual or gradual display process.