Individual Portion

The final step in developing the software development plan is to conduct a risk assessment for the project. This is an area often overlooked in software development plans, but it can make a tremendous difference in the success of the plan. Your goal in this stage of the project is to identify areas of the plan that might be at risk, and to prepare risk mitigation action plans for the high-probability and high-impact risk items. You will also further refine the plan to produce the final draft version for the project. Updates may be based on peer and instructor feedback.

The following are the project deliverables:

  • Update the software development plan document title page with a new date and project name.
  • Update the previously completed sections based on your instructor’s feedback.
  • Please include the following new content in 3–4 additional pages:
    • Risk Analysis:
      • Use appropriate risk analysis techniques to identify the areas of the project you consider to be high risk.
      • Describe why these are high-risk areas and their potential effects on the project.
      • For each risk, document a risk mitigation strategy.
  • Complete the following for the software development plan final version:
    • Review the entire document for any changes and improvements you would like to make.
    • Ensure this final version of the plan is sufficiently detailed to allow the engineering team to move forward with the development.
    • Any previous instructor feedback should be addressed with appropriate changes.
  • Be sure to update your table of contents before submission.
  • Name the document yourname_SWE481_IP5.doc.
  • Submit the document for grading.

Group Portion

Throughout the course, you have been working on the sections of your individual software development plan for a project selected by your team at the beginning of the course. The group project deliverable for the course is a software development plan that incorporates the best thinking from all of the members of your team. The individual areas of the completed plan should be cohesive with no overlap and represented as a single, cohesive document, rather than a combination of separate individual projects from individual team members.

Each week, you were instructed to share your individual projects with your team, and the teams were instructed to incorporate the new material into the collective team software development plan. If your team has been keeping pace with these instructions, you should currently have a substantial part of your deliverable completed. The structure and format of your team’s software development plan will be the same as the individual project software development plan.

In addition to the group’s software development plan document, your team will prepare and submit a PowerPoint presentation summarizing the contents of the software development plan. It will be helpful to divide the content of the presentation among the group members.

Note: Because the risk assessment is part of the individual project due at the end of the week, the group must communicate well during the week to incorporate this content into the group software development plan document. Group members should work on their individual project as early as possible to ensure that they have meaningful risk assessment information to share with the team.

Assignment

For the group project deliverable, create a software development plan (8–10 pages) incorporating the collective work from the individual project assignments submitted by the team members. The software development plan should contain the content listed below, and it should conform to the same requirements as the individual project weekly assignments.

In addition to the software development plan document, your team should prepare a PowerPoint presentation of 10–15 slides that summarizes the contents and highlights of the software development plan. The presentation should be usable as the basis for a presentation that might be given to the stakeholders of a project to gain final approval for moving forward with the project into the development stage.

The requirements for the presentation are listed below:

  • Software development plan document (Word document)
    • Title page
      • Course number and name
      • Project name
      • Group Name
      • Student names
      • Date
    • Table of contents
      • Auto-generated TOC
      • Separate page
      • Maximum of 3 levels deep
      • Fields of TOC should be up-to-date before submitting
    • Project Outline
    • Development Methodology
    • Requirements
    • Design
    • Development and Testing
    • Project Schedule
    • Risk Analysis
  • Software development plan presentation (PowerPoint document)
    • Title page
      • Course number and name
      • Project name
      • Group Name
      • Student names
      • Date
    • Slides covering the highlights and key points of the following content areas from the software development plan:
      • Project Outline
      • Development Methodology
      • Requirements
      • Design
      • Development and Testing
      • Project Schedule
      • Risk Analysis
  • Name the software development plan document groupname_SWE481_GP.doc.
  • Name the PowerPoint presentation groupname_SWE481_GP.ppt.
  • Submit the documents for grading.

What Students Are Saying About Us

.......... Customer ID: 12*** | Rating: ⭐⭐⭐⭐⭐
"Honestly, I was afraid to send my paper to you, but you proved you are a trustworthy service. My essay was done in less than a day, and I received a brilliant piece. I didn’t even believe it was my essay at first 🙂 Great job, thank you!"

.......... Customer ID: 11***| Rating: ⭐⭐⭐⭐⭐
"This company is the best there is. They saved me so many times, I cannot even keep count. Now I recommend it to all my friends, and none of them have complained about it. The writers here are excellent."


"Order a custom Paper on Similar Assignment at essayfount.com! No Plagiarism! Enjoy 20% Discount!"


0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *