Design concepts-Analysis of design documents

No matter how cool and creative the designers are, they inevitably face the actual "deliverables"-the problem of writing interactive documents. Especially in some large companies, the beauty of document writing is sometimes the key to "make your work visible".

In actual projects, documents can be grouped into three categories:

-User Requirements Documentation

-Business strategy Document

-Design Documents

The user needs the document mainly solves the website to provide the service for "who", the user is the question. Business strategy documents are mainly about product concept model, website main content and business competition analysis. The writing of design documents is the focus of this discussion.

First, find out who the document is associated with:

-The person who wrote the document

-The person who used the document

-The person who approved the document

If you are a "person who writes the document", then you have to meet the needs of the other two groups-to get the "people who use the document" (whether they are developers or researchers) to understand your design intent; Let the "person who approves the document" (perhaps your boss or shareholder) clearly understand the advantages of your design and plan for reasonable durations and costs.

Different companies to design documents are different, Ali here is called "DRD", hereinafter used DRD abbreviation to refer to the design document.

There are four main categories of design documents:

1. sitemap (Site maps)

2. Flowchart (Flow charts)

3. Wireframe (wireframes)

4, visual style (screen designs)

The following analysis:

1, sitemap (site maps): Is the visual way to express the level of the site structure.

2. Flowchart (Flow charts): An expression of a user's or system's process of executing a task.

3, Wireframe (wireframes): More like the final product presented in the hair embryo. In short, it is to throw away the color, font style, pictures and other prototype design.

4, visual style (screen designs): Almost the final state of the site to render. It includes dimensions and definitions for CSS.

Finally on the use of the document a few more words. The document sounds like a boring word, a designer who has written a document may also have a feeling that a document is finished, or that the document is written to an engineer, that the document specification is a set of content, that the developed version is a different set of content, and that sometimes the communication efficiency of the document is not as efficient as verbal ... In fact, there are many other benefits to the document besides conveying your design philosophy:

-A powerful tool for team communication: Whether it's a record of new ideas, or communication through documents and other links, "style" design documents are always easier to understand than "invisible" ideas.

-avoidance teams differ in design perceptions: A team of different people may understand the same design differently. If only by oral teaching, it will inevitably occur because of the different aspects of understanding, resulting in the final design can not butt. By designing a document, you can define concepts, and a fixed description record keeps the team consistent with the design knowledge.

-Traceable: Document recording project changes, like a history book to facilitate the review of the results of each revision. It is good for subsequent iterative design development and analysis of the results of the changes. You can also avoid project delays due to staff mobility or new entrants.

Article from the baby Swimming pool: http://www.uptui.com reprint Please indicate the original place.