Most the time the requirements process isn’t about identifying, and then assessing, and then documenting, and then validating. In reality, most of these tasks are being performed simultaneously. Another reality is the requirements process is quite often skipped or short changed. Because a site is a visual representation of the content you want to provide to your audience, it is easy to assume that you can jump straight to the design phase. If you already know which CMS you will be using and are an experienced planner, you can combine aspects of the requirements, design, and development phases of the life-cycle.
admin1 - Sat, 2009-11-21 15:50
type of content: