|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Most projects begin with a brief discovery phase to identify a project's goals and requirements, measurements of success, and implementation schedule. Careful attention is paid to market competitors, customer feedback (when available), and input from client team members.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The process of specifying a project's features and functionality can vary greatly from client to client, depending on a project's objective, scope, and delivery schedule. For a promotional or brochure site, a site map and content plan are typically the only deliverables at this stage. For sites with greater functionality, a detailed user interface or functional specification may be required.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A project's design phase often overlaps the specification phase, at least initially. During this phase, a site's page layout, look and feel, and branding are all designed through a series of Photoshop screen mock-ups. Depending on the project's scope and timetable, multiple design directions may be produced, followed by one or more iterations or refinements.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Once a project's functionality and look & feel are established, the process of building the site begins. Photoshop mock-ups are converted to HTML templates, which are then tested for cross-platform compatibility and optimized for downloading. (All HTML is hand-coded and commented for easy maintenance). A clickable prototype of the site or application is then developed and posted to a secure production server for client approval and revisions. Formal usability testing may be conducted at the client's discretion.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Once all revisions, additions, and testing are completed, the site is delivered to the client's production engineers for deployment. As needed, I work with the client to ensure a clean site launch.
|
|