Details of this Paper

You have been asked to lead a software development team




Question;ScenarioYou have been asked to lead a software development team to build a system fulfilling theStatement of Need specified in project 1. Your team is employed by a small company. Thecustomer wants a project that balances reasonable development cost, timely delivery, softwarequality, and functionality.In this project, you will develop the tool for planning, managing and controlling all yoursoftware development efforts on the B&B project. Note that typically this is the first documentthat you produce not the last as we do in class. But we had to produce the other documents firstto develop an appreciation of what a project plan entails and requires.Completing this project will require that you produce a software project plan (SPP) document forthe system. An SPP must also develop project reporting and team communication mechanisms.SPP TemplatesPlease develop your SPP using the IEEE Standard for Software Project Management Plans,standard 1058-1998, posted in the Reserved Readings section on the Class Menu. Read page 4of the standard to review the outline. Follow the outline in Figure 1 but omit the followingsections from your SPP: 1.1.4 (budget summary), 1.2, 5.1, 5.2.4, 5.3, 5.5, 6.3, 6.4, all of 7, all of8, Annexes.The assignmentComplete the template as best as you can. Pay special attention to the bulletized points below.Make any reasonable assumptions based on your understanding of the problem that allow you toaddress as many sections of the SPP template as possible. (Please read the ?project descriptions?in the project description section of the syllabus for additional context and information on courseprojects).Pay special attention to the following. The bulk of your grade will be decided on how well youaddress these issues.?Project schedule (Timeline): Develop a schedule for the entire project.?Project task set: Perform a work break down scheduleRisk Management: Assess and rank the project and technical risks on the project.Explain the risk mitigation steps for these identified risks?Software Configuration Management: Revise and reference your software qualityassurance and software configuration management (SCM) procedures from project 3.?Hints and suggestionsProject schedule (Timeline): Use the Waterfall or Gantt Chart format but you may chooseanother format if it communicates equivalent information.?Activities/tasks: Organize these according to the software development tasks of, analysis,design, code, and test. Decompose these high-level tasks into at least one additional lower-levelsub-task, e.g.,?oDesign TaskoModule and Interface Design Sub-taskoData Design Sub-taskProject risks (section 5.4): Identify the risks that will jeopardize the successfulcompletion of the project. You must quantify and rank risks based on their severity. You do thisby estimating the risks cost to the project, typically in dollars, and the probability that the riskwill occur, an estimate between 0 and 1. Use the example in the Module Commentary tocompute a "weighted" risk which can be used to compare risks for criticality. For the mostcritical risk, propose a mitigation strategy, in other words, how to avoid or minimize theconsequences if the risk were to occur.?Software development process (section 6.1): specify one for your project, i.e., LinearSequential (Waterfall) or one of the concurrent/iterative processes. Which process you chooseshould be reflected in our Project Schedule.?Project Duration: Information in the Problem Statement has been given for the purpose ofcomputing project duration and effort. Use these to compute project duration and effort. Projectduration should be consistent with the time-line of your Schedule. Knowing project duration andeffort permits the computation of staff size, i.e., the number of software engineers required(divide effort by duration to yield staff size). I want to see the computation for effort and staffsize in the relevant template Section (section 5.2.3).?Make sure your work is neat and legible. Your charts, illustrations and diagrams can be doneusing any word processing, drawing, and/or software CASE drawing tool (or by hand) as longas it is neat and organized. Embed or scan any diagrams that you create in your SPP document?do not upload them separately.Statement of NeedJohn and Jane are starting a bed?and?breakfast (B&B) in a small New England town. They will have three bedroomsfor guests. They want a system to manage the reservations and to monitor expenses and profits. When a potentialcustomer calls for a reservation, they will check the calendar, and if there is a vacancy, they will enter the customername, address, and phone number, dates, agreed upon price, credit card number, and room numbers. Reservationsmust be guaranteed by 1 day?s payment. Reservations will be held without guarantee for an agreed upon time. If notguaranteed by that date, the reservation will be dropped.Below is the outline for the project.Title PageSignature PageChange HistoryPrefaceTable ContentsList of FiguresList of tables1. Overview1.1. Project summary1.1.1 Purpose, scope, and objectives1.1.2 Assumptions and constraints1.1.3 Project deliverables1.1.4 Schedule and budget summary (not required)1.2 Evolution of the plan (not required)2. References3. Definitions4. Project organization4.1 External interfaces4.2 Internal structure4.3 Roles and responsibilities5. Managerial process plans5.1 Start?up plan (not required)5.1.1 Estimation plan5.1.2 Staffing plan5.1.3 Resource acquisition plan5.1.4 Project staff training plan5.2 Work plan5.2.1 Work activities5.2.2 Schedule allocation5.2.3 Resource allocation5.2.4 Budget allocation (not required)5.3 Control plan (not required)5.3.1 Requirements control plan5.3.2 Schedule control plan5.3.3 Budget control plan5.3.4 Quality control plan5.3.5 Reporting plan5.3.6 Metrics collection plan5.4 Risk management plan5.5 Closeout plan (not required)6. Technical process plans6.1 Process model6.2 Methods, tools, and techniques6.3 Infrastructure plan (not required)6.4 Product acceptance plan (not required)7. Supporting process plans (not required)7.1 Configuration management plan (not required)7.2 Verification and validation plan (not required)7.3 Documentation plan (not required)7.4 Quality assurance plan (not required)7.5 Reviews and audits (not required)7.6 Problem resolution plan (not required)7.7 Subcontractor management plan (not required)7.8 Process improvement plan (not required)8. Additional planes (not required)Annexes (not required)Index


Paper#36548 | Written in 18-Jul-2015

Price : $37