Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
it's simple format for SRS document
Typology: Lab Reports
Uploaded on 09/27/2020
1 document
1 / 33
This page cannot be seen from the preview
Don't miss anything!
[[Document Configuration Identifier]] [[Date]]
Team Name: Team Member 1: Team Member 2: Team Member 3: Team Member 4: Team Member 5:
[[Document Configuration Identifier]] [[Date]]
ii
[[Document Configuration Identifier]] [[Date]] RECORD OF CHANGES *A - ADDED M - MODIFIED D – DELETED VERSION NUMBER DATE NUMBER OF FIGURE, TABLE OR PARAGRAPH A M D* TITLE OR BRIEF DESCRIPTION CHANGE REQUEST NUMBER iv
[[Date]]
Section Page PROJECT MANAGEMENT PLAN............................................................................................................I FOR THE.....................................................................................................................................................I [[PROJECT NAME]]...................................................................................................................................I [[DOCUMENT CONFIGURATION IDENTIFIER]]..................................................................................I
[[Document Configuration Identifier]] [[Date]] SECTION 1. OVERVIEW
IEEE Std 1058-1998 Guidance The IEEE Std 1058-1998 provides no specific guidance on Project Summary (Subclause1.1). This section may be tailored as needed to provide additional subsections in which a project may be more fully described. For example, 1.1 Project Summary, 1.1.1 System Overview, 1.1.2 Purpose, Scope, and Objectives, etc. 1.1.1 Purpose, Scope, and Objectives IEEE Std 1058-1998 Guidance (Subclause 1.1.1) Purpose, scope, and objectives This subclause shall define the purpose, scope, and objectives of the project. This shall include a brief statement of the business or system needs to be satisfied by the project, with a concise summary of the project objectives, the products to be delivered to satisfy those objectives, and the methods by which satisfaction will be determined. The project statement of purpose shall describe the relationship of this project to other projects, and, as appropriate, how this project will be integrated with other projects or ongoing work processes. 1.1.2 Assumptions and Constraints IEEE Std 1058-1998 Guidance (Subclause 1.1.2) Assumptions and constraints This subclause shall describe the assumptions on which the project is based and imposed constraints on project factors such as the schedule, budget, resources, components to be reused, acquirer components to be incorporated, technology to be employed, and product interfaces to other products. 1.1.3 Project Deliverables IEEE Std 1058-1998 Guidance (Subclause 1.1.3) Project deliverables This subclause shall list the work products that will be delivered to the acquirer, the delivery dates, delivery locations, and quantities required to satisfy the terms of the project agreement. In addition, this subclause shall specify the delivery media and any special instructions for packaging and handling. The list of project deliverables may be incorporated into the document directly or by reference to an external document such as a Contract Data Requirements List (CDRL) or a Product Parts List (PPL). 1.1.4 Master Schedule and Budget Summary IEEE Std 1058-1998 Guidance (Subclause 1.1.4) Schedule and budget summary
[[Document Configuration Identifier]] [[Date]] This subclause shall provide a summary of the schedule and budget for the project. The level of detail should be restricted to an itemization of the major work activities and supporting processes as, for example, those depicted by the top level of the work breakdown structure.
IEEE Std 1058-1998 Guidance (Subclause 1.2) Evolution of the Plan This subclause shall specify the plans for producing both scheduled and unscheduled updates to this planning document. Methods of disseminating the updates shall be specified. This subclause shall also specify the mechanisms used to place the initial version under configuration management and to control subsequent changes to the planning document.
General Guidance This section has been added to the template to help provide the reader of the final planning document an understanding of the structure and content of the document without having to reference the IEEE Std 1058-1998. This plan is organized as follows: a. Section 1, Project Overview. This section provides an overview of the scope and objectives of the project, the project’s assumptions and constraints, reference to the project deliverables, schedule and budget, and a description of the evolution of the plan. b. Section 2, References. This section provides a list of all documents, policies, templates, processes, and other sources of information referenced in the plan. c. Section 3, Definitions. This section contains the abbreviations and acronyms required to properly understand this planning document. d. Section 4, Project Organization. This section identifies interfaces to organizational entities external to the project, the project’s internal organizational structure, and defines roles and responsibilities for the project. e. Section 5, Management Process. This section describes the planning, measurement, tracking, reporting, risk control mechanisms needed to provide management control over the technical processes and product quality, and appropriate project initiation and closeout procedures. f. Section 6, Technical Process. This section describes the technical solution in terms of a process model and implementation methods, tools, and techniques to be used to develop the various work products, plans for establishing and maintaining the project infrastructure, and the product acceptance. g. Section 7, Supporting Processes. This section describes processes that are employed to facilitate and control the technical processes and the state of the product. These include, but are not limited to, configuration management, verification and validation, documentation, quality assurance, reviews and audits, problem resolution, and contractor management, and methods to ensure continuous process improvement. h. Section 8, Additional Plans. This section addresses the logistic support strategy to be applied to increase the system’s operational effectiveness.
[[Document Configuration Identifier]] [[Date]] SECTION 2. REFERENCES IEEE Std 1058-1998 Guidance (Clause 2) References This clause shall provide a complete list of all documents and other sources of information referenced in the document. Each document should be identified by title, report number, date, author, path/name for electronic access, and publishing organization. Other sources of information, such as electronic files, shall be identified using unique identifiers such as date and version number. Any deviations from referenced standards or policies shall be identified and justifications shall be provided.
The standards and documents listed below are referenced in this document:
[[Document Configuration Identifier]] [[Date]] SECTION 3. DEFINITIONS IEEE Std 1058-1998 Guidance (Clause 3) Definitions This clause shall define, or provide references to, documents containing the definition of all terms and acronyms required to properly understand this planning document.
[[Document Configuration Identifier]] [[Date]] SECTION 5. MANAGEMENT PROCESS
IEEE Std 1058-1998 Guidance (Subclause 5.1) Project start-up plan This subclause shall specify the estimation plan, staffing plan, resource acquisition plan, and training plan. Depending on the size and scope of the project, these plans may be incorporated directly or by reference to other plans. . 5.1.1 Estimation IEEE Std 1058-1998 Guidance (Subclause 5.1.1) Estimation plan This subclause shall specify the cost and schedule for conducting the project as well as methods, tools, and techniques used to estimate project cost, schedule, resource requirements, and associated confidence levels. In addition, the basis of estimation shall be specified to include techniques such as analogy, rule of thumb, or local history and the sources of data. This subclause shall also specify the methods, tools, and techniques that will be used to periodically re-estimate the cost, schedule, and resources needed to complete the project. Re-estimation may be done on a monthly basis and/or periodically as necessary. 5.1.2 Staffing IEEE Std 1058-1998 Guidance (Subclause 5.1.2) Staffing plan This subclause shall specify the number of staff required by skill level, the project phases in which the numbers of personnel and types of skills are needed, the source of personnel and the duration of need. Resource Gantt charts, resource histograms, spreadsheets, and tables may be used to depict the staffing plan by skill level, by project phase, and by aggregations of skill levels and project phases. 5.1.3 Resource Acquisition IEEE Std 1058-1998 Guidance (Subclause 5.1.3) Resource acquisition plan This subclause shall specify the plan for acquiring the resources in addition to personnel needed to successfully complete the project. The resource acquisition plan should include a description of the resource acquisition process, including assignment of responsibility for all aspects of resource acquisition. The plan should include, but not be limited to, acquisition plans for equipment, computer hardware and software, training, service contracts, transportation, facilities, and administrative and janitorial services. The plan should specify the points in the project schedule when the various acquisition activities will be required. Constraints on acquiring the necessary resources shall be specified.
[[Document Configuration Identifier]] [[Date]] 5.1.4 Staff Training IEEE Std 1058-1998 Guidance (Subclause 5.1.4) Project staff training plan This subclause shall specify the training needed to ensure that necessary skill levels in sufficient numbers are available to successfully conduct the project. The training schedule shall include the types of training to be provided, numbers of personnel to be trained, entry and exit criteria for training, and the training method (e.g., lectures, consultations, mentoring, or computer-assisted training). The training plan should include training as needed in both technical and managerial skills.
IEEE Std 1058-1998 Guidance (Subclause 5.2) Work plan This clause shall specify the work activities, schedule, resources, and budget details for the project. The following paragraphs provide a working management plan for the acquisition of the [[Project Name]]. 5.2.1 Work Activities IEEE Std 1058-1998 Guidance (Subclause 5.2.1) Work activities This subclause shall specify the various work activities to be performed in the project. A work breakdown structure shall be used to depict the work activities and the relationships among work activities. Work activities should be decomposed to a level that exposes all project risk factors and allows accurate estimate of resource requirements and schedule duration for each work activity. Work packages should be used to specify, for each work activity, factors such as the necessary resources, estimated duration, work products to be produced, acceptance criteria for the work products, and predecessor and successor work activities. The level of decomposition for different work activities in the work breakdown structure may be different depending on factors such as the quality of the requirements, familiarity of the work, and novelty of the technology to be used. 5.2.2 Schedule Allocation IEEE Std 1058-1998 Guidance (Subclause 5.2.2) Schedule allocation This subclause shall provide scheduling relationships among work activities in a manner that depicts the time-sequencing constraints and illustrates opportunities for concurrent work activities. Any constraints on scheduling of particular work activities caused by factors external to the project shall be indicated in the work activity schedule. The schedule should include frequent milestones that can be assessed for achievement using objective indicators to assess the scope and quality of work products completed at those milestones. Techniques for depicting schedule relationships may include milestone charts, activity lists, activity Gantt charts, activity networks, critical path networks, and PERT.
[[Document Configuration Identifier]] [[Date]] 5.3.2 Schedule Control IEEE Std 1058-1998 Guidance (Subclause 5.3.2) Schedule control plan This subclause shall specify the control mechanisms to be used to measure the progress of work completed at the major and minor project milestones, to compare actual progress to planned progress, and to implement corrective action when actual progress does not conform to planned progress. The schedule control plan shall specify the methods and tools that will be used to measure and control schedule progress. Achievement of schedule milestones should be assessed using objective criteria to measure the scope and quality of work products completed at each milestone. The following paragraphs define the management approach for schedule control of the [[Project Name]]. 5.3.2.1 Schedule Tracking. 5.3.2.2 Schedule Performance Reports. 5.3.2.3 Schedule Reviews. 5.3.2.4 Progress Variance Monitoring. 5.3.2.5 Progress Variance Resolution. 5.3.2.6 Follow-Up on Corrective Action. 5.3.3 Budget Control IEEE Std 1058-1998 Guidance (Subclause 5.3.3) Budget control plan This subclause shall specify the control mechanisms to be used to measure the cost of work completed, compare planned cost to budgeted cost, and implement corrective action when actual cost does not conform to budgeted cost. The budget control plan shall specify the intervals at which cost reporting will be done and the methods and tools that will be used to manage the budget. The budget plan should include frequent milestones that can be assessed for achievement using objective indicators to assess the scope and quality of work products completed at those milestones. A mechanism such as earned value tracking should be used to report the budget and schedule plan, schedule progress, and the cost of work completed. The following paragraphs define the management approach for budget control of the The following paragraphs define the management approach for schedule control of the [[Project Name]]. . 5.3.3.1 Cost Management. 5.3.3.2 Methods to Ensure Cost Adherence. 5.3.3.3 Cost Control.
[[Document Configuration Identifier]] [[Date]] 5.3.3.4 Contractor Cost Control. 5.3.3.5 Cost Variance Measurement. 5.3.3.6 Cost Variance Corrective Action. 5.3.4 Quality Control IEEE Std 1058-1998 Guidance (Subclause 5.3.4) Quality control plan This subclause shall specify the mechanisms to be used to measure and control the quality of the work processes and the resulting work products. Quality control mechanisms may include quality assurance of work processes, verification and validation, joint reviews, audits, and process assessment. 5.3.5 Project Reporting and Communication IEEE Std 1058-1998 Guidance (Subclause 5.3.5) Reporting plan This subclause shall specify the reporting mechanisms, report formats, and information flows to be used in communicating the status of requirements, schedule, budget, quality, and other desired or required status metrics within the project and to entities external to the project. The methods, tools, and techniques of communication shall be specified in this subclause. The frequency and detail of communications related to project measurement and control shall be consistent with the project scope, criticality, risk, and visibility. The following paragraphs define the management plan for ensuring the broadest communication of needed information for project coordination. 5.3.5.1 Electronic Media. 5.3.5.2 Meetings. 5.3.5.3 Information Repository. 5.3.5.4 Reviews. 5.3.5.5 Status Reporting. 5.3.6 Metrics Collection IEEE Std 1058-1998 Guidance (Subclause 5.3.6) Metrics collection plan This subclause shall specify the methods, tools, and techniques to be used in collecting and retaining project metrics. The metrics collection plan shall specify the metrics to be collected, the frequency of collection, and the methods to be used in validating, analyzing, and reporting the metrics.
[[Document Configuration Identifier]] [[Date]] SECTION 6. TECHNICAL PROCESS
IEEE Std 1058-1998 Guidance (Subclause 6.1) Process model This subclause shall define the relationships among major project work activities and supporting processes by specifying the flow of information and work products among activities and functions, the timing of work products to be generated, reviews to be conducted, major milestones to be achieved, baselines to be established, project deliverables to be completed, and required approvals that span the duration of the project. The process model for the project shall include project initiation and project termination activities. To describe the process model, a combination of graphical and textual notations may be used. Any tailoring of an organization’s standard process model for a project shall be indicated in this subclause.
IEEE Std 1058-1998 Guidance (Subclause 6.2) Methods, tools, and techniques This subclause shall specify the development methodologies, programming languages and other notations, and the tools and techniques to be used to specify, design, build, test, integrate, document, deliver, modify and maintain the project deliverable and non-deliverable work products. In addition, the technical standards, policies, and procedures governing development and/or modification of the work products shall be specified.
IEEE Std 1058-1998 Guidance (Subclause 6.3) Infrastructure plan This subclause shall specify the plan for establishing and maintaining the development environment (hardware, operating system, network, and software), and the policies, procedures, standards, and facilities required to conduct the project. These resources may include workstations, local area networks, tools for analysis, design, implementation, testing, and project management, desks, office space, and provisions for physical security, administrative personnel, and janitorial services.
IEEE Std 1058-1998 Guidance (Subclause 6.4) Product acceptance plan This subclause shall specify the plan for acquirer acceptance of the deliverable work products generated by the project. Objective criteria for determining acceptability of the deliverable work products shall be specified in this plan and a formal agreement of the acceptance criteria shall be signed by representatives of the development organization and the acquiring organization. Any technical
[[Document Configuration Identifier]] [[Date]] processes, methods, or tools required for product acceptance shall be specified in the product acceptance plan. Methods such as testing, demonstration, analysis, and inspection should be specified in this plan.
