1 / 15

Mar 31 ~ Announcements~

Mar 31 ~ Announcements~. Design competition : Sign up sheet: 2 responsibilities per team member Y ou are the “Lead” of those two. But help each other with all responsibilities

tao
Download Presentation

Mar 31 ~ Announcements~

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mar 31 ~ Announcements~ • Design competition: • Sign up sheet: 2 responsibilities per team member • You are the “Lead” of those two. • But help each other with all responsibilities • Now that you have an idea about what your design will address, do some Googling to see what others have done that’s similar. • In your design package, indicate how your design is better than prior designs • Questions? • Friday April 11 is the Human Factors and Applied Psychology (HFAP) conference. Homework assignment is to attend three talks or the keynote speech and turn in brief commentaries on each talk attended. • If you attend additional talks and turn in a commentary for them, that will count as extra credit.

  2. - INCOSE

  3. Requirements-Based Development Friday-Quiz Alert • Requirements are usually contractual • Ramifications of this = ? • Requirements must be valid • Or so they say • Requirements must be verifiable • And they mean this one • Verifiable by: inspection, analysis, demonstration, test (not by experiment) • Requirements must be traceable • Backwards to a requirement • How about evidence? • Forward to a test/verification • Numbered!

  4. Requirements-Based Development Friday-Quiz Alert • The rest of the list: Requirements should be • Necessary • Implementation Independent • “What”, not “how” • This one kills me • Clear and concise • Complete • Consistent • With existing guidance and regulations • Achievable

  5. Can You Identify Four Ways to Improve this Requirement?

  6. Can You Identify Four Ways to Improve this Requirement?

  7. Friday-Quiz Alert • Use “Shall” • not “will”, not “is to be”, not “should” • “must” indicates a strong desire of the customer, not a requirement • One requirement per requirement • Be precise • What’s wrong with: “The unit shall survive exposure to the non-operating temperature range of -40°C to +65°C.”

  8. “3.2.1.2.1 The unit shall survive exposure to the non-operating temperature range of -40°C to +65°C.” • “3.2.1.2.1 The unit shallperform as specified after exposure to the non-operating temperature range of -40°C to +65°C.”

  9. The application should continuously show the user’s location using a red arrow displayed on a map. The system’s user interface shall be easy to use by experienced users. Friday-Quiz Alert Requirements Related to Human Factors are Problematic Main Conflicts: - Verifiability - Implementation Free

  10. NASA Requirements for Constellation Program Vehicles • 3.5.4.1.1 Exercise Availability The Constellation Architecture shall allow aerobic and resistive exercise training for 30 continuous minutes each day per crewmember for missions greater than 8 days. [HS6032] Rationale: An exercise capability is not required on CEV missions to ISS or for missions with total durations of less than 8 days. Exercise is required on Lunar missions greater than 8total days to maintain crew cardiovascular fitness (to aid in ambulation during g-transitions and to minimize fatigue), to maintain muscle mass and strength/endurance (to complete mission taskssuch as EVA walk-back and contingency response capability) and for recovery from strenuoustasks, confined postures, and to rehabilitate minor muscle injuries. Per Apollo crew participating in the June 2006 Apollo Medical Summit (Houston, TX), exercise should be…

  11. NASA Requirements for Constellation Program Vehicles • 3.6.2.1.1 Crew Interface Usability - Nominal The vehicle shall provide crew interfaces with usability error rates of less than or equal to 5% (TBR-006-072). [HS7066] Rationale: For optimal safety and productivity, crew interfaces must support crewperformance with minimal errors. Errors will be defined in the context of a usability test (astructured evaluation involving the performance of representative high-fidelity tasks, duringwhich usability data such as completion times, errors, and verbal protocol comments are gathered). Usability errors include missed or incorrect inputs or selections, navigation errors,loss of situational awareness, and inability to complete a task. The usability error rate will becomputed as a percentage, (i.e., ratio of number of errors to number of task steps performed).

  12. NASA Requirements for Constellation Program Vehicles • 3.6.2.2.2 Workload Measures - "Loss of Crew/Vehicle" The vehicle shall provide crew interfaces that result in a workload rating of 30 (TBR-006-065) or lower on the NASA-TLX Workload Scale when used to perform tasks that can result in a loss of crew or loss of vehicle. [HS7001] Rationale: The intent of this requirement is to ensure that the crew is not overloaded bynominal or single-failure tasks. The TLX workload rating assessment technique is the mostwidely used workload measurement tool in operational settings similar to spacecraft vehicleoperation. Workload may be lowered through a combination of task simplification, automation,and user-interface design. A single-failure process is one which must be managed by the crew ina timely manner, but which does not have immediate intra-or inter-system mission-threateningimpacts. This is not to be confused with a "single-point" failure.

More Related