《软件开发计划(IEEE1058)》由会员分享，可在线阅读，更多相关《软件开发计划(IEEE1058)（21页珍藏版）》请在金锄头文库上搜索。
1、Software development PlanThis document outline is based on the IEEE Standard 1058.1-1987 for Software Project Management Plans.This is the controlling document for managing a software project, and it defines the technical and managerial processes necessary to deliver the project requirements.The par
2、agraphs written in the “Comment” style are for the benefit of the person writing the document and should be removed before the document is finalized.VERSIoN: DRAFT25 APRIL, 2022AUTHORSREVISION CHARTThis chart contains a history of this documents revisions. The entries below are provided sol for purp
3、oses of illustration. Entries should be deleted until the revision they refer to has actually been created.The document itself should be stored in revision control, and a brief description of each version should be entered in the revision control system. That brief description can be repeated in thi
4、s section. Revisions do not need to be described elsewhere in the document except inasmuch as they explain the development plan itself.VersionPrimary Author(s)Description of VersionDate CompletedDraftTBDInitial draft created for distribution and review commentsTBDPreliminaryTBDSecond draft incorpora
5、ting initial review comments, distributed for final reviewTBDFinalTBDFirst complete draft, which is placed under change controlTBDRevision 1TBDRevised draft, revised according to the change control process and maintained under change controlTBDRevision 2TBDRevised draft, revised according to the cha
6、nge control process and maintained under change controlTBDetc.TBDTBDTBDPREFACECONTENTSNew paragraphs formatted as Heading 1, Heading 2, and Heading 3 will be added to the table automatically. To update this table of contents in Microsoft Word, put the cursor anywhere in the table and press F9. If yo
7、u want the table to be easy to maintain, do not change it manually.1. INTRODUCTION 61.1 PROJECT OVERVIEW61.2 PROJECT DELIVERABLES 61.3 EVOLUTION OF THE SOFTWARE PROJECT MANAGEMENT PLAN61.4 REFERENCE MATERIALS61.5 DEFINITIONS AND ACRONYMS 72. PROJECT ORGANIZATION82.1 PROCESS MODEL82.2 ORGANIZATIONAL
8、STRUCTURE 82.3 ORGANIZATIONAL BOUNDARIES AND INTERFACES92.4 PROJECT RESPONSIBILITIES 103. MANAGERIAL PROCESS113.1 MANAGEMENT OBJECTIVES AND PRIORITIES113.2 ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS113.3 RISK MANAGEMENT113.4 MONITORING AND CONTROLLING MECHANISMS 113.5 STAFFING PLAN124. TECHNICAL PRO
9、CESS 134.1 METHODS, TOOLS, AND TECHNIQUES134.2 SOFTWARE DOCUMENTATION 134.3 PROJECT SUPPORT FUNCTIONS145. WORK PACKAGES, SCHEDULE, AND BUDGET155.1 WORK PACKAGES 155.2 DEPENDENCIES155.3 RESOURCE REQUIREMENTS155.4 BUDGET AND RESOURCE ALLOCATION 155.5 SCHEDULE156. ADDITIONAL COMPONENTS167. INDEX 178. A
10、PPENDICES18List of FiguresNew figures that are given captions using the Caption paragraph style will be added to the table automatically. To update this table of contents in Microsoft Word, put the cursor anywhere in the table and press F9. If you want the table to be easy to maintain, do not change
11、 it manually.This section can be deleted if the document contains no figures or if otherwise desired.Error! No table of figures entries found.1. INTRODUCTIONThis section should describe the project and the software product being to be built. No text is necessary between the heading above and the hea
12、ding below unless otherwise desired.1.1 Project OverviewGive a short summary of the project objectives, the software to be delivered, major activities, major deliverables, major milestones, required resources, and top-level schedule and budget. Describe the relationship of this project to other proj
13、ects, if appropriate.1.2 Project DeliverablesList all of the major items to be delivered to the customer (external customer, in-house user, etc.).List the deliverables, delivery dates, delivery locations, delivery method (email, FTP, CD, etc.), and quantities necessary to satisfy the projects requir
14、ements.1.3 Evolution of the Software Project Management PlanDescribe how you expect this document to evolve over time. This section should be very similar to the “Revision Chart” earlier in the document. The revision chart should list what has already been done to this document. This section should
15、list what is expected to be done to this document.This chart contains a plan for the documents revisions. The entries below are provided for purposes of illustration. The progression from “Draft” to “Preliminary” to “Final” and then through a section of “Revisions” is one typical approach.VersionPrimary Author(s)Description of VersionDate ExpectedDraftTBDInitial draft created for distribution and review commentsTBDPreliminaryTBDSecond draft incorporating initial review comments, distributed for final reviewTBDFinalTBDFirst complete draft, which is placed unde
