stamp systems theory accident modeling and processes

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Requirements are sufficient to distinguish the desired behavior of the software from that of any other undesired program that might be designed. Requirements Completeness Criteria (2) How were criteria derived? Mapped the parts of a control loop to a state machine I/O I/O Defined completeness for each part of state machine States, inputs, outputs, transitions Mathematical completeness Added basic engineering principles (e.g., feedback) Added what have learned from accidents · Ë · À Í Ê Î Å » ¹ É º È ¹ Ç ¸ Å · Æ µ Å ¶ Ã µ ´ c µ Ç Å  Á  ¸ ¿ · Ë · À Î Ê Î Å » ¹ É º È ¹ Ç ¸ Å · Æ µ Å ¶ Ã µ ´ µ c Ç Å  Á  ¸ ¿ Requirements Completeness Criteria (3) About 60 criteria in all including human−computer interaction. (won’t go through them all they are in the book) Robustness Data age Latency Feedback Reversibility Preemption Path Robustness Startup, shutdown Mode transitions Inputs and outputs Value and timing Load and capacity Environment capacity Failure states and transitions Human−computer interface Most integrated...
View Full Document

This note was uploaded on 11/07/2011 for the course AERO 16.36 taught by Professor Alexandremegretski during the Spring '09 term at MIT.

Ask a homework question - tutors are online