|
Symposium
Tutorials
Contact:
Dr. Eric Chukwu,
chair or John Leonard,
co-chair
The Symposium theme "Engineering Tomorrow's World
Today!" calls on delegates to address a more complex
and technologically sophisticated world, where Systems
Engineering and higher-level systems thinking are increasingly
needed to handle the challenges of new technologies.
Please note that Tutorial proposals and presentations
at the Symposium are presented in English, the official
language of the INCOSE 2003 Symposium.
Frequently
Asked Questions
Sunday
Optional Professional Tutorial:
Tutorial #FOO: Applied SE 101: Essentials
of Productive SE Processes
Monday
Full-Day Tutorials:
Tutorial # F01: Object Oriented Systems
Engineering Method (OOSEM)
Tutorial # F02: Process Modeling in a
Systems Engineering Context
Tutorial # F03: The Past, Present and
Future of Structured Analysis
Tutorial # F04: Measurable Systems Engineering
Tutorial # F05: Requirement-Based Product
Line Engineering
Tutorial # F06: Maximizing the Systems
Aspects of Systems Engineering
Tutorial # F07: Applied Statistical Decision
Theory in Systems Engineering
Tutorial # F08: Requirements and Modeling:
A Structured Approach
Monday
Half-Day Optional Professional Tutorials - Morning:
Tutorial # H01: A Systems Engineering
Cost Model for Information Processing Systems &
Subsystems
Tutorial # H02: Eisner's Architecting
Method (EAM)
Monday
Half-Day Optional Professional Tutorials-Afternoon:
Tutorial # H03: Reconciling Requirements,
Use Cases and Object-Oriented Modeling for Systems Engineering
Tutorial # H04: Systems and Software
Engineering Processes and Products from a Standards
Perspective: Stand on Standards
Alternates:
1. Fault Analysis for Systems Engineers
2. Writing Requirements
Tutorial # F00: Applied Systems
Engineering 101: Essentials of Productive SE Processes
Technical Abstract:
The application of system engineering continues to evolve.
Initially applied to stand-alone, single purpose DoD
/ Aerospace systems, systems engineering focused on
large, complex, expensive, and long-lived systems. Today,
we develop military and commercial systems across a
wide range of size, cost, and complexity. Though many
principles remain constant, the system engineering processes
of yesterday are no longer universally applicable.
Applied SE is a flexible system engineering process
suitable for system development tasks across the complexity
spectrum. Based upon the tenets of model-driven design,
Applied SE focuses on eliciting the proper requirements,
understanding the problem and solution domain, solid
communication amongst the design team and the stakeholders,
and satisfying the system need. Rather than emphasizing
process and documentation standards, Applied SE is centered
upon the true deliverable - the system and its design.
Applied SE applies a layered modeling approach in order
to:
· provide traceability to mission needs;
· identify and resolve risks and issues on a
progressive, just-in-time basis;
· avoid critical knowledge gaps without expending
unnecessary effort and expense;
· maximize communication and minimize miscommunication;
· maintain an effective balance across the requirement,
behavior, and physical domains;
· self-document the design, handling specifications
and documentation as a natural by-product of the system
design;
· provide complete, consistent system deliverables
at any point in time with increasing level of detail
as development progresses; and
· maintain flexibility, efficiency, and effectiveness.
Systems ranging from the simple to the complex, whether
those containing embedded software and COTS elements
or those comprising systems-of-systems, can be developed
more effectively and efficiently using these modern
development methodologies. Proven across a diverse set
of applications ranging from weapon systems to process-intensive
information systems, Applied SE is today's solution
for supporting, capturing, analyzing, and documenting
complete system engineering activities with complexities
varying from days to months.
Brief Biographies:
Mr. James Long is the CEO of Vitech Corporation
- the developer of the system engineering support tool
COREâ. 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.
During 16 years at TRW, Mr. Long worked on many system
developments with an emphasis on complex MIL/AERO and
satellite systems with embedded software and C3I. In
the previous 13 years at General Motors he worked on
advanced flight and propulsion systems and derived mission
requirements for high- and low-thrust interplanetary
missions.
He is a member of INCOSE and served as vice-president
and then president of the Washington Metropolitan Area
Chapter, the largest chapter of INCOSE.
Mr. Long has been selected as an Eminent Engineer by
Tau Beta Pi, the honorary engineering scholastic society.
The eminent engineering designation is recognition for
career achievement in engineering.
Mr. Long received the M.S. in Astronautics from Purdue
and the B.S. in Mechanical Engineering from General
Motors Institute. He has authored many technical papers
in System Engineering techniques and applications and
has consulted and taught System Engineering classes
to numerous organizations including AT&T, FedEx,
USAA, CSC, GE, Lockheed Martin, SAIC, Northrop Grumman,
Textron, Boeing, US Dept of Energy, and US Dept of Defense.
Dinesh Verma received the Ph.D. and the M.S.
in Industrial and Systems Engineering from Virginia
Tech. He is now the Associate Dean for Outreach and
a Professor in Systems Engineering at Stevens Institute
of Technology. Prior to joining Stevens Institute, Dr.
Verma served as a Technical Director with a focus on
Systems and Supportability Strategy at Lockheed Martin
Undersea Systems, in Manassas, Virginia, where his duties
included development of adapted systems and supportability
engineering processes, methods and tools for complex
system development.
Prior to joining Lockheed Martin, Verma worked as a
Research Scientist at Virginia Tech and managed the
University's Systems Engineering Design Laboratory.
While at Virginia Tech and afterwards, Verma has served
in a consulting capacity with numerous companies to
include Eastman Kodak, United Defense, PSI, VOLVO Car
Corporation (Sweden), NOKIA (Finland), RAMSE (Finland),
Johnson Controls, Ericsson-SAAB Avionics (Sweden), and
Motorola. His professional and research activities emphasize
systems engineering and design with an emphasis on conceptual
design evaluation, preliminary system design and system
architecture, design decision-making, life cycle costing,
and supportability engineering. In addition to his publications,
Verma has patents pending in the areas of system life-cycle
costing and fuzzy logic techniques for evaluating conceptual
system designs.
Dr. Verma has authored over 75 technical papers, book
reviews, technical monographs, and co-authored two textbooks:
Maintainability: A Key to Effective Serviceability and
Maintenance Management (Wiley, 1995), and Economic Decision
Analysis (Prentice Hall, 1998). He was awarded the Author
of the Year Award by Lockheed Martin Undersea Systems
in 1999, the Outstanding Paper Presentation Award at
the INCOSE Symposium (Boston) in 1996, the President's
Award of Merit by the Society of Logistics Engineers
in 1993 and 1999, and received the Young Logistician
of the Year Award in 1992.
Dr. Verma serves on the Board of Directors for the
RAMS Symposia and on the Board of Governors of the Logistics
Education Foundation. He is an active member in INCOSE
and SOLE, and was elected to Sigma Xi, the honorary
research society of America.
Tutorial # F 01: Tutorial: Object
Oriented Systems Engineering Method (OOSEM)- T11
Technical Abstract:
This tutorial will introduce an Object Oriented Systems
Engineering Method (OOSEM), which integrates a top down
systems approach with object oriented concepts and modeling
techniques. . Based upon the widely known Unified Modeling
Language (UML), this method brings object oriented modeling
to the systems engineering community, and adapts it
for modeling systems-level requirements and design.
OOSEM leverages some of the advantages of OO to help
architect more flexible, extensible, and upgradeable
systems with new evolving technology. Another major
goal of OOSEM is to ease integration with object oriented
methods for software engineering. Models developed by
this method simultaneously serve the needs of systems
engineers, and as the front end of an integrated method
for systems and software engineering.
The System Engineering community typically uses top
down structured analysis techniques to capture and analyze
the system to be developed. Software methods have evolved
over the year from structured techniques to an object
oriented approach for analysis and design. Systems and
software engineers struggle to communicate with these
different techniques. The OOSEM approach integrates
a top down systems approach with OO concepts and UML
to help bridge this gap.
This tutorial will introduce the student to the OOSEM
method, which has evolved from a combination of research
and early application to projects. This work is summarized
in various INCOSE papers. (Lykins, Friedenthal, Meilich
2000, Meilich and Rickels 1999, Steiner, Friendenthal,
Oesterheld 2001), and was first presented at the INCOSE
2000 Symposium. The tutorial describes how the system
level activities are performed and artifacts are developed
using UML to address systems-level concerns. Important
concepts and issues are illustrated by simple examples
presented by the instructors. The tutorial will conclude
with a discussion of future development in this area.
Topics covered include:
· An overview of systems engineering to provide
the context for OOSEM
· An overview of UML and object oriented concepts
and their relevance to OOSEM
· An in-depth overview of OOSEM activities and
work products
· An overview of tool support requirements and
identification of some of the available tools.
· Future work including updates to the UML standard
being proposed by the OMG
Brief Biographies:
Sanford Friedenthal: Mr. Friedenthal's 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 been a manager for systems engineering
at Lockheed Martin responsible for ensuring systems
engineering processes are implemented on the programs,
and enhancing overall systems engineering capability.
He has been a lead developer of 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 Object-Oriented Systems Engineering
Method (OOSEM). Mr. Friedenthal is the liaison between
INCOSE and OMG, and chairs the OMG Systems Engineering
Domain Special Interest Group (SE DSIG) to support development
of a UML profile for System Engineering.
Abraham Meilich, Ph.D., C.C.P.: Dr. Abe Meilich
is employed as a Certified Systems Architect at Lockheed
Martin Mission Systems presently the Manager, Enterprise
Engineering on the U.S. Customs Modernization Program.
He has a BS in Engineering from UCLA, an MSME from Stanford,
an MS in Systems Management from USC, and a Ph.D. in
Systems Management from Walden University, and a Certified
Computing Professional (CCP) Certification. His career
spans 34 years in the mechanical, electrical, computer,
aerospace and information systems engineering domains.
He is an adjunct professor at the University of Maryland
Graduate Program in Technology Management, Systems Acquisition,
and Information Systems and in the Walden University
School of Applied Management and Decision Sciences,
Information Systems Division. He is past Secretary and
Newsletter Editor, and Director of the Washington Metropolitan
Area Chapter of INCOSE. His current focus in on the
application of systems engineering principles and best
practices in systems architecture development to the
design of command and control systems for the U.S. Army
and modernization of government Enterprise systems.
Howard Lykins: Mr. Lykins has more than 25 years
of experience with systems and software development,
including development of engineering processes and methods,
the specification, design, and implementation of software-intensive
products, application of formal models, training, consulting
and process improvement. He has taught college seniors,
graduate students, and professionals since 1984. In
addition to OOSEM, Mr. Lykins has contributed to the
development of functional and declarative modeling techniques
and the methods for applying them in industry. Mr. Lykins
also has experience in the development and administration
of management information systems. He is a member of
the OOSEM working group and the Model Driven System
Design working group, where he served as co-chair for
four years.
Tutorial # F 02: Process Modeling
in a Systems Engineering Context
Technical Abstract:
By focusing on the processes that create customer value,
enterprises are able to provide products and services
faster, better, and cheaper. Process understanding stems
from effective process modeling. (By "process model"
we are not referring to capability maturity models.)
It is especially difficult to model a process for systems
design and engineering. Different techniques are necessary
than those potentially sufficient for business or manufacturing
processes.
New engineering standards advocate integrated processes
for the engineering of complex systems. Standards also
specify the inclusion of new activities that may have
not been part of an organization's traditional processes.
In many cases, companies may not have formally described
their existing processes. Even when processes have been
described explicitly, often they are not integrated.
Furthermore, many attempt to apply simplistic process
modeling techniques to complex processes for the engineering
of systems. The definition and practice of world-class
systems engineering requires well-understood and continuously
improving approaches and techniques.
This tutorial focuses on the techniques for describing
processes in a systems engineering context-i.e., a context
where the processes are creative, complex, non-linear,
strongly interrelated, and based on information flow.
A variety of methods and tools will be presented, including:
fundamental building blocks of process models, collecting
information for process models, building and integrating
process models, model representation, model analysis,
the Design Structure Matrix (DSM), value streams, etc.
The presentation will include application of process
models to a variety of uses, including: program planning,
program execution, continuous improvement, knowledge
retention and learning, process visualization, training,
tool management, metrics collection, and compliance
with standards. The costs and benefits of process models
will also be discussed. Through the presentation of
a variety of methods, tools, and applications, we will
transfer experience and insight from three presenters
from different industries to provide direct benefit
to attendees.
Brief Biographies:
Dr. Tyson R. Browning holds the position of Senior
Project Manager, Architecture & Design in Integrated
Company Operations at Lockheed Martin Aeronautics Company
in Fort Worth, Texas, USA. He is the technical lead
and chief integrator for a number of teams in developing
the enterprise process architecture for the Aeronautics
Company. He is also the lead author of company policies
and processes driving the transition to a process-based
company. Browning previously worked with the Product
Development Focus Team of the Lean Aerospace Initiative
at MIT, conducting research at Lockheed Martin, General
Electric, Boeing, Raytheon, Sundstrand, and Daimler
Chrysler. Browning earned a Ph.D. in Technology Management
and Policy (management and systems engineering) and
two Master's degrees from MIT. Several of his papers
on organizational integration, risk management, the
design structure matrix, and process modeling have been
published and are forthcoming. He has been a member
of INCOSE since 1995 and has presented papers and/or
tutorials at each of the last seven international symposia.
Dr. Ernst Fricke recently started working for BMW Group
as In-House Consultant. Previously, he was the Head
of Systems Engineering & Support at CargoLifter
Development GmbH, where one of his areas of responsibility
was initiatives to improve the product development and
systems engineering process. Before that, Ernst was
wissenschaftlicher Mitarbeiter in the Division of Astronautics
at the Technical University of Munich, working with
aerospace and automotive industry on projects to implement
Systems Engineering. He received his Master's degree
in Aerospace Engineering in 1994 and his Ph.D. in Systems
Engineering in January 1999 from the Technical University
of Munich. He is a founding member of the German Chapter
of INCOSE and was Technical Co-Chair of the Second European
Systems Engineering Conference (EuSEC 2000).
Dr. Herbert Negele holds the position of Senior
Systems Engineer, Electrics/Electronics Development
at BMW Group, Munich, where he is responsible for initiatives
on process/project management and systems engineering.
He received his Master's degree in Aerospace Engineering
in 1993 and his Ph.D. in Systems Engineering in 1998
from the Technical University of Munich. Until November
1999, he worked as an Assistant Professor in the Division
of Astronautics in the field of Systems Engineering,
with special focus on systems modeling and simulation,
integrated product and process development, and systems
engineering management. Herbert is a founding member
of the German Chapter of INCOSE, served as its Vice
President in 1997 and 1998, and was Technical Co-Chair
of the Second European Systems Engineering Conference
(EuSEC 2000).
Tutorial # F03: The Past, Present,
and Future of Structured Analysis
Technical Abstract:
Over the past 50 years a fascinating story, yet to be
heard by many in our profession, has evolved regarding
structured modeling methods and the many and varied
structures that resulted. The whole evolutionary process
started in the 1950s with flow charting used by both
hardware and software analysts. Hardware and systems
engineers remained with flow charts, drawn horizontally
rather than vertically, but software people migrated
to a host of models over a period of 50 years. Now,
there emerges a model from the software community that
promises to restore unity between hardware, software,
and system engineers and their works encouraging improved
human communication and consequently significantly improved
system integration during development. On-going work
between Object Modeling Group (OMG) and the International
Council On Systems Engineering (INCOSE) promises to
close the gap between Unified Modeling Language (UML)
use for software development and its use for systems
and hardware development. This common modeling environment
can also be projected into a new evolving world of development
referred to as model driven development.
Brief Biography:
The tutorial will be jointly presented by James Long
and Jeffrey Grady. James Long's biography is included
under tutorial F00 above. 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 as a system engineer, engineering
manager, field engineer, customer training instructor,
and project engineer. Jeff has authored five recently
published books in the system engineering field 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 Irvine campuses, University
of Alabama at Huntsville, and Indian Purdue University
in Fort Wayne, IN. Jeff is an International Council
On Systems Engineering (INCOSE) Fellow and Founder.
Tutorial # F04: Measurable Systems
Engineering
Technical Abstract:
Teams develop complex products and systems using engineering
methods of varied effectiveness. Whether it is called
"product design" or "systems engineering,"
the process moves at an overwhelming pace that sometimes
seems to drown good practice. Good design groups, however,
constantly seek to improve their design effectiveness.
Measurement is essential to that improvement, providing
the necessary control tools.
This full-day tutorial gives you practical measurement
and improvement techniques that apply to the design
of complex products and systems. These techniques and
measurements are both usable and effective for any systems
engineering effort, and they have been proven to work
without requiring massive expenditures or process improvement
bureaucracies. Many techniques provide real-time information
that can guide each project while it is in work. Measurements
include the most recent "Value of Systems Engineering"
information learned through research by the INCOSE Systems
Engineering Center of Excellence (SECOE). They are simple
to use and can be implemented on your program now.
Brief Biograghy:
Mr. Eric Honour has been in international leadership
of the engineering of
systems for over a decade, part of a 34-year career
of complex systems
development and operation. His energetic and informative
presentation style
actively involves class participants. He was the founding
Chair of the
INCOSE (International Council on Systems Engineering)
Technical Board
in 1994, was elected to INCOSE President for 1997, and
continues as
Director for Sponsored Research. He was selected in
2000 for Who's Who
in Science and Technology. He has been a systems engineer,
engineering manager, and program manager at Harris Information
Systems, E-Systems Melpar, and Singer Link, preceded
by nine years as a US Naval Officer flying P-3 aircraft.
He has led or contributed to the development of 18 major
systems, including the Air Combat Maneuvering Instrumentation
systems, the Battle Group Passive Horizon Extension
System, the National Crime Information Center 2000,
and the DDC1200 Digital Zone Control system for heating
and air conditioning. Mr. Honour now heads Honourcode,
Inc., a consulting firm offering effective methods in
the development of system products. Mr. Honour has a
BSSE (Systems Engineering) from the US Naval Academy
and MSEE from the Naval Postgraduate School.
Tutorial # F05: Requirements-Based
Product Line Engineering
Technical Abstract:
Reuse and requirements are very important for efficient
and successful systems development. However there are
many open issues about performing them well, in particular
the reuse of requirements. This tutorial presents the
experiences of requirements reuse using a Method for
Requirements Authoring and Management (MRAM).
For modern, highly complex, high reliability systems,
the need for properly structured, carefully controlled
requirements specifications, which are understandable,
complete and consistent is essential in order for the
resultant computer-based system to be delivered on time,
within budget and to the desired high level of quality.
One approach to managing these problems is to establish
a pool of reusable product line requirements and to
construct the requirements for a new system by making
a selection from the pool. A product line is a group
of products within the same market segment e.g. mobile
phones. A concern of this approach is the efficient
and clean selection of a valid combination of requirements.
A valid combination is one in which the requirements
selected satisfy any constraints imposed by the product
line model.
MRAM is a method for establishing and selecting from
product line requirements that addresses this concern.
Using MRAM means the management of the requirements
definition process is more effective and efficient,
producing more accurate and complete requirements documents.
TRAM (Tool for Requirements Authoring and Management)
is a software tool to support MRAM that utilises current
proven office technology (MS-Word, MS-Access). The tutorial
presents the results of MRAM/TRAM as it has been applied
to Product-Line Engineering of a real-world application.
Brief Biographies:
Prof Michael Mannion is Dean of School of Computing
and Mathematical Sciences, Glasgow Caledonian University,
Glasgow, Scotland, UK. He has a BSc in Computer Science
from Brunel University and a PhD in Artificial Intelligence
from Bristol University. He worked as a Software Engineer
for GEC Marconi Radar and Praxis Systems. He lectured
at Napier University, Edinburgh 1992-2000. He is a member
of IEEE, ACM, British Computer Society (BCS).
Prof. Hermann Kaindl has just recently joined
the Institute of Computer Technology at the Vienna University
of Technology in Vienna, Austria. Prior to moving to
academia, he was a senior consultant with the division
of program and systems engineering at Siemens AG Austria.
There he has gained more than 24 years of industrial
experience in software development. His current research
interests include software engineering with a focus
on requirements engineering, and human-computer interaction
as it relates to scenario-based design and hypertext.
He has published three books and more than seventy papers
in refereed journals, books and conference proceedings.
He is a senior member of the IEEE, a member of the ACM,
and is on the executive board of the Austrian Society
for Artificial Intelligence.
Tutorial # F06: Maximizing the
Systems Aspects of Systems Engineering
Technical Abstract:
What makes systems engineering different from all other
engineering disciplines? It is the use of systems thinking,
the systems approach, systems analysis, and systems
processes. Many of those practicing systems engineering
employ only a few of the many systems concepts that
exist. In this tutorial we will explore the common systems
concepts that will enhance the definition and the development
of new products and the effective use and support of
legacy systems that will continue to exist well into
the 21st Century. The tutorial will review and explore
the concepts of systems thinking, system science, systems
approaches and systems analysis and trace the development
of systems engineering as it is now practiced. A comparison
of how these concepts have been applied to natural and
environmental systems, organizational and management
systems, traditional engineered systems as well as the
more familiar defense and aerospace systems will identify
weaknesses that can be minimized by applying the full
spectrum of systems concepts. How system concepts have
been utilized in object oriented methods, formal modeling
languages and software engineering will also be explored.
This tutorial will allow the practicing systems engineer,
software engineer, or any engineer to identify potential
systems concepts that they can utilize to improve their
job skills and career potential. This tutorial will
also benefit those engineers or program managers seeking
a concise presentation of what systems engineering is
and how to determine good systems engineering from the
bad.
Brief Biographies:
Dr. Brian W. Mar is a Professor Emeritus. Prior
to his retirement, he was at the University of Washington
for over 30 years and was a Professor of Civil and Systems
Engineering. The Boeing Company employed him for 10
years prior to joining the University of Washington.
He holds a Ph. D. in Chemical/Nuclear Engineering as
well as several degrees in Civil and Chemical Engineering
and has served on International and National councils
and advisory boards. He is a member of Phi Beta Kappa
and Tau Beta Pi Honor Societies. He is one of the founders,
a fellow and a Past President of INCOSE and has published
several books and over 200 papers.
Mr. Morais is the President of Synergistic Applications,
Inc. and has over forty years of Program management
and Systems Engineering experience in industry. He holds
a BSEE from California State Polytechnic University
and M.S. in Systems Management from the University of
Southern California. One of the more significant achievements
in his career was leading the development of the first
Systems Engineering Management Guide for the Defense
Systems Management College when he was Director of Space
Systems Division Systems Engineering for the Lockheed
Missiles and Space Company. He has been an Adjunct Professor
at San Jose State University. He has provided lectures
in Systems Engineering at many other universities including
Stanford, the University of Illinois, University of
Southern California, University of Michigan, and the
Czech Technical University. He has provided consulting
support and training for National and International
government agencies as well as communications and energy
companies. He is a founding member of INCOSE, and was
the first Treasurer. He was the first Executive Director
for the initial period of the formation of INCOSE.
Tutorial # F07: Applied Statistical
Decision Theory for Systems Engineering
Technical Abstract:
Systems Engineering is a discipline that has at its
heart processes for making near optimal technical decisions
in an environment of uncertainty. Systems Engineers
make important decisions in every aspect of the Project
Lifecycle, often simultaneous and sequentially. Providing
good technical decision support for such decisions,
sometimes with an unknown level of decision maker risk
aversion, has never been easy, and often is almost impossible.
Statistical Decision Theory as traditionally taught
to address this problem is rarely practical for the
Systems Engineer in such situations. However, recent
advances in Statistical Decision Theory combined with
applications of Markov Chain Monte Carlo methods have
finally made Statistical Decision Theory practical for
the Systems Engineer in all decision making scenarios.
This tutorial addresses these state of the art techniques
for making good technical decisions, and provides attendees
with both the theory and the tools to apply the theory.
You will learn:
- how to apply decision analysis and theory in actual
practice
- conditional probability analysis
- Markov Chain Monte Carlo (MCMC) techniques
- how to provide good support for decisions with unknown
decision maker risk aversion
You will take home a CD-ROM Disc with
- a probability and statistics programming language
suitable for decision analysis and MCMC methods
- example software programs using conditional probability
analysis and MCMC techniques
- the example exercises presented in the tutorial of
actual SE decision making
- extensive references
(Attendees will be strongly encouraged to bring
a laptop computer (Windows compatible with a CD-ROM
drive) to perform the computational tutorial exercises
in parallel with the lecture, but a laptop is not required.)
Brief Biography:
Mark Powell has spent over 30 years in a wide variety
of technical environments, including DoD, NASA, DoE,
and commercial. In these environments, Mr. Powell served
as project manager, engineering manager, chief systems
engineer, and research scientist. Mr. Powell is currently
a member of the University of Idaho Adjunct Engineering
Faculty teaching courses in the systems engineering
graduate program, while maintaining an active engineering
and management consultation practice. He spent the 2000-2001
academic year on sabbatical at the University of Texas
at Austin performing research in the area of applied
statistical decision theory, the practical applications
of which are presented in the tutorial. Mr. Powell is
currently teaching two graduate level asynchronous internet
courses in this topic as well. He is an active member
of Sigma Xi, ISBA, and was a founding member of the
INCOSE Texas Gulf Coast Chapter. Mr. Powell's currently
affiliation is with the INCOSE Snake River Chapter.
Tutorial # F08: Requirements and
Modeling: A Structured Approach
Technical Abstract:
System requirements are often poorly structured and
poorly written. There are special techniques available
to help organize the requirements and make sense of
them. This tutorial will discuss these techniques and
give you essential principles and concepts that will
help in developing a structured set of complete and
consistent requirements for the system under development.
An overall document tree is used to structure the different
sets of requirements and supporting information such
as the concept of operations, mission needs statement,
requirements documents, test plans, and so on. How and
when to model different aspects of the system will also
be discussed.
We start with the "operational requirements"
for a system and show how these are derived from the
needs of the users, operators, operating organizations,
and other stakeholders. We discuss how a "concept
of operations" is developed to capture the essential
features of how users and operators interact with the
system and to drive the architecture development. We
then discuss the nature of a "capstone requirements
document" and how it relates to downstream requirements.
We will also discuss how the system architecture relates
to requirements and how various architecture frameworks
can be used to help organize the development effort.
Two of the frameworks discussed will be the C4ISR Architecture
Framework and the Zachman Framework.
Brief Biographies:
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 eighteen 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.
Steven Heidorn is a highly accomplished systems
engineer with over sixteen year's experience across
a wide range of defense, intelligence and commercial
systems. As a lead systems engineer, development engineering
manager and chief engineer at IBM Federal Systems, he
developed real-time, software-intensive, radar and sonar
signal processing systems. At the MITRE Corporation,
he developed concepts for software-reconfigurable sensor
and communications processing systems and contributed
to the architecture of the Joint Tactical Radio System.
At the Aerospace Corporation, he provides system engineering
and system architecting expertise across a wide range
of information-intensive commercial, civil and intelligence
systems and also teaches at The Aerospace Institute.
Mr. Heidorn holds BS and MS degrees in electrical engineering
from the University of Illinois at Urbana-Champaign
and has done additional postgraduate work in statistical
communication theory at George Mason University.
Monday
Half-Day Optional Professional Tutorials - Morning:
Tutorial # H01: A Systems Engineering Cost Model
for Information Processing Systems & Subsystems
Technical Abstract:
We invite you to learn about the latest cost model for
system engineering tasks in information processing systems
and subsystems. The material presented will be a summary
of the last two years of work on COSYSMO (Constructive
Systems Engineering Cost Model) by the COCOMO II research
group at the Center for Software Engineering at the
University of Southern California. You will be exposed
to the following:
* Background and challenges faced while developing COSYSMO
* Operational Concept for COSYSMO
* Potential use of the model
* Direction of the model
* The use of EIA 632 and ISO 15288 in the model
* A prototype version of the model
* Details on the data collection process
By attending this workshop you will also have the opportunity
to influence the direction and scope of the model.
Brief Biography:
Dr. Barry W. Boehm is the Director of the Center
for Software Engineering at USC. His current research
interests include software process modeling, software
requirements engineering, software architectures, software
metrics and cost models, software engineering environments,
and knowledge-based software engineering. His contributions
to the field include the Constructive Cost Model (COCOMO),
the Spiral Model of the software process, the Theory
W (win-win) approach to software management and requirements
determination and two advanced software engineering
environments: the TRW Software Productivity System and
Quantum Leap Environment.
Gary D. Thomas is an Engineering Fellow at Raytheon
Garland where he has worked
since 1976. He serves on the staff to the Director of
the Garland
Software Engineering organization and has been involved
with numerous
research efforts with the Center for Software Engineering
at USC since
1996. Gary received his Bachelor of Science in Education
in 1964 from
the University of Missouri at Columbia.
Mr. Ricardo Valerdi is a Research Assistant
at the Center for Software Engineering and a PhD student
at USC. Previously he worked as a Systems Engineer at
Motorola and General Instrument. His research interests
are in applying System Engineering principles to Information
Technology projects.
Tutorial #H02: Eisner's Architecting
Method (EAM): Prescriptive Process and Products
Technical Abstract:
Systems Architecting has been recognized as one of the
key elements of systems engineering. Although there
has been considerable documentation of the features
of a systems architecture, many questions still remain,
especially with respect to (a) a prescriptive method
for constructing an architecture, and (b) a short-form
and practical set of products (outputs) that follow
immediately from the above method. In addition, reviews
of descriptions and diagrams that are claimed to be
architectures suggest limited and often misleading views
that can create more problems than they solve.
This tutorial focuses on describing, by example, a
short-form prescriptive process for the architecting
of systems, along with various products. This process
and products have been tested for many years in both
industry and academia. It is demonstrated that the same
process applies as well to designing and building software
systems. In addition to this tutorial's focus on a systematic
and repeatable process for architecting systems, both
relevant standards and the DoD's C4ISR approach are
also discussed.
Brief Biography
Dr. Howard Eisner serves as Distinguished Research
Professor and Professor of Engineering Management and
Systems Engineering at The George Washington University.
He joined the faculty at GWU in 1989, after 30 years
in industry where he held executive and research positions
with ORI, Inc., Intercon Systems Corporation, and the
Atlantic Research Corporation. He was president of Intercon
Systems Corporation and the Atlantic Research Services
Corporation.
Dr. Eisner has written three books. His first, "Computer-Aided
Systems Engineering" (Prentice-Hall, 1988), was
the first in showing more precisely how computer tools
could support the many aspects of systems engineering.
His second book, "Essentials of Project and Systems
Engineering Management" (Wiley, 1997, 2nd Edition
2002), specifically integrates the topics of project
management and systems engineering. His other book,
"Reengineering Yourself and Your Company"
(Artech House, 2000), explores migration paths from
engineer to manager to leader as well as strategic planning
issues.
Over the years, Dr. Eisner taught also at the University
of Maryland (Systems Engineering), The George Washington
University (Modulation & Noise, Information Theory),
Columbia University (Electrical Engineering) and Brooklyn
College (Physics). He is a Life Fellow of the Institute
of Electrical and Electronics Engineers (IEEE) and a
member of Tau Beta Pi, Eta Kappa Nu, Sigma Xi, and Omega
Rho, various engineering and research honor societies.
In 1994, he was given the Outstanding Achievement Award
from the GWU Engineering Alumni. He has also served
the government and industry on a variety of evaluation
and advisory panels.
He holds the following degrees: B.E.E, The City College
of New York (1957); M.S., Columbia University (1958);
Doctor of Science, The George Washington University
(1966)
Monday Half-Day Optional Professional Tutorials - Afternoon:
Tutorial # H03: Reconciling Requirements,
Use Cases and Object-Oriented Modeling for Systems Engineering
Technical Abstract:
· How do scenarios / use cases fit together with
functional requirements?
· How can OO (object-oriented) principles like
classification help organizing a huge number of requirements?
· How can the application domain be better understood
using OO modeling?
This tutorial addresses these questions because they
are relevant for industrial software development but
too many misunderstandings still exist with regard to
OO processes and methods as related to requirements
engineering. It shows how each requirement given in
natural language can be modeled as an object, which
facilitates a clean organization and association. While
scenarios / use cases can somehow illustrate the overall
functionality, additionally functional requirements
for the system to be built should be formulated and
related to them appropriately. In order to better understand
scenarios, the goals to be achieved by them should be
explicitly defined and linked to them as well. All kinds
of requirements typically make statements about the
application domain, which should be represented in an
OO Domain Model of conceptual classes, in order to make
the requirements better understandable.
Among other things, this tutorial proposes solutions
to issues discussed in a panel organized by this proposer
at OOPSLA 2001 "How do Requirements Relate to Objects?".
It includes also material on real-world experience from
the approach developed by this proposer as presented
in an invited State-of the-Practice Talk at RE'01.
Brief Biography:
Prof. Hermann Kaindl has just recently joined the
Institute of Computer Technology at the Vienna University
of Technology in Vienna, Austria. Prior to moving to
academia, he was a senior consultant with the division
of program and systems engineering at Siemens AG Austria.
There he has gained more than 24 years of industrial
experience in software development. His current research
interests include software engineering with a focus
on requirements engineering, and human-computer interaction
as it relates to scenario-based design and hypertext.
He has published three books and more than seventy papers
in refereed journals, books and conference proceedings.
He is a senior member of the IEEE, a member of the ACM,
and is on the executive board of the Austrian Society
for Artificial Intelligence.
Tutorial # H04: Systems Engineering
and Software Engineering Processes and Products from
a Standards Perspective: Stand on the Standards
Technical Abstract:
Systems engineering and software engineering standards
have been around since the late 1960's, have evolved,
and will continue to evolve. However, systems engineering
and software engineering have continued to be two of
the least well-understood engineering disciplines.
The goals of this tutorial are to: 1) describe the
systems engineering and software engineering standards
heritage, processes, and products; 2) show the relationship
between systems engineering and software engineering
processes and products based on the standards; and 3)
encourage and challenge the participants to read, understand,
select, tailor, and apply the systems engineering and
software engineering 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. Understanding
the standards will significantly aid in understanding
the relationship between systems engineering and software
engineering.
Customers, companies, authors, educators, managers,
engineers, and others may have an understanding of portions
of systems engineering and software engineering based
on these other sources. Standards, developed by subject
matter experts and approved by a nationally recognized
standards organization, provide a more complete and
common understanding of systems engineering and software
engineering, and thus provide a firm foundation for
product and process development. Knowledge of these
standards and experience in applying them are also significant
enhancements to any engineer's career.
Brief Biography:
Mr. John Clark is a Chief Engineer at Northrop Grumman
Information Technology, Defense Mission Systems, Warfare
Systems Engineering in Virginia Beach VA. He is currently
supporting Northrop Grumman Newport News at the Virginia
Advanced Shipbuilding Carrier Integration Center (VASCIC)
on the new CVN 77 and CVN 21 aircraft carrier programs.
John's background includes over 37 years of experience
in applying systems engineering and software engineering
to a wide variety of systems including the acquisition,
development, verification/testing, operations, and support/maintenance
of military tactical command, control, communications,
computer, intelligence, radar, sonar, electronic warfare,
identification, weapon, network, scientific, and information
systems. He earned a Bachelor of Science degree in Electrical
Engineering from the Pennsylvania State University and
a Master of Science degree in Electrical Engineering
from the State University of New York. John's current
professional memberships include INCOSE and IEEE. He
and his wife Linda of over 36 years have four children,
Robin, Kristin, Jason, and Aimee. John is an active
member of his church and leads the Royal Rangers outreach
ministry program for at-risk boys in a local trailer
park.
Alternate 1: Fault Analysis for
Systems Engineers
Technical Abstract:
Murphy said that if anything can go wrong, it will.
Robust design can reduce the rate of hardware failure,
but it will never reach zero, and software provides
its own class of "failure". During the system
design process the systems engineer must assess failure
conditions and determine appropriate system responses
to failure. Waiting for detailed design completion is
too late, but starting a fault analysis without a design
can be intimidating. The conference theme, "Problem
Solving through Structured Thinking", suggests
that the Systems Engineer should understand how failure
affects system behavior before the design is completed.
Appropriate mitigation can then be designed into the
system via the requirements.
This tutorial will provide the processes and methods
during requirements analyses to lead the design in the
area of failure analysis and system or subsystem response
to failure. The attendee will learn how to perform functional
failure analysis to produce a failure modes and effects
analysis (FMEA) prior to SDR and PDR, rather than waiting
for CDR, when it's generally too late to influence the
design. Focusing on functional failure implies that
the analysis can be valid regardless of the eventual
implementation in hardware, software, or something else.
The utility of the analyses for Safety and Logistics
activities will also be described.
This introduction to fault analysis for systems engineers
follows the new industry standard, ARP5580 ("Recommended
Failure Modes and Effects Analysis (FMEA) for Non-Automotive
Applications"), which focuses on functional behavior
and consequences rather than the more traditional piece-part
analysis. The tutorial will carefully define terms used
in the subject of fault analysis, describe the basis
for functional failure, and describe the different kinds
of fault analyses and when they should be applied. In
addition, this tutorial will demonstrate how to integrate
failure analysis into the requirements analysis process.
ARP5580 will be reviewed in some detail. Finally, we
will demonstrate how to conduct a functional failure
modes and effects analysis on a system and integrate
the results in requirements using the techniques described.
Brief Biography:
Dr. Carson is an Associate Technical Fellow in Systems
Engineering in the Integrated Defense Systems organization
of The Boeing. During his career he has worked on requirements
analysis for various military and commercial systems
including locomotives, missiles, high-power lasers,
the Boeing 777 Cabin Management System, and the Boeing
Phased Array Communication Antenna System for live,
satellite-broadcast television. He received "Best
Paper" Award at the 1995 Symposium of the International
Council on Systems Engineering for his work on "A
Set Theory Model for Anomaly Handling in System Requirements".
During 1999-2000 he was responsible for analyzing failure
modes and effects of the Boeing Joint Strike Fighter
design. He is currently responsible for the design of
airborne intelligence, surveillance, and reconnaissance
systems, and fault analysis for various applications,
including Connexion by BoeingSM. He has a Ph.D. in Nuclear
Engineering from the University of Washington, and a
B.S. in Applied Physics from the California Institute
of Technology.
Alternate 2: Writing Requirements
Technical Abstract:
What is a good requirement? How do you write a good
requirement? This one-day seminar focuses on how to
write good requirements - the characteristics of good
requirements and how to turn bad into good. It covers
how to turn an implementation or operational statement
into a requirement. It covers other data you need, such
as rationale, in order to make understanding requirements
easier over the project life cycle. It discusses types
of requirements - functional, performance, reliability,
etc.
Theory is turned into practice using a set of exercises
designed to give participants hands-on practice in identifying
common errors in writing requirements. Students work
as teams to determine problems with requirements - terminology,
ambiguous terms, stating implementation and operations
as opposed to requirements, and level distinctions.
Examples of how to rewrite implementation and operational
requirements as verifiable requirements are shown. Students
are given a project scope and operational concepts and
then do a team exercise to define a set of requirements.
Management of data relevant to requirements - rationale,
traceability, and others - are discussed.
Brief Biography:
Lou Wheatcraft is an expert in requirements development
and management who educates and consults organizations
on the importance of writing good requirements. Lou
is a member of INCOSE, the INCOSE Requirements Working
Group, and Project Management Institute, Toast Masters,
International, and the World Futures Society
Lou Wheatcraft is a senior instructor joining Compliance
Automation, Inc. in the summer of 2000. Lou has over
35 years experience in the aerospace industry, including
22 years in the United States Air Force as part of the
Military Space Program. Prior to joining Compliance
Automation, Lou worked five years at the Johnson Space
Center in the Astronaut Office developing operational
concepts and requirements for how the astronauts are
living and working on the International Space Station.
Lou has co-authored a paper with Ivy Hooks titled, Scope
Magic, authored an INSIGHT Special Feature Article,
The Importance Of Scope Definition Prior to Developing
Space System Requirements, Published in INCOSE INSIGHT,
January 2002, Vol. 4 Issue 4, and authored an article,
Back To Basics: Delivering a quality product that meets
your customer's expectations, to be published online
in CrossTalk, January 2003, Vol 16 No. 1.
Lou has a BS degree in Electrical Engineering from
Oklahoma State University, an MA degree in Computer
Information Systems from the University of Houston -
Clear Lake, an MS degree in Environmental Management
from the University of Houston - Clear Lake, and is
completing an MS degree in Studies of the Future from
the University of Houston - Clear Lake.
Call
for Tutorials
Tutorial
Submission Form
|
