1 Don Schaefer – 703.984.3388 Mission Engineering TM - a transformational business analysis and...

1

Don Schaefer – 703.984.3388

Mission EngineeringTM - a transformational business analysis and system engineering approach

“Challenge the Dominant Paradigm”

2


Mission Engineering (ME) Defined

ME is an advanced requirements gathering and analysis method

ME is focused on capturing & translating the ‘intent’ of the customer’s mission needs into implementable system/software/data requirements

ME reduces interpretation of textual requirements by using visually robust products as the central communication device

ME provides notational linkage of the implementable requirements to the originating customer mission needs

ME is an engineering method that can be used with any system or software engineering processME is a repeatable method where all of the processes and artifacts can be used, or it can be tailored with only a subset of the overall method

ME analysis and artifacts support acquisition analysis, BOE costing and portfolio management.

ANALYSIS, COMMUNICATION & UNDERSTANDING

3


Why Was Mission Engineering Developed?

Deliver systems with greater user satisfaction

Speed up design and development time

Provide analytical defendable traceability from customer need to architecture design

Provide a better way to derive/illustrate COTS/GOTS/Technology integration requirements

Identify the risk…technical, operational and programmatic

Provide a more integrated and holistic view of the enterprise

Customers spend millions of dollars…purchase the best hardware, the best software, and the best engineers…and if the users don’t like

or use the system…the system development was a failure

4


Mission Engineering and the DODAF Pyramid

OperationalView

Identifies What Needs to be Accomplished and Who Does It

Technical StandardsView

Prescribes Standards and Conventions

SystemsView

Relates Systems and Characteristics to Operational Needs

• Specific System Capabilities Required to Satisfy Information exchange

• Technical standards Criteria Governing Interoperable Implementation/Procurement of the Selected System Capabilities

• System

s that

Support the

Activit

ies an

d Inform

ation

Exchan

ges

• What Nee

ds to B

e Done

• Who Does

It

• Informati

on Exchan

ges

Require

d to G

et It D

one

•Operational Requirements

and Capabilities

•Basic Technology

Supportability

•New Technical Capabilities

5


Community

SPECIFICATIONSPECIFICATION

ARCHITECTUREARCHITECTURE

DESIGNDESIGN

OPERATIONSOPERATIONS

DEPLOYMENTDEPLOYMENT

VERIFICATIONVERIFICATION

INTEGRATIONINTEGRATION

Mission Engineering

Systems AnalysisMultiple Dimensional Requirement's

Reqt’s Mapping to ActivitiesDerive Requirements

Risk AnalysisRequirement's Visualization

Operational Scenarios

Community FeedbackLaunch & Learn via Portal

ACQUISITION / CONSTRUCTIONACQUISITION / CONSTRUCTION

DEVELOPMENTDEVELOPMENT TESTTEST

INPUT To…Field Documentation (Manuals)Training Material Development

INPUT To…Fault Isolation

Problem Isolation

Program Office

INPUT To…Detail DesignActor Inventory

Visualization & GUI designUse Case Description

Activity / Sequence / etc…UMLCOTS/GOTS/Custom Code Integration

Opportunities

Business Rule ConflictRisk Areas & OpportunitiesPrioritization of EAR - Activities

Community AnalysisCommunity Model

Interface Transaction InventoryVisual Con Ops

Advocacy Products - CV

CommunityClient InformationExisting Ops Cons & Req

Legacy systems Constraints

INPUT To…ICD Identification

Actor/Organization Interfaces

CONCEPTCONCEPT

Operations AnalysisEnterprise Activity Roadmap

Concept Visualization Mission Process Mapping

Technology Mapping

INPUT To…COTS/GOTS

Integration

INPUT To…Test Plan & Procedures

Used To…Validate design

6


Mission Engineering – What it will do, what it won’t do Mission Engineering WILL:

– Provide your program with enough functional requirements and preliminary design content to get you to your programs Preliminary Design Review (PDR) gate

– Provide your program with a ‘conceptual’ design of the system/application

– Provide your program with high level business process flows that are linked to requirements

– Provide data architects with a preliminary first draft data dictionary

– Provide software architects with a complete workflow analysis, functional behaviors and interface points for COTS integration

– Provide Business Process Analysts with lower level (level 5) process flows and business rules

– Provide Test engineers with a first draft of the system test procedures

– Provide Test engineers with multiple Mission and Capability functional threads

– Provide Trainers with input to both standup and/or computer based training course material development

– Provide system engineers and architects with preliminary interface definitions and architectural behaviors

– Provide stakeholders (Customers) with an easily understood view of what will be developed and how it will be used

– Provide your program high quality, rigorous, analytical business and engineering content…if you have the right team

Mission Engineering will NOT:– Provide your program with detailed design; e.g. logical model, physical model, UML

– Provide you with ‘system’ level requirements; e.g. –ilities (maintainability, scaleability, etc), network protocals, etc Provide you with hardware requirements Provide you with network requirements, etc

– Be useful to the program if you do not have the right team working on the analysis.

7


Customer NeedCustomer Need Engineering Reqt’s Engineering Reqt’sANALYSIS, COMMUNICATION & UNDERSTANDING

Phases of Mission Engineering

8


INPUTS Goals Processes Products Existing

Documents User Types

Core Products Community Interface Model Transaction Inventory Actor Inventory Background Information

Additional Products Visual Operations & Requirements Spec Concept Visualizations Advocacy Material Requirements Standardized Architectural Views e.g. C4ISR Value Engineering

TEAM• Customer• Domain Analysts• Mission Eng Analyst• Desktop Multimedia

Producer

Input To: Arch Analysis Program Marketing Training Reqt’s Analysis ICD Development

Mission Engineering Phase I – Community Analysis Process

9


Transaction IDTransaction ID

Develop Information Develop Information Transaction InventoryTransaction Inventory

Info Sent Info Sent FromFrom

Info Received Info Received FromFrom

When When transactedtransacted

Info Info TypeType

Network Network DomainDomain EAR EAR

Service Service AreaArea

EAR EAR ActivityActivity

ME ME TraceabilityTraceability

Develop Develop Community ModelCommunity Model

Analyze and Define:• Mission Customers, Mission Partners• Mission Roles: Analyst, Consumer, Collection Manager• Information transactions• Information developed & delivered among roles• Value Chain & Capabilities

Develop understanding and advocacy for Customer's Goals and Transformation

Develop Concept Develop Concept VisualizationVisualization

Community Analysis – Advocacy & Understanding

10


11


Phase 1 Summary of content

At this point, we should have developed:– First draft of community model

– Beginning of the actor list

– Beginning of the tools (COTS/GOTS) list

– Supplier list

– Customer list

– Partner list

– Information Transaction table

– TIME Elapsed: 1 to 3 weeks

Additionally, if the program desires, we should also begin the story board for the concept visualization work

12


Core Products Enterprise Activity Roadmap Activity Goals & Descriptions Capability Descriptions Enterprise Activity Function Map Mission Process Models

Additional Products Business/Mission Process Analysis Technology Evaluation Matrix Mission Threads/Product Threads Actor and Activity Matrix Requirements Analysis C4ISR Views

TEAM• Customer• Domain Experts• Business Analysts• Mission Eng Analyst• Information Architect• System Arch

Output To: Community Model Updates ME Phase 3 BPR activities Program Marketing Strategic Acquisition

Mission Engineering Phase II – Operations Analysis Process

13


Work with stakeholders on the mission of the organization and the product & service value chain scenarios from a task flow perspective.

Identify high level “Mission or Operational” Service Areas

Identify “functional activities” involved within the system workflow…logical groupings

Create an inventory illustrating the actor functional activities required in the performance of their mission or in production of a product or service

The Enterprise Activity Roadmap is developed in an Integrated Product Team environment

14


Increment 1Increment 1



Operational Operational ServicesServices

Functional Functional ActivitiesActivities

Activity Name:Activity Code:Actor Class;Actor:Pre-:Post-:COTS/GOTS:Arch service:Source:

Enterprise Activity Roadmap defined…

Commercial Commercial Tool ATool A

Commercial Commercial Tool BTool B

Legacy App 1Legacy App 1 No Tool IDNo Tool ID

15


Functional Breakdown of COTS/GOTS tools

There are two ways to map tools to the activity roadmap; complete tool or tool function.

For instance, in the illustration below, lets assume the yellow icon represents the Microsoft Office Tool.

– As the MS Office tool, you can see exactly what activities have been identified that the MS Office tool will be used or integrated.

– Or, if you break MS Office into its high level component functions, (e.g. E-Mail, Notes, Tasks, Contacts, Calendar), you would see which activities will use MS Office, but, you could also then see which component of MS office as well.

– You would have: OL-C – outlook-calendar OL-E – outlook-e-mail OL-N – outlook-notes

Add COTS/GOTS component as an attribute to activity

16


Mission Process Map (MPM) Overview

Service Area Service Area IdentifierIdentifier

A Mission Process Map (MPM) shows the BPR results in the context of a Mission thread. The steps in the MPM are mapped directly to the Activities in the Roadmaps and Service Areas in the Community Model

Activities Activities mapped to the mapped to the

RoadmapRoadmap

17



At this point, we should have:– First draft of every enterprise ‘segment’ activity roadmap

– Full definition of each service area

– Written all goals and descriptions for all activities

– Begun to prioritize the activities per client needs, implementation schedule and funding

– A number of Mission Process Maps completed, may include state changes

– A candidate set of Capability Vignettes completed or identified

– Full description of each actor role

– Mapped actor roles to activities

– Functional breakdown of tools

– Mapped Tools/functions to activities

– Listed ‘source’ for each activity, e.g. document, legacy, person

– Final draft of the Community model with Service areas shown

– TIME Elapsed: 2 to 6 weeks

18


Core Outputs Functional Requirements Data Elements and Attributes Multidimensional Requirements View Data Tables/Relationships Business Rule to Function Mapping

Additional Outputs System Requirements Enterprise Requirements Documents Business Process Analysis Requirements Mapping Requirements Traceability Matrix Requirements Visualization Information Architecture

Output To: Tool Evaluation Testing Procedures Training Architecture Field Documentation SW Detailed Design DB Design BPR

TEAM• Domain Experts• Architects – SW, DB,

SYS, SEC, Info• Mission Eng Analyst• Mission Eng

Facilitator

Mission Engineering Phase III – Systems Analysis Process

19


Multi-Dimensional Requirements View (MRV)Multi-Dimensional Requirements View (MRV) Created in an IPT environment of stakeholder, developers and integrators Captures the activity workflow of people and systems Captures the behaviors between functions, applications and data Derives new requirements from integrated architecture analysis Provides framework to map existing legacy requirements

Requirements VisualizationRequirements Visualization

EAREAR

ActivityActivity

Service AreaService Area

Web viewable; Web viewable; DOORS, RequistPRODOORS, RequistPRO

Central Repository

Define operational functional steps – activity workflow

Map ops functions to system layer applications

Map data created & data read to functions

Derive new requirements, map existing requirements

Derive and/or Map business rules to functions

MRVMRV

System Requirements – Workflow, Interfaces, Behaviors

20


MRV ‘SET’….For each functional activity…

21


22


MRV to RV development…”test drive the requirements prior to development”

23


MRVs explained & link to rest of programBusiness Segment Business Segment User RoleUser Role Business Segment ActivityBusiness Segment Activity

Business Segment Service AreaBusiness Segment Service Area

Activity Functional StepsActivity Functional Steps

Architecture Segments – Application Architecture Segments – Application COTS/GOTS interfaceCOTS/GOTS interface

Data Store Name – Read / WriteData Store Name – Read / Write

Activity Functional RequirementsActivity Functional Requirements

Activity Function Business RulesActivity Function Business Rules

Maps Activity / Requirements to Capabilities on CDR Criteria for Tech EvaluationInput to Software DesignInput to Test ProceduresInput to Training ScenariosInput to User ExperienceInput to Information ArchitectureInput to TE Business Process Analysis

DOORS Database

24



At this point, you should:– Begin development of the integrated Ops and Requirements Document

– Completed a first draft of the prioritized MRVs

– Defined performance goals for each MRV to the level required

– Can begin development of the data dictionary from each MRV

– Analyze the COTS/GOTS functional interfaces for integration

– Updated the Community model

– Updated the Activity Roadmaps

– Updated the Business process flows

– TIME Elapsed: 1 to 3 MRVs per day

25


The Linkage

ISPAN

SYSTEM

ISPAN

SYSTEM

Portal

CSCI

Portal

CSCI

Mission Planning

CSCI

Mission Planning

CSCI

Workflow and Executive

CSCI

Workflow and Executive

CSCI

Common Planning Framework

CSCI

Common Planning Framework

CSCI

Decision Support

CSCI

Decision Support

CSCI

Data Services

CSCI

Data Services

CSCI

Infrastructure

CSCI

Infrastructure

CSCI

Optimization

CSCI

Optimization

CSCI

Effects Based Planning

CSCI

Effects Based Planning

CSCI

Collaboration Services

CSCI

Collaboration Services

CSCI

COTS/GOTS

CSCI

COTS/GOTS

CSCI

ActivityActivity

Missile Defense Mission ThreadMissile Defense Mission Thread

CSCsCSCs

Multidimensional Requirements View (MRV)Multidimensional Requirements View (MRV)

Perform Ballistic Missile OptimizationACT Code: OP-PBMOPActor: PA, PLArch CSCI: OPTIMZCOTS/GOTS: ILOG, IMEA, JMEM, MEM, MGPS Mission Ops Activity Roadmap

0042 Deliver Basic Detailed Planning Optimization

Community ModelCommunity Model

Requirements to Requirements to Architecture View (RAV)Architecture View (RAV)

MCPMCP

26


Users validate Information Architecture

Users work with Geoscout to determine activity and service needs

Customer Services Management

Customer DB

Customer Request

Customer Self Service

Product/Service Catalog

Geospatial Analyst

((IS))

Collection Tasking

My Information

Information Discovery

De

NSGI Community

Expert ListCollaborate (Synchronously)Expert RegistrationCommunity of InterestGet Expert AdviceParticipate Polls/Surveys

My GIO Portal

My Community

My Tasks

My Calendar

Role SpecificServiceFunction

My GIODesktop

Portal Management

User ProfilesUser PreferencesUser

My Information Technology ManagementPortal

My Portal My Tasks

My Calendar

Role SpecificServiceFunction

My EMDesktop

My Portal

GIO BusinessManagement

Assignment List/StatusExport Query Response

QL / Review

Portal Management

Setup

Manage Preferences

Advanced SearchMy Agents -Manage Existing -New Setup-Link Analysis


((IS))

CollectionSTATUS

-Review submissions

Log In

Role Based

Enterprise Site Function Map

InformationArchitecture

Information Technology Management Operations

IT Operator ArchActor

Geospatial Intelligence Operations (GIO)

Mission Ops - ArchActor Role

FunctionalOPSTBD

CorporateOPSTBD

Corp Ops -Actor Role

KEYGold = Geospatial OpsGreen = Functional OpsOrange = Corp OpsBrown = ITM OpsRed = CES Ops

This document is still under development

Security Administration

Network Security

Anti-Virus

Interfaces

Product Classification

Reporting

Data Administration

Data Model

DB Performance

DB Administration

Meta Catalog

Reporting

Supervisor Function

Training

Training Catalog -Review -Update

Supervisor Function

Supervisor Function

Supervisor Function

System Administration

User Accounts

Hardware/Software Tracking

Software Licenses

Upgrades

Reporting

Supervisor Function

Supervisor

Assignments Assign Tasks -To Staff -To Team Review Status -By Staff -By Team -SearchWork Flow Setup Status Approval

Resources Staff List(Assignment &Availability)

Metrics Staff Production Team Production QuantitySupervisor

Assignments Assign Tasks -To Staff -To Team Status All SearchWork Flow Setup ApprovalCalendar Team Corporate

Resources Staff List(Assignment &Availability)

Metrics Team Production Customer Feedback Quantity

Intelligence Analyst

Collection Tasking

My Information


GI References

Supervisor Function

Supervisor Function

Collection Managment

Tasking Status

New Tasking

Supervisor Function

GIO AdministratorsRequest PKIIdentify and Nominate ExpertsProcess Expert RegistrationProcess Community of Interest(Manage)Process Customer Feedback (Prod& Services)

GI Metrics Mgt

Corp Ops

Supervisor Function

GIO Customer ServiceReview GI Service RequestReview GI Product Request

Service MetricProduct Metric

Assignment ListWorkflow stop (if approved)

My TeamMy Business SegmentNIMA

Tools

Provide “mirror”sites for

download ofnew functions,tools, versions

Network Management

Node Status

Supervisor Function

Customer Feedback - Review - Historical - Metrics - Forward

Feedback

Configuration Management

Supervisor Function

Performance Management

Collect/Report CS metrics

Monitor service requirements trendanalysis

NSGI Splash View

New Products News

New Services NSGI Content

NSGIWorkspace I.O.

?

Parent Parent

Tools

Provides“mirror” sites

or download ofnew tools,

functions, andversions

New GIO Product/Service

Advertisement

Ads servedpersonalized

by role

My NSGI News

My Mail

GIO Customer Service

GI Product CatalogGI Service Catalog

Order StatusSubmit Need

Provide FeedbackReadiness Requirements

Get Help

Collaboration(may be thick

client)Desktop

Icon

MyGI

Info

FoldersContentNotes

Non (role specific)content

Review ListPlace Order

GIOEM

Sets preferences for“push” applicable

products and services

Perform linkanalysis betweendata/information

GI References

KeysTutorialsExamplesExports

My Info

Personal-Notes-Content-Reference-Historical Products

Team-Folders-Content

WorkProductionAnalysis

Team

Consider (sourcemanagement) role

Consider mergeto “analyst” role

???

Last updated 01/21/04 @ 2:43:43 PM010603 Enterprise Site Function Map v0 r4.vsd

Stakeholder Insight

User Groups from NGA Mission Segments; GIO, Corp, Funct, ITM

NGA Community ModelNGA Community Model Activity RoadmapsActivity Roadmaps

Users drive Ops function needs in MRV-member of design team

Users support Business Process Analysis & Mission Process Mapping

Business Processes from

each Mission Segment

Activity Mapping to

Mission Threads & Business Processes

Requirements Viz & Requirements Viz & Tech DemosTech Demos

Users evaluate prototypes and tools

Multidimensional Multidimensional Requirements View Requirements View

(MRV)(MRV)NSGI Site MapNSGI Site Map

1 for 1 relationship of user activity to

MRV

Communications

27


INPUT

PRESENTATION & ANALYSIS

OUTPUT

Legacy SystemRequirements

User & StakeholderInput

Developer Input & Ideas

User Validated Operational Concept

Requirement’s Validation: Mapping Requirements to Functionality

Risk Identification

Training Input

Information Architecture

Test Plan & Procedures BPR

Tasks

Technology Evaluations

Use Case InputActivity Diagrams

Sequence Diagrams

Business Objects

Etc…

Interface Design

Deferred / Derived

Requirements

Strategic Analysis

Now Next After Next

Capability Delivery Roadmap

BLOCKS

Capabilities

Now Next After Next

Capability Delivery Roadmap

BLOCKS

Capabilities

Business Cases

Capability Value Chains

Converting Needs into Requirements , Communicating Results

Mission Engineering Summary

28


Client Project Name Client Project Name

NGA Integrated Exploitation Capability (IEC)

NRO XOComm

Air Force

Space Based Blue Force Tracking

NGA Big Idea

DISA Traces2 NSA Stone Mason

Joint Staff

Airborne ISR Requirements Based Allocation

DIA HUMINT/CI Comms Architecture Eval

DIA JIVA DISA Meteorological Info System Terminal (MIST)

SPAWAR Strike Fighter Training System (SFTS)

NGA GeoScout

Booz Allen Has Successfully Applied Mission Engineering to a Wide Range of Clients and Products

29


Value and benefits of using Mission Engineering

Fosters Communication and Understanding

Translates mission needs into engineering requirements

Reduces interpretation of textual requirement

Illustrates user functions within work flow

Illustrates COTS/GOTS/Custom code integration/interfaces

Supports the early identification of risk; technical, business and program

Supports product/artifact reuse across the system/software engineering lifecycle

Support the development of test and training material

Supports development of DODAF views

Date post:	27-Mar-2015
Category:	Documents
Upload:	kaitlyn-ellis
View:	212 times
Download:	0 times