These documents are necessary to properly plan and document a website, application or production project, and they are critical to successful development, launch and maintenance/updates. Here are some examples of my work creating documentation, and my notes on what should be included in these documents.
Creative Brief
The Creative Brief is also called a site plan, depending on the project. This is the first document to be created, usually from the initial information obtained from the client or project director.
Your Creative Brief should include:
- The Site Purpose
What is the point of this website? And how is it going to fulfill that purpose better than any other site on the Web? - The Site Goals
SMART goals can help you take a mediocre site and make it great. Once you know the goals of the site, you can plan around them. - The Customers
Who is going to read this website? Try to be as specific as you can regarding your target audience. Include details like: age, hobbies, income, job title(s), and so on. You might envision different people coming to different parts of your site – that’s fine. But know who the audience is that you want to attract. And if your site is already live, you should include data on the audience that you currently have. - The Content
What will be on the site? Will the content change regularly? Will you focus on selling products with product pages or focus on providing information through articles? Is your content going to be mostly text or images or multimedia? Do you have the content already created or do you still need to get it? - The Design
What colors will your site be? Remember that design aesthetic varies across different demographics. So if you’re planning a website for cutting edge designers, it will have a different look than one designed for stay-at-home dads (except maybe those stay-at-home dads that are also cutting edge designers…). The design includes things like graphic elements, colors, fonts, and typography. The more you plan ahead of time, the easier the design phase will be. - The Timeline
Once you have the rest of the pieces of the plan together, you should decide on a schedule. Don’t forget to include time for testing, revision, and user feedback.
Flowcharts
So far I have found that this is a good way to visualize the MVC design flow.
Use case diagram
Here is how to write an effective use case and user story.
What is UML use case diagram
Site Map
I’m not sure if this is the same as what I need. This Sitemap is a google search meta code for html pages.
Here is a little info about the site map, it really is just a simple diagram showing the pages and how they link together.
WireFrame
Sequence Diagrams
Component Diagrams
Deployment Diagram
Database Diagrams