Impacts | Free Templates, Checklists, Forms for Microsoft Office

Entries Tagged as 'Impacts'

Concept of Operations Template

October 25th, 2009 · Comments Off · Business, Software Development

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.

[Read more →]

Tags:Assumptions·Business and Economy·Concept of Operations·Constraints·Deployment·Functional Requirement·Impacts·Issues·Justification·Language·Modes·Non-Functional Requirements·Objectives·Operations·Policies·Priorities·Programming·Requirement·Requirements Traceability·Risks·scope·Stakeholders·United States·Use Case·User classes·Users classes

Software Requirements Specification (SRS) Template

July 8th, 2009 · Comments Off · F R E E

This SRS template pack includes a 29-page Software Requirements Specification template, Use Case, Requirements Traceability Matrix and Data Dictionary templates in Microsoft Word.

[Read more →]

Tags:Accuracy·Audit Trail·Availability·Capacity Limits·Communications Hardware·Communications Interfaces·Communications Requirements·Communications Software·Data Dictionary·Data Framework·Data Inputs·Data Outputs·Data Requirements·Data Retention·Data Structures and Relationships·Database·Design Constraints·Functional Requirements·Hardware Characteristics·Hardware Design Constraints·Hardware Functionality·Hardware Interfaces·Hardware Requirements·Hardware Standards·Impacts·Improvements and Impacts·Improvements to Existing Capabilities·Input Requirements·Inter-functional Data Definitions·Interface Requirements·Margins and Contingency·Memory Constraints·Non-Functional Requirements·Operating System·Operational Constraints·Operational Impacts·Operational Requirements·Performance·Portability·Recoverability·Reliability·Requirements templates·Requirements Traceability·Security Requirements·Software Characteristics·Software Functionality·Software Interfaces·Software Packages·Software Requirements·Specification·SRS·System Requirements·Timing·Tolerance·Usability Requirements·Use Case·User Characteristics·User Impacts·User Interface Constraints·User Interfaces·User Requirements

Statement of Work

July 7th, 2009 · Comments Off · Software Development

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.

[Read more →]

Tags:Community Outcomes·Continuous Monitoring·Cost Estimates·Costs·Current Setup·Impact & Outcomes·Impacts·Investment·Investment Support·Organizational Outcomes·Outcomes·Participant Outcomes·Performance Measures·Project Budget·Resource Identification·Resource Loading Chart·Resource Requirements·SOW·Statement of Work·Strategic Alignment

Interface Control Document

July 6th, 2009 · Comments Off · Software Development

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.

[Read more →]

Tags:Checklists·Community Outcomes·Continuous Monitoring·Cost Estimates·Forms·ICD·IEEE·Impact & Outcomes·Impacts·interface·Interface Control Document·Organizational Outcomes·Participant Outcomes·Project Budget·Resource Identification·Resource Loading Chart·Resource Requirements·SDLC·Spreadsheets