We Are All Systems Engineers and Why That is Important
•Download as PPTX, PDF•
1 like•1,372 views
Presented by: Rebecca Reck
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to We Are All Systems Engineers and Why That is Important
Similar to We Are All Systems Engineers and Why That is Important (20)
More from Society of Women Engineers
More from Society of Women Engineers (20)
Recently uploaded
Recently uploaded (20)
We Are All Systems Engineers and Why That is Important
- 1. We are all systems engineers And why that is important Rebecca Reck Senior Systems Engineer, Rockwell Collins Section Representative, SWE-ECI rebecca.reck@swe.org www.rebeccaee.com
- 2. • Background • Systems Engineering Model • Characteristics of Good Requirements • Practice • Verification and Validation • Resources • Questions Agenda Nov. 9 20122 Rebecca M. Reck, www.rebeccaee.com
- 3. “Systems Engineering is an engineering discipline whose responsibility is creating and executing an interdisciplinary process to ensure that the customer and stakeholder's needs are satisfied in a high quality, trustworthy, cost efficient and schedule compliant manner throughout a system's entire life cycle.” Systems Engineering Background Nov. 9 20123 Rebecca M. Reck, www.rebeccaee.com A consensus definition from the INCOSE Fellows.
- 4. 1940s – Term systems engineering used at Bell Telephone Labs 1971 – 1st ABET Accredited Systems Engineering BS Degree at the US Naval Academy 1990 – INCOSE formed History of Systems Engineering Nov. 9 20124 Rebecca M. Reck, www.rebeccaee.com
- 5. Systems Engineering Models Nov. 9 20125 Rebecca M. Reck, www.rebeccaee.com From Systems Engineering for Intelligent Transportation Systems, Federal Highway Administration, US DOT
- 6. • Individual Requirements • Necessary • Implementation Independent • Unambiguous • Complete • Singular • Feasible • Verifiable • Correct • Conforming Characteristics of Good Requirements Nov. 9 20126 Rebecca M. Reck, www.rebeccaee.com From Guide to Writing Requirements, INCOSE
- 7. • Sets of Requirements • Complete • Consistent • Feasible • Bounded Characteristics of Good Requirements Nov. 9 20127 Rebecca M. Reck, www.rebeccaee.com From Guide to Writing Requirements, INCOSE
- 8. • Validation • Are you building the right thing? • Verification • Are you building it right? Validation and Verification Nov. 9 20128 Rebecca M. Reck, www.rebeccaee.com
- 9. • INCOSE – International Council on Systems Engineering • www.incose.org • MIT Open Courseware – Engineering Systems Division • http://ocw.mit.edu/courses/engineering-systems-division/ • Systems Engineering Fundamentals – Defense Acquisition University, DoD • http://www.dau.mil/pubs/pdf/SEFGuide%2001-01.pdf • Systems Engineering for Intelligent Transportation Systems – Federal Highway Administration, US DOT • http://ops.fhwa.dot.gov/int_its_deployment/sys_eng.htm • SAE – Society of Automotive Engineers • www.sae.org • Wikipedia Resources Nov. 9 20129 Rebecca M. Reck, www.rebeccaee.com
- 10. "Great discoveries and improvements invariably involve the cooperation of many minds" — Alexander Graham Bell Nov. 9 201210 Rebecca M. Reck, www.rebeccaee.com
Editor's Notes
- The term systems engineering dates back to Bell Telephone Laboratories in the early 1940s [Schlager, 1956; Hall, 1962; Fagen, 1978]. Fagen [1978] traces the concepts of systems engineering within Bell Labs back to early 1900s and describes major applications of systems engineering during World War II. Hall [1962] asserts that the first attempt to teach systems engineering as we know it today came in 1950 at MIT by Mr. Gilman, Director of Systems Engineering at Bell.