INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario - PowerPoint PPT Presentation

Loading...

PPT – INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario PowerPoint presentation | free to download - id: 40532d-NzdhM



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario

Description:

INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon ron.williamson_at_incose.org Jan 21-22, 2012 – PowerPoint PPT presentation

Number of Views:57
Avg rating:3.0/5.0
Slides: 17
Provided by: omgwikiOr
Learn more at: http://www.omgwiki.org
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario


1
INCOSE (MBSE)Model Based System Engineering
Integration and Verification Scenario
  • Ron Williamson, PhD
  • Raytheon
  • ron.williamson_at_incose.org
  • Jan 21-22, 2012
  • INCOSE IW12 MBSE Workshop

15
INCOSE IW12 MBSE Workshop
2
Integration Verification Scenario
  • Concept of Operations
  • Word document and Scenarios Model
    (Behavior/Structure)
  • Requirements Architecture
  • Word Document and Requirement Objects,
    Architecture Framework Languages
  • Design and Implementation
  • Diagrams and Word document à SW and HW Models
    (Form Function)
  • Test
  • Plans and Test Models
  • Integration
  • Model Integration
  • Verification
  • Model Verification
  • Operation and Maintenance
  • Operational Models

17
INCOSE IW12 MBSE Workshop
3
Integration Verification Scenario
Project Modeling
Operations Maintenance
Concept of Operations Model
Model Synch
Model vs Implementation
Project Definition
Requirements Architecture Models
System Verif Validation
Model vs Impl.
Model Synch
Project Test Integration
Detailed Design Models
Integration, Test Verification
Model Synch
Model vs Impl.
Implementation
Time
18
INCOSE IW12 MBSE Workshop
4
Integration Test Scenario
  • Problem Description
  • Challenges It's all about better
    communication!!
  • Use Cases
  • Opportunities How can MBSE help?
  • Experience (lessons learned)
  • Methodologies (Process, Methods, Tools)

5
Challenge Summary
  • Communication gaps and/or mis-understanding
    across teams, disciplines and phases
  • Funding early involvement of integration and
    verification planners and designers
  • IVV teams are not working in the model
  • Lack of consistency across lifecycle team
  • IVV ends up fixing problems from early phases,
    increasing risk, cost and schedule
  • No benchmarking has been performed to help gather
    metrics
  • Lack of knowledge transfer from integrator/tester
    to the knowledge base (manually or via tool)

6
Use Case Summary
  • Choose development model
  • Introduce inter disciplines early
  • Share models across phases
  • Bring cross functional teams together using the
    models
  • Validate science merit functions using models
  • Assess performance/quality risks using the models
  • Use models to perform failure/fault analysis
  • Testers (must now) validate the models
  • Proactive integration (continuous)
  • Generate test plans/optimization from the
    analysis models
  • Perform risk assessment based on the models
  • Customers use model based acquisition
  • Help with incremental integration using models

7
OpportunitiesHow can MBSE Help?
  • Improved, more rigorous communication with and
    across disciplines including across analysis and
    IVV teams.
  • Support for continuous integration
  • Better visualization and communication within
    domains by SysML
  • Improve opportunities for automating tasks across
    analysis and IVV
  • Better linkage between system elements/interfaces
    and requirements
  • Improve coverage and gap analysis

8
Meeting NotesIV Scenario Breakout Session

9
Challenges
  • Early involvement of the integration planners and
    designers.
  • Fidelity of model keeping models up to date
    with the latest state of affairs
  • Model management and maintenance
  • VV folks not working in the model
  • Should create a model of the test environment
  • Duplication of effort we have lots of models
    of the same thing, How do you know you are
    testing the right thing?
  • Model validation
  • Consistency across lifecycle
  • Define problem cost, quality and include Use
    cases
  • Early VV
  • Consistent IV Funding

10
Challenges
  • IVV fix problems from early cycle
  • Better communication coordination
  • Formal methods
  • Cost avoidance
  • Test environment a development effort also
  • Assumption of Vee model? Alternatives are
  • Spiral integration
  • Functional integration
  • Simulate, emulate, test and validate
  • Plug and play IT

11
Challenges
  • Derive test cases from systems model
  • Concurrent Engineering
  • No benchmarking 
  • Opportunities/Successes
  • Communication better communication standards
    e.g. SysML
  • Things transferred between the sides of the VEE
  • Push UC/Requirements, UC/CONOPS, UC/architecture
  • Pull What model influence from IVV
  • Minimize integration risk through use of
    simulations and emulations
  • Capture dependencies between each phase.

12
Challenges
  • Method Use of SysML BDDs
  • High level activity diagrams
  • Model effort (Minimal) 50 schedule
    reduction/avoidance
  • Apply SysML satisfy links between requirements
    and system model
  • Coverage analysis/gap analysis e.g. Have all
    events passing through a port been tested?
  •  Model based design helps reduce defects
  • Methodology (process, methods and tools)
  • Does SysML/architecture/etc help?
  • Vee model If modeling on the left side, how do
    we pass on information to the right side?
  • Tools manual -gt more automation only 50 being
    tested
  • Knowledge transfer from tester to tool/knowledge
  • Tying models together e.g. model center

13
Use Cases
  • UC/Choose a development model
  • UC/introduce interdisciplinary early
  • UC/IVV drivers define main topics, models
    IVV in charge?
  • UC/Share models constrained by proprietary
    information
  • UC/Subcontractor role Interfaces, performance,
    budget, CONOPS
  • Models integration plans
  • UC/SE communication (Models as enabler) Bring
    team together
  • UC/SE validate science merit functions
  • Lost trades/risk
  • UC/SE performance/quality
  • Dynamic models
  • UC/Domain knowledge experience

14
Use Cases
  • UC/Fault Failure analysis
  • UC/perform inter/intra model consistency checking
  • UC/USE MBE methods to solve IVV problems
  • UC/Models used to help better organize
    steps/artifacts in system Vee
  • UC/Proactive integration
  • UC/Test planning and optimization
  • UC/Continuous integration support
  • UC/Agile system development
  • UC/New test role to validate the model
  • UC/Assess risks based on model
  • UC/Model based acquisition
  • UC/Help with incremental validation

15
OpportunitiesHow can MBSE Help?
  • Tying models together e.g. model center
  • Method Use of SysML BDDs
  • High level activity diagrams
  • Model effort (Minimal) 50 schedule
    reduction/avoidance
  • Apply SysML satisfy links between requirements
    and system model
  • Coverage analysis/gap analysis e.g. Have all
    events passing through a port been tested?
  • Model based design helps reduce defects
  • Communication better communication standards
    e.g. SysML
  • Methodology (process, methods and tools)
  • Does SysML/architecture/etc help?
  • Vee model If modeling on the left side, how do
    we pass on information to the right side?
  • Tools manual -gt more automation only 50 being
    tested
  • Knowledge transfer from tester to tool/knowledge

16
Opportunities
  • IVV fix problems from early cycle
  • Better communication coordination
  • Formal methods
  • Cost avoidance
  • Test environment a development effort also
  • Assumption of Vee model? Alternatives are
  • Spiral integration
  • Functional integration
  • Simulate, emulate, test and validate
  • Plug and play IT
  • Things transferred between the sides of the Vee
  • Push UC/Requirements, UC/CONOPS, UC/architecture
About PowerShow.com