|
Contact us at
info@mooreseminars.com if you have suggestions for a template to add
to this list or you would like us to find you a template.
Third-party links are provided as a convenience to
visitors and the inclusion of a link does not imply approval or
endorsement of the linked site. If you decide to leave this site and
access any third-party web site, you do so at your own risk.
The
Requirements Process Chart (
Adobe PDF File) The
Requirements Management Process is a structured approach to the capture,
organization and management of Business Requirements.
Requirements
Templates
This document is a generic Requirements Analysis
Scope Template for use in the analysis phase of a project. It
provides guidance and template material which is intended to assist
the relevant management or Analyst, whether client or supplier, in
producing an Analysis Phase Scope Statement document.
This document is a generic User Requirement document
for use in a project. It provides guidance and template material
which is intended to assist the relevant management or technical
staff, whether client or supplier, in producing a project specific
Requirement document.
-
The IEEE
Guide to Software Specification
- (
Adobe PDF File) The content and qualities of a good Software Requirement
Specification (SRS) are described and several sample SRS outlines
are presented. This recommended practice is aimed at specifying
requirements of software to be developed but can also be applied to
assist in the selection of in-house and commercial
software products.
Requirements
Tools
This site provides access to various software tools
developed by the NASA Software Assurance Technology Center (SATC).
After going through a short registration process, you will have the
ability to download all tools available on the site. Information
collected during the registration process is used for statistical
analysis only by SATC staff and will not be shared with other
parties. A valid email account is required for registration;
However, once the registration process is completed, you will not be
contacted via email unless you opt-in to receive product news and
update information from the SATC.
ARM: Automated Requirements Measurement Tool (2.1) ARM is an
early life cycle tool for assessing requirements that are specified
in natural language.
RUT: Requirements Use case Tool (0.1) RUT provides assistance to
managers, customers, and developers in assessing the quality of use
cases and serves as a database repository for requirements developed
as use cases.
Testing Templates
This Test Plan Template is meant to be a guideline,
not an absolute dictation of form. You should add or modify sections
as appropriate for your project.
This Test Plan Template is meant to be a guideline,
not an absolute dictation of form. You should add or modify sections
as appropriate for your project.
The Installation Test Case Template can be used to
create, execute and gather metrics for Installation Test Cases. The
template is broken into two sections Installation and Build
Verification Test Cases. The Template is meant to be a guideline.
You should add or modify sections as appropriate for your project.
The Integration Test Case Template can be used to
create, execute and gather metrics for Integration Test Cases. The
template is broken into three sections Component, Failover and
Functional Test Cases. The Template is meant to be a guideline. You
should add or modify sections as appropriate for your project.
The System Test Case Template can be used to create,
execute and gather metrics for System Test Cases. The template is
broken into five sections Concurrency, Business Scenario, Security,
User Interface and Performance Test Cases. The Template is meant to
be a guideline. You should add or modify sections as appropriate for
your project.
The Test Progress Report Template can be used to
report Plan -vs- Actual Progress of Test Case Creation, Test Case
Execution and Defects Found during Testing.
Test Management & Defect Tracking
Tools
Test Case Manager (TCM) is a tool designed for
software test engineers to organize test cases for storage and
execution logging. Test cases are written up in a standard format
and saved into the system. Test cases can be organized by level
(Smoke, Critical Path, Acceptance Criteria, Suggested), by area (GUI
breakdown, installation, data, etc.), by status (pass, fail,
untested, etc.), or other breakdown criteria. Once test cases are
built, testers use TCM to track and report success or failure of
test cases. TCM provides an unlimited number of central, multi-user
databases, each of which will support an entire test team. TCM is
intended for use by small to midsize software development companies
or organizations. TCM was designed to be easy to learn and use. Most
features are implemented as intuitive wizards for users to step
through.
Buggit manages bugs and features throughout the
software development process. Testers, developers, and managers can
all benefit greatly by using Buggit. It enables them to enter and
edit bugs/issues, perform quick lookups of existing issues, print
from a wide variety of powerful reports and graphs (see screen shots
at PBSys webpage - www.pb-sys.com), administer new bug project
databases, and much more. Buggit provides an unlimited number of
central, multi-user databases, each of which will support multiple
concurrent users in the development team.
Checklists
Heuristic evaluation (Nielsen and Molich, 1990;
Nielsen 1994) is a usability engineering method for finding the
usability problems in a user interface design so that they can be
attended to as part of an iterative design process. This checklist
is for evaluators to examine the system interface and judge its
compliance with recognized usability principles (the "heuristics").
Other Templates
-
Taxonomy-Based Risk Identification -
This
report describes a method for facilitating the systematic and
repeatable identification of risks associated with the development
of a software dependent project. This report focuses on risk
identification and is based on the simple premise that without
effective and repeatable risk identification methods, truly
effective risk management is impossible.
-
Project Change Request Form -
Used by any
stakeholder to request a change in the project. When it applies to
scope, budget, schedule, or quality, a formal Change Control Process
is invoked.
-
Communications Plan -
Details who requires
what information, when, in what format, how it will be delivered,
and by whom.
-
Meeting Minutes - A convenient format for
recording minutes from Project team and other meetings.
-
Monthly Status Report
- Used to report project status. Provides a consistent format,
including an Executive Summary section, for enhanced communication
with upper management.
-
Simple Scope Statement Lite - A simpler
Scope document for Tier 1 ("Small") projects. Describes all of the
work – and only the work – required to complete the project.
-
Use Case Template - Used to document
functional requirements of the project that can be expressed as Use
Cases.
-
Lessons Learned
- Record commentary
regarding Lessons Learned throughout the project in this form.
More Free Project Management
Templates -
A full suite of Project Management templates that you can download and
use, right out of the box.
|
Microsoft Excel ".xls" File) 
WinZip
".zip" File)