Software engineering

Software Engineering Capstone II

Unit 1: Summary of Plan Changes

Terelle Allen, Phillip Hart, and Destiny Barrera

1/10/2018

In this phase of the project, Phillip’s responsibility was proofing the original document, making the minor grammatical corrections, and adding the agreed upon material to the risk analysis. This material can be found in the Risk Analysis section of the accompanying document paragraph 9. Below I have listed the grammatical corrects made, none of which affected the content of the material.

The API can be used by “as” many applications as necessary. Project Outline- par. 1 sent. 7

Adding abbreviation designation (SM). Development Methodology- par.5 sent.2

Even “in” the most talented development teams a project will suffer with a bad or incomplete set of requirements. Requirements- par.1 sent.2

“In” was removed from the beginning of Requirements- par. 3 sent. 2

Requirements Matrix Table row 3 column 5 spelling correction “received”

These risks are Generic risks, which are risks to every software project and Product-Specific risks, or risks which only “affect” the system being built. Risk Analysis- par. 1 sent. 3

Risk Analysis- par. 3 sent. 2 Sentence revised, fragment removed.

In this phase Terelle updated the accompanying project plan and schedule. He changed the dates, reassigned all tasks to current group members, and added the agreed upon slippage connect to the schedule making the necessary adjustments to the timetables. He also removed unnecessary hypothetical tasks such as the hiring process and orientation. He was also gracious enough to permit usage of his original project for this group exercise.

Unfortunately, Destiny’s group contribution was not available at the time of this submission, and additional changes submitted by her will need to be added in subsequent revisions of this document.