<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Free Templates, Checklists, Forms for Microsoft Office &#187; Impacts</title>
	<atom:link href="http://www.mysoftwaretemplates.com/tag/impacts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysoftwaretemplates.com</link>
	<description>Word, Excel and Visio templates for Office, Business, Sales &#38; Software Development</description>
	<lastBuildDate>Tue, 25 Oct 2011 18:44:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Concept of Operations Template</title>
		<link>http://www.mysoftwaretemplates.com/business-templates/concept-of-operations-template/740/</link>
		<comments>http://www.mysoftwaretemplates.com/business-templates/concept-of-operations-template/740/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 02:42:30 +0000</pubDate>
		<dc:creator>ivanwalsh</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Assumptions]]></category>
		<category><![CDATA[Business and Economy]]></category>
		<category><![CDATA[Concept of Operations]]></category>
		<category><![CDATA[Constraints]]></category>
		<category><![CDATA[Deployment]]></category>
		<category><![CDATA[Functional Requirement]]></category>
		<category><![CDATA[Impacts]]></category>
		<category><![CDATA[Issues]]></category>
		<category><![CDATA[Justification]]></category>
		<category><![CDATA[Language]]></category>
		<category><![CDATA[Modes]]></category>
		<category><![CDATA[Non-Functional Requirements]]></category>
		<category><![CDATA[Objectives]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[Policies]]></category>
		<category><![CDATA[Priorities]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Requirement]]></category>
		<category><![CDATA[Requirements Traceability]]></category>
		<category><![CDATA[Risks]]></category>
		<category><![CDATA[scope]]></category>
		<category><![CDATA[Stakeholders]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[Use Case]]></category>
		<category><![CDATA[User classes]]></category>
		<category><![CDATA[Users classes]]></category>

		<guid isPermaLink="false">http://www.mysoftwaretemplates.com/?p=740</guid>
		<description><![CDATA[The Concept of Operations document (CONOPs) describes the purpose of a proposed system, the environment in which it will be operated, how it will be used, roles and responsibilities of users, resources required for its implementation, and other information project stakeholders will need to fund the proposed system. Use this template to: Assist stakeholders in [...]]]></description>
		<wfw:commentRss>http://www.mysoftwaretemplates.com/business-templates/concept-of-operations-template/740/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software Requirements Specification (SRS) Template</title>
		<link>http://www.mysoftwaretemplates.com/free/software-requirements-specification-srs-template/368/</link>
		<comments>http://www.mysoftwaretemplates.com/free/software-requirements-specification-srs-template/368/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 03:30:11 +0000</pubDate>
		<dc:creator>ivanwalsh</dc:creator>
				<category><![CDATA[F R E E]]></category>
		<category><![CDATA[Accuracy]]></category>
		<category><![CDATA[Audit Trail]]></category>
		<category><![CDATA[Availability]]></category>
		<category><![CDATA[Capacity Limits]]></category>
		<category><![CDATA[Communications Hardware]]></category>
		<category><![CDATA[Communications Interfaces]]></category>
		<category><![CDATA[Communications Requirements]]></category>
		<category><![CDATA[Communications Software]]></category>
		<category><![CDATA[Data Dictionary]]></category>
		<category><![CDATA[Data Framework]]></category>
		<category><![CDATA[Data Inputs]]></category>
		<category><![CDATA[Data Outputs]]></category>
		<category><![CDATA[Data Requirements]]></category>
		<category><![CDATA[Data Retention]]></category>
		<category><![CDATA[Data Structures and Relationships]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Design Constraints]]></category>
		<category><![CDATA[Functional Requirements]]></category>
		<category><![CDATA[Hardware Characteristics]]></category>
		<category><![CDATA[Hardware Design Constraints]]></category>
		<category><![CDATA[Hardware Functionality]]></category>
		<category><![CDATA[Hardware Interfaces]]></category>
		<category><![CDATA[Hardware Requirements]]></category>
		<category><![CDATA[Hardware Standards]]></category>
		<category><![CDATA[Impacts]]></category>
		<category><![CDATA[Improvements and Impacts]]></category>
		<category><![CDATA[Improvements to Existing Capabilities]]></category>
		<category><![CDATA[Input Requirements]]></category>
		<category><![CDATA[Inter-functional Data Definitions]]></category>
		<category><![CDATA[Interface Requirements]]></category>
		<category><![CDATA[Margins and Contingency]]></category>
		<category><![CDATA[Memory Constraints]]></category>
		<category><![CDATA[Non-Functional Requirements]]></category>
		<category><![CDATA[Operating System]]></category>
		<category><![CDATA[Operational Constraints]]></category>
		<category><![CDATA[Operational Impacts]]></category>
		<category><![CDATA[Operational Requirements]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Portability]]></category>
		<category><![CDATA[Recoverability]]></category>
		<category><![CDATA[Reliability]]></category>
		<category><![CDATA[Requirements templates]]></category>
		<category><![CDATA[Requirements Traceability]]></category>
		<category><![CDATA[Security Requirements]]></category>
		<category><![CDATA[Software Characteristics]]></category>
		<category><![CDATA[Software Functionality]]></category>
		<category><![CDATA[Software Interfaces]]></category>
		<category><![CDATA[Software Packages]]></category>
		<category><![CDATA[Software Requirements]]></category>
		<category><![CDATA[Specification]]></category>
		<category><![CDATA[SRS]]></category>
		<category><![CDATA[System Requirements]]></category>
		<category><![CDATA[Timing]]></category>
		<category><![CDATA[Tolerance]]></category>
		<category><![CDATA[Usability Requirements]]></category>
		<category><![CDATA[Use Case]]></category>
		<category><![CDATA[User Characteristics]]></category>
		<category><![CDATA[User Impacts]]></category>
		<category><![CDATA[User Interface Constraints]]></category>
		<category><![CDATA[User Interfaces]]></category>
		<category><![CDATA[User Requirements]]></category>

		<guid isPermaLink="false">http://www.mysoftwaretemplates.com/?p=368</guid>
		<description><![CDATA[This SRS template pack includes a 29-page Software Requirements Specification  template, Use Case, Requirements Traceability Matrix and Data Dictionary templates in Microsoft Word.]]></description>
		<wfw:commentRss>http://www.mysoftwaretemplates.com/free/software-requirements-specification-srs-template/368/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Statement of Work</title>
		<link>http://www.mysoftwaretemplates.com/software-development-ms-word-templates/statement-of-work/340/</link>
		<comments>http://www.mysoftwaretemplates.com/software-development-ms-word-templates/statement-of-work/340/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 04:09:56 +0000</pubDate>
		<dc:creator>ivanwalsh</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Community Outcomes]]></category>
		<category><![CDATA[Continuous Monitoring]]></category>
		<category><![CDATA[Cost Estimates]]></category>
		<category><![CDATA[Costs]]></category>
		<category><![CDATA[Current Setup]]></category>
		<category><![CDATA[Impact & Outcomes]]></category>
		<category><![CDATA[Impacts]]></category>
		<category><![CDATA[Investment]]></category>
		<category><![CDATA[Investment Support]]></category>
		<category><![CDATA[Organizational Outcomes]]></category>
		<category><![CDATA[Outcomes]]></category>
		<category><![CDATA[Participant Outcomes]]></category>
		<category><![CDATA[Performance Measures]]></category>
		<category><![CDATA[Project Budget]]></category>
		<category><![CDATA[Resource Identification]]></category>
		<category><![CDATA[Resource Loading Chart]]></category>
		<category><![CDATA[Resource Requirements]]></category>
		<category><![CDATA[SOW]]></category>
		<category><![CDATA[Statement of Work]]></category>
		<category><![CDATA[Strategic Alignment]]></category>

		<guid isPermaLink="false">http://www.mysoftwaretemplates.com/?p=340</guid>
		<description><![CDATA[A Statement of Work (SOW) is a narrative description of the deliverables or services required to fulfill a contract. The Statement of Work specifies requirements at high-level. When an organization wishes to have work done, it produces a SOW, possibly as part of a Request for Proposal. Vendors (i.e. prospective contractors) respond to this with Proposals. ]]></description>
		<wfw:commentRss>http://www.mysoftwaretemplates.com/software-development-ms-word-templates/statement-of-work/340/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interface Control Document</title>
		<link>http://www.mysoftwaretemplates.com/software-development-ms-word-templates/interface-control-document-2/299/</link>
		<comments>http://www.mysoftwaretemplates.com/software-development-ms-word-templates/interface-control-document-2/299/#comments</comments>
		<pubDate>Mon, 06 Jul 2009 07:35:57 +0000</pubDate>
		<dc:creator>ivanwalsh</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Checklists]]></category>
		<category><![CDATA[Community Outcomes]]></category>
		<category><![CDATA[Continuous Monitoring]]></category>
		<category><![CDATA[Cost Estimates]]></category>
		<category><![CDATA[Forms]]></category>
		<category><![CDATA[ICD]]></category>
		<category><![CDATA[IEEE]]></category>
		<category><![CDATA[Impact & Outcomes]]></category>
		<category><![CDATA[Impacts]]></category>
		<category><![CDATA[interface]]></category>
		<category><![CDATA[Interface Control Document]]></category>
		<category><![CDATA[Organizational Outcomes]]></category>
		<category><![CDATA[Participant Outcomes]]></category>
		<category><![CDATA[Project Budget]]></category>
		<category><![CDATA[Resource Identification]]></category>
		<category><![CDATA[Resource Loading Chart]]></category>
		<category><![CDATA[Resource Requirements]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[Spreadsheets]]></category>

		<guid isPermaLink="false">http://www.mysoftwaretemplates.com/?p=299</guid>
		<description><![CDATA[An Interface Control Document (ICD) describes the relationship between system components in terms of data items and messages passed, protocols observed and timing and sequencing of events. Interface control documents are a key element of systems engineering as they define and control the interface(s) of a system, and thereby bound its requirements.]]></description>
		<wfw:commentRss>http://www.mysoftwaretemplates.com/software-development-ms-word-templates/interface-control-document-2/299/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

