SoftwareProjectManagementPlan.docx

1、SoftwareProjectManagementPlanSoftware-Project-Management-PlanSoftware Project Management PlanFor Revision Change logDateVersionDescriptionAuthor Project Management Plan of some details modified according to the actual operationTable of contents Project Deliverables.4 Data flow diagram.5 Definitions

2、and abbreviations.121 INTRODUCTION This document defines the Software Project Management Plan for the Computer Store Management System(CSMS) product of Team Mission Possible (TMP). This plan is based on IEEE STANDARD , Standard for Software Project Management Plans (ANSI). Project Overview The proje

3、ct is to develop a computer store sales management system. The system is intended to enhance the operational efficiency of the supermarket. Through comprehensive information collection and processing, supporting the decision-making to improve the level of the supermarket. Use of this system, you can

4、 quickly improve the management level of the supermarket, in order to reduce operating costs, improve efficiency, enhance the ability of supermarket expansion, to provide effective technical support。 Project Deliverables Project delivery date is 10 weeks on Thursday, the place of delivery to the ver

5、sion control server . Main deliverables are: CSMS system installation procedure, system source code, user manuals, technical documentation package (including requirements specification, system design specifications, system test specifications, project summary documents, etc.), project progress log p

6、ackage (at least weekly copies).2. PROJECT ORGANIZATION This section provides the process model to be followed, team organization, the roles and responsibilities of each team member. Software Process ModelThe teams process model will have the following integrated software life cycle and DFD.2.1.1 So

7、ftware life cycle1.It uses a waterfall development model2.There are three phases: Requirement, Analysis & Design and Construction3.It uses small TSPi cycles in each phase4.In construction phase, each cycle includes coding, unit test and building . 2.1.2 Data flow diagram DFD is the structure of the

8、basic tools of systems analysis, process modeling is the modeling techniques used in the main. It reflects the input and output data in the system and process Customer orders receipt inventory information product sales formatted inventory dataformatted sales data Daily inventory consumption D Daily

9、product sales management reporting Roles And ResponsibilitiesRolesResponsibilitiesNameProject Managerto develop project plans and lead the developers to be successfulTeam LeaderSpecific guidance on software development and designUsersdirectly or indirectly dealing with the product, is part of the cu

10、stomerCustomersThe companys obligations to achieve its investment objective or to purchase productsDemand Analystsresponsible for the preparation requirements and passed to the development teamDevelopersdesign, implementation and maintenance of productsTesting Personnelto determine whether the produ

11、ct is consistent with the expectedDocumentation Staffresponsible for writing user manuals, training materials and systems to helpLegal Staffdetermine the product complies with relevant laws and regulationsProduction Personneldevelopment of products containing the software; Marketingtechnical support

12、 and other products with clients and staff; Tools And Techniques It is group design organization structure; programming languages C #; using object-oriented analysis and design methods; using UML for system modeling; uniform file naming, code layout, comments and other coding standards; coding staff

13、 code walkthrough and then compile the code; tester unit test under the test documentation; the final realization of software delivery. Development environment for the DirectX SDK October 2006 +. Net + Visual Studio 2005.3 PROJECT MANAGEMENT PLAY Tasks3.1.1 Task 1-SOW Creation Description Create SOW

14、 for the team project Through the users description to collection the information ,the developers understand the development background and the users request, then to submit brochures, by the client for review. Deliverables And Milestones SOW Outline, SOW draft, review SOW, sign SOW, final SOW for t

15、he term Resource Needed Description of the product and customers demand; The developers understand the background of product development Dependence And Constraints Task assignment; Risk Plan, SQAP, Estimation plan, Process Plan are all ready Post the final SOW on team web page, Keep the signed docum

16、ent in the archives Risks And Contingencies The first step in software development, it is easy to have communication barriers between customers and developers. It makes work hard to go on.3.1.2 Task2-Create document Description SPMP for the team project SRS for the team project design documents; Tes

17、t DocumentationLearn CSMS development process and the development of background and raised in the document the functional requirements of the CSMS, running environment, the development of the system, project budget and project time. Deliverables And Milestones SPMP and the SRS and other documents,th

18、e Milestones includes SPMP Outline, SPMP draft, review SPMP, final SPMP for the term and Elicitation of requirements, synergys SRS studied, SRS Outline, SRS draft, review SRS, final SRS for the term . Resource Needed Development of background information, customer demand, the relevant laws, regulati

19、ons and documents and other material specifications. Dependence And Constraints On information obtained from the customers understanding of the use of synergies between the level of team members, task allocation and schedule estimates, risk assessment and software product quality are all closely rel

20、ated. Risks And Contingencies Document preparation is essential to the process of software development as part of pre-prepared document guiding the direction of software development, a good start is half the battle, as long as the written documents, be possible to produce high quality software produ

21、cts, in document the development process, prone to many problems, such as: developers and users can not communicate very well understood, resulting in the misunderstanding of the needs of customers on the products they need not give a clear description, there needs and vulnerability are often risks

22、written document.3.1.3 Task3-coding and testing Description The physical process of software development, software development process is a very important part, need to work between members and the project leader of the right co-ordination arrangements need to be invested in this part of the larger

23、human and material resources. Deliverables And MilestonesInstallation, the system source code, user manual and so on Resource Needed Staff : The software development team members, customers; support software: Microsoft Visual Studio. NET 2005, TortoiseSVN, Office. Office: Institute of laboratories a

24、nd dormitories; computer hardware: servers; laboratory equipment: personal PC, laptop, lab dedicated PC, public server; project resources to maintain the number and types of demand: 4 personal computer (Pentium III 800 above CPU, 256M or more memory); Dependence And Constraints 1) To organize the pr

25、oject team is to complete the prerequisite software, a clear division of responsibility; 2) As a result of public facilities, equipment procurement team completed the basic need; 3) environment was created for coding the test fully prepared; 4) configuration management throughout the software develo

26、pment and testing process; 5) Software Project needs analysis is an important symbol to enter the development stage; 6) The system design is based on the analysis based on demand, but also based on the principles of coding; 7) encoding test is the important process of software development progress ;

27、 Risks nd Contingencies There are many risks of the procedure, such as: 1. Development of technology immaturity, leading to the development progress blocked, code sharing difficult. 2. Demand frequent changes affect the overall software architecture and development progress. These risks are differen

28、t levels of the software quality, is especially needed attention. Assignmentsname workGroup1Document designGroup2design and codingGroup3testGroup4graphical interface design TimetableWeek 1(Completed) Met with client, and determined requirements artifacts. Inspectedrequirements artifacts.Weeks 2,3(Co

29、mpeleted) Produced analysis artifacts, and inspected analysis artifacts. Showedartifacts to client, who approved them. Produced software project management plan, and inspected software projct management plan.Weeks 4,5Product design artifacts, and inspect design artifactsWeeks 610Implementation and i

30、nspection of each class, unit testing and documentation,integration of each class, integration testing, product testing, and documentationinspection4 ADDITIONAl MATERIALS Reference material SPMP standard template; course notes; Definition and Abbreviations CSMSComputer Store Management SystemSPMPSoftware Project Management PlanSOWStatement Of WorkSRSSoftware Requirements SpecifcationSDD Software design documentsSTDSoftware Test Documentation