Mendel:
This is a wonderful chapter. I really like the lists throughout, and it has prompted me to think more carefully. In some ways this article summarizes much of what we have been discussing about design up to this point. The authors remind us that 'content' is more than the words and pictures we put in our pages. Everything we do in an application communicates in some way.
For me personally, it means that my designs end up taking longer because there is more to consider. However, I think they have improved as a result. I think I am finally getting the "hang" of colour. My Home web site as well as the Mink Hollow web site use only three main colours: a light cream, reddish-brown, and dark green. I want the sites to look organic and so have chosen fairly natural colours. The colours are not meant to interfere with the other content, but rather to augment it. The links on the site have also been changed to these colours. Unvisited links are green (closest to the common blue), and visited ones are reddish-brown (like the red). I use underlining throughout to mark links - I like links to be obvious. I also chose these colours because I did not want them to clash with or detract from other graphics.
In the past year I have now been introduced more formally to Instructional Design, Interface Design, and Multimedia design. I find it fascinating how many elements of design are similar regardless of what it is we are designing. While the bulk of my personal experience is with software design and systems analysis, I have also had occasion to design: clothing, small buildings, cages and enclosures, dog training, university courses, web sites, and other things. I have also had the good fortune to see the design process in action when applied to the entertainment industry (movies, theater, radio productions, music, and other forms of multi-media), the advertising industry (in-store displays), and others. The range of applications is diverse, yet the design process in each case has significant common elements.
Almost all design tasks share a number of major elements. The exact terminology will change from domain to domain, but the processes remain. In software design, they are (Budgen, 1993):
- Requirements: needs and constraints (what is needed)
- Specification (what will be done)
- ** Design ** (how it will be done)
- Implementation (actually making it)
- Testing : verification :[are we building the thing right?]; Validation: [are we building the right thing?] (Making sure it was the right thing done right)
Since all of these elements appear in one form or another in almost every single design process, regardless of the thing being designed, it would indicate that lessons learned from applications of various models in other disciplines could be beneficial to the design processes we are currently considering (applications, instructional solutions, interface, etc.). Software design (the current trends in software engineering are just a small subsection) is one area where the design process has been extensively studied and so it has many insights to offer.