You have been asked to lead a software development team

Scenario
You have been asked to lead a software development team to build a system fulfilling the
Statement of Need specified in project 1. Your team is employed by a small company. The
customer wants a project that balances reasonable development cost, timely delivery, software
quality, and functionality.
In this project, you will develop the tool for planning, managing and controlling all your
software development efforts on the B&B project. Note that typically this is the first document
that you produce not the last as we do in class. But we had to produce the other documents first
to 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 for
the system. An SPP must also develop project reporting and team communication mechanisms.
SPP Templates
Please 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 4
of the standard to review the outline. Follow the outline in Figure 1 but omit the following
sections 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 of
8, Annexes.
The assignment
Complete 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 to
address 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 course
projects).
Pay special attention to the following. The bulk of your grade will be decided on how well you
address these issues.
?

Project schedule (Timeline): Develop a schedule for the entire project.

?

Project task set: Perform a work break down schedule

Risk 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 quality
assurance and software configuration management (SCM) procedures from project 3.
?

Hints and suggestions
Project schedule (Timeline): Use the Waterfall or Gantt Chart format but you may choose
another 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-level
sub-task, e.g.,
?

o

Design Task

o

Module and Interface Design Sub-task

o

Data Design Sub-task

Project risks (section 5.4): Identify the risks that will jeopardize the successful
completion of the project. You must quantify and rank risks based on their severity. You do this
by estimating the risks cost to the project, typically in dollars, and the probability that the risk
will occur, an estimate between 0 and 1. Use the example in the Module Commentary to
compute a “weighted” risk which can be used to compare risks for criticality. For the most
critical risk, propose a mitigation strategy, in other words, how to avoid or minimize the
consequences 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 choose
should be reflected in our Project Schedule.
?

Project Duration: Information in the Problem Statement has been given for the purpose of
computing project duration and effort. Use these to compute project duration and effort. Project
duration should be consistent with the time-line of your Schedule. Knowing project duration and
effort 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 staff
size in the relevant template Section (section 5.2.3).
?

Make sure your work is neat and legible. Your charts, illustrations and diagrams can be done
using any word processing, drawing, and/or software CASE drawing tool (or by hand) as long
as it is neat and organized. Embed or scan any diagrams that you create in your SPP document
—do not upload them separately.
Statement of Need
John and Jane are starting a bed­and­breakfast (B&B) in a small New England town. They will have three bedrooms
for guests. They want a system to manage the reservations and to monitor expenses and profits. When a potential
customer calls for a reservation, they will check the calendar, and if there is a vacancy, they will enter the customer
name, address, and phone number, dates, agreed upon price, credit card number, and room numbers. Reservations
must be guaranteed by 1 day’s payment. Reservations will be held without guarantee for an agreed upon time. If not
guaranteed by that date, the reservation will be dropped.

Below is the outline for the project.
Title Page
Signature Page
Change History
Preface
Table Contents

List of Figures
List of tables
1. Overview
1.1. Project summary
1.1.1 Purpose, scope, and objectives
1.1.2 Assumptions and constraints
1.1.3 Project deliverables
1.1.4 Schedule and budget summary (not required)
1.2 Evolution of the plan (not required)
2. References
3. Definitions
4. Project organization
4.1 External interfaces
4.2 Internal structure
4.3 Roles and responsibilities
5. Managerial process plans
5.1 Start­up plan (not required)
5.1.1 Estimation plan
5.1.2 Staffing plan
5.1.3 Resource acquisition plan
5.1.4 Project staff training plan
5.2 Work plan
5.2.1 Work activities
5.2.2 Schedule allocation
5.2.3 Resource allocation
5.2.4 Budget allocation (not required)

5.3 Control plan (not required)
5.3.1 Requirements control plan
5.3.2 Schedule control plan
5.3.3 Budget control plan
5.3.4 Quality control plan
5.3.5 Reporting plan
5.3.6 Metrics collection plan
5.4 Risk management plan
5.5 Closeout plan (not required)
6. Technical process plans
6.1 Process model
6.2 Methods, tools, and techniques
6.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

Our website has a team of professional writers who can help you write any of your homework. They will write your papers from scratch. We also have a team of editors just to make sure all papers are of HIGH QUALITY & PLAGIARISM FREE. To make an Order you only need to click Ask A Question and we will direct you to our Order Page at WriteDemy. Then fill Our Order Form with all your assignment instructions. Select your deadline and pay for your paper. You will get it few hours before your set deadline.