Read the case study scenario and analyze the scenario using the material from the course. There are several potential tie

$-$

ins to the course material. Be explicit when you are applying a theory. The primary objective is to demonstrate you can apply the course material to a practical scenario.

Feel free to add other discussion based on your experience, but this should not be the sole reason for your conclusion

$$

it should reinforce your conclusion. If your experience agrees with the theory you are applying, please reinforce the point with an example. This shows you understand the material more deeply and can identify situations in your experience where they applied.

Use documentation like work breakdown structure, concept of operations, top

level requirements, interface control document, systems specification

SYou are one of the few trained systems engineers on staff at your company. The CTO has asked you to

perform a postmortem on the project to determine the causes of these issues and to make

recommendations on how to avoid these problems on future projects. She doesn$$t feel like the

company can withstand another failed project like this without going out of business$$therefore$,$ she is

willing to make substantial changes to the engineering process if necessary.

You start by having a meeting with the Program Manager and Chief Engineer for the project. Your

discussion with the two of them is enlightening. The PM tells you the project was doomed from the

start. When the company was bidding on the project, they were desperate to win the contract and get a

foot in the door in the automotive market. As a result, they included too many features in their offering

for the price and the schedule was dramatically compressed to meet the time to market requirement.

To achieve this schedule compression, they dramatically cut the planned requirements gathering time

and the planned integration time. The chief engineer felt that the team was not adequately staffed to

execute the project. Due to the price cuts in the proposal, the experience level of the technical staff

were reduced in order to keep the engineering costs down. Formal milestone reviews were tailored out

of the process in order to streamline the development activities. They organized the team around the

four primary system functions as well as the hardware. The top level of the Work Breakdown Structure

$($WBS$)$ was structured the same way at the top two levels. The organization is shown in Figure $1$Figure $1.$ Technical Organization