Garlic bread? Web design lifecycle?

June 5, 2006 | Published in: Web design & development | Tags: , , 1

This article introduces a planned work flow for developers to use on their projects. Like garlic and bread they DO actually go! Using a lifecycle a project is more organized and important principles such as scope and goals can be confirmed more quickly. Very few web developers use a lifecycle for their projects thinking that it invades the creative process, when actually a lifecycle will fine tune your ideas and streamline your work. Well take a look at the Prototype model for use in web development.
Written by Anthony Brewittt

Every project has generic phases or steps that it must go through from the beginning stages of the project to the end of the projects life span; the way that these phases are characterized is referred to as its process; methodology or lifecycle.There are many methodologies that are useful for a web development project but one that is blatantly obvious in its keen use in this kind of project is the Prototyping model (Fig 1).This is because the website project client will usually present very general objectives and not detailed requirements. This suits the prototyping models key characteristic which is an immediate product followed by a revision of that product and then the changes are made to the product and the cycle continues.

Prototyping model

The Prototyping process begins like many lifecycles with requirements gathering. Meet with the client and discuss and define the overall objectives of the project, some will be known, others will need further discussion and more time to define.
From this discussion a mock-up design of the project is produced, the mock-up matches the requirements of the initial objectives. It focuses on look and feel and functionality of the initial requirements gathering.

This quick mock-up leads to the construction of a prototype. The prototype is evaluated by the client, and then given back to the developer whom in turn revises the prototype. This cycle continues until all goals and objectives are achieved. The aim of the Prototype model is to use an iterative path to create a system that will finally meet the full objectives of the user. The more iterations the Prototyping Model has, the finer tuned the system. These initial mock-ups or quick designs are usually throw a ways and that the second or even third revision is usually more suited.

Pros

  • The idea of the prototype lifecycle is that developer gets to produce a product immediately
  • The clients get a good taste for what will be produced in the initial stages of a project.
  • The developer can get feedback throughout the projects lifespan.
  • The prototype model can be accomplishes with little paperwork.

Cons

  • The customer sees the immediate mock-up and sometimes believes that it is working, the actual truth is that the quick design will have little depth or quality.
  • Sometimes an easy and quick approach is used by the developer to reuse the code / techniques from the original product, including the bad habits / routines that lie in the old design.
  • Using the quick design approach developers sometimes use programming languages that are very well known to them to achieve a quick design rather than using a more suited language they may have to learn.

Conclusion

As developers we usually produce quick designs anyway, so we may as well incorporate a method of work that can use this behavior to our advantage. The fundamental structure of the prototype model allows a mock-up website to be built to serve as a mechanism to define the requirements of the project.

It is my belief that for website development the prototyping model is an excellent method of work because naturally we want to be productive and create. This way we get to keep the creative juices flowing as well as maintaining a structured approach that will please the client. If you dont use this model you can at least keep in your minds eye the fundamentals of the model and repeat these steps until the clients happy; listen, build/revise then test drive.

Found this post useful? Why not buy me a coffee!

Related Entries

Popular Entries

One Response to “Garlic bread? Web design lifecycle?”

RSS feed for comments on this post.

  • 1 - Artikelverzeichnis says: Reply to this comment

    Gravatar

    Thank You for another very interesting article. It’s really good written and I fully agree with You on main issue, btw. I must say that I really enjoyed reading all of Your posts. It’s interesting to read ideas, and observations from someone else’s point of view… it makes you think more. So please try to keep up the great work all the time. Greetings

    Comment made on November 20, 2007 at 1:28 am

About this site

Blue Anvil is the online web design journal & portfolio of , a web designer from Norfolk, England. Read More »
ThemeSlice

  • Featured work - More

    • Beefjack
    • Integrity
    • theotaku.com
    • Manic Melon

  • Latest Tweet - More

    • Hot and stuffy in today. Cut the lawn and cleaned the pets. Poor puff died the other day. Looks like the meds to cure the head tilt failed

  • Out of the blue - More

    • Wordpress 2.8 Memory Usage

      With the release of wordpress 2.8 some people are experiencing out of memory php errors along the lines of:

      Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 228968 bytes)

      You may also be seeing pages fail to load fully (for example the wordpress admin dashboard) if php error messages are hidden. I’ve already had one case where we thought certain plugins were to blame but in fact it was just out of memory. A possible fix (which worked in the previously mentioned case) is to add:

      @ini_set('memory_limit','64M');

      to your wp-config file. Has anyone else encoutered this error?

    • jQuery Curvy Corners 1.x and 2.x updated and moved to Google Code

      I have updated the jQuery Curvy Corners plugins (both versions) with jQuery 1.3.2 support and other enhancements. The beta 2 version is looking good and is working in all version of IE, Opera, and Firefox (as far as I can tell).

      You can grab the latest files from Google Code here. Enjoy.

    • I’m too nice: Wordpress Download Monitor plugin page add-on now included with Download Monitor version 3.1.

      It was going to be a paid add-on, but today I had a change of heart and bundled it with the newest version of download monitor. The add-on lets you make a download page using a shortcode; it lists your downloads/categories with full sorting, pagination, and search functionality. Not bad eh? See the documentation topic to see full instructions for usage, or see my download page to see it in action.

      And if you use it, please consider making a donation to ensure the continued development of the plugin!

    • 2 Announcements: New Support forum, and feedback wanted for new download page add-on

      First, I’ve implemented a support forum to Blue Anvil mainly for plugin support and ideas which can be found here. Hopefully this will make supporting my plugins easier. Feel free to add to the discussions (there is also a general web design forum too).

      Secondly, I’ve added a demo of the new download page add-on I’m making for Download Monitor. This will be a paid add-on and it would be cool to get any feedback or suggestions from anyone who would like such a feature. My download page is here. Please leave feedback on the forum or in the comments.