| Here's the LSE Development Plan template that will be included with
XLSE X1.2 (to be released "n" midnights from now).
NOTE: This template includes several new placeholders that are not part
of the distributed LSE support for SDML.
--------------------
<DOCTYPE>(REPORT)
<COMMENT>
Component Software Product - DEVELOPMENT PLAN
If you have questions or need more information about this document,
please contact: Chris Strutt, ADVISE::STRUTT, DTN: 381-1340.
A DEVELOPMENT PLAN is the description of the development project to
design, build, test and evaluate, and deliver a Component Software
Product. It confirms to the Product Team (refer to Phase Review Policy,
SDP&P: 7A8-2) that all top-level project planning, evaluation, and
management decisions have been made.
It is written in response to the Specification for a Component Software
Product, which defines what is to be built. It also usually
corresponds to a reference from a System Plan.
It is the starting point for detailed planning of each individual team
member's work, and for the definition of specific project procedures
and conventions. It is also used to communicate and to manage
interproject dependencies.
Detailed guidelines for the content of each section are provided in
file DEVPLAN.GDE.
<ENDCOMMENT>
<COMMENT>
Title page
<ENDCOMMENT>
<DEFINE_SYMBOL>(PRODUCT_NAME\{product-name})
<DEFINE_SYMBOL>(VERSION_NUMBER\{version-number})
<FRONT_MATTER>
<TITLE_PAGE>
<TITLE>( Component Software Product
<LINE>DEVELOPMENT PLAN
<LINE>for
<LINE><REFERENCE>(PRODUCT_NAME) <REFERENCE>(VERSION_NUMBER) )
<SUBHEAD1>(Written by:)
<P><LINE>(INDENT){name}, {job-title}
<SUBHEAD1>(Issued by:)
<P><LINE>(INDENT){name}, {job-title}
<SUBHEAD1>(Reviewed by:)
<P><LINE>(INDENT){name}, {job-title}
<P><LINE>(INDENT){name}, {job-title}
<P><LINE>(INDENT){name}, {job-title}
<P><LINE>(INDENT){name}, {job-title}
<CENTER_LINE>(<DATE>\BIGSKIP)
<CENTER_LINE>(Copyright � 1987 by Digital Equipment Corporation\BIGSKIP)
<CENTER_LINE>(For Internal Use Only\SMALLSKIP)
<CENTER_LINE>(<DEC_LOGO>\SMALLSKIP)
<ENDTITLE_PAGE>
<COMMENT>
Table of Contents
<ENDCOMMENT>
<CONTENTS_FILE>
<COMMENT>
Preface
To ensure that any reader understands the purpose of a Development Plan,
the preface should contain the following wording (or something
equivalent).
<ENDCOMMENT>
<PREFACE>
<P> This is a Component Software Product DEVELOPMENT PLAN.
It is the description of the development project to design, build, test,
evaluate, and deliver <REFERENCE>(PRODUCT_NAME) <REFERENCE>(VERSION_NUMBER).
It confirms to the Product Team that all top-level project planning,
evaluation, and management decisions have been made.
<SUBHEAD1>(Associated Documents)
<LIST>(UNNUMBERED)
<LE> The <EMPHASIS>(<REFERENCE>(PRODUCT_NAME) <REFERENCE>(VERSION_NUMBER)
System Plan\ITALIC) that describes the plan to deliver the total System, of
which this Software Product is a Component.
<LE> The <EMPHASIS>(<REFERENCE>(PRODUCT_NAME) <REFERENCE>(VERSION_NUMBER)
Component Software Product Specification\ITALIC),
which describes the goals, capabilities and external characteristics of the
product that will be delivered by this project.
<ENDLIST>
<SUBHEAD1>(Change History)
<LINE>
<TABLE>
<TABLE_ATTRIBUTES>(\MULTIPAGE)
<TABLE_SETUP>(3\10\7)
<TABLE_HEADS>(Date\Issue #\Description/Summary of Changes)
<COMMENT>( Use "<TABLE_ROW>(date\#\description)" for each edition. )
<TABLE_ROW>([issue-date]\1\Initial release of this plan.)
<ENDTABLE>
<ENDPREFACE>
<ENDFRONT_MATTER>
<RUNNING_TITLE>(<REFERENCE>(PRODUCT_NAME) <REFERENCE>(VERSION_NUMBER) ---
Development Plan \ For Digital Internal Use Only)
<HEAD1>(STRATEGY)
<COMMENT>
A brief summary of the strategy for this project, placing particular
emphasis on unusual or problematical areas.
<ENDCOMMENT>
<P> {text}
<HEAD1>(TASKS AND ESTIMATES)
<COMMENT>
- Definition of product DEVELOPMENT and VERIFICATION tasks associated
with each goal, capability and external characteristic of the
Component Software Product stated in the Specification.
- Statement of relationship(s) between tasks and goals.
- Estimate of concentrated manpower for the completion of each task.
- Definition of the content of each base level planned.
<ENDCOMMENT>
<P> {text}
<HEAD1>(RESOURCES)
<COMMENT>
Statement of Resources required to accomplish all the TASKS defined
in Section 2.
<ENDCOMMENT>
<HEAD2>(Staffing)
<P> {text}
<HEAD2>(Training)
<P> {text}
<HEAD2>(Hardware and Software)
<P> {text}
<HEAD2>(Tools)
<P> {text}
<HEAD2>(Travel)
<P> {text}
<HEAD2>(Other)
<P> {text}
<HEAD1>(RESPONSIBILITIES)
<COMMENT>
Statement of the responsibilities of the people involved in this
project, both on the product development team and outside the team.
<ENDCOMMENT>
<P> {text}
<HEAD1>(PROJECT PROCEDURES)
<COMMENT>
Description of project processes and conventions for ensuring
successful delivery of the product.
<ENDCOMMENT>
<HEAD2>(Specifications)
<P> {text}
<HEAD2>(Plans)
<P> {text}
<HEAD2>(Schedules/Progress)
<P> {text}
<HEAD2>(Dependency Management)
<P> {text}
<HEAD2>(Design)
<P> {text}
<HEAD2>(Code)
<P> {text}
<HEAD2>(Publications)
<P> {text}
<HEAD2>(Testing/Test Results)
<P> {text}
<HEAD2>(Base Level Control)
<P> {text}
<HEAD2>(Maintenance)
<P> {text}
<HEAD2>(Project Security)
<P> {text}
<HEAD2>(Post-FRS Project Review)
<P> {text}
<HEAD2>(Document Retention)
<P> {text}
<HEAD1>(PHASES OF PRODUCT TEST AND EVALUATION)
<COMMENT>
Description of the sequence of testing and evaluation activities
planned and the objectives of each phase of activity.
<ENDCOMMENT>
<HEAD2>(Phase 2 (Internal Testing))
<P> {text}
<HEAD2>(Phase 3 (Qualification))
<P> {text}
<HEAD2>(Phase 4B (Postrelease Product Evaluation))
<P> {text}
<HEAD1>(KEY ENTRANCE/EXIT CRITERIA)
<HEAD2>(Field Test Start Criteria)
<P> {text}
<HEAD2>(SDC Submission Criteria)
<P> {text}
<HEAD1>(MILESTONE DEFINITIONS)
<COMMENT>
- State the differences between the milestone definitions given in
SDP&P: 7A8-3, and those for this project, if any.
- Define any other milestones added to the Planner.
<ENDCOMMENT>
<P> {text}
<HEAD1>(DEPENDENCIES, RISKS, AND CONTINGENCIES)
<COMMENT>
For each dependency, state the deliverable, the responsible person,
the associated risk and the contingency plan.
These external dependencies must appear as milestones on the Phase
Review Planner.
<ENDCOMMENT>
<HEAD2>(Dependencies of this Project on other Projects/Events)
<P> {text}
<HEAD2>(Dependencies of other Project/Events on this Project)
<P> {text}
<HEAD2>(Risks)
<P> {text}
<APPENDIX>(PHASE REVIEW PLANNER)
<COMMENT>
- Names of Product Team
- Milestone dates.
<ENDCOMMENT>
<HEAD1>(Development Team)
<LIST>(UNNUMBERED)
{list-element}...
<ENDLIST>
<HEAD1>(Milestone Summary)
<LIST>(NUMBERED)
{list-element}...
<ENDLIST>
<ENDAPPENDIX>
<APPENDIX>(STAFFING)
<COMMENT>
- Names of people external to the Development Team
- Names of people on the Development Team
<ENDCOMMENT>
<HEAD1>(External Individuals)
<LIST>(NUMBERED)
<LE> {text}
[list-element]...
<ENDLIST>
<HEAD1>(Development Team)
<LIST>(NUMBERED)
<LE> {text}
[list-element]...
<ENDLIST>
<ENDAPPENDIX>
<APPENDIX>(FIELD TEST REQUIREMENTS PROFILE)
<COMMENT>
Statement of the type and number of field test sites required in order
to be able to carry out an effective validation of the product in the
expected user environment.
<ENDCOMMENT>
<P> {text}
<ENDAPPENDIX>
<APPENDIX>(OUTSTANDING ISSUES)
<COMMENT>
List of outstanding issues referenced by number, with names of people
responsible and completion dates.
<ENDCOMMENT>
<P> <REFERENCE>(outstanding_issues) lists the outstanding issues related
to this <REFERENCE>(PRODUCT_NAME) <REFERENCE>(VERSION_NUMBER)
development plan.
<TABLE>(Outstanding Issues\outstanding_issues)
<TABLE_SETUP>(4\4\30\15)
<TABLE_HEADS>(No.\Description\Responsible <LINE>Individual\Completion Date)
<TABLE_ROW>(1\{item}\{item}\{item})
<TABLE_ROW>(2\{item}\{item}\{item})
[rows]...
<ENDTABLE>
<ENDAPPENDIX>
|