Design Methodologies
Prototyping with style, good points about creating content first, then css file(s) for design page layout; most client's concentrate on visual design first. Good to be able to show clients different visual (css) styles.
Don't forget Neilsen's comments about using paper first, ideal for user testing and eliminating navigation errors before any coding!
Waterfall model too rigid and unforgiving, requires client requirements 'up-front', many 'new' clients don't know what they specifically require. Clients look for guidance from developer. The process requires a more interactive approach with clients throughout the whole development and especially with user testing. Good to bring attention to ongoing maintenance, all important to keep a site up-to-date, quickly, any errors MUST be resolved at once!
Don't forget Neilsen's comments about using paper first, ideal for user testing and eliminating navigation errors before any coding!
Waterfall model too rigid and unforgiving, requires client requirements 'up-front', many 'new' clients don't know what they specifically require. Clients look for guidance from developer. The process requires a more interactive approach with clients throughout the whole development and especially with user testing. Good to bring attention to ongoing maintenance, all important to keep a site up-to-date, quickly, any errors MUST be resolved at once!
posted by Allan Maund | 6:58 PM
1 Comments:
Well, that's true. But, don't forget with the spiral model there is a combination of designer expertise (to create the initial layout etc) and user feedback to fine tune it to what either the user or the client wants.
Both with this, and with information systems design, I would go for the spiral method. This is especially relevant to web design since often the client doesn't really have any idea what they want, or what they want may be unsuitable for the purpose.
Post a Comment
<< Home