This aspect is crucial because, let??™s face it, the visitor is often more impressed with how
a site looks and how easy it is to use than about which technologies and techniques are used
behind the scenes or what operating system the web server is running. If the site is slow, hard
to use, or easy to forget, it just doesn??™t matter what rocket science was used to create it.
Unfortunately, this truth makes many inexperienced programmers underestimate the
importance of the way the invisible part of the site is implemented??”the code, the database,
and so on. The visual part of a site gets visitors interested to begin with, but its functionality
makes them come back. A web site can sometimes be implemented very quickly based on
certain initial requirements, but if not properly architected, it can become difficult, if not
impossible, to change.
For any project of any size, some preparation must be done before starting to code. Still,
no matter how much preparation and design work is done, the unexpected does happen, and
hidden catches, new requirements, and changing rules always seem to work against deadlines.
Even without these unexpected factors, site designers are often asked to change or add
functionality many times after the project is finished and deployed. This will also be the case
for TShirtShop, which will be implemented in three separate stages, as discussed in Chapter 1.
Pages:
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67