 |
|
|
|
|
|
|
|
 |
|
||||||
 |
 |
 |
 |
 |
 |
 |
|
|
|
|
 |
|
|
 |
 |
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
 |
|
|
All material on this web site is copyrighted by Honourcode, Inc. 1999-2007.
Fundamentals of Systems Engineering
| The Basics of Creating Successful Systems Today’s complex systems present difficult challenges to develop. From military systems to aircraft to environmental and electronic control systems, development teams must face the challenges with an arsenal of proven methods. Individual systems are more complex, and systems operate in much closer relationship, requiring a system-of-systems approach to the overall design. This workshop presents the fundamentals of a systems engineering approach to solving complex problems. It covers the underlying attitudes as well as the process definitions that make up systems engineering. The model presented is a research-proven combination of the best existing standards. Register here to receive more
information on our courses. |
 |
| Participants in this workshop practice the processes on a realistic system development |
| Attend this course if you are:
|
The course is aimed at
|
Baltimore, MD - 18-19 Mar 08-
register
thru ATI |
Course Topics
|
Systems Engineering Model – An underlying process model that ties together all the concepts and methods. System thinking attitudes. Overview of the systems engineering processes. Incremental, concurrent processes and process loops for iteration. Technical and management aspects. Where Do Requirements Come From? – Requirements as the primary method of measurement and control for systems development. Three steps to translate an undefined need into requirements; determining the system purpose/mission from an operational view; how to measure system quality, analyzing missions and environments; requirements types; defining functions and requirements. Where Does a Solution Come From? – Designing a system using the best methods known today. What is an architecture? System architecting processes; defining alternative concepts; alternate sources for solutions; how to allocate requirements to the system components; how to develop, analyze, and test alternatives; how to trade off results and make decisions. Establishing an allocated baseline, and getting from the system design to the system. Systems engineering during ongoing operation.
|
Ensuring System Quality – Building in quality during the development, and then checking it frequently. The relationship between systems engineering and systems testing. Technical analysis as a system tool. Verification at multiple levels: architecture, design, product. Validation at multiple levels; requirements, operations design, product. Systems Engineering Management – How to successfully manage the technical aspects of the system development; planning the technical processes; assessing and controlling the technical processes, with corrective actions; use of risk management, configuration management, interface management to guide the technical development. Systems Engineering Concepts of Leadership – How to guide and motivate technical teams; technical teamwork and leadership; virtual, collaborative teams; design reviews; technical performance measurement. Summary - Review of the important points of the workshop. Interactive discussion of participant experiences that add to the material.
|
The Instructors
 Mr.
Eric Honour has been in international leadership of the engineering
of systems for a dozen years, part of a 38-year career of complex
systems development and operation. His energetic and informative presentation
style actively involves class participants. He was the founding Chair
of the INCOSE (International Council on Systems Engineering) Technical
Board in 1994, was elected to INCOSE President for 1997, and served
as Director of the Systems Engineering Center of Excellence (SECOE).
He was selected in 2000 for Who’s Who in Science and Technology
and in 2004 as an INCOSE Founder. He is on the editorial board for
Systems Engineering. He has been a systems engineer, engineering manager,
and program manager at Harris Information Systems, E-Systems Melpar,
and Singer Link, preceded by nine years as a US Naval Officer flying
P-3 aircraft. He has led or contributed to the development of 17 major
systems, including the Air Combat Maneuvering Instrumentation systems,
the Battle Group Passive Horizon Extension System, the National Crime
Information Center 2000, and the DDC1200 Digital Zone Control system
for heating and air conditioning. Mr. Honour now heads Honourcode,
Inc., a consulting firm offering effective methods in the development
of system products. Mr. Honour has a BSSE (Systems Engineering) from
the US Naval Academy, MSEE from the Naval Postgraduate School, and
is a doctoral candidate at the University of South Australia. |
 Dr.
Scott Workinger has led innovative technology development efforts
in complex, risk-laden environments for 30 years in the fields of
manufacturing (automotive, glass, optical fiber), engineering and
construction (nuclear, pulp & paper), and information technology
(expert systems, operations analysis, CAD, collaboration technology).
He currently teaches courses on program management and engineering
and consults on strategic management and technology issues. Scott
has a B.S in Engineering Physics from Lehigh University, an M.S. in
Systems Engineering from the University of Arizona, and a Ph.D. in
Civil and Environment Engineering from Stanford University. |
Page last modified 1 Feb 08