The Waterfall Model
This model is quite a traditional one that focuses on more of the technical side of what's being done. It labels the design process, but in a very simplified way, which is practically common sense. This model shows very little consideration to the user. It shows mostly what the designer thinks and because the designer is the one creating the product, they get to know their work very well, so what might seem very simple to use and look nice to them, can be completely different for the user, who has never used this product before. If however, the processes could be done in a way where they can interact with not just one other process, then it would be less restricting and if the processes could involve steps that involve what should be done for the users, then that would make this model much more beneficial.
User-Centered System Design
Here, you can see that the UCSD model does include the user, which is obvious from its title. This is why I think this is the better model for me to use. I am creating a website and the way the users feel when they use it, is extremely important. This is a very iterative process, which allows me to keep fine-tuning my developments so I end up with a good website with lots of results and research to back up all the reasons on the way the site looks and functions. 
No comments:
Post a Comment