<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "http://docs.oasis-open.org/dita/v1.1/CD01/dtd/topic.dtd">
<?xml-stylesheet type="text/css" href="http://tc.eserver.org/css/dita-view.css"?>

<topic id="tc34277">
<title>Introduction to Requirements: The Critical Details That Make or Break a Project</title>
<shortdesc>Every project has requirements. It doesn&apos;t matter if it&apos;s building hardware solutions, developing software solutions, installing networks, protecting data, or training users. For the project to be a success, knowing what the requirements are is an absolute must.&#xD;&#xD;Requirements exist for virtually any components of a project or task. For example, a project may require specific methods, expertise levels of personnel, or the format of deliverables. This whitepaper will discuss the various kinds of information technology requirements, their importance, the different requirement types, the concept of requirements engineering, and the process for gathering requirements.</shortdesc>
<body>
<p>Every project has requirements. It doesn&apos;t matter if it&apos;s building hardware solutions, developing software solutions, installing networks, protecting data, or training users. For the project to be a success, knowing what the requirements are is an absolute must.&#xD;&#xD;Requirements exist for virtually any components of a project or task. For example, a project may require specific methods, expertise levels of personnel, or the format of deliverables. This whitepaper will discuss the various kinds of information technology requirements, their importance, the different requirement types, the concept of requirements engineering, and the process for gathering requirements.</p>
<ul>
<li>Access restricted (by the publisher) to members/subscribers/customers only.</li>
<li><a href="http://tc.eserver.org/dir/Articles/Project-Management/Business-Communication/Specifications">All works in 'Articles &gt; Project-Management &gt; Business-Communication &gt; Specifications'</a></li>
<li><a href="http://tc.eserver.org/dir/Articles">All works in 'Articles'</a>, <a href="http://tc.eserver.org/dir/Project-Management">'Project Management'</a>, <a href="http://tc.eserver.org/dir/Business-Communication">'Business Communication'</a>, <a href="http://tc.eserver.org/dir/Specifications">'Specifications'</a></li>
</ul>
</body>
<related-links format="html" scope="local">
 <link type="reference" href="http://tc.eserver.org/dir/Articles/Project-Management/Business-Communication/Specifications" role="parent" scope="local"><linktext>All works in 'Articles &gt; Project-Management &gt; Business-Communication &gt; Specifications'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Articles" role="parent" scope="local"><linktext>All works in 'Articles'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Project-Management" role="parent" scope="local"><linktext>All works in 'Project Management'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Business-Communication" role="parent" scope="local"><linktext>All works in 'Business Communication'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/dir/Specifications" role="parent" scope="local"><linktext>All works in 'Specifications'</linktext></link>
 <link type="reference" href="http://tc.eserver.org/publisher/Global_Knowledge" role="parent" scope="local"><linktext>All 5 works published by Global Knowledge</linktext></link>
</related-links>
</topic>