Documents needed for a web project
Abstract: A web project can be resolved with 3 documents. A. A project document. Objectives, strategy, etc … B. An arborescence. C. A development of screens.
With these documents we can carry out a web project with confidence and, above all, confident you are using a language of communication between departments standard, useful and easy to put into action.
The project document
This can be a word document or power point which we express clearly the following points.
Site Objectives
Target
Strategies
Resource requirements
Deadlines
The objectives must be clear and realistic. It is very important at this point give ideas how to evaluate and define specific values for both our objectives.
Instead of “Increase sales”, say that our goal is “Increase sales by 10%.”
This objective is clear, is measurable and can be evaluated at the end of the project.
The advantage of measurable objectives is to create security and removes some of the uncertainty of many projects are started without knowing where it ends.
The target audience is essential that you are very well defined so that communication with them is appropriate. It is no use pointing to the entire universe with a communication too generic as it will be difficult to assess results.
Best design actions for each user group so we can evaluate faster and more accurate results.
The strategy is needed to implement the operational levels. I personally opt for simple strategies soil (reducing the weight of the site, shorten the registration fields, create pages with directories) and much of the success will be in the operational and monitoring.
The strategy may be more crucial in the launching of new sites in new markets and mature markets that is increasingly difficult to get noticed, but otherwise the experience will teach us that old ideas (search engines, LDAP directory) are still the stars of Site and that the difference between success and failure is in the operation thereof (eg Google Altavisa front …).
Within Resource requirements need to describe as accurately as possible “who” and “what” is necessary. Within the “who” is the team that developed the project, but need to list the individuals within the organization will be required to be available. Marketing, customer service, etc …
Within the “what” as soon as possible will be essential to list the needs that we will describe the project and where possible their usefulness. “We need the logs to assess which parts of the site are being visited, otherwise we risk to remove parts of use to users.
Finally, we offer a timetable as realistic as possible describing stages of delivery, control points, which may be decisive elements for the completion of the project … “The content must be approved by 15 and that will start data entry from 17″
Arborescence
The arborescence is an illustration of the planned site where the basic information unit responds to each page that the user will find on your journey.
In turn, these basic units are connected to each other just as the links will create links to visualize the depth of navigation.
At the end of the document usually has a tree structure.
This map is essential to detect possible flaws in our architecture because we will see if the tree branches weighed more than others, if relevant documentation is far behind the front, and so on.
This document is very useful at the production level as we have on one page the whole site and we can mark items developed for developing, etc …
This paper also can be painted calls to databases, with access restricted sections, search engines, loops, etc …
A development of screens
The latter document shows every single screen of the site developed as closely as possible with the final elements of navigation.
This document is where you can check the labeling of our site and if our navigation system is capable of supporting all cases to which we can face.
Usually a site will pass through sections where the main menu is sufficient, others where necessary a second level of navigation and others where necessary, a third layer for possible calls, extended documentation, other sections within the site ..
It is key in this development of screens to give consistency all these cases and prepare templates for future expansion … or have in mind possible mergers of sections to gain space at the entrance of new content.
This document is best to develop it in HTML format. Is the system easier to update, we can create a prototype of low quality that the customer will see the web in a fairly close to the final product will be especially easy to update.