Hola:

Pragmatic Software tiene una página interesante donde deja descargarse gratis varias plantillas útiles en distintas etapas del ciclo de vida. Esta muy bien si no tienes nada. La reproduzco.

Un saludo,

Ramiro Carballo.

Pragmatic Software Free Templates

Template

Size

Description

All Templates (Zipped)

307 kb

To download all the templates on this page (in zipped format), click here.

Project Management
Guidelines

576 kb

The Project Management Guidelines explain the project management methodologies and detailed deliverables that should accompany each phase of the software development project. The following project life-cycle phases are covered:

• Planning Phase
• Design Phase
• Iterative Code/Test/Release Phase
• Production Phase
• Post-Mortem Phase

Functional
Specification

237 kb

The Functional Specifications describes the items that will be delivered in the software release and how they will be delivered.  It includes:

• Project goals, justification & success criteria
• Product features
• Security requirements
• Data conversion requirements
• Performance requirements
• Installation requirements
• Localization requirements
• Parallel testing requirements
• Cross-system interface requirements
• Data archival, backup & retrieval
• Reporting requirements
• Project flexibility matrix
• Stack ranking of features
• Roles and responsibilities 

Architectural Overview

119 kb

The Architectural Overview describes the architectural roadmap for implementing the software solution and is used as a framework for creating new products.  Topics covered include:

• Hardware design
• Security design
• Software component design

Detailed Design

148 kb

The Detailed Design describes the detailed technical design for the system.  It specifies all known components needed to deliver a complete system.   Topics include:

• Hardware requirements
• Software requirements
• Presentation layer
• Business layer
• Database layer
• Other design considerations
• Detailed design to functional spec cross- reference

Quality Assurance
Strategic Planning 
Document

221 kb

The Strategic Planning Document is a template for creating or enhancing your quality assurance department.  It addresses the following topics:

• Mission Statement
• Core competencies needed by testers and test leads
• Hiring policies and organizational chart
• Standardized test team deliverables to control costs
• Tools used in the testing process and client test lab
• Transition Plan
• Risks

Test Design

396 kb

The Test Design describes the activities that will verify the software product as a high quality product that meets the needs of the business community.  These activities focus upon identifying the following: 

• Items to be tested
• Testing approach
• Roles and Responsibilities
• Release criteria
• Hardware
• Project plan and budget
• Risk and contingencies

Risk Assessment

31 kb

The Risk Assessment document is used to track risks and to assign additional hours to your project plan to mitigate that risk.  This plan should be kept updated throughout your development cycle.

Weekly Status

25 kb

The Weekly Status is used to communicate with management regarding issues that arise during the software development lifecycle.  It covers:

• Urgent issues (Red)
• Items that may be slipping (Yellow)
• Successes (Green)
• Next week priorities
• Metrics

User Acceptance
Test Release Report

153 kb

The User Acceptance Test Release Report is used to briefly explain the test coverage and open issues of the testing effort at the time of the release to User Acceptance testing.  It covers:

• Installation procedures
• Defect entry and resolution
• Responsibilities
• Drop schedule
• Open Severity 1 / 2 defect items
• System test coverage
• Defect analysis
• Test case analysis

Post Mortem

197 kb

The Post Mortem Report describes the specific activities that were most effective and those that need adjustments during the development of the product.  A goal of the document is to inform future project teams of the obstacles encountered during this release. These activities focus upon identifying the following:

• Processes that were most effective
• Processes that had a negative effect
• How to continue doing what was done right
• How to correct what needs improvement