11.11.2014 Views

Professional Web Design: Techniques and Templates, Fourth Edition

Professional Web Design: Techniques and Templates, Fourth Edition

Professional Web Design: Techniques and Templates, Fourth Edition

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

42<br />

Chapter 3 ■ Things to Consider Before Beginning<br />

2. B<strong>and</strong>width requirements: The way a site is designed will determine how<br />

large of a download the site will require. By underst<strong>and</strong>ing the b<strong>and</strong>width<br />

(download size) requirements, a designer can determine the balance between<br />

graphics <strong>and</strong> text to be used.<br />

3. Resolution requirements: A site with improper resolution can hinder its<br />

usability or credibility.<br />

4. Scalability requirements: Because nearly all sites are in continual evolution,<br />

it is important for the designer to consider how the site can be exp<strong>and</strong>ed<br />

or changed in the future.<br />

5. Content requirements: The content volume of a site will influence nearly<br />

all other requirements, including the look <strong>and</strong> feel, the b<strong>and</strong>width, resolution,<br />

<strong>and</strong> scalability.<br />

Depending on the size of a <strong>Web</strong> site, different levels of documentation are necessary.<br />

Many small sites (around 5 to 15 pages) only require the designer <strong>and</strong><br />

client to email or call each other during the development process. Larger sites<br />

(more than 15 pages) often require more thorough documentation, which includes<br />

an official requirements document. Without such documentation, the<br />

designer could have a site nearly completed when the client says, ‘‘Oh, that’s not<br />

what I meant. You actually need to do it this way.’’ At that point, changes are not<br />

only time-consuming <strong>and</strong> painful, but the designer is left in the awkward position<br />

of whether to make the corrections pro bono or charge the client an additional<br />

fee. This mode of edits continually coming in with no foreseeable end is<br />

referred to as scope creep.<br />

Because of documentation time, site requirements might increase the cost of the<br />

site. However, while initially taking more time <strong>and</strong> money, requirements can<br />

save considerable expense when the designer has everything planned prior to<br />

development.<br />

Take, for example, a 20-field form. Without requirements, the form might start<br />

out at 20 fields. The client, though, after seeing the first draft, says, ‘‘Oh, I forgot<br />

a few items we need to add.’’ They probably do not know that this involves<br />

making changes to not only the form, but also to the database <strong>and</strong> additional<br />

server-side scripted pages that complete the functionality. And that is just the<br />

first draft. The client might then run the form by a peer or boss who will have

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!