MIT16_842F09_lec03

MIT16_842F09_lec03 - Requirements Definition Prof. Olivier...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

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

Unformatted text preview: Requirements Definition Prof. Olivier de Weck How we should (attempt to) specify exactly what is needed before we start designing 16.842 Fundamentals of Systems Engineering Session 3 Fall 2009 1 V-Model Sept 25, 2009 Systems Engineering Overview Stakeholder Analysis Requirements Definition System Architecture Concept Generation Tradespace Exploration Concept Selection Design Definition Multidisciplinary Optimization System Integration Interface Management Verification and Validation Commissioning Operations Lifecycle Management Cost and Schedule Management Human Factors System Safety Overview What are requirements? Definition, Example, Evolution, Standards NASA Requirements Process Challenges of Requirements Definition Flowdown and Allocation Validation and Verification Writing good requirements Requirements Definition Requirements describe the necessary functions and features of the system we are to conceive, design, implement and operate. Performance Schedule Cost Other Characteristics (e.g. lifecycle properties) Requirements are often organized hierarchically At a high level requirements focus on what should be achieved, not how to achieve it Requirements are specified at every level, from the overall system to each hardware and software component. Critically important to establish properly DC-3 Requireme Requirements based on desire improvements to DC-2 Very simple 3 page RfP (McDonnell Museum) Marathon phone call between Smith and Douglas Key Requirements Range: 1000 miles Cruise Speed: 150 mph Passengers: 20-30 Depending on configuration Twin Engines Rugged and Economical nts d Image by jfhweb on Flickr. 1 st flight: 17 Dec 1935 Over 10,000 built Requirements Explosion More and more requirements were added as systems grew in performance and complexity Source: AIAA MDO TC White Paper, 1991 Producibility Affordability Supportability CITS P 3 l Observables Fly-by-wire Laser Nuclear Nonnuclear Noise Damage tolerance Smart weapons Computerized management information Specified reliability Flotation Specified flight life Energy maneuverability Rough field landing Acoustic fatigue Stress corrosion Rain erosion Radar transparency Handling qualities Laminar flow Pressurization Corrosion control Maneuver and gust accelerations 1-g flight 1900 1903 1910 1920 1930 1940 1950 1960 1970 1980 1990 Design requirements growth for aerospace vehicles. Image by MIT OpenCourseWare. Requirements are not static Submitter Assignee only Pending Implemented Rejected Unknown Affected by 87 CR Unaffected Social Layer Engineers Based on the research of Michael Pasqual Process Layer Change Requests System Layer Subsystems 7 Documentation 1- Requirements Data from Raytheon IDS Image by MIT OpenCourseWare. Requirements Standards NASA Systems Engineering Handbook NASA/SP-2007-6105 Section 4.2 (pp. 40-48) Technical Requirements Definition Section 6.2 (pp. 131-135) Requirements Management...
View Full Document

Page1 / 34

MIT16_842F09_lec03 - Requirements Definition Prof. Olivier...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online