Our Process
| 423 Project Development Process |
 |
 |
 |
AnalysisThe focus of the analysis phase is to determine the objectives of the Web site, to answer the question, what must it do?" to determine the information needs of the end users the audience. Come up with a list of things that users will need/want to get done on the site (use cases) and the process they'll roughly follow to get that done. Start sketching storyboards and/or diagrams that reflect how the user will move through the site to accomplish these goals. At this point, you might want to do a basic mockup or sketch out a design.During this phase, some questions to consider are:
Pre-ProductionThe subjects discussed in Pre-production are important aspects of website development. However, there are no guidelines relating to these subjects. These are mainly to give interested parties an impression of the less technical aspects of website development. A few best practices are also indicated.DesignThe focus of the design phase is to determine how the Website will meet the clients objectives, and to determine the necessary specifications for the hardware, software, people and data resources. From your storyboard/diagrams and your requirements, come up with the best way to organize your information and functionality. This will dictate your site structure. Once you have all these issues thought through and diagrammed, your team can start doing the actual coding, content, layout, and graphics work on the basis of what you've planned.During this phase, some questions to consider are:
DevelopmentThe focus of the implementation phase is to create and assemble the HTML, images, and scripts necessary for the polished and fully functional Web site that can be uploaded to a web server environment for testing. You'll want to test as you go, even though your team should have a final testing phase to make sure everything works, the look is consistent, the code is valid, and everything is accessible.Remember always that many web development practices that are common are not necessarily correct or even good ideas. That doesn't mean you should never break the rules; it just means you need to have a good reason for doing so, and that reason needs to be documented as part of your planning process. Generally speaking, in current development practice, it is better to use external (as opposed to document-level or inline) CSS to do your formatting (including layouts) than using tables and transitional HTML. This is true for a wide variety of reasons. You may decide for your project that it would be better for the users if you used older methodologies or some combination of CSS and older methods. This is sometimes a wise decision, but once again, you'll want that decision and the reasons for it documented as part of your planning process. Testing & TrainingThe focus of the testing & Training phase is ensure that the Web site works as intended and downloads quickly and all users can navigate and administrate.Some areas of testing include:
LaunchThe launch phase deals with the live deployment of the Web site. If your team finishes early, use that extra time to improve your site. There is always something more that could be done. Do more thorough testing. Go back through your planning documents and fill in the gaps. Make sure every requirement was met. Write a document explaining your design choices. Conduct a usability test and document the results. Put helpful comments in your code. Check and see if your graphics are fully compressed. Add a design element to make the site look nicer. Add some extra accessibility features. Look for places where JavaScript might help the user be more efficient.Next... Launch Your Site…!
|
| Our Process |
| Our Workflow |
