Scribd
Upload
85 views

System Design Keys

This document provides an overview of system design and key steps for forming requirements. It discusses reviewing level 1 and 2 requirements from NASA documentation. Important steps include branching level 2 requirements from level 1 requirements and the product breakdown structure, ensuring each level 1 requirement has at least one level 2 requirement. Requirements should be clear, consistent, and elaborate on their purpose. Trade-off studies and examples of level 2 requirements are also referenced.

Uploaded by

api-308151707
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
85 views

System Design Keys

This document provides an overview of system design and key steps for forming requirements. It discusses reviewing level 1 and 2 requirements from NASA documentation. Important steps include branching level 2 requirements from level 1 requirements and the product breakdown structure, ensuring each level 1 requirement has at least one level 2 requirement. Requirements should be clear, consistent, and elaborate on their purpose. Trade-off studies and examples of level 2 requirements are also referenced.

Uploaded by

api-308151707
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

System Design

Keys
By Christine Vu

Overview
Requirement Review
Trade-Off Studies
Examples

Important
Steps for
forming/
revising
requirement
s

NASA Systems Engineering Handbook


Level 1 Requirements (Pg. 40) Section 4.2 Technical
Requirements Definition Start
(Pg. 279) Appendix C Page A
Level 2 Requirements (Pg. 49) Section 4.3 Logical
Decomposition

Level 1 Requirements and Product Breakdown


Structure (PBS)
REMEMBER: Requirement by definition is quantitative

Important
Steps for
forming/
revising
requirement
s

Branch from each Level 1 Requirement and PBS


There should be at least one Level 2 requirement per
Level 1 requirement
Detailed thinking Think about each component
required to build up your project

Format: Paragraph form or list form? Make sure it is


consistent
Elaborate on why you created your requirement

Ask for your teams opinion


Your requirements should be clear so that anyone can
read it and understand it on the first try

Form a checklist

Important
Steps for
forming/
revising
requirement
s

1. Figure out whether it is quantitative. If its not, then


do research.
2. Double-check your grammar
3. Check for unclear words (etc., but not limited to,
approximately, high).
a. Reasons why it is unclear: It may not be
quantitative.
b. If it is unclear, then you should research about it
to make it clearer (find studies).
4. How did you find your quantitative values?
a. Dont forget to cite any resources/references that
you used.
5. Is your requirement only about one thing?
a. Split it if its not.

Obtained from Preliminary Design:


http://web.csulb.edu/~hill/ee400d/Documentation%20Lectu
re%20Series/04%20Preliminary%20Design%20Document.pdf

Trade-Off
Studies

Recent Top-Notch First Blog:

Level 2
Example

http://arxterra.com/category/communites/members-an
d-communities/a-techtop-wednesday
/

Questions?
End of Presentation

You might also like