<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to collect web design requirements from customer?</title>
	<atom:link href="http://www.advancewebs.com/website-design/52-how-to-collect-web-design-requirements-from-customer/feed" rel="self" type="application/rss+xml" />
	<link>http://www.advancewebs.com/website-design/52-how-to-collect-web-design-requirements-from-customer</link>
	<description>Website Building And Web Design Tips, Articles &#38; Resources</description>
	<lastBuildDate>Tue, 07 Sep 2010 15:02:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Akira Matsushima</title>
		<link>http://www.advancewebs.com/website-design/52-how-to-collect-web-design-requirements-from-customer/comment-page-1#comment-108</link>
		<dc:creator>Akira Matsushima</dc:creator>
		<pubDate>Sun, 07 Feb 2010 13:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.advancewebs.com/website-design/52-how-to-collect-web-design-requirements-from-customer#comment-108</guid>
		<description>The most effective way to obtain the requirements is through interviews. Make an appointment with you customer and ask them what they want on their website. Prepare the questions well in advance.
Type of questions:

1. Functional Requirements
 - This basically tells you what the website should do and how does it functions.
 - Example: What the website do? What is it for? What function should be there?

2. Non-Functional Requirements
 - This is not about the functionality of the website rather than it relates to how should the website looks and anything that is not in the functional side.
 - This requirements if it is not done the website will still function perfectly as it was intended to.
 - Example: Whats the website layout? Whats the color theme? What is the tolerable amount of time for the website to response to a request.

These are some basic yet the most important requirements you need to know.
You can always search at Yahoo! and Google for a more detailed design/software/ website requirement document sample and template.</description>
		<content:encoded><![CDATA[<p>The most effective way to obtain the requirements is through interviews. Make an appointment with you customer and ask them what they want on their website. Prepare the questions well in advance.<br />
Type of questions:</p>
<p>1. Functional Requirements<br />
 &#8211; This basically tells you what the website should do and how does it functions.<br />
 &#8211; Example: What the website do? What is it for? What function should be there?</p>
<p>2. Non-Functional Requirements<br />
 &#8211; This is not about the functionality of the website rather than it relates to how should the website looks and anything that is not in the functional side.<br />
 &#8211; This requirements if it is not done the website will still function perfectly as it was intended to.<br />
 &#8211; Example: Whats the website layout? Whats the color theme? What is the tolerable amount of time for the website to response to a request.</p>
<p>These are some basic yet the most important requirements you need to know.<br />
You can always search at Yahoo! and Google for a more detailed design/software/ website requirement document sample and template.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
