Documente Academic
Documente Profesional
Documente Cultură
Problem Definition /
Concept Exploration
Requirement Analysis
Specification
Design
Prototyping
Implementation &
Unit Testing
Brainstorming :
In general, coming up with a goal statement is fairly
straightforward. The challenge is to keep the statement concise &
realistic. The site can’t be everything to everyone; you must have a
specific audience & set of tasks in mind. To more fully explore site
goals & features, team members often need a brainstorming session.
The purpose of a brainstorming session is simply to bring out as many
possible ideas about the site as possible. Focus the group by talking
about site issues they should all agree on. Attempt to find common
design philosophy by having people discuss what they don’t want to
see in the site.
Audience
Throughout site development & particularly when goals are being
discussed, you should consider the site’s audience. What a
brainstorming user wants & what an end user wants don’t always
match. We need to make sure that site’s goals are in line with its
users’ needs. To do this we need to actually describe the audience &
their reason for visiting the site.
Instead, think about what kind of people your end users are.
Consider asking some basic questions about the site’s users, such as :
• Where are they located ?
• How old are they ?
• What is their gender?
• What language do they speak?
• How technically & Web proficient are they?
• Are the users disabled (sight, movement, & so on) in any
manner?
• What kind of connection would they have to the Internet?
• What kind of computer would they use?
• What kind of browser would they probably use?
For most sites, there are many types users, each with different
characteristics & goals.
Server Logs
If the site has been running for some time, you have a gold mine of
information about your audience – your Web site access logs. Far too
often designers don’t really look at logs for anything other than basic
trends, such as number of page views. However, from looking at log
files you should be able o determine useful information, such as the
type of browsers commonly accessing the site, the general pattern of
when & how visitors use the site such as entry & exit points.
Site Requirements
Based on the goals of the site & what the audience is like, the site’s
requirements should begin to present themselves. These requirements
should be roughly broken up along visual, technical, content, &
delivery requirements.
To determine requirements you might ask questions such as the
following :
The first three steps of the typical Web project process may be
repeated numerous times until a site plan or specification is finally
agreed upon.
The Site Plan
Once a goal, audience, & site requirements have been discussed &
documented, a formal site plan should be drawn up.
The site plan should contain the following :
Design Phase
Wireframes
Visual design of the site should proceed top -down. On should
design the home page first, followed by subsection pages, & finally
content pages & subtask pages.First , consider creating page
mockups on paper in ablock form commonly called a wireframe.
Wireframes enable designers to focus on the types of objects in
the page & their organization without worrying too much about
precise placement & detail of the layout itself. The wireframe
approach also helps the designer make templates for pages, which
makes it easier to implement the pages later on. Make sure to
create your wireframe within the constraints of a Web browser
window. The browsers border can be a significant factor. Once the
home page wireframe has been built, flesh out the other types of
pages in the site in a similar fashion. Once a complete scenario has
been detailed in this abstract sense, make sure that the path
through the wireframe is logical.
Screen & Paper Comps
Testing
Testing is key to a positive user expirience with your site. Don't force
your users to test your site after its release.
Functionality Testing
Most sites contain at least basic functions such as navigation. make
sure to check every link in a site & rectify any broken links. Broken
links should be considered catastrophic functional errors. Make sure to
test all interactive elements such as forms or shopping carts. Use both
realistic test situations as well as extreme cases. Try to break your
form by providing obviously bad data. Remember users won't think as
you do, so prepare for the unexpected.
Content Proofing
The content details of a site are very important. Make sure content is
all in place & that grammar & word usage is consistent & correct.
Check details such as product names, copyright dates, & trademarks.
Always remember to check the spelling. Clients and users often will
regard an entire site as being poor just on the basis of one small typo;
the importance of this cannot be stressed enough. the best way to
perform this test is to print each page & literally read every single line
for accuracy.
Delivery Testing
Check to make sure the site is delivered adequately. Try browsing the
site under real user conditions. To simulate site traffic, consider using
testing software to create virtual users clicking on the site. This will
simulate how the site will react under real conditions. Make sure that
you test the site on the actual production server to be used or a
system equivalent to it. Be careful not to underestimate delivery issues
such as hosting.