Managing IOOS Regional Association Development with Todays Systems Engineering Approach SEA

1
Managing IOOS Regional Association Development
with Todays Systems Engineering Approach (SEA)

• September 19, 2006
• Robert Vorthman, John Linn III and Fred Klein

2
In 15 minutes

• Issue Awareness - Are these True or False?
  (T/F ?)
• Systems Engineering for RCOOSs is the same as for
  IOOS.
• IOOS is starting Systems Engineering in the
  middle.
• A late start requires extra effort and time to
  catch up.
• Risks to IOOS interoperability are known and
  managed.
• Agenda
• Definition Phase of Systems Engineering
• Terminology
• Framework for Success Factors of SE success
• ConOps
• Communicates to all Stakeholders
• ConOps of an RCOOS vs the US IOOS ConOps
• What should Systems Engineers do with the ConOps?

3
Clear, Measurable, Testable Requirements
Would you tell me, please, which way I ought to
go from here? That depends a good deal on where
you want to get to, said the Cat. I dont much
care where, said Alice. Then it doesnt matter
which way you go, said the Cat.
so long as I get somewhere. Alice added as an
explanation. Oh, youre sure to do that, said
the Cat, if you only walk long enough.
4
Systems Engineering Phases
Define
Design
Develop
Deploy
Operate Maintain, Enhance, and Sustain
Dispose
Systems Engineering Life Cycle

• Definition phase of a system
• Key systems engineering processes
• Concept of Operations (from the operators view)
  and
• Requirements Engineering
• Exit criteria for each phase
• In a larger context, these SE Phases must
  integrate with other System Life Cycle Processes
  per ISO/IEC 15288
• The Framework for Success slide shows some of
  these.

5
Elements of a System
Components
Elements
System

• A element is a collection of components

6
System
Components
Elements
System

• A system is a collection of hardware, software,
  people, procedures, facilities and data to
  accomplish some common objectives. 1
• A System Engineer leads and manages
• Facilities Engineer
• HW Engineer
• SW Engineer
• Specialty Engineers
• Communications Engineers

• ANSI/IEEE Std 729-1983, IEEEStandard Glossary of
  SoftwareEngineering Terminology

7
System Boundary
Components
Elements
System

• A System has a boundary.
• Define whats inside.
• Define whats outside.
• Thats a model of the system that to analyze and
  design.
• Keep it simple.
• Dont gerrymander.
• If the boundary changes, update the analysis and
  design.
• SEs lead and manage whats in.
• SEs interface to whats outside the system and
  coordinate across the interface.

Elements Communicate
Communications
Interface
8
A System e.g., an RCOOS
Components
Elements
System

• A system is as previously defined
• In Common
• RA business leadership, management, and
• RA system engineering leadership, management
• Resources
• Funding
• People

Funding Source

Leadership Management
Interface
Communications
9
System of Systems SoS, e.g., NOAA IOOS
Components
Elements
System
SoS

• SoS is a collection of Systems to accomplish
  some common objectives.
• Systems have own objectives.
• Do IOOS or original system objectives have
  priority?
• In Common (a goal)
• Business leadership, management, and
• System engineering leadership, management, and
• resources (funding and people).
• SoS Engineering Projects
• Accomplish milestones for
• Definition phase,
• Design phases,
• Development phase, and
• Deployment phase
• for IOOS PMO approval.

Common Funding Source

Common Leadership Management

Communications
Interface
Interface
RCOOSs
US IOOS GEOSS
Interface
Interface
Interface
Interface
10
Federation of Systems FoS, e.g., US IOOS
Components
Elements
FoS
System
SoS

• FoS is a collection of Systems to accomplish
  some common objectives.
• Systems have own objectives.
• Conflict identification and resolution?
• In Common (a goal)
• Business leadership, management, and
• SoS engineering leadership, management, and
• resources (funding people).
• FoS Engineering Projects
• Accomplish milestones for
• Definition phase,
• Design phases,
• Development phase, and
• Deployment phase
• for IOOS PMO approval.

Some Common Funding Sources - OMB

Common Leadership, CoordinationPerformance
Tracking of IOOS Capabilities
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
11
Corporate PolicyRequirementsFramework?
Clear,
complete, correct, consistent, communication is
critically important to accomplish IOOS.
12
Framework for Success - Missions
Framework for IOOS as a FoS

• This is similar to ISO/IEC 15288 System Life
  Cycle Processes

13
Framework for Success - Missions
Missions, Objectives in ConOps ? Definition Input

• Systems Engineering begins by defining the
  system, system of systems and/or the federation
  of systems. What does each stakeholder expect?

What will each stakeholder accept?
14
Framework for Success - Programs
Program Capabilities, Functions from ConOps ?
Definition Input

• Understand and document in terms of program
  capabilities functions what each can contribute
  to IOOS.

what will each will commit (staff and funds) to
contribute to IOOS.
15
Framework for Success Life Cycle
Phase in Life Cycle from ConOps ? Definition
Input

• Understand the life cycle phase of each legacy
  system. Is it research, operational, well
  supported, unsupported, or scheduled for
  replacement?

Align appropriate phases to model and improve
IOOS development.
16
Framework for Success - Constraints
Constraints from ConOps ? Definition Input
See and hear moreon Constraints in a paper
9/20at Oceans 2006.

• Constraints must be identified, and if validated
  they are managed as requirements in the
  Definition Phase. Standards may be constraints.

Find and manage the constraints now that you
dont want as a surprise later.
17
Sources of Constraints
Constraints are managed as requirements.
Unmanaged constraints are a major cause of
integration problems during implementation.
18
Sections of an RAs ConOps
Scenarios identify interfaces between systems to
accomplish end-to-end objective.

• ConOps is a high-level document in clear, but
  non-technical language to communicate to all
  stakeholders.
• Describes what the system does from an operators
  perspective.

19
ConOps Facilitates Communications Understanding
Agreement Among Stakeholders
Not including all stakeholder views hinders the
process and degrades the result.
20
ConOps Presents Users Views with text and
graphics
Mission Objectives, Capabilities, Functions,
Performance measures Rationale
Relevant Customer, Developer, User
Organizations and their Policies

• Constraints
• Limitations
• Laws
• Regulations
• Standards
• Policies
• Contracts
• Local Culture

Operational Philosophies
Operational System Characteristics
External Interfaces and Requirements
21
ConOps Integration

• Each IOOS systemshould have a ConOps
• Agency
• RCOOS
• Other IOOS systems
• A top-level IOOS ConOps must integrate
  representative individual ConOps.
• Operational Scenarios that crossseveral systems
  that must beintegrated to make the right
  decisions and accomplish an end-to-end
  objective.

Provide the right information, in the right
format, at the right time, to the right people,
to make the right decisions.
Who are these people?
What decisions are they making?
22
Requirements Engineering

• A facilitated process conducted by systems
  engineers with all appropriate stakeholders to
  define complex systems.
• Four interactive and iterative phases to achieve
  agreement.
• Elicitation
• Negotiation
• Documentation,
• Verification and Validation
• Prerequisite to Exit the Definition Phase and
  begin Design.
• Next Milestone is a Conceptual Design Review
  (CDR)
• CDR is a formal systems engineering milestone
• CDR establishes a functional baseline.
• Next Systems Engineering phase is Design

23
Key questionWhat should IOOS accomplish?

• Satisfy its top level requirements, e.g.,

Provide the right information, in the right
format, at the right time, to the right people,
to make the right decisions.
VADM Conrad C. Lautenbacher, Jr., USN (Ret.)
February 15, 2006
How do SEs respond to this What from a
Systems Engineering perspective, with the How?
24
Key questionWhat should IOOS Systems Engineering
accomplish?

• Model IOOS to identify risks before building it
  at great expense, e.g.,
• Manage the risks to interoperability to deliver
  an IOOS that satisfies its stakeholders.

SE Stakeholders
One IOOS requirement of many
Provide the right information in the right
format at the right time to the right people
to make the right decisions. Forecast all
risks to IOOS interoperability, to plan IOOS (as
SEs do), to recommend action or guidance, to
manage those risks.
FoS System Metadata
SE Decisions
25
Take Home MessagePerforming SE well will resolve
IOOS Top Ten Challenges and more

• Top Ten Challenges
• Alphabet Soup
• Stove Pipes
• Integration
• Architecture
• Data Management
• Data Sharing
• User Needs
• Maximizing Benefits
• Communication
• Execution
• 11. Doing Systems Engineering Well

• IOOS Systems Engineering Approach1 will
• Provide standard, defined terms, IOOS-wide
• Analyze defined problems synthesize balanced
  solutions to validated integration requirements
• Accomplish by applying SE processes to a FoS
• Work with architects to create (and use) a US
  IOOS EA
• Achieve DM as with all validated IOOS
  requirements
• Achieve DS as with all validated IOOS
  requirements
• Facilitate eliciting, and negotiating verified,
  validated, objective requirements that trace to
  validated needs
• Prioritize IT capital investment recommendations
• Engage right stakeholders for definition,
  approval, etc.
• Accomplish planned2, funded, project
  deliverables, on time, on budget to stakeholder
  satisfaction and
• 11. Resolve root causes behind symptoms of
  concern.

1 INCOSE Systems Engineering Approach 2
PMIs Project Management Book of Knowledge
26
Successful projects start by defining requirements
IOOS
27
Questions
Questions?
IOOS
28
Questions, Title, Authors
Managing IOOS Regional Association Development
with Todays Systems Engineering Approach (SEA)
Questions?
Robert Vorthman, John Linn III and Fred
Klein vorthman_at_mitretek.org
29
End Blue Screen