For the assignments in this course, you will not be implementing the actual soft
ID: 3694881 • Letter: F
Question
For the assignments in this course, you will not be implementing the actual software project, but rather, you will be developing a comprehensive software development plan document. Your first task in this process will be to select a project to use as the basis of your design. You will also create the shell document for the final project deliverable that you will be working on during each unit. As you proceed through each project phase, you will add content to each section of the final document to gradually complete the final project delivery.
The project requires that you do the following:
Submit the project proposal to your instructor for approval.
Software Development Plan Document Shell
Use Word
Title Page
Course number and name
Project name
Student name
Date
Table of Contents
Use auto-generated TOC
Separate page
Maximum of 3 levels deep
Be sure to update the fields of the TOC so it is up-to-date before submitting your project.
Section Headings (Create each heading on a new page with TBD as content except for sections listed under New Content below.)
Project Outline
Planning
Analysis
Design
Quality Assurance
Implementation
Maintenance
New Content
Project Outline
Briefly describe the project.
Include a list of the major goals and constraints for the project.
Material can be taken from approved proposal submitted to instructor.
Be sure this project is approved by the instructor.
Planning
Identify the stakeholders for the project.
Identify the tools required for the project and how they will be used.
Identify the software development life cycle model that will be used for the project, including justification of the selection.
Identify the major phases of the project, and illustrate how they fit in the selected development model.
Name the document "yourname_ITSD422_IP1.doc."
Explanation / Answer
For completing this assignment, you can use the following guidelines:
1. For Project Proposal: For a given problem/project, Project Proposal is possibly the first document that describes the problem and possible approach/solution to solve that problem. It should have following sections:
a) Detailed Problem Statement
b) Proposed Solution
c) Constraints, Objectives and scope
d) Methodology/Approach to be adopted
e) Duration required to complete the project
f) Budget, if any.
Here one thing to note is that problem statement should be complete in all aspects covering all possible scenarios and issues. Also, objectives and scope of the work should be clearly defined because these will form the basis of further work to be specified in project outline.
2. For Project Outline: Once project proposal is approved, Project Outline is the next step that describe the project in much greater detail in terms of background, executive summary, work to be done, its objectives, deliverables and milestones, stakeholders, timeline, detailed costing, team composition, infrastructure and technology requirements etc. It should have the following sections:
a) Executive Summary
b) Project Overview
c) Obectives and Scope
d) Detailed System description and architecture
e) Major deliverables/subsystems
f) Timeline with respect to major milestones
g) Stakeholders of the system
h) Technology & Deployment platform and requirements
i) Detailed Costing
j) Development team details
Major sections to be described critically in proposal are c, d, e, f, h and i.
3) For Project Plan: Project Plan document in detail describes how project will progress. In fact, it is the blue print of the work to be done. It has the following sections:
a) Project Objectives, Scope and assumptions: Scope should clearly specify what is included and what is exculded.
b) Project Stakeholders and their role, responsibilities in project
c) Project Team organisation in terms of Project Lead, Team Lead and Team Members.
d) Software Development Model/Methodology: Under this section, all the phases to be undergone and their outcomes should be described. Typical phases of a development model (waterfall) are: Requirement gathering, Analysis, Design, Implementation, Testing, Deployment. Use of a particular model with respect to the context of the system should also be specified under this section.
e) Work Breakdown Structure (WBS): WBS hierarchically specifies the order, schedule and corresponding resources of project activities to be undertaken starting from phases to sub-phases to atomic (no further decomposition possible) task highlighting all major milestones and critical paths.
f) Risk management, if any: Highlights major risks to the successful completion of the project.
g) Development, Technology and testing environment being used
h) Software configuration and change management for code, version and change control
i) Deployment environment
j) Testing, Delivery and Deployment plan
k) Security Considertions, if any
Hope this helps you.