WELCOME TO THE OFFICIAL 2006 INCOSE INTERNATIONAL SYMPOSIUM WEBSITE

H0A - Model-Based System Engineering - A Primer on What, Why, and How
Mr. James Long, Vitech Corporation

Biography:
James Long is the CEO of Vitech Corporation. He has been a performing system engineer and innovator since creating the first behavior diagrams (then called Function Sequence Diagrams) at TRW in 1967. He played a key technical and management role in the maturing and application of that system engineering process and technology at TRW and Vitech. Mr. Long worked on many system developments with an emphasis on complex MIL/AERO, satellite, and C3I systems with embedded software for over 45 years.. He is a member of INCOSE, active in NDIA’s Systems Engineering Division and its M&S Committee, and supporting the OMG’s efforts to expand UML 2.0 to systems engineering (SysML). Mr. Long has authored many technical papers and delivered tutorials in System Engineering techniques and applications to much of the Defense and Intelligence community. Mr. Long received the M.S. in Astronautics from Purdue and the B.S. in Mechanical Engineering from General Motors Institute.

Abstract:
This basic tutorial identifies the elements and benefits of a complete model-based system engineering process, and demonstrates its value for project success and tailorability using vignettes from a sample application.

H0B - Introduction to Patterns Through Writing Systems Engineering Patterns
Ms. Cecelia Haskins, NTNU and Mr. Amir Raveh, Omnisys

Biography:
Ms. Haskins and Mr. Raveh are both active in INCOSE and conducted the IS05 free introduction to patterns tutorial.

Abstract:
This course addresses the subject of writing patterns to communicate the practices of Systems Engineering. The need for this tutorial has been reinforced by high participation levels for the last 2 years. This introductory pattern writing course covers a brief history of the patterns movement, a survey of the variety of pattern forms, and an exercise in which the participants actually write a pattern and conduct an actual workshop of their pattern.

Anyone interested in writing patterns or understanding patterns better will want to attend.

H0C - A Global Vision of Systems Engineering
Mr. Jean-Philippe Lerat, SODIUS

Biography:
Jean-Philippe LERAT is the director and founder of SODIUS, a company that helps since 6 years companies to set up and improve their design processes. He trains Systems engineers of companies in several countries. He also represents France at ISO for several standardization efforts, especially for ISO15288 and ISO12207.

Abstract:
The goal of this tutorial is to outline the key concepts and vocabulary for Systems Engineers within the INCOSE community.

By experience, both words "systems" and "engineering" are used in many different ways, leading to many misinterpretations. At the end of this session, the audience will have a clear understanding of the nature of Systems Engineering and its relationships with other engineering disciplines, with other domains such as project management, or with some activities such as requirement management, validation & integration, etc.

Having this broad vision on Systems Engineering, the attendee is sure to draw the best of the INCOSE Symposium tutorials, papers and panels. No special skills or knowledge is required. The audience is composed of people willing to acquire a global vision of Systems Engineering with the key concepts. It is warmly recommended to INCOSE new members, and has a real interest for people coming from other disciplines to understand the reality of Systems Engineering.

H0D - Stand on the Standards
Mr. John Clark, Northrop Grumman

Biography:
John O. Clark is a Chief Engineer with Defense Mission Systems, a Division of Northrop Grumman Mission Systems. He is located at the Warfare Systems Engineering Department in Virginia Beach, VA. John currently supports the CVN 21 aircraft carrier program and the NAVSEA PEO Integrated Warfare System Technical Director. He has 40 years experience applying systems and software engineering to the acquisition, development, verification/testing, operations, and support/maintenance of military command, control, communications, computer, intelligence, radar, sonar, electronic warfare, identification, weapon, network, scientific, and information systems. John received a BS in Electrical Engineering from the Pennsylvania State University and an MS in Electrical Engineering from the State University of New York.

Abstract:
Systems engineering and software engineering continue to be two of the least well-understood engineering disciplines. Knowledge of the systems and software engineering standards significantly aids this understanding, including the relationship between systems and software engineering. This knowledge enhances any engineer's career.

The goals of this tutorial are to: 1) describe the systems engineering and software engineering standards heritage, processes, and products; 2) show the relationships between processes, products, and people based on these standards; and 3) encourage and challenge the participants to read, understand, select, tailor, and apply these standards, i.e., "stand on the standards," as opposed to relying solely on other sources such as instructions, procedures, guides, textbooks, education, training, and experience. Individuals may have an understanding of portions of systems and software engineering based on these other sources. Standards, developed by subject matter experts and approved by nationally recognized standards organizations, provide a more complete and common understanding.

Monday - Thursday
Available at an Additional Fee or with Passport Registration

Monday, 10 July 2006

F01 - Complete Picture to Model Complex Systems: What, When, How, and Why Model Systems (full day)
Mr. Jean-Philippe Lerat , SODIUS and Mr. Alain Faisandier, MAP système

Biographies:
Jean-Philippe Lerat is the director and founder of SODIUS, a company that helps since 6 years companies to set up and improve their design processes. He trains Systems engineers of companies in several countries. He also represents France at ISO for several standardization efforts, especially for ISO15288 and ISO12207.

Alain Faisandier is the director and founder of MAP système, a trainer and international senior expert in Systems Engineering. Thirty years experiences in systems design, engineering, integration, project management, requirements and design methods. He is co-chair of the INCOSE Standard Technical Committee, Ambassador of INCOSE, and co-chair of the Symposium Committee. He was head of the French Delegation for ISO 15288 (Systems life cycle processes), and now the editor of revision and harmonization of both ISO 15288 & ISO 12207.

Abstract:
Systems that are currently under design within enterprises are more and more complex. The economical context raises more constraints than ever. The cause of most of industrial problems, leading to project slipping and over costs can be found in a weak engineering.

Quite often, the design team’s members do not master the right intellectual tools that help to solve complex problems. Without a global/holistic vision of the system, hence called “a system vision”, and without the knowledge of the modelling techniques that can be used, the system design is not supported by the right models. This situation leaves the highest levels of system without a solid, consistent and cost-effective architecture.

Systems Engineering focuses on :
- a general “system-level” approach,
- a framework to structure design & development activities
- a set of processes, methods and modelling techniques,
- a cost-effective implementation inside the organizations.

This tutorial focuses on modelling techniques and aims to refresh this domain with an introduction to advanced techniques.

The tutorial provides keys to effectively model systems and to derive the most cost-effective organization to engineer a system. It draws a comprehensive view of modern Systems Engineering, using the latest achievements in terms of processes and modelling techniques.

The tutorial is built as a progression from basic modelling techniques to new concepts and techniques, ending with SAGACE, a state of the art method for system modelling.

The tutorial is composed of two parts :

The first part describes modelling techniques that are efficient to elicit use cases, needs and expectations. The tutorial presents the way they can be used to generate and analyse requirements, to design behavioural, logical architectures and physical architectures. The modelling techniques are aligned with the generic technical processes defined in modern international standards such as ISO-IEC 15288, ANSI-EIA 632, ANSI-IEEE 1220.

The second part goes deeper in system modelling, with an introduction to methods and design patterns useful to model systems.

The tutorial comes with world-class training material and is organized with an on-going example that is considered under the different point of views.

F02 - What You Will Need to Know About Chaos, Complexity, and Complex Adaptive Systems to do System Engineering Well Into the 21st Century (full day)
Ms. Sarah Sheard, Third Millenium Systems, LLC

Biography:
Sarah Sheard has been an INCOSE member since 1992, when she won Best Presentation for her paper, Capturing the Systems Engineering Process. In 2002 she was awarded the coveted “red sweater” with INCOSE’s Founder’s award. Sarah’s enthusiastic and engaging style draws standing-room only crowds at every symposium presentation. Her last tutorial was in 1997 when she presented, “Navigating the Compliance Frameworks Quagmire.”

Abstract:
This tutorial surveys the exciting new sciences of chaos and complexity theory, complex adaptive systems, networks, small world theory, and even advances in cognitive science, and shows how they relate to systems engineering. Exciting new discoveries are appearing in the news every day...just this week a research study was publicized that showed that during sleep the brain functions as smaller disconnected networks instead of one large coherent network. While quite mysterious according to traditional views of the brain, when looked at from these new views this becomes intuitively understandable and sensible, providing insight into the function of sleep that has puzzled doctors for ages.

Similarly, our approach to building, using, and maintaining ever more complex systems, particularly those systems that involve independently owned and operated, interconnected computers that continually adapt to the environment around them, can be viewed much more simply and intuitively if we understand how complex adaptive systems work together in networks similarly to networks of biological systems.

Building on the author’s very successful 2005 paper presentation on Practical Applications of Complexity Theory for Systems Engineers, this tutorial goes into more detail on chaos and complexity theory, including exercises such as a group exercise where students behave as birds in a flock according to simple rules, noting the changes in flock behavior as the simple rules change. The tutorial then examines various kinds of networks including random networks, small-world networks (including the concept of six degrees of familiarity). The tutorial then explains why the structure of all common networks requires growth and preferential connection to form, and exercises are performed that show the application of these different kinds of networks to the systems that systems engineers are building, modifying, and fitting systems into.

H01 - Working the Tough Issues of Systems of Systems Planning, Estimating, and Execution (half day)
Dr. Barry Boehm and Ms. Jo Ann Lane, USC Center for Software Engineering

Biography:
Barry Boehm, Ph.D., is the TRW professor of software engineering and director of the Center for Software Engineering at the University of Southern California. He was previously in software engineering, systems engineering, and management positions at General Dynamics, Rand Corp., TRW, the Defense Advanced Research Projects Agency, where he managed the acquisition of more than $1 billion worth of advanced information technology systems. Dr. Boehm originated the spiral model, the Constructive Cost Model, and the stakeholder win-win approach to software management and requirements negotiation.

Jo Ann Lane is currently a System Architecting PhD student at USC working in the area of System Architecting and Engineering and teaches software engineering at San Diego State University. Prior to joining the USC PhD program, she was a key technical member of Science Applications International Corporation’s (SAIC) Software and Systems Integration Group. She has over 28 years of software engineering, software-intensive system development, and program management experience.

Abstract:
Our experiences in helping to define, acquire, develop, and assess 21st century Software-Intensive Systems of Systems (SISOS) have taught us that traditional acquisition and development processes and estimation methods do not work well on such systems. This tutorial will summarize the characteristics of such systems, and indicate the major problem areas in using traditional processes (waterfall, V, simple spiral) and estimation methods (analogy, bottom-up, simple parametric) on them.

We will also present new processes and estimation methods that we and others have been developing, applying, and evolving to address 21st century SISOS. These include extensions to the risk-driven spiral model and COCOMO II suite of estimation models to cover broad (many systems), deep (many supplier levels), and long (many increments) acquisitions needing rapid fielding, high assurance, adaptability to high change traffic, and complex interactions with evolving COTS products, legacy systems, and external systems. Some practice case studies will also be provided.

H02 - Verifying Requirements (half day)
Mr. David Gelperin, ClearSpecs Enterprises

Biography:
David Gelperin is Chief Technology Officer of ClearSpecs Enterprises. He has more than 35 years experience in software engineering with an emphasis on software quality, verification, and testing and software process engineering. David cofounded Software Quality Engineering and catalyzed the launch of Better Software magazine. He chaired the working groups that developed the ANSI/IEEE standards on software testing – 829 on software test documentation and 1008 on software unit testing. David received a PhD in Computer Science from the Ohio State University. More information is available at www.clearspecs.com under the About tab.

Abstract:
Requirements information has long been recognized as a critical success factor. Effective requirements are second only to good people as a catalyst for product quality.

Unfortunately, recent polls show that:

40% of respondents consider their requirements to be unsatisfactory in satisfying the information needs of project managers, architects, and testers (requirements information is insufficient)
50% of those doing root cause analysis trace more than 50% of their software defects to requirements defects (many software defects start as requirements defects)

NASA’s Space Station Project found that over 50% of the requirements defects involved missing or incomplete requirements.

Requirements defects are important to remove, but difficult to detect early. However, they will be detected later at a much higher cost. There are many types of defective and missing requirements. Individual requirements may be obscure, ambiguous, inaccurate, incomplete, and noncompliant – in many ways. Suites can be obscure, inconsistent, imbalanced, insufficient, and unsatisfiable – also in many ways. Different defects need different detection techniques.

The Solution

Use formal (defect profile, i.e., types and likelihoods) or informal methods to identify the defect types to be reduced and then apply a corresponding set of focused detection techniques. This tutorial surveys over two-dozen powerful techniques for requirements verification.

Tuesday, 11 July 2006

F03 - Introduction to the System Modeling Language (SysML) (full day)
Mr. Sanford Friedenthal, Lockheed Martin and Mr. Alan Moore, Artisan Software

Biography:
Sanford Friedenthal has been a lead developer for advanced systems engineering processes and methods, including the Lockheed Martin Integrated Engineering Process, the Software Productivity Consortium's Integrated Systems and Software Engineering Process, and the UML-based Object-Oriented Systems Engineering Method (OOSEM). He is the liaison between INCOSE and OMG, Chair of the OMG Systems Engineering Domain Special Interest Group (SE DSIG), and Chair of the SysML Submission Team.

Mr. Friedenthal is a principal systems engineer at Lockheed Martin. His experience includes the full system life cycle from conceptual design through development and production on a broad range of systems including missile systems, electro-optical navigation and targeting systems, and information systems. Mr. Friedenthal has also been manager for systems engineering responsible for ensuring systems engineering processes are implemented on the programs, and enhancing overall systems engineering capability.

Alan Moore has 22 years of experience in the development of real-time and object-oriented methodologies, and their application in a variety of problem domains. He is responsible for the development and evolution of Real-time Perspective, ARTiSAN's process for real-time systems development. He is an active member of the Object Management Group and chaired both the finalisation and revision task forces for the UML Profile for Schedulability and Performance and Time, and is the co-chair of the OMG’s Real-time Analysis and Design Working Group. Most recently he has acted as the Specification Architect for the SysML Submission Team.

Abstract:
INCOSE and the Object Management Group (OMG) have been collaborating on an initiative to extend the Unified Modeling Language (UML) to provide a general-purpose systems modeling language to support specification, analysis, design, and verification of complex systems that includes hardware, software, data, personnel, and procedures. The visual modeling language is considered a key enabler for transitioning the practice of systems engineering from a document-centric to a model-centric approach.

The UML for Systems Engineering (SE) Request for Proposal (RFP) was issued by the OMG in March 2003 and contained the requirements for the modeling language. SysML was developed in response to this RFP, and provides an extension to the recently adopted UML V2.0 to provide a robust systems modeling capability. The adoption of SysML V1.0 is expected to begin in early 2006.

This tutorial provides an introduction on how SysML can address the needs of systems engineering. The tutorial is directed to systems engineers and others who may be involved in modeling systems, which may include software, hardware, and test engineers. The tutorial includes the background on the language, an overview of key modeling concepts, a summary of the different SysML diagram types, and an application of the language to a sample problem. It will also provide a summary of what can be expected of SysML modeling tools.

It is assumed the students have had some system modeling experience and a basic understanding of UML. The learning objectives for the participants are to understand the following:

Motivation and background for SysML

Key modeling concepts that provide the foundation for SysML

SysML diagram types and how to interpret them

SysML modeling artifacts generated during a typical systems engineering process

What should be expected of SysML tools

F04 - System Analysis, Design, and Development (full day)
Mr. Charles S. Wasson, John Wiley Author

Biography:
Charles S. Wasson, BSEE/MBA, is a member of INCOSE and the IEEE. He has held systems engineering, program management, and functional management positions in several Fortune 500 companies. Currently a member of Lockheed Martin Senior System Engineering Staff, his SE accomplishments include membership on the corporation’s System Engineering Subcouncil, chairmanship of the Education and Professional Development Working Group, and other corporate level assignments.

Charles is the author of the forthcoming textbook System Analysis, Design, and Development: Concepts, Principles, and Practices from John Wiley & Sons, Inc. due for release in the 4th quarter of 2005.

Abstract:
Poor contract and task performance is often traceable to decision makers who lack proper training in SE and attempt to shortcut best practices via a quantum leap from requirements to a point solution. The leap is rationalized on the premise of economizing and expediting schedules only to result in cost overruns, schedule risk from rework, or system failure with potential catastrophic consequences.

One of the key contributors to quantum leap approaches is the placement of inexperienced personnel in key programmatic decision-making roles without adequate SE education and training. When individuals or organizations pursue SE education and training, the instructional focus is often an understanding of the philosophical and theoretical aspects of System Engineering with a limited vocabulary of disciplinary buzzwords that many use but few understand. Fundamental concepts of how systems are structured, analyzed, operated, and supported that serve as the cornerstones for understanding system analysis, design, and development practices are often ignored. When individuals equipped with philosophical theory return to their programs and attempt to translate the theory into practice, organizations scoff and question SE effectiveness. Then, resort to traditional “business as usual” practices that continue to produce poor performance results.

Where SE education and training is inadequate and ineffective, program managers, technical directors, project engineers, engineers, and others must adapt to accumulating varying levels of system engineering knowledge, skills, and experience through osmosis and on the job training over 30+ years. Given this reality, the question is: how can we capture practitioner knowledge that enables instructors, individuals, and organizations to leverage that knowledge as a means of improving the uniformity and level of personal and organizational capabilities in SE.

This tutorial is based on a selection of key topics from the presenter’s forthcoming System Analysis, Design, and Development textbook from John Wiley and Sons, Inc. due for release in late 2005. The text represents a practitioner’s contribution as an SE disciplinary solution for satisfying the education and training needs discussed above.

The tutorial consists of topical series organized in two parts.

Part 1 System Analysis Concepts provides the analytical foundation in understanding how systems operate and interact with their operating environment.

Part 2 System Design and Development Practices builds on the foundation established in Part 1 and provides the “How To” practices for system design and development.

Using a problem-solving/solution development framework and associated methodologies, the tutorial presents fresh new approaches to concepts, principles, and practices that can be applied to small, medium, and large organizations in business sectors such as medical, transportation, construction, finance, education, government, aerospace and defense, and utilities. Equipped with this knowledge, program managers, designers, and developers are better prepared to make informed decisions for streamlining various practices to minimize the pitfalls of shortcut approaches that attempt quantum leaps leading to technical, cost, and schedule performance problems.

H03 - Introduction of the Systems Engineering Dual Vee Model (half day)
Mr. Hal Mooz and Dr. Kevin Forsberg, Center for Systems Management

Biography:
Hal Mooz is the Founder and CEO of Center for Systems Management, Co-author of Visualizing Project Management John Wiley, September 2005.

Co-author of Communicating Project Management – John Wiley 2002, Contributing author to The Wiley Handbook of Managing Projects - John Wiley 2005.

Mr. Mooz is a member of PMI and presenter of papers and tutorials at PMI, ProjectWorld, and international project management conferences. He is a Certified Project Management Professional (PMP) Member of International Council on System Engineering (INCOSE), Certified Systems Engineering Professional – CSEP, a Recipient of the CIA Seal Medallion for contributions in project management and Recipient of the INCOSE 2001 Pioneer Award for furthering the cause of System Engineering.

Abstract:
In 1990 Dr. Kevin Forsberg and I introduced the Vee model that has enjoyed wide spread multinational adoption and a core reason for the success of Visualizing Project Management having sold almost 40,000 copies. Since then we have continued to evolve the Vee into the Vee+ and the Vee++ models. We have now expanded the model to simultaneously address both solution development and architecture complexity management. This tutorial will cover all development models leading up to the Vee, Vee+, Vee++ and the Dual Vee Model.

Objectives:

Students will learn:

The power of models

The role of solution development models

The heritage and objective of the Waterfall

The evolution of the Spiral and win-win Spiral

The motivation and birth of the Vee

Solution development and architecture management issues

Vee model versions and enhancements

The power of the Dual Vee

Implementation strategies and tactics

How to apply to unified, incremental, linear and evolutionary development.

Applicability to Agile Development

H04 - Architecting and Engineering Systems, Processes, and Organizations Using the Design Structure Matrix (DSM) (half day)
Mr. Tyson R. Browning, MJ Neeley School of Business, Texas Christian University

Biography:
Dr. Tyson R. Browning is Assistant Professor of Enterprise Operations at the M.J. Neeley School of Business at Texas Christian University, Fort Worth, Texas. He teaches Operations Management, Project Management, and Program Management in the MBA program and conducts research on engineering management, process modeling, product development, enterprise engineering, and systems engineering.

Prior to joining TCU, he was a Senior Project Manager (S6) in Integrated Company Operations at Lockheed Martin Aeronautics Company, where he was the technical lead and chief integrator of the enterprise process architecture and author of company policies and processes driving the transition to a process-based company. Before joining Lockheed Martin, he worked with the Lean Aerospace Initiative at the Massachusetts Institute of Technology, conducting on-site research at Boeing, Texas Instruments (now Raytheon), McDonnell Douglas (now Boeing), Lockheed Martin, General Electric Aircraft Engines, Sundstrand (now Hamilton Sundstrand), and Daimler Chrysler. He has also worked for Honeywell Space Systems in Clearwater, Florida (where he grew up) and Los Alamos National Laboratory in New Mexico.

Tyson received a B.S. in Engineering Physics from Abilene Christian University and two Master’s degrees and a Ph.D. from MIT. He has authored or co-authored over 25 papers on engineering management, risk management, the design structure matrix, organization design, process modeling, and value measurement—publishing in IEEE Transactions in Engineering Management, Systems Engineering, Project Management Journal, Technology Management Handbook, and others—including nine papers at past INCOSE symposia. A paper he co-authored for the 2005 symposium in Rochester received the best paper award. He is a member of INCOSE (since 1995) and the Institute for Operations Research and the Management Sciences (INFORMS) and is on the Editorial Board for the journal Systems Engineering.

Abstract:
Products, processes, and organizations are complex systems. They are challenging to plan and manage. Fortunately, an advantageous method is coming into mainstream practice for representing and analyzing complex system architectures. This method, the design structure matrix (DSM), is helping practitioners plan and manage product architectures, organizational structures, and process flows.

Akin to a traditional N2 diagram and the System2 matrix (SV-3) in the DoD Architecture Framework, the DSM is a square matrix that documents dependencies between system components. These components can be product parts, teams, processes, activities, or other elements. By doing some simple analysis, one can prescribe a modular system architecture or organization structure. Adding a time-basis enables one to prescribe a faster, lower-risk process. Because the DSM highlights process feedbacks, it helps identify iteration and rework loops—key drivers of cost and schedule risk. The DSM can also show how delays in external inputs, such as requirements and equipment, trace directly to increased cost, schedule, and risk.

The DSM is concise and visually appealing and is in use in a number of industries, companies, and agencies. (It is also known as the dependency structure matrix and the dependency source matrix.) People have found the tool extremely useful for fostering architectural and organizational innovation, and for enabling the situation awareness and empowerment of people executing complex processes.

This tutorial introduces the DSM and four distinctive applications useful to product developers, project planners, project managers, systems engineers, and organizational designers. Real-life examples are presented. Participants will come away with a clear understanding of why dependencies and interfaces are important and how to manage them. Participants will leave with a course notebook of descriptive materials and access to free tools that can be applied immediately to projects.

Wednesday, 12 July 2006

F05 - Architecture Frameworks and Modeling (full day)
Mr. James N. Martin, The Aerospace Corporation

Biography:
James N. Martin is an internationally known writer and lecturer on systems engineering. He wrote one of the most widely read books on systems engineering, “Systems Engineering Guidebook,” published by CRC Press. His experience includes over twenty years in systems development of telecommunications products and services (most of this with Bell Labs) as program manager, systems engineering manager, system architect, requirements manager, and lead systems engineer. His experience with technology includes mobile wireless, underwater fiber optic, satellite broadband wireless, reconnaissance sensors and distribution networks, and airborne network hubs.

At the Aerospace Corporation, Mr. Martin is a system architect for communications networks and space systems. He also teaches at The Aerospace Institute and at seminars around the world. He led the development of ANSI/EIA 632, the US national standard that defines the processes for engineering a system. Mr. Martin graduated with an MS from Stanford and a BS from Texas A&M. He is a Fellow member of INCOSE.

Abstract:
Architecture provides the unifying structure (or roadmap) for exploration of the problem space and for characterization of the solution space such that better decisions can be made. Architecture is an arrangement of feature and function that maximizes some objective. This tutorial will describe fundamental concepts used in architecture modeling that will assist you in developing and using your own architectures.

The use of an architecture framework leads to a more model-driven systems approach and allows you to “discover” the essential attributes of the problem space that must be addressed by the system solution. Architecture models are where these essential attributes are defined and evaluated. This approach to architecting will be described within the context of the DOD Architecture Framework (DODAF) and other frameworks like the Federal Enterprise Architecture Framework (FEAF) and the Zachman Framework.

There is usually a hierarchy of architectures that helps focus the architecture team on the right level of abstraction. One common hierarchy starts at the top with National level architectures and works down to the levels of Department/Federal, Service/Agency, Mission Area/Cross-Mission Area, Program/Node, and so on. The architecture you develop will have impacts above and below you in the hierarchy. The notion of levels in a hierarchy will be discussed along with how to use this to structure your modeling and simulation activity.

An example of a mission architecture will be described to illustrate some of these key concepts. The DOD Architecture Framework will be used in this illustration to demonstrate the essential features of architecture frameworks and to show how it can help to “frame” the problem to increase your understanding of the system’s context. This illustration will also serve to help you understand how technical and non-technical modeling plays a part in architecture development.

F06 - An Effective Specification Development Algorithm (full day)
Mr. Jeffrey O. Grady, JOG System Engineering, Inc

Biography:
Jeffrey O. Grady has been the president of JOG System Engineering, Inc a system engineering consulting and training company since 1993. Prior to that he had 30 years of industry experience in aerospace companies (Librascope, Teledyne Ryan Aeronautical, and General Dynamics Convair and Space Systems) as a system engineer, system development manager, field engineer, customer training instructor, and project engineer. Jeff has authored five recently published books in the system engineering field with a sixth published in December 2005 and holds a Master of Science in System Management from USC. He teaches system engineering courses around the country on-site at companies as well as at University of California, San Diego and other universities. Jeff is an International Council On Systems Engineering (INCOSE) Fellow and Founder.

Abstract:
The data structures upon which current specification work is based were crafted for typewriter technology and badly organized relative to the ways engineers should derive content using structured analysis models. This tutorial combines instruction in the most up to date modeling techniques, the development of a sound set of DIDs coordinated with the methods through which the analysts gain insight into the appropriate content, and modern databases for the capture of the results of the analysis work.

The application of the techniques covered in this tutorial by a system development organization will result in the timely and affordable capture of all of the essential characteristics in the specifications it publishes.

The tutorial presents the best we can do at the plateau we currently reside upon. Eventually, we will move to a new plateau where all requirements work is accomplished in a merged version of UML/SysML in a model driven development world. By mastering the current best practices plateau, which few organizations have done, one will be prepared to advance to the next plateau, which has not yet been defined.

H05 - Competitive Systems Engineering: How to do System Engineering in Hot Competition. Detailed Pragmatic and Unconventional Techniques (half day)
Mr. Tom Gilb, Result Planning Limited

Biography:
Tom Gilb is an international consultant, teacher and author. His 9th book is ‘Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage’ (January 2005 Publication, Elsevier)’ which is a definition of the planning language ‘Planguage’ and includes Evolutionary Project Management as a Major subject..’.

He works with major multinationals such as HP, IBM, Nokia, Ericsson, Motorola, US DOD, UK MOD, Symbian, Philips, BAe, Intel, Citigroup, Boeing and many others. See www.Gilb.com for much more detail, and free publications on Competitive Engineering

Abstract:
Some systems engineering is done in continuous international competition. For example telecommunications products. For example military systems. The problem is not merely to get it done well on time, but to visibly beat the competition in quality and price while also beating them on time to market. There are specific engineering methods and processes that emphasize the ability to ‘beat the enemy’. This tutorial will highlight the specific methods we can offer to aid the competitive engineering process. The methods are innovative and the key idea is the ability to quantify all critical qualitative aspects of a system, not just the conventional ones.

H06 - Performance-Based Earned Value (half day)
Mr. Paul Solomon, Northrop Grumman Corporation

Biography:
Paul Solomon is a consultant on project management and Earned Value Management Systems (EVMS) and manages EVMS in the Northrop Grumman Corporation, Integrated Systems Western Region. He has supported the B-2 Stealth Bomber, Global Hawk, and F-35 Joint Strike Fighter programs. He was on the team that wrote the EVMS standard and received the DoD David Packard Excellence in Acquisition Award. He was a Visiting Scientist at the Software Engineering Institute where he authored “Using CMMI to Improve Earned Value Management.” His book, “Performance-Based Earned Value®,” co-authored with Ralph Young, will be published in 2006 by the IEEE Computer Society / Wiley & Sons. Paul holds BA and MBA degrees from Dartmouth College and is a certified Project Management Professional. He may be contacted at SolomonPBEV@msn.com

Abstract:
Whether you are a supplier or a customer, this tutorial will show how to use Performance-Based Earned Value (PBEV) to integrate project technical, schedule, and cost performance.

PBEV is a set of principles and guidelines that specify effective measures of technical performance as the base measures of EV. It is based on standards and models for systems engineering, software engineering, and project management. PBEV complies with DoD acquisition guidance including:

Defense Acquisition Guidebook

Systems Engineering Plan Preparation Guide

Work Breakdown Structure Handbook

Integrated Master Plan and Integrated Master Schedule (IMS) Preparation and Use Guide

PBEV is based on:

Progress towards completing the set of enabling work products such as drawings or software modules and

Progress towards meeting the product requirements.

PBEV also integrates risk management into the Performance Measurement Baseline and the Estimate at Completion (EAC).

You will learn to incorporate the product requirements or technical baseline into the project plans, schedules, and work packages. Guidance and practical examples will show how to define the right entrance and exit criteria in the IMS. Your actions will ensure that performance reports include actual vs. planned achievement of:

Allocated product requirements

Technical performance measures (TPM)

Technical maturity success criteria

Trade study objectives

The following topics will be discussed and illustrated with best practices, examples and templates:

Manage the technical baseline using earned value

Use the Integrated Baseline Review to agree on criteria for event-driven technical reviews.

Use the Requirements Traceability Matrix to develop the plan.

Verify that the correct base measures for earned value have been specified.

Monitor project performance with meaningful variance analysis.

Perform independent assessments of product maturity, schedule progress, and the EAC.

Thursday, 13 July 2006

H07 - CSEP Application Preparation Tutorial (half day)
Mr. Robert B. Wheeler, The Center for Systems Management

Biography:
Robert B. Wheeler has thirty years increasing responsibility and successful achievement in management of business units engaged in complex projects involving high technology. A unique blend of business management and information technology expertise gained through experience with IBM, World-wide consulting to large international companies, and support to small businesses.

Mr. Wheeler has an MBA – Executive MBA Program, University of RI, an MS in Physics – Syracuse University and a BSEE – Drexel University. His career highlight is providing business and project management and training services to Fortune 100 companies world wide. He created the first INCOSE Certified Systems Engineering Professional preparation program and provided project management/systems engineering training and consulting services to international Fortune 100 companies in Asia, Europe and North America.

Mr. Wheeler has led a small re-seller to establish successful performance reputation on systems integration contracts with US Navy, US Air Force, Internal Revenue Service and NOAA. He has directed key aspects of strategic business task force to define, implement and measure IBM World wide market-driven business processes; managed all aspects of $250M command and control systems integration programs, including complex software development, systems integration and extensive subcontract management. He has led successful defense conversion of small (120 employee) business unit.

As Systems Engineering Manager, Mr. Wheeler is responsible for development of complex systems for US Navy and US Air Force and for developing and implementing new Systems Engineering technology for use in government systems sector and later adapted to commercial sectors.

Abstract:
Becoming a Certified Systems Engineering Professional (CSEP) involves more than simply taking the CSEP certification examination. In fact, CSEP candidates must pass a rigorous experience review before they are allowed to sit for the certification examination. This review is conducted by a team of veteran INCOSE members and is based on the information that candidates put on their CSEP application forms.

Therefore, it is critical that CSEP candidates provide complete detailed experience information on their application forms. It is also critical that candidates’ experience meets the requirements established by the INCOSE Certification Committee and that the experience be verifiable by recognized advocates who are knowledgeable about Systems Engineering.

This ½ day tutorial will provide the hands-on experience that participants need to prepare complete detailed application forms that will stand up to the rigorous INCOSE review.

Guided by an experienced instructor, Participants will

Conduct an individualized analysis of their Systems Engineering experience,
Document their experience in the areas required for CSEP Certification
Receive guidance on how to effectively translate that experience onto the INCOSE Certification Application and
Learn how to select and prepare references who can verify their experience and serve as professional advocates.

Upon completion of the tutorial participants will be able to

Prepare an application for Engineering Professional Certification that will present their experiences in a way that aligns with the criteria used for INCOSE review
Select and prepare references who can validate experience and serve as advocates for the certification candidates

H08 - Introduction to Architecture Frameworks (half day)
Mr. Rolf Siegers, Raytheon Company

Biography:
Rolf Siegers is an Engineering Fellow and Chief Architect of the Garland Engineering Center in Raytheon’s Intelligence and Information Systems. Rolf joined Raytheon in 1984. He currently leads the Raytheon Enterprise Architecture Process (REAP) Initiative, Raytheon’s standardized, company-wide architecture process. Rolf’s program experience includes leading several multi-discipline software architecture teams for large-scale, software-intensive systems since 1997. He is a certified TOGAF-8 architect (The Open Group), ATAM? Evaluator (Software Engineering Institute), and Software Architecture Professional (Software Engineering Institute). He has previously presented at conferences by The Open Group, US Department of Defense, Integrated Defense Architectures, and INCOSE. Rolf holds bachelor degrees in Computer Science and Mathematics from Huntingdon College and is a member of IEEE and INCOSE.

Abstract:
CAF, DoDAF, E2AF, FEAF, IAF, MODAF, TEAF, TOGAF, Zachman – an alphabet soup of architecture frameworks has emerged over time to support our architecting efforts. Understanding the core focus of these frameworks provides enterprise and system architects the ability to properly leverage these resources and to unify them when appropriate. Each framework typically addresses a key aspect such as architecture methodology, product description, reference models, categorization, or classification, but no single framework fully covers all the concerns of the architect.

This tutorial will overview some of the major architecture frameworks currently in use including The Open Group Architecture Framework (TOGAF), Zachman Framework for Enterprise Architecture, US Department of Defense Architecture Framework (DoDAF), UK Ministry of Defence Architecture Framework (MODAF), and the US Federal Enterprise Architecture Framework (FEAF). There will be a focus on each framework’s background, fundamental concepts, usage, benefits, and limitations.

Downloadable Files

INCOSE 2006 Tutorial Abstracts



Contact Webmaster			2006 INCOSE International Symposium Hosted by the INCOSE Central Florida, Orlando, and Space Coast Chapters
Generated Tuesday, December 02, 2008 at 10:12:56am