|
|
|
Here is a depiction
of our tailored process.
|
|
|
|
The Requirements
Analysis Process began in July, with Top Level Requirement delivered to TSSE,
and ensuing clarification between the two teams.
|
|
|
|
TSSE then tailored
the classic process by adding an additional step. This was the development of a Notional
Payload and Operational Concept. This
step was a combination of Requirements and Functional Analysis as indicated
by the two color block in the upper right.
This step was taken as a means of providing a scalable payload in
terms of volume and weight that could be used as a basis for conducting an
Analysis of Alternatives, or AoA. This
notional payload was fedback to SEA for their analysis to either accept,
modify or reject as our final payload.
After some modification, it was accepted by both teams, and became a
critical piece of the TSSE alternative.
|
|
|
|
We then began our
Functional Analysis by performing a top level AoA which determined the best
choice of ship size. We then developed
an Initial Requirements Document including a list of Critical Design
Parameters based on top level and derived requirements.
|
|
|
|
The Critical Design
Parameters were then input into the design synthesis. Each of the three blocks under Synthesis
then underwent their own versions of the classical SE process.
|