Phone Company (WLPC) is a provider of wireless phone service in the US with 100,000 customers serving mostly small markets. WLPC has just purchased additional airwaves in the US, Canada and Mexico. They are expecting to win bids on airwaves in Eastern Europe, India and China. Because WLPC is serving the smaller markets, they have not invested in online billing and payment. With the expected growth and the larger markets, WLPC management has decided they need to offer customers the ability to review their airtime usage and bills as well as pay the bills online. You are a software engineer for WLPC online site and have been tasked by WLPC management to lead the team responsible for requirement elicitation and analysis, design, test and creating software development project plan.
Software Development Plan (SDP)
Using the Software Project Problem Specification (SS) in the syllabus, create and deliver a document artifact, Software Development plan (SDP) for the software system
Address the following software project management activities and create the artifacts for each of the activity:
Risk Assessment and Management:
- Identify and atleast five potential risks to the successful completion of your project.
- Rank the risks from greatest to least according to their severity (also referred to as Criticality). In order to quantify the severity of a risk, you need to estimate's its impact to the successful completion of the project and its probability of occurrence. Impact can be measured in ($) lost and probability is a value between zero and 1. Use your judgment for quantifying impact and probability for each risk.
Work Breakdown and Scheduling a Software Project:
- Perform task breakdown for the project. Assign task sets to individuals or teams and allocated resources, scheduled for execution, assigned budget, and so on
- Develop a schedule for the entire project. Assume the project will start January 1, 2012 and must be complete by December 31, 2012. You can submit the schedule as a chart or table.
Use the following references for guidance on how to develop software project management plan
1. Module 5 commentary (available in the course content section)
2. IEEE standard documents (available in the reserved readings section)
- Standard 1058-1998, Standard for Software Project Management Plans
SDP Grading rubric
|
Essential Contents
|
Unacceptable
(0-5 pts.)
|
Acceptable
(6-10 pts.)
|
Distinguished
(11-12 pts.)
|
|
problem statement
|
- Problem statement is not included
|
- Problem statement is included, with some elaborating discussion to provide context for IT system
|
- Problem statement is included, with a detailed discussion of the boundaries of the IT system, with engineering rationale
|
|
project scope
|
- No project scope discussion is provided
|
- Project scope is discussed, but this section essentially reiterates the problem statement
|
- Project scope is clearly discussed and clearly linked to problem statement, with engineering rationale
|
|
actors and responsibilities
|
- There is limited to no discussion of the roles and responsibilities of the key actors in the project
|
- Only the project manager and software engineers are discussed
|
- The project manager, software engineers, testers, QA, CM, V&V, and client are discussed
|
|
project effort and duration estimates
|
- Only a qualitative discussion of effort and duration is provided
|
- A quantitative analysis of project effort and duration is provided based on techniques discussed in the text or other valid references
|
- Multiple quantitative methods for effort and duration are provided to demonstrate the need to show variations and rationales for the best-estimate
|
|
project schedule with work breakdown
|
- No Gantt chart or other graphic depiction of the SDLC schedule is given
- There is no correlation of the schedule and the duration and effort estimates
- There is no decomposition of high-level SDLC tasks into lower-level sub-tasks, i.e., work breakdown
|
- Gantt or other chart depicting critical SDLC tasks over time is provided
- Project timeline is consistent with the project duration estimate
- SDLC tasks are insufficiently or not at all decomposed
|
- Schedule correlates with project effort and duration estimates
- SDLC task decomposition, i.e., work breakdown, within schedule is detailed, and incorporates overarching CM and QA tasks.
|
|
staffing
|
- No estimate is made of staff size based on effort and duration estimates
- There is only a limited discussion of the required staffing, with no rationale
|
- Staff size estimate is quantitative but not based on the methods provided in the text or other references
|
- Detailed discussion of staffing is provided using formal estimation models, e.g., COCOMO, that are based on the text or other valid references
|
|
resources, dependencies, and project specifics
|
- Little to no discussion of project resources, including staff, is provided
- No discussion of project dependencies is given
|
- Discussion includes resources, besides staff, that are required for the successful completion of the project
- Project dependencies are addressed
|
- Comprehensive discussion itemizes all resources required for the successful completion of the project
- SDLC process is selected
- Programming language is identified with rationale
- Project dependencies are discussed
|
|
risk assessment
|
- No risk assessment is provided
|
- Project risks are discussed qualitatively, with no analysis or ranking of risks
|
- Project risks are presented quantitatively and ranked according to techniques described in the text or other valid references
- Risk mitigation is discussed for the highest-ranked risks
|
|
formal document structure based on an industry standard, including title page, TOC, references
|
- SDP has little formal structure
- No references are provided
|
- SDP has little formal structure
- References are provided
|
- SDP has formal structure based on an SDP standard
- Complete list of references is provided, including problem statement and SPP standard
|