# Presentation: 186738

##   International Council on Systems Engineering Introduction.....    

***Susan Jones*****,  INCOSE Region V Director for Industry Affairs**
***The Aerospace Corporation***
***Chantilly, VA USA***
***susan.e.jones@aero.org***
** **

## Outline

**Overview****	*****Ken Kepchar******	******Region V Director***
**Technical Committees and ****	*****John Snodderly*****Working Groups****	*****President Elect******	******Past Technical Board Chair***
**Education and Research TC****	*****Dennis Buede******	******Technical Committee Chair***
**Chesapeake Chapter****	*****Jerry Woodall*****	**** *****Chapter President***
**Washington Metro Area Chapter****	*****Bruce Shelton*****	**** *****Chapter President***
**Southern Maryland Chapter****	*****Karl Geist*****	**** *****Chapter President***

## Our Past 

**Started in 1990 by 35 US leaders as National Council on Systems Engineering (NCOSE)**
**First Annual Symposium held in 1991  **
**Most early members from defense/aerospace **
**Most early activity focused on sharing within the organization**
**Became International (INCOSE) in 1996**

## Our PresentINCOSE is an international authoritative body promoting the application of an interdisciplinary systems approach to enable the realization of successful systems   

## Our Present 

**Steady growth in membership with increasing diversity **
**Non-US participation and leadership has increased significantly **
**Key participant in industry standards and models**
**Increasing collaboration between university, industry, and government**
**Affiliations/interactions with other professionals bodies and industry societies to produce shared outcomes**

## INCOSE Goals

**Provide a focal point for dissemination of knowledge**
**Promote collaboration in systems engineering education and research**
**Establish professional standards for integrity in the practice of systems engineering**
**Improve professional status of all people engaged in the of practice of systems engineering**
**Encourage support from government and industry for research and educational programs**

## INCOSE Regions

**III**

**V**

**VI**

**I**

**IV**

**II**

## INCOSE Governance Structure

**Board of Directors **
**Executive Committee (officers) **
**Corporate Advisory Board**
**Technical Board  **
**Technical Committees (7)**
**Working Groups/ Interest Groups (30+) **
**Systems Engineering Center of Excellence**
**Administrative Committees (5)**
**Chapters, Communications, Membership, Symposium, Ways & Means  **
**Central Office  **

## Corporate Advisory Board

**Corporate Advisory Board**

**Consists of one representative from each corporate sponsor (37 and growing) **
**Provides recommendations to INCOSE on overall direction, focus, and priorities **
**Acts as a conduit between INCOSE and sponsoring corporations for resolving key issues**
**Seeks to influence the future of systems engineering standards, practices, education, research and other key issues**

- NASA  joined as a CAB Member in 1999

## CAB Members

**Aerojet**
**The Aerospace Corporation**
**Astrium GmbH**
**BAE Systems**
**The Boeing Company**
**Boeing Satellite Systems**
**Boeing - Military Aircraft & Missiles Systems**
**C.S. Draper Laboratory**
**The Defence Evaluation and Research Agency**
**Delphi Automotive Systems**
**EADS Military Aircraft Division**
**Department of Energy - Idaho**
**General Dynamics Corporation**
**Honeywell International**
**Israel Aircraft Industries**
**Jet Propulsion Laboratory**
**Litton/PRC**
**Litton/TASC**
**Lockheed Martin Corporation**
**The MITRE Corporation**

**Motorola**
**National Aeronautics and Space Administration**
**Naval Air Systems Command**
**Naval Surface Warfare Center - Dahlgren Division**
**Northrop Grumman Corporation**
**Raytheon Systems Company**
**Raytheon Systems Company/Texas**
**Rockwell Collins Avionics & Communications**
**Science Application International Corporation**
**Structural Dynamics Research Corporation**
**Software Productivity Consortium**
**TRW Systems & Information Technology Group**
**Telelogic AB**
**Thomson-CSF Racal PLC**
**United Technologies**
**Vitech Corporation**
**Xerox Corporation**

## INCOSE Membership Benefits 

**INCOSE Journal**
**INSIGHT **
**Symposia, Workshops, Conferences**
**Membership discounts**
**Early visibility into emerging standards **
**Knowledge of engineering from a global perspective**
**Means to tap expertise of industry experts**
**Networking with colleagues from around the world**
**...****..and more **

## INCOSE

- Networking

**Technical**

- Committee

**Professional**

- Disciplines

**Geographical**

- Region

**Domains**

- Branch

- Chapters

- Working Groups

- Joint Activities

- Interest  Group

## Our FutureINCOSE is the world’s premier engineering professional society for enabling holistic solutions to problems and needs  

## Six Strategic Priorities

**(1) Provide **_**high value products and services**_** and opportunities for professional networking**
**(2) Position INCOSE as **_**a unifying force**_** across engineering communities and related specialties **
**(3) Promote **_**growth through diversification**_** of stakeholder base and products/services**** **

## Six Strategic Priorities

**(4) Attract **_**highly qualified leaders**_**  and provide **_**infrastructure and balanced leadership        organization**_** to accomplish targeted initiatives**
**(5) Gain further recognition of the **_**importance of systems engineering**_** **
**(6) Achieve wide **_**acceptance of INCOSE as                       the leading systems engineering society**_** **

## Advancement

**Develop **_**products and services to foster advancement of individual member’s knowledge**_
**SE Body of Knowledge  **
**Examine means to **_**create partnerships between industry & universities**_
**Academic Forum**** **
**Foster **_**selected research opportunities**_** through INCOSE Systems Engineering Center of Excellence (SECOE)**
**Expand the **_**circulation of the INCOSE journal**_** **

## Influence 

**Sponsor/participate in **_**targeted conferences  **_
**Many regional/chapter events, and INCOSE track at Software Technology Conference **
**34th Engineering and Technical Management Conference (EIA/GEIA, INCOSE, NDIA)  **
**2nd European Systems Engineering Conference**
**Continue **_**participation and leadership in standards**_
**ISO, IEEE, EIA and others   **
**Offer INCOSE's **_**expertise and participation **_**in selected industry initiatives/advisory boards**
** ****BOD voted yes; opportunities being identified **

## 2001 International Symposium

## Other Events 

_***Regional Conferences ***_**  **
**Events hosted by regions or chapters with most of the elements of the annual symposium**
_***Chapter Events***_**  **
**Local events which may include chapter business meetings, special working sessions, tutorials, speakers**
_***Working/Interest Group Meetings ***_**  **
**Events held in one location or as virtual meetings with focus on a particular        product or topic area**

## SUMMARY

**Local Chapters Sponsor a Variety of Activities of Interest for NASA Personnel**
**The Mid-Atlantic Chapters Work Together to Bring Quality Programs to their Members**
**The Chapter Meetings and Programs Provide an Avenue**
**For Attendees to Exchange Ideas**
**Learn New Concepts to Employ at Work**
**Develop New Resources for Research**

**Notes:**
Might want to expand this slide into three and further develop each bullet:
-List some of the exhibitors we intend to market
-List some of the sites (museums/zoo/Historical stuff), this slide could be very important in selling the area.  People forget what is here, remind them that this is both a professional and personal opportunity (you might be able to expand this to a couple of slides, this is where you market the area)
-Technical Tours have an awesome potential (Naval Research Lab, Mitre has a bunch of stuff, huge opportunity to go look at stuff)

##   International Council on Systems Engineering Advancing the State of the Art in Systems Engineering    

***John Snodderly*****,  INCOSE President Elect and Past Technical Committee Chair**
***Defense Systems Management College***
***Fort Belvoir, VA USA***
***john.snodderly@incose.org***
** **

## Vision   

**An international body comprised of leading organizations and experts contributing to the body of knowledge  on systems engineering  **
**An organization whose leadership and members are recognized as having the highest expertise to solve systems problems  **
**A contributing partner in strategic alliances with other professional societies and leading universities worldwide**
**A center of competence for research, theory, and practices applied to systems challenges **

**Vision   **

***INCOSE is the world’s ***
***premier engineering professional society ***
***for enabling holistic solutions to problems and needs***

## WHY is INCOSE Needed ?

- Is the world of SE in trouble today?
- How would you know?
- What are some recent examples that point out a lack of SE?

## DoD  SE Problems

- “USAF Urges F-22 Production Without Test- ...ready to move into its production phase even if _an important software milestone, which legally must be reached first, is not passed_”*
- “Software Pushes Up JSF Price Tag to $31 Million - ...Marketplace changes, the software went straight up.  _Turns out it was more for software than we thought_.”*
- “...A draft report from the GAO, a government watchdog agency here, charges that the JSF program is rushing to the engineering manufacturing and development stage _before critical technologies have matured_.”*
- “_Integrating JSF engine-control software_ with avionics software has proven challenging.”*
**Defense news April 10, 2000*

## From the Mars Climate Orbiter Mishap Investigation Board Phase I Report:

- Absence of a mission systems engineer during the operations phase to provide the bridge between the spacecraft system, the instrument system and the ground/operations system.
- Lack of identification of acceptable risk by the operations team in the context of the “Faster, Better, Cheaper” philosophy.
- Navigation requirements set at too high a management level, insufficient flowdown of requirements and inadequate validation of these requirements.
- Several significant system and subsystem design and development issues, uncovered after the launch of the Mars Climate Orbiter
- Inadequate attention, within the system engineering process, to the transition from development to operations.

## From the Wide-field Infrared Explorer Mishap Investigation Board Report (Briefing by Darrell Branscome, Board Chair):

- “Detailed, independent technical peer reviews are essential. Furthermore, it is essential that peer reviews be done to assess the integrity of the system design, including an evaluation of system/mission consequences of the detailed design and implementation.”
- “Perform electronics power turn-on characterization tests, particularly for applications involving irreversible events.”
- “Test for correct functional behavior and test for anomalous behavior, especially during initial turn-on and power-on reset conditions.”

## From Lewis Spacecraft Mission Failure Investigation Board Report:

- Especially in “Faster, Better, Cheaper” projects, communication of decisions to senior NASA and contractor management is essential to successful program implementation.
- “Requirements changes without adequate resource adjustments” indirectly contributed to the failure.
- “Inadequate engineering discipline” indirectly contributed to the failure.
- “The Government and the contractor must be clear on the mutual roles and responsibilities of all parties, including the level of reviews and what is required of each side and each participant in the Integrated Product Development Team.”

## From the “Faster, Better, Cheaper” Study (Briefing by Tony Spear):

- NASA must pick capable PMs. PMs should be “certified.”
- Important to communicate project risks to project team, senior management, and to the public. PMs should project a “risk profile” or “risk signature” at start of project, monitor for changes over life of project and explain them.
- Peer reviews must include the “right” people.
- For a lander mission, it’s important to have telemetry on spacecraft descent.
- PMs must pick capable project teams. Certification of project team members should be considered.

## Orlando Figueroa's 5 major points

**Engineering Excellence in NASA**
**Advance Engineering excellence in NASA & Strengthen Systems Engineering**
**Process Documentation**
**PAPAC (Agency -wide process) Policy 7120**
**Promote infrastructure to move to a collaborative environment**
**Advanced Engineering Environments**
**NASA Collaboration with National & International bodies(i.e. INCOSE)**
**Stimulate NASA Engineering participation in National Academy of Engineering**

## How does INCOSE Advance the SE State of the Art?

- Through innovative INCOSE Technical Board Products & Services
- Provide Products and services by INCOSE Working Groups & Interests Groups
- Examples

## Technical Committees

**Technical Committees**
**Hierarchy Diagram**

*Technical*
*Board*

***Measurement***
***Technical Committee***

**Technical**
**Committees**

***Process & Methods***
***Technical Committee***

***Standards***
***Technical Committee***

***Modeling & Tools***
***Technical Committee***

***SE Management***
***Technical Committee***

***Education & Research***
***Technical Committee***

***SE Applications***
***Technical Committee***

*Education Development*
*Working Group*

*Concepts & Terms*
*Working Group*

*Education Measurements*
*Working Group*

*Capability Assessment*
*Working Group*

*Measurement*
*Working Group*

*Comm & Public Internet*
*Working Group*

*Space Systems*
*Working Group*

*Resource Mgmt.*
*Working Group*

*Telecommunications.*
*Working Group*

*Joint Comm. Aircraft*
*Working Group*

*Health Care*
*Interest Group*

*Motor Vehicles.*
*Interest Group*

*Railway Transportation*
*Interest Group*

*Principles*
*Working Group*

*Systems Architecture*
*Working Group*

*SE and the Internet*
*Interest Group*

*Tools Database*
*Working Group*

*Tools Integration*
*Working Group*

*Soft Systems*
*Interest Group*

*Model-Driven System *
*Design Working Group*

*Requirements*
*Working Group*

*Risk Management*
*Working Group*

*SE Mgmt Methodology*
*Working Group*

*Verification & Validation*
*Interest Group*

*Systems & Supportability*
*Interface Research*
*Working Group (SECOE)*

**1.2**

*Systems Engineering*
*Body of Knowledge*
*(SE BOK) Working Group*

*Environmental Systems*
*Working Group*

*Infrastructure Systems*
*Working Group*

*Human Systems*
*Working Group*

*SE Handbook*
*Working Group*

*Configuration Mgmt.*
*Interest Group*

*Information Model & *
*Process Working Group*

## Systems Engineering Applications Technical Committee (SEATC)

**Excerpts from:**
**International Workshop Summary Presentation**
**Mesa, AZ**
**January 2001**
**Dr. William Mackey, Chair**
**Ralph Godau, Co-Chair **
**Scott Jackson, Co-Chair**
**Pat Sweeney, Co-Chair**

## Systems Engineering Applications Technical Committee Charter

**Foster formation and operation of working groups and interest groups**** **
**Specific application domains**
**Across domains**** **
**Examine systems engineering tools, techniques, and processes within specific application domains**
**WG/IGs grow from a core WG (the CPIWG) into specific application domain WG/IGs**

**Notes:**
This comm is focused on commercial app domains as well as the Aerospace industry.  It also works on cross app domains including inter net, simulation and collab engineering environment. It works with the products of other Committee to carry out its activities. Works out of a core group that is called the commercial and public interest working group(CPIWG). 

## Interfaces With Other Technical Committees and Working Groups

_**Cross Applications**_

**Education**
**and**
**Research**

**SE**
**Management**

**Modeling and**
**Tools**

**Processes**
**and Methods**

**Measurement**

**Standards**

**UMUC**
**Profiles**

**UNLV**
**Seminar**

**U. Birming**
**Rail Activity**

**Aircraft**
**Guidelines**

- Commercial and Public Interest
- Commercial Aircraft
- Environmental Systems
- Infrastructure Systems Engineering
- Resource Management
- Space Systems
- Telecommunications
- Health Care
- Motor Vehicles
- Railway Transportation

_**Specific Applications**_

**Communications**

**INSIGHT**
**V1-I3-1998**

**INSIGHT**
**V2-I2-1999**

**INSIGHT**
**V3-I3-2000**

**Joint ****Symposium**
**Panel**

**Notes:**
What is shown here is how the TC works with other TCs. Left side is the ten working and interest groups. They have recently produced in INCOSE’s quarterly technical publication “INSIGHT”.  Second row shows work with academia , UMD a t College park,  UNLV and UN of Birmingham in England.  Many people teach not only at these universities but also USC, GMU, RMIT in Australia. As examples.   We have joint panels and are producing guideline documents for products such as Commercial Aircraft.  

## Where We Are Today

- Transportation Sector—Ashok Jain
**Joint Commercial Aircraft Working Group (JCAWG)— ****Greg Mathers, and Erwin Duurland**
**Motor Vehicles Interest Group (MVIG)—Paul Berry**
**Railway Transportation Interest Group (RWTIG)—****John Williams and Jeff Allan**** **
- Resources Sector—Ralph Godau
**Infrastructure Systems Engineering Working Group (ISEWG)—Pat Sweeney and Ralph Godau**
**Resource Management Working Group (RMWG)— ****Ted Dolton and Bill Cutler**
**Environment Systems Working Group (ESWG)—Ralph Hill**** **

**Notes:**
We have three sectors with in the TC.  The working groups fall into these three sectors.  We have representatives from all the major industry segments as well as government, and International Participants from Australia etc.    in these working groups. 

## Where We Are Today (Cont’d) 

- Public Services Sector—Pat Sweeney
**Commercial and Public Interest Working Group—****Jerry Bauknight and William Mackey**
- Space Systems Working Group (SSWG)—David Durham and Ray Granata
- Telecommunications Working Group (TELWG)—Martin Warner and Ruediger Kaffenberger
**Health Care Interest Group (HCIG)—John Zaleski and Orlando Illi**

**Notes:**
Third public sector.  Space systems is represented by David Durham (JPL) and Ray Granada (Goddard) both co chairs of this important working group.  This group currently is made up of 60 people and is the largest Working Group in INCOSE made up of all NASA centers, contractors and USAF,

## SEATC Accomplishments

**Approximately 242 SE applications papers have been presented in 20 commercial and public interest domains at the Symposia from 1992 to 2000 **** **
**The SEATC has offered application specific sessions at the symposia since 1996**** **
**Nine symposia panels and five regional seminars in commercial and public interest domains have been presented**

## SEATC Accomplishments (Cont’d) 

**Key products include:**** **
**SE Applications Profiles Document (Version 3.0 on WEB)**
**SE Applications Organization Document (Version 1.0 on WEB)**
**Edited three commercial themed issues of *****INSIGHT***** (1998. 1999, 2000)**
**Framework for the Application of SE in the Commercial Aircraft Domain (Version 1.2 Released in July 2000)**
- Telecommunications Industry Application Guidebook (TBD)
- Space Systems Application Guidebook (TBD)
**44 professional papers and 5 SE Applications Panels were conducted at the Minneapolis, MN Symposium**** **
**Several volunteer SE projects are underway in San Francisco Bay Area Chapter and other local chapters**

**Notes:**
These are some of our primary products.  You can download all of these products from the INCOSE web sight. SSWG is looking to develop a space sys applications guidebook.

## Systems Engineering Applications Domains

***Applications domains currently represented in document**

-  1.	Agriculture	14.	Housing and Building Systems
-  2.	Commercial Aircraft	15.	Information Systems
-  3.	Commercial Avionics	16.	Manufacturing
-  4.	Criminal Justice and Legal	17.	Medical Devices
- 	Systems	18.	Motor Vehicles
-  5.	Drug Abuse Prevention	19.	Natural Resource Management
-  6.	Emergency Systems	20.	Political and Public Interest
-  7.	Energy		Systems
-  8.	Environment Restoration	21.	Service Industries
-  9.	Facilities Systems Engineering	22.	Space Systems
- 10.	Food Service	23.	Telecommunications
- 11.	Geographic Information Systems	24.	Transportation
- 12.	Health Care	25.	Urban Planning
- 13.	Highway Transportation Systems	26.	Waste Management and 				Disposal

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

*****

**Notes:**
These are the 26 Domains and those that are starred are included in the profiles document.  (Space Systems is being updated)    

## Standards Technical Committee

**1.1**

**January 2001**
**James Martin, Chair**
**John Velman, Co-Chair **
**Alain Faisandier, Co-Chair**

**Notes:**
Technical Committee Models
Standards Technical Committee

## Current SE Standards

- ANSI/EIA-632
**Processes for Engineering a System, Dec 1998**
**www.geia.org/eoc/G47/main.html**
- EIA/IS-731
**Systems Engineering Capability Model, Dec 1998**
**www.geia.org/eoc/G47/main.html**
**IEEE 1220**
**Application and Management of the Systems Engineering Process, 1998**
**ECSS-E-10A**
**System Engineering, Apr 1996**
**European Cooperation for Space Standardization**
**www.estec.esa.nl/ecss/standard/status.html **

**Co-developed by INCOSE**

## International Standards(under development) 

**System Life Cycle Processes, ISO/IEC 15288**
**JTC1/SC7/WG7**
**SE Capability Maturity, ISO/IEC 15504 (SPICE)**
**JTC1/SC7/WG10**
**SE Data Exchange, ISO 10303-AP233**** **
**TC184/SC4/WG3/T8**
**Systems Engineering (Space Systems)**
**TC20/SC14 **
**To adopt ECSS-E-10 as ISO standard**

## Other Standards (under development) 

**Capability Maturity Model Integration (CMMI) **
**National Defense Industry Alliance (NDIA)**
**Electronic Industries Alliance (EIA)**
**System Architecture, IEEE P1471**
**INCOSE Architecture WG working this task**
**Engineering Management Book of Knowledge (EMBOK)**
**IEEE Engineering Mgmt Society**
**Project Management Book of Knowledge (PMBOK)**
**Project Management Institute (PMI)**
**Currently available, but upgrades are planned**

## Liaison Activities

_**INTERNATIONAL**_
_**ISO JTC1/SC7**_**, Technical Liaison**
**Robert Halligan appointed by BOD**
**Standards 15288/15504 under authority of SC7 working groups**
_**ISO 15288**_**, System Life Cycle Processes**
**SC7 Liaison, Robert Halligan**
_**ISO 15504**_**, Systems Engrg Capability Model**
**SC7 Liaison, Robert Halligan**
_**ISO 10303-AP233**_**, STEP Systems Engrg Data Exchange**
**POC is Sylvain Barbeau**
**David Oliver, INCOSE Liaison**

_**UNITED STATES**_
_**EIA G47**_**,  Systems Engineering Committee**
**TBD, primary **
**Richard Harwell, alternate**
_**AIAA**_**, Systems Engineering Technical Committee**
**Informal POC is Richard Harwell**
**Formal liaison being considered**
_**IEE**__**E**_**, Systems Engineering Standards Committee**
**Liaison being worked with Paul Croll**

## Slide 45

## Slide 46

## Chapters - Technical Board Combined Efforts 

- Positive Steps taken for cooperative efforts
- Potential Funding of Special Projects By Chapters
- EIA AP233 UML Effort
- GEIA G-47

## INSIGHT Magazine for July

**Reports from INCOSE’s**
**Technical Board,**
**Technical Committees and**
**Working Groups **

## INCOSE Technical Journal 

- Quarterly Publication
- Refereed Journal
- Andy Sage GMU Editor

## Commercial Aircraft Guidebook

**DRAFT**
**Framework for the Application of Systems Engineering ****in the**
**	****Commercial Aircraft Domain**
**Version 1.1**
**Jun 15, 2000**

**Draft Circulated for**
**comment July 00**

## Establishment of Liaisons for Standards

- Definition of Liaison - “A linking up or connecting of the parts of a whole, as of military units, in order to bring about proper coordination of activities*”
- Robert Halligan SC-7 Liaison for 15288
- David Oliver AP-233 Liaison
- Richard Harwell EIA/G-47 Liaison

*** Webster New World Dictionary**

## SE Handbook Update

**Handbook currently **
**being reviewed.**

## Proposed INCOSE SE BoK similar to PMI-PM BoK and ISO-SE BoK

**Format widely accepted**
**Significant similarity and overlap with PMI and ISO models**
**Integration with other disciplines is simplified**
**Broad perspective is useful for many**
**Simplified update over a comprehensive document**
- Disadvantages
**Not comprehensive in the near to intermediate term thus requiring multiple references**
**Format May reduce likelihood of SE BoK becoming a standard**
**Requires constant monitoring of references**

## We need NASA’s help!

**Provide their SE technical expertise to INCOSE WG’s (especially Space WG)**
**Provide technical input to special projects (I.e. SEBOK)**
**Become members of our (Corporate Advisory Board - **Orlando is** **NASA HQ CAB member**), **David Durham is JPL CAB member
**Attend and participate in local chapters activities and working groups.**

##   International Council on Systems Engineering Education and Research in Systems Engineering    

***Dennis Buede*****,  Education and Research Technical Committee**
***George Mason University***
***Fairfax, VA USA***
***dbuede@gmu.edu***
** **

## Status of SE Research & Education

## Topics

**Activities in the Education & Research TC**
**Charter and Working Groups**
**Education development WG**
**SE Body of Knowledge WG**
**Research in SE Center of Excellence**

## Education and Research Technical Committee 

- To make Systems Engineering education a proven, value-adding, activity that matures in a systemic manner to the satisfaction of the key stakeholder groups - Industry, Systems Engineers and Educators
**Chair - Dennis Buede, +1 703-993-1727, dbuede@gmu.edu**** **
**CoChairs**
**Phil Brown, +1 972-262-0530, phil.brown@seconcepts.com**
**Stephen Cook, +61 8 8302 3818, stephen.c.cook@unisa.edu.au**** **
**Education Development Working Group **
**Define and develop databases that describe educational opportunities at the undergraduate and graduate level of systems engineering that can be used as a guide for formal academic programs at all levels.**** **** **
**Concepts and Terms Working Group **
**Define and document the conceptual foundations of SE within the framework of a common set of terms (with definitions) to support more effective communication of SE.**** **
**Educational Measurements Working Group **
**To assist and make Systems Engineering education a proven, value-added, activity that matures in a systemic manner.**** **
**Systems and Supportability Interface Research Working Group**** **
**To research cause-and-effect relationships that link system architectural and design decisions to impacts on system operational effectiveness and life-cycle cost in an increasingly competitive and resource constrained environment.**** **
**SE Body of Knowledge Working Group**
**To create a Guide to the SE Body of Knowledge.**

## Education Development WG

**SE Bibliographies**
**SE Education and Training Resources**

## SE Bibliographies

**Overall Bibliography**
**Started with SEFT Bibliography (53 pages)**
**Updated with Annotations by GMU M.S. Students (79 pages)**
**Updated by Jack Fisher’s Bibliography (98 pages)**
**(To be) Updated by Don Clausing’s Bibliography**
**Bibliography of SE Books**
**Bibliography of Books about Systems**

- Goal: Update once each year
- Publish on INCOSE web site
- Advertise in INSIGHT

## Books on Systems Engineering

- Ackoff, R.L. and Emery, F.E. (1972). *On Purposeful Systems*.
- Akao, Y.A. (1990). *QFD: Integrating Customer Requirements into Product Design*.
- Alexander, C. (1964). *Notes on the Synthesis of Form*.
- Andriole, S.J. (1996). *Managing Systems Requirements: Methods, Tools, and Cases*.
- Asimow, M. (1962). *Introduction to Design*.
- Athey, T.H. (1982). *Systematic Systems Approach: An Integrated Method for Solving Systems Problems*.
- Baumgartner, J.S. (1979). *Systems Management*.
- Baylin, E.N. (1990). *Functional Modeling of Systems*.
- Beam, W.R. (1990). *Systems Engineering: Architecture and Design*.
- Beam, W.R. (1989). *Command, Control, and Communications Systems Engineering*.
- Beer, S. (1985). *Diagnosing the System for Organizations*.
- Belcher, R. and Aslaksen, E. (1992). *Systems Engineering*.
- Bellamy, L.J. (1985). *The Safety Management Factor: An Analysis of the Human Error Aspects of the Bhopal Disaster*.
- Blair, R.N. and Whitston, C.W. (1971). *Elements of Industrial Systems Engineering*.
- Blanchard, B.S. (1991). *System Engineering Management*.
- Blanchard, B.S., and Fabrycky, W.J. (1998). *Systems Engineering and Analysis*.
- Boardman, J. (1990). *Systems Engineering: An Introduction*.
- Bowen, J.P. and Hinchey, M.G. (1999). *High-Integrity System Specifications and Design*.
- Buede, D.M. (2000). *The Engineering Design of Systems: Models and Methods*.
- Card, S.K., Moran, T.P., and Newell, A. (1983). *The Psychology of Human-Computer Interaction*.
- Carroll, J.M. (ed.). (1995). *Scenario-Based Design*.
- Carter, D.E. and Baker, B.S. (1992). *Concurrent Engineering: The Product Development Environment for the 1990’s*.
- Chapanis, A. (1996). Human Factors in Systems Engineering.
- Chapman, W.L., Bahill, A.T., and Wymore, A.W. (1992). *Engineering Modeling and Design*.
- Chase, W.P. (1974). *Management of System Engineering*.
- Checkland, P.B. (1981). *Systems Thinking, Systems Practice*.
- Chestnut, H. (1967). *Systems Engineering Methods*.
- Chestnut, H. (1965). *Systems Engineering Tools*.
- Chorafas, D.N. (1989). *Systems Architecture and Systems Design*.
- Churchman, C.W. (1971). *The Design of Inquiring Systems*.
- Churchman, C.W. (1968). *The Systems Approach*.
- Cochin, I. And Plass, H.J. (1997). *Analysis and Design of Dynamic Systems*.
- Cooper, D. and Chapman, C. (1987). *Risk Analysis for Large Projects: Models, Methods and Cases*.
- Corbett, J., Dooner, M., Meleka, J., and Pym, C. (1991) *Design for Manufacture: Strategies, Principles, and Techniques*.
- Coulouris, G., Dollimore, J., and Kindberg, T. (1994). *Distributed Systems Concepts and Design*.
- Cross, N. (1989). *Engineering Design Methods*.
- Daenzer, W.F. (ed.) (1976). *Systems Engineering*.
- Dandy, G.C. and Warner, R.F. (1989). *Planning and Design of Engineering Systems*.
- Defense Systems Management College. (1989). *Risk management: Concepts and guidance*.
- DeMarco, T. (1978). *Structured Analysis and System Specification*.
- de Neufville, R. and Stafford. J.H. (1971). *Systems Analysis for Engineers and Managers*.
- Dept. Of Army, (1969). *A Guide to Systems Engineering.*
- Dhillon, B.S. (1989). *Life Cycle Costing: Techniques, Models, and Applications*.
- Dhillon, B.S. (1982). *Reliability Engineering in Systems Design and Operation*.
- Dickinson, B.W. (1991). *Systems: Analysis, Design, and Computation*.
- Dix, A.J. (1991). *Formal Methods for Interactive Systems*.
- Dixon, J.R. (1966). *Design Engineering – Inventiveness, Analysis, and Decision-Making*.
- Dommasch, D.O. and Landeman, C.W. (1962) *Principles Underlying Systems Engineering*.
- Dorny, C.N. (1993). *Understanding Dynamic Systems: Approaches to Modeling, Analysis and Design*.
- Eisner, H. (1988). *Computer-Aided Systems Engineering*.
- Eisner, H. (1996). *Essentials of Project and Systems Engineering Management*.
- Fabrycky, W.J., Thuesen, G.J., and Verma, D. (1997). *Economic Decision Analysis*.
- Fabrycky, W.J. and Blanchard, B.S. (1991). *Life-Cycle Cost and Economic Analysis*.
- Faurre, P. and Depeyrot, M. (1977). *Elements of System Theory*.
- Flagle, C.D., Huggins, W.H. and Roy, R.H. (eds.) (1960). *Operations Research and Systems Engineering*.
- Flood, R.L. and Carson, E.R. (1988). *Dealing with Complexity, an Introduction to the Theory and Application of Systems Science*.
- Forrestor, J.W., (1968). *Principles of Systems.*
- F ortune, J. (1995). *Learning from Failure: The Systems Approach*.

- Ostwald, P.F. and Munoz, J. (1997). *Manufacturing Processes and Systems*.
- Padulo, L. and Arbib, M. (1974). *System Theory: A Unified State-Space Approach to Continuous and Discrete Systems*. Pages, A. and Gondran, M. (1986). *System Reliability: Evaluation and Prediction in Engineering*.
- Perrow, C. (1984). *Normal Accidents: Living with High-Risk Technologies*.
- Perry, W.E. (1988). *A Structured Approach to Systems Testing*.
- Phadke, M. (1989). *Quality Engineering Using Robust Design*.
- Prasad, B. (1996). *Concurrent Engineering Fundamentals: Integrated Product and Process Organization*.
- Proctor, R.W., Van Zandt, T., and Ehrenstein, A. (1993). *Human Factors in Simple and Complex Systems*.
- Pugh, S. (1990). *Total Design*.
- Purdy, D.C. (1991). *A Guide for Writing Successful Engineering Specifications*.
- Rasmussan, J. (1986). *Information Processing and Human-Machine Interaction*.
- Rasmussan, J. et al. (1994). *Cognitive Systems Engineering*.
- Rea, K.P. and Lientz, B.P. (1998). *Breakthrough Technology Project Management*.
- Rechtin, E. and Maier, M.W. (1996). *The Art of Systems Architecting*.
- Rechtin, E. (1991). *Systems Architecting: Creating and Building Complex Systems*.
- Reilly, N.B. (1993). *Successful Systems Engineering for Engineers and Managers*.
- Revelle, C.S., et al. (1997). *Civil and Environmental Systems Engineering*.
- Roland, H.E. and Moriarty, B. (1990). *System Safety Engineering and Management*.
- Rouse, W.B. (1991). *Design for Success: A Human-Centered Approach to Designing Successful Products and Systems*.
- Rouse, W.B. and Boff, K.R. (1987). *System Design: Behavioral Perspectives on Designers*, *Tools, and Organizations*
- Ryschkewitsch, M.G. (1992). The NASA Mission Design Process: An Engineering Guide to the Conceptual Design, Mission Analysis, and Definition Phases.
- Sage, A.P. (ed.) (1999). *Handbook of Systems Engineering*.
- Sage, A.P. (1995). *Systems Management for Information Technology and Software Engineering*.
- Sage, A.P. (1992). *Systems Engineering*.
- Sage, A.P. (1991). *Decision Support Systems Engineering*.
- Sage, A.P. (1977). Methodology for Large-scale Systems.
- Savas, E.S. (1965). *Computer Control of Industrial Processes*.
- Schuman, S. et al. (1994). *Systems, Models, and Measures: Formal Approaches to Computing and Information Technology*.
- Shearer, J.L. et al. (1997). *Dynamic Modeling and Control of Engineering Systems*.
- Shina, S.G. (ed.). (1994). *Successful Implementation of Concurrent Engineering Products and Processes*.
- Shinners, S.M. (1976). *A Guide to Systems Engineering and Management*.
- Shuey, R.L., Spooner, D.L., and Frieder, O. (1997). *The Architecture of Distributed Computer Systems*.
- Sommerville, I. (1997). *Requirements Engineering: A Good Practice Guide*.
- Stevens, R., et al. (1998). *Systems Engineering: Coping with Complexity*.
- Suh, N.P. (1990). *The Principles of Design*.
- Taguchi, G. (1989). *Introduction to Quality Engineering*.
- Taguchi, G., Elsayed, E.A., and Hsiang, T.C. (1989). *Quality Engineering in Production Systems.*
- Thayer, R.H. and Dorfman, M. (eds.) (1990) *System and Software Requirements Engineering*.
- Thome, B. (ed.) (1993). *Systems Engineering: Principles and Practice of Computer-Based Systems Engineering*.
- Truxal, J.G. (1972). *Introductory System Engineering*.
- Turbide, D.A. (1996). *Why Systems Fail: And How to Make Sure Yours Doesn’t*.
- Turner, W.C., Mize, J.J., Case, K.E., Nazemetz, J.W., Mize, J.H. (1992). *Introduction to Industrial and Systems Engineering*.
- Van Gigch, J.P. (1978). *Applied General Systems Theory*.
- Vickers, G. (1983). *Human Systems Are Different*.
- Von Bertalanffy, L. (1968). *Gerneral Systems Theory*.
- Wallace, I. (1995). *Developing Effective Safety Systems*.
- Wallace, R., Stockenberg, J. and Charrette, R. (1987). *A Unified Methodology for Developing Systems*.
- Warfield, J.N. (1990). *A Science of Generic Design: Managing Complexity through Systems Design. (Vol. 1 and 2)*.
- Warfield, J.N. (1976). *Societal Systems: Planning, Policy, and Complexity*.
- Warfield, J.N. and Hill, J.D. (1972). *A Unified Systems Engineering Concept*.
- Williams, T.J. (1961). *Systems Engineering in the Process Industries*.
- Wilson, B. (1984). *Systems: Concepts, Methodologies, and Applications*.
- Wright, R.T. (1990). *Manufacturing Systems*.
- Wymore, A.W. (1993). *Model-based Systems Engineering*.
- Wymore, A.W. (1977). *A Mathematical Theory of Systems Engineering: The Elements*.
- Wymore, A.W. (1976). *Systems Engineering Methodology for Interdisciplinary Teams*.

- Fowlkes, W.Y. and Creveling, C.M. (1995). *Engineering Methods for Robust Product Design*.
- Frankel, E.G. (1988). *Systems Reliability and Risk Analysis*.
- Gane, C. and Sarson, T. (1979). *Structured Systems Analysis: Tools and Techniques*.
- Gasparski, W. (1984). *Understanding Design: The Praxiological-Systemic Perspective*.
- Gheorghe, A. (1982). *Applied Systems Engineering*.
- Gibson, J.E. (1968). *Introduction to Engineering Design*.
- Glegg, G.L. (1981). *The Development of Design*.
- Glegg, G.L. (1969). *The Design of Design*.
- Goode, H.H. and Machol, R.E. (1957). *System Engineering – An Introduction to the Design of Large-Scale Systems*.
- Gosling, W. (1962). *The Design of Engineering Systems*.
- Grady, J.O. (1995). *System Engineering Planning and Enterprise Identity*.
- Grady, J.O. (1993). *System Requirements Analysis*.
- Grady, J.O. (1994). *Systems Integration*.
- Grady, J.O. (1997). *System Validation and Verification*.
- Hajek, V.J. (1984). *Management of Engineering Projects*.
- Hall, A. (1962). A *Methodology for Systems Engineering*.
- Hall, A. (1989). *Metasystems Methodology*.
- Hartley, J.R. (1990). *Concurrent Engineering*.
- Hatley, D.J. and Pirbhai, I.A. (1988). *Strategies for Real-Time System Specification*.
- Hazelrigg, G.A. (1996). *Systems Engineering: An Approach to Information-Based Design*.
- Hill, P.H. (1968). *The Science of Engineering Design*.
- Hitchins, D.K. (1992). *Putting Systems to Work*.
- Hollnagel, E., Mancini, G., and Woods, D. (1988). *Cognitive Engineering in Complex Dynamic Worlds*.
- Hubka, V. and Eder, W.E. (1988). *Theory of Technical Systems: A Total Concept Theory for Engineering Design*.
- Hunger, J.W. (1995). *Engineering the System Solution*.
- Jalote, P. (1994). Fault Tolerance in Distributed Systems.
- Jenkins, G.M. and Youle, P.V. (1971). *Systems Engineering: a Unifying Approach in Industry and Society*.
- Jerger, J.L. (1960). Systems Preliminary Design, Principles of Guided Missile Design.
- Johnson, R.A., Kast, F.E., and Rosenzweig, J.E. (1963) *The Theory and Management of Systems*.
- Karayanakis, N.M. (1995). *Advanced System Modeling and Simulation with Block Diagram Languauges*.
- Katzan, H. (1976). *Systems Design and Documentation*.
- Kavi, K.M. (ed.) (1992). *Real-Time Systems: Abstractions, Languages, and Design Methodologies*.
- Kerzner, H. (1995). *Program Management: A Systems Approach to Planning, Scheduling, and Controlling*.
- Klir, G. (1985). *Architecture of Systems Problem Solving*.
- Kusiak, A. (ed.) (1992). *Intelligent Design and Manufacturing*.
- Kusiak, A. (1992). *Concurrent Engineering: Automation, Tools, and Techniques*.
- Lacy, J.A. (1992). *Systems Engineering Management: Achieving Total Quality*.
- Laplante, P.A. (1997). *Real-Time Systems Design and Analysis: An Engineer’s Handbook*.
- Larson, W.J. and Wertz, J.R. (eds.) (1992). *Space Mission Analysis and Design*.
- Lee, A.M. (1970). *Systems Analysis Frameworks*.
- Levi, S. and Agrawala, A.K. (1994). *Fault Tolerant System Design*.
- Lin, Y. (1999). *General Systems Theory: A Mathematical Approach*.
- Lucas, H.C. (1974). *Towards Creative System Design*.
- MacAulay, L.A. (1996). *Requirements Engineering*.
- Machol, R.E. (1965). *Systems Engineering Handbook*.
- Martin, J.N. (1996). *Systems Engineering Guidebook: A Process for Developing Systems and Products*.
- McClamroch, N.H. (1980). *State Models of Dynamical Systems*.
- McLeod, R. Jr. (1994). *Systems Analysis and Design: An Organizational Approach*.
- McMenamin, S.M. and Palmer, J.F. (1984). *Essential Systems Analysis*.
- Meredith, D.D. and Wong, K.W. (1973). *Design and Planning of Engineering Systems*.
- Mesarovic, M.D. and Takahara, Y. *General Systems Theory: Mathematical Foundations*.
- Michaels, J.V. and Wood, W.P. (1989). *Design to Cost*.
- Miles, R.F. (ed.) (1971). *Systems Concepts*.
- Miller, J.G. (1978). *Living Systems*.
- Moody, J.A. et al. (eds) (1997). *Metrics and Case Studies for Evaluating Engineering Designs*.
- N
- adler, G. (1967). *Work Systems Design: The IDEALS Concept*.
- Norman, D.A. (1988). *The Design of Everyday Things*.
- Norman, D.A. and Draper, S.W. (1986). *User Centered System Design*.
- Oliver, D.W., Kelliher, T.P., and Keegan, J.G., Jr. (1997). *Engineering Complex Systems with Models and Objects*.
- Optner, S.L. (ed.) (1973). *Systems Analysis*.

## SE Education Resources World-wide

**U.S. Programs**
**32 M.S. and Ph.D. Programs**
**21 B.S. Programs**
**U.K. Programs**
**5 Graduate Programs**
**2 Undergrad Programs**
**Europe – Programs embedded in other disciplines**
**Australia – 2 Graduate Programs**
**Remaining World – 3 Graduate Programs           (Israel, South Korea, Viet Nam)**

## INCOSE Members from Universities

- 98 - University of Virginia
- 21 - Hampton University
- 14 - George Mason University
- 09 - University of Houston
- 08 - George Washington University
- 06 - Virginia Tech
- 05 - University of Maryland
- 05 - Texas A & M University
- 04 - University of Alabama
- 04 - University of South Florida
- 04 - Georgia Tech University
- 03 - Old Dominion University
- 02 - University of Texas
- 02 - Texas Tech University

- 55 - University of Arizona
- 11 - MIT
- 11 - US Naval Postgraduate School
- 09 - University of California
- 06 - University of Colorado
- 05 - University of Washington
- 05 - University of Missouri Rolla
- 04 - University of Southern California
- 04 - University of Idaho
- 04 - Stanford University
- 02 - United States Military Academy
- 02 - University of Kansas
- 02 - University of Michigan
- 17 - 5 international universities

- Based on November 2000 INCOSE Membership Roles

***Region V***

***Other Regions***

**INCOSE Members from Universities**

## Guide to the SE Body of Knowledge

**Goal and Objective**
**Structure for the Guide to the SE BoK**
**Implementation of Guide to SE BoK**

## Goal and Objective

**Short-term goal is to identify and “connect” existing sources of knowledge through a common framework using document automation techniques such as links, tiering or outlining, hot points, etc.**
**Intermediate-term is to discover or produce missing knowledge as indicated by the framework **
**Long-term objective is to win standards bodies recognition of the SEBOK and INCOSE as **_*the*_** producer of the SEBOK Guide.**
**Long-term goal is to create an auto-evolvable KM system for SEBOK.**

## Org. Structure for the Guide to the SE BoK

**I - Systems Engineering Fundamentals**
**	****Purpose, What is a system?, What is SE?, ...**
**II - SE Processes**
**	****Librarian description of process views (e.g., DoD, Comm’l A/C, Automotive, Int’l Aerospace)**
**III - Career Development of SE Practitioners**
**	****Education & Training suppliers, standards bodies, professional societies, OJT**
**IV - SE Process Capability/Assessment**
**	****CMM models**

## Implementation of Guide to SE BoK

- 					-----------------  Guide Section ----------------
- 					I		II			III				IV
- 1. Manage development of Guide
- 	[Rob Leibrandt, ?]
- 2. Produce sections of guide		P. Brown	B. Tufts	J. Ring			? CAWG?
- 					J. Clymer	J. Fisher	W. Wymore
- 3. Design / Select Usage Arch
- 	[Jack Ring, ?]
- 4. Develop references
- 5. Review / Test
- 	[Rob Leibrandt, ?]
- 	(Academic, Prof. Soc.,
- 	Stds. Bodies, Ed./Tng
- 	Suppliers)

## Research in the SE Center of Excellence

**Research Initiatives**
**Value of SE and Elements of SE **
**Human Productivity in SE Activities **
**SE Processes and Process Improvement **
**SE Methods **
**Design Techniques **
**Cost Issues **
**Risk and Trade Techniques **
**SE Automation **
**Formal Methods for SE**

**Decision-based Design via Life-Cycle Modeling and Simulation**** **
**Create a decision architecture for design decision making**
**Create a process for developing an interconnected set of variable-resolution simulation models**
**Create a modeling structure for the development system and operational system with their key modes of interaction so as **
**to examine effective and ineffective development system structures**
**to examine trade offs between testing and modeling **

##   International Council on Systems Engineering Chesapeake Chapter    

***Jerry Woodall*****,  Chesapeake Chapter President**
***Zyan Corporation***
***jwoodall@zyan.com***

## Chartered –  January 1994 with Constitution, Operating  Plan, etc., prior to Chartering

**Chartered** –  January 1994 with Constitution, Operating  Plan, etc., prior to Chartering
**Key Mission** - Providing a forum and communications channel to exchange systems engineering information, questions, concepts, etc. on a local level, complementing the international level organization

## Chesapeake Chapter Area Served

**BWP**

**50**

**270**

**State College**

**York**

**Fredrick**

**Rockville**

**DC**

**Baltimore**

**PA**

**MD**

**VA**

**Membership**

**Organizations**

**Annapolis**

**97 Members in 2001 Representing > 43 Organizations**

## Chesapeake Chapter Area Served

**BWP**

**50**

**270**

**State College**

**York**

**Fredrick**

**Rockville**

**DC**

**Baltimore**

**PA**

**MD**

**VA**

**Membership**

**Organizations**

**Annapolis**

- Dr. Eric W. Young	NASA/GSFC

## Chesapeake Chapter Accomplishments in 2000

**Technical Meetings** – Focus on Systems Engineering Tools, with presentations by seven tool vendors
**Mid-Atlantic Regional Conference** –  Participated with leader WMA in very successful technical conference in DC
**Hosted Object Oriented SE (OOSE) Seminar** – At JHU/APL based on earlier WMA sponsored event
**Contributed** – To review of 15288 International Standard
**Baltimore Engineering Society** – Joined as associate member organization: Interaction with non-aerospace, commercial organizations and members plus gaining access  to excellent facilities of the Society
**Initiated** – OOSE Interest Group formation

## Chesapeake Chapter Plans for 2001

**Technical Meetings** – Every other month (March) focusing on OOSE IG/WG progress + new topics
**Members Meetings** – On alternate months w/topics of general interest (at GSFC on 21 Feb)  + expansion outside aerospace
**Chartered OOSE Interest Group** – Chairman Jim Chism, IG is underway and meets at APL on designated Saturdays
**Second Review of 15288** – Committee being formed
**Update of Chesapeake Chapter (CSPK) Website** – To improve communications using available tools more effectively               http://www.incose.org/chesapek

##   International Council on Systems Engineering Washington Metropolitan Area Chapter    

***Bruce Shelton*****,  WMA Chapter President**
***ANSER Inc.***
***Washington, DC USA***
***sheltonb@anser.org***
** **

## Washington Metropolitan Area Chapter (WMA)

**Largest Chapter within INCOSE - 450+ members **
**Will Host the INCOSE 2003 International Symposium in Concert with the other Mid-Atlantic Chapters**
**Hosted INCOSE Mid-Atlantic Regional Conference 2000**
**200+ attendees, 10 Patrons, 19 Exhibitors**
**60 technical papers-3 tracks, 2 panels, 4 tutorials, 3 featured speakers**

**Notes:**
Good slide

## Chapter Activities

**Regular Monthly Meetings with a Special Guest Speaker**
**Second Tuesday of each Month**
**Tysons Corner Area**
**4-6 Tutorials per Year **
**Special Programs Addressing Unique Topics**
**INCOSE on the Mall - Brown Bag Lunch Meetings Downtown**

## WMA Programs

**Tutorials**
**Systems Engineering, Architecting, and Business Process Reengineering**
**Planning and Controlling Collaborative Teams**
**Object Oriented Systems Engineering Method**
**Humans and Systems: The Rest of the Story**
**Using Standard Processes in Systems Engineering**
**Special Programs**
**Systems Engineering Education Open House**
**Panel Discussion - Requirements Management Tools **
**Joint Program Management Institute (PMI)-WMA Meeting**

**Notes:**
Might want to place this slide in experience section after slide 14

##   International Council on Systems Engineering Southern Maryland Chapter    

***Karl Geist, ***** Southern Maryland Chapter President**
***US Naval Air Warfare Center Aircraft Division***
***Patuxent River, MD USA***
***geistkc@navair.navy.mil***
** **

##   International Council on Systems Engineering Summary    

***Susan Jones*****,  INCOSE Region V Director for Industry Affairs**
***The Aerospace Corporation***
***Chantilly, VA USA***
***susan.e.jones@aero.org***
** **

## INCOSE Membership Benefits 

**INCOSE Journal**
**INSIGHT **
**Symposia, Workshops, Conferences**
**Membership discounts**
**Early visibility into emerging standards **
**Knowledge of engineering from a global perspective**
**Means to tap expertise of industry experts**
**Networking with colleagues from around the world**
**...****..and more **

## Cost of Membership

**Dues are $80 per year**
**Dues year begins in June**
**Prorated over rest of year**
**Cost to join now is $40**
**Time and effort**
**Participate in local chapter events**
**Participate in Technical Committee Working Groups**

## Upcoming Local Events

- Tutorials and Seminars
- May 9-10,* Risk Management Seminar*, Hampton Roads, VA
- March 24,* C4ISR Architectures and Their Implementation Challenges*
- Chapter Meetings
- Feb 13, *Systems Engineering Old and New Perspectives, WMA Chapter*
- Feb 20*, Monthly meeting, Chesapeake Chapter*