top of page

The Lesson

  • First, we defined the problem to be addressed.

  • Needs

    • Needs were derived from stakeholders. Data used to generate specific requirements was found in previous studies by NASA and other research groups.

    • Needs were developed by splitting needs by stakeholder and envisioning what these stakeholders needed

  • Functional analysis

    • This is hard to do without a more narrowed solution to the problem. It serves a more a thought experiment.

    • How to do this before system is fully designed?

    • How do we define the functions of the life support system, if we don’t have a design selected?

  • QFD

    • For a complex system, many requirements are intertwined and relate to others strongly.

    • Coming up with a metric to judge the importance of various requirements helps justify design.

    • Thresholds and targets were approximated due to large possibility of parameters for different systems.

  • Concept Selection

    • Treating each subsystem as independent of each other may leave out key system interactions that we need to consider.

    • But how do we find out about these systems interactions besides research and our own experience/engineering judgement?

“Mistakes are lessons by another name.” - Rosi S. Phillips

Contact US

Proudly created with Wix.com

  • Facebook - White Circle
  • Google+ - White Circle
  • Instagram - White Circle
  • Twitter - White Circle
  • YouTube - White Circle

Neil Armstrong Hall of Engineering

W Stadium Ave

West Lafayette, IN 47907

​​

Tel: 123-456-7890

​

contact-us@spaceponics.com

Name *

Email *

Subject

Message

Success! Message received.

bottom of page