Publicly Available Raytheon Input To NextGen SME Requirements

Publicly Available Raytheon Input To NextGen SME Requirements

Publicly Available Raytheon Input To NextGen SME Requirements Raytheon Company Bobbi Young, Christopher Finlay, Louisa Guise, Marty Ray, Ron Williamson, Stephanie Chiesi This document does not contain technology or technical data controlled under either the U.S. International Traffic in Arms Regulations or the U.S. Export Administration Regulations. Publicly Available Introduction Context SysML v2 Working Group Joint INCOSE/OMG group Developing requirements for and RFP to solicit proposals from industry and tool vendors for the next generation systems modeling language, SysML v2

Wiki page is available at: http:// www.omgwiki.org/OMGSysML/doku.php?id=sysml-road map:sysml_assessment_and_roadmap_working_group System Modeling Environment (SME) Summarized in the figure to the right Non-Export Controlled See Slide 1 02/06/2020 2 Publicly Available

Introduction Raytheon MBSE TIG Workshop Goal Raytheon Topics Covered To develop a set of requirements, use cases, measures of effectiveness for the next generation system modeling environment To share these requirements with the industry working group To influence the industry inputs to the SysML v2 standards process Objective Convene several virtual meetings to brainstorm on Gaps and Requirements Convene a face to face workshop to finalize the Raytheon community inputs to the next generation SysML language standard

Product Line Architecture Collaboration with External Partners Standardized API Methodology Enablement Model Analytics Reporting Approach Capture Gaps in the current SysML 1.x language standard

Capture Requirements (shall statements) Capture Roles & Use Case Scenarios Capture Measures of Effectiveness Non-Export Controlled See Slide 1 02/06/2020 3 Publicly Available Product Line Architecture Use Cases Non-Export Controlled See Slide 1

Publicly Available UC: Indicate Model Variations (1 of 2) GAP: Ability to indicate and visualize model variants Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling language shall provide standardization of product line terminology as it applies to modeling environments and notation. The modeling language shall provide a stereotype to identify variant model elements and views. The model shall provide the capability to define and visualize variation points, variant model elements, and views. The modeling environment shall provide the capability to have variants based on structural and dynamic/behavioral characteristics. The modeling environment shall provide the capability to identify and model a catalog of variant features. The modeling environment shall provide helper tools to automatically identify and indicate variant model elements associated with a defined variant model element (e.g. if a block is defined as a variant, then the model will automatically identify any ports, value properties, operations,

relationships, swim lanes, object lifelines, etc. as variants). Non-Export Controlled See Slide 1 Publicly Available UC: Indicate Model Variations (2 of 2) Driving Requirements (cont): If a variant model element is deleted, the modeling environment shall delete any associated variant model elements. For example if a block is variant then the associated parts, relationships, value properties, and ports would also be variant and need to be deleted. The modeling environment shall provide the capability to organize variants (e.g. configurations of a missile or test equipment) The modeling environment shall provide the capability to define user defined rules associated with variant features such as required features, features that cannot co-exist, features that have security or regulatory constraints. The modeling environment shall execute the user defined rules when building product configurations. The modeling environment shall provide the capability to define used defined rules

associated with variant model elements (e.g. identify a model element as COTS would not allow a port to be defined as a variant) The modeling environment shall execute the user defined rules when creating or modifying model elements. Non-Export Controlled See Slide 1 Publicly Available UC: Manage Reusable Model Elements GAP: Ability to structure a model into reusable elements and behaviors that can be shared across multiple models without clone and own techniques Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling environment shall provide the capability to integrate a referenced model element with no linkage limitation due to read only access. The modeling environment shall provide the capability to view model elements from different models.

The modeling environment shall provide the capability to identify reusable model elements by comparing the usage of model elements across individual models. The modeling environment shall provide the capability to build a catalog of reusable capabilities. The modeling environment shall provide the capability to reuse components from a repository (classified and unclassified) within a model. Non-Export Controlled See Slide 1 Publicly Available UC: Manage Product Unique System Solution GAP: Ability to define a product based on a set of common and variant model elements and behaviors GAP: Ability to maintain product definitions Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling environment shall provide the capability to define product model configurations through user identification of a combination of common and variant model elements and their views from the core model.

The modeling environment shall provide the capability to manage (add, delete, or modify) product model configurations for unique products. The modeling environment shall provide the capability to easily view product variation combinations to define products known and those that could be defined for future marketing opportunities. Non-Export Controlled See Slide 1 Publicly Available UC: Configure Product Solution Model GAP: Ability to generate a product model from a defined product set of common and variant model elements and behaviors Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling environment shall provide the capability to configure a product solution model based on the product model configuration definition with all variation identification removed. The modeling environment shall provide the capability to regenerate a configured product at any time. The modeling environment shall provide the capability to merge program specific modifications with

product line modifications. The modeling environment shall provide the capability to include program specific modifications into the superset as variations. The modeling environment shall provide the capability to limit the ability to modify variations outside of the core superset. The modeling environment shall provide the capability to load or remove modular portions of the model. The modeling environment shall provide the capability to configure for security (e.g. Select DISA Security Technical Implementation Guides (STIG)s) Non-Export Controlled See Slide 1 Publicly Available UC: Merge Unclassified With Classified Model Data (1 of 2) GAP: Ability to easily merge unclassified models with classified models Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling environment shall provide the capability to maintain models in separate unclassified and classified environments with the ability to merge the unclassified data with

the classified data to produce a product configuration. If a model is in multiple environments, The modeling environment shall provide the capability to specify the master as read only when moving models from one environment to be merged with a model in another environment. The modeling environment shall provide the capability to indicate security classification and EXIM markings on model elements and views. The modeling environment shall provide the capability to define and apply rules to enforce security markings. Non-Export Controlled See Slide 1 Publicly Available UC: Merge Unclassified with Classified Model Data (2 of 2) Driving Requirements (cont): The modeling environment shall provide the capability to report on model elements and views not tagged with the appropriate security classifications. The modeling environment shall provide the capability to highlight a conflict when a model

element and related model element do not have consistent security classifications. The modeling environment shall provide the capability to apply specific markings to different products within the product line ( some product configurations in the PL may require different security markings due to association with a particular customer security classification guide). The modeling environment shall provide the capability to merge models at a finer granularity than package level. (For example, an activity flow may have an action whose variant may be of different classifications. When merging an unclassified model with a classified model, sometimes the variant may be in one environment vs the other depending on the product configuration) The modeling environment shall provide the capability to do trusted downloads on models. Non-Export Controlled See Slide 1 Publicly Available UC: Exchange Model Variant Information GAP: Ability to capture and exchange product variant information with other tooling domains (i.e. requirements, simulation models, test environments, hardware variants)

Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling environment and modeling language standards shall provide the capability to exchange variant design information with 3rd party tooling. Each design tool needs an understanding of product variation and how those variations affect other designs. (not just linking) Non-Export Controlled See Slide 1 Publicly Available UC: Report PLA Metrics GAP: Ability to generate model variation metrics Actor: Systems/Software/Test Engineering, Architect Driving Requirements: The modeling environment shall provide the capability to generate reports on PLA variation management to include: Model elements and views included in each product configuration Instances and location of each model element/view variant associated with a particular

capability/feature/parameter Unused model variants Identification of possible reusable variant components Impact (identify whats affected) of setting a model element as a variation on all related elements and views Number of products a variant is associated with Number of products a reusable component is associated with Test coverage for variants Internal simulation coverage executable model simulation. Cost associated with variants. ( When doing product trades, need to understand the cost of each product configuration) Non-Export Controlled See Slide 1 Publicly Available PLA Measures of Effectiveness Expressive: Ability to express feature catalog, feature variants, variation points, variant model elements and associated properties, variant views

Manageable: Ability of the modeling environment to provide helpers to automate/identify associated variations within a model to reduce modeling time and errors Manageability: Ability to manage identify and manage product configurations based on feature variations Presentation: Ability to automatically generate customer specific product model to reduce delivery time Interoperability: Ability to exchange variant information with other system design environments Non-Export Controlled See Slide 1 Publicly Available Collaboration With External Partners Use Cases Non-Export Controlled See Slide 1

Publicly Available Systems Modeling Environment Collaboration with external "partners" We need to be able to interact with organizations external to Raytheon in a model based way What do we mean by external partners? Customers Suppliers Competimates other defense companies with whom we are partnered on contracts Other Raytheon business units that may not be ITAR permitted (non US persons) Non-Export Controlled See Slide 1 Publicly Available

UC: Protect Information While Sharing And Creating Model (1 of 2) Gap: Protect information this includes protecting data rights while sharing key pieces of information (IP, ITAR, contract specific information requirements, ability to mark classification of pieces of models beyond just a comment on a diagram) GAP: Partition information - Ability to hide/expose different level of model elements and model information from different users (ex. When working with subcontractors that may not be allowed to see parts of the model due to competitive nature) GAP: Ability to protect model information that only certain stakeholders are allowed to see (role based permission, ability to mark information, etc.) Ability to partition data visibility and protect information across the entire environment GAP: Ability to share models across firewalls and collaborate with stakeholders Tool to tool visibility and protection Ability to partition data visibility and protect information across the entire environment Non-Export Controlled See Slide 1

Publicly Available UC: Protect Information While Sharing And Creating Model (2 of 2) Actors: Raytheon systems engineers, suppliers, EXIM, legal Driving Requirements: The modeling environment shall provide protection of intellectual property while creating a unified, robust system model while being accessed by multiple suppliers. The modeling environment shall provide protection of ITAR restricted information from various suppliers on an individual basis (each conforming with the rules associated with the individual legal disclosure licenses). The modeling environment shall provide the ability to mark the classification and controls for each part of the model. This may be different in the same model depending upon the suppliers involved.

Non-Export Controlled See Slide 1 Publicly Available UC: Manage configuration Over Time And Across Stakeholders (1of 2) GAP: Temporal Management Ability for difference disciplines to be able to update models at different stages. For example.systems develop use case scenarios to capture end state. Systems integration uses these scenarios but only portions of them as hardware and software become available. As the scenarios are being changed over time, test must keep them based on the test they need do at any particular time. Want to use the same scenario flows but they are updated at different intervals. Ability to manage a phased approach of a capability or architecture over time GAP: External management

To align with external sources (PLM, workflow, engineering tools, etc.) also accessing the data For baseline and configuration control For product line engineering and total enterprise solution development Ability to share models with various stakeholders (maybe as "read only") - how do you get the models integrated? Linking and integrating models GAP: Configuration management Ability to appropriately mark the configuration state (e.g. initial, draft, final, deprecated) of pieces of a model beyond just a comment on a diagram Ability to configuration manage models from external source Non-Export Controlled See Slide 1 Publicly Available UC: Manage configuration Over Time And Across Stakeholders (2 of 2)

Actors: Raytheon systems engineers, suppliers, other Raytheon disciplines Driving Requirements: The modeling environment shall provide a mechanism for managing the configuration of the system model as the various stakeholders (suppliers, other discipline engineers) make changes. These modifications may happen at different times. The modeling environment shall be capable communicating changes to baselines and versions with multiple stakeholders. The modeling environment shall provide the capability to mark the configuration state (e.g. initial, draft, final, deprecated) of pieces of a model. The modeling environment shall provide the capability to manage updates to the models over time. For example, Systems Engineering updates a model at a different cadence then Test Engineering. Systems takes a holistic view when developing scenarios, Test needs to test per build and what HW and SW is available. Non-Export Controlled See Slide 1 Publicly Available

UC: Collaborative review with stakeholders GAP: Ability to collaborate on model visualization across stakeholders (including real-time development or model review) Actors: Raytheon systems engineers, suppliers, other Raytheon disciplines, customers Driving Requirements: The modeling environment shall provide the capability to continually and collaboratively review models with external stakeholders. The modeling environment shall provide the capability to capture comments on different versions of the model. The modeling environment shall provide the capability to report status of comments against a model. The modeling environment shall provide the capability to apply the appropriate access control to the model comments. The modeling environment shall provide the capability to recognize a product line asset and be able to indicate when comments/changes apply to all variants. Non-Export Controlled See Slide 1

Publicly Available Collaboration With External Partners Measures of Effectiveness Ability to share and collaborate on model information for development and reviewing while protecting Intellectual Property and ITAR/Classification restrictions with multiple stakeholders/suppliers. Non-Export Controlled See Slide 1 Publicly Available Standardized API Use Cases Non-Export Controlled See Slide 1

Publicly Available UC: Integrate System Models with Suppliers GAP: Ability to integrate and execute system models developed by our suppliers with our own integrated system model. (Can also facilitate transferring our models to third parties) GAP: Improve ability to integrate designs with third-party systems Actors: System Engineers Driving Requirements: The model execution API shall be standardized across SysML modeling environments to run on multiple SysML modeling tools without modification to facilitate third party model integration, execution and verification. Model Execution APIs shall be well documented with easy access to documentation. The System Modeling environment shall have semantics for indicating where a third party model integration point exists. If the capability/element/symbol is available from the User Experience, it shall be available in the API. Tool vendor's UX shall provide, at a minimum, a precise, exact set of SysML elements for SysML diagrams (not a slight variation)

Non-Export Controlled See Slide 1 Publicly Available UC: Apply Automation Scripts Across SysML Modeling Tools GAP: Ability to apply automation scripts to the creation/modification of elements within the integrated system model that were created using different tools (e.g., Rhapsody, Magic draw). GAP: Ability to manipulate models across different SysML tools using a common programming API Actors: System Engineers Driving Requirements: Modeling APIs shall be standardized across SysML modeling environments to run on multiple SysML modeling tools without modification to the automation program using the API, to facilitate third party model integration, execution and verification. Define standard API calls based on SysML standard from creation, modification and

destruction of SysML elements to be used across all SysML modeling tools. Tool vendors shall provide the ability to use the API as described in the above bullet. Non-Export Controlled See Slide 1 Publicly Available UC: Apply Automation Scripts Across Modeling Tools in Diverse Domains (1 of 2) GAP: Ability to apply automation scripts to the creation/modification, linking and checking of elements within the integrated system model that were created using different tools (e.g., CAD, SysML, UML, Matlab, FMI/FMU, etc...). GAP: Ability to inspect, link to , and /or manipulate model elements and structure across different model types. (e.g., CAD, SysML, UML, Matlab, FMI/FMU, etc...) Actors: SE, SW, HW and Life Cycle Engineers Driving Requirements: Modeling APIs shall be capable of creating or modifying model data across multiple model types

without modification to the automation program using the API, to facilitate third party model integration, execution and verification. Non-Export Controlled See Slide 1 Publicly Available UC: Apply Automation Scripts Across Modeling Tools in Diverse Domains (2 of 2) Driving Requirements (cont): The modeling language shall define a set of common cross model (SysML, UML, CAD, etc..) relationships between model elements The modeling environment shall implement these cross model relationships between different tool vendors. The modeling API shall define a generic "export/import" APIs that are precise and complete (i.e., no data loss). The modeling environment shall provide the ability to access "attributes" from other

models (e.g., wire diagram from CAD model) to facilitate design checking and consistency and requirements compliance while maintain but must be the single source of truth. The modeling environment shall provide the ability to raise an issue across other models based on above linkages. Non-Export Controlled See Slide 1 Publicly Available UC: Review Models Across Different Environments GAP: Ability to apply automation scripts to create a design review environment of the certain aspects of the integrated system model where individual model elements were created using different environments GAP: Improve ability to hold model reviews across different modeling tools/environments Actors: All stakeholders.

Driving Requirements: The System Modeling Environment shall enable model based design reviews across multiple model types. Non-Export Controlled See Slide 1 Publicly Available Standardized APIs Measures of Effectiveness Compliance with consumption by the different discipline standards (e.g., SysML, UML, IGES, STP, etc..) # of attributes of tool accessible by the API or vice versa Non-Export Controlled See Slide 1 Publicly Available Methodology Enablement

Use Cases Non-Export Controlled See Slide 1 Publicly Available UC: Tailor Modeling Environment Based On User Experience GAP: Varying levels of modeling expertise [Beginner, Expert,] Actors: Seasoned MBSE practitioners and Systems Engineers new to system modeling Driving Requirements: The System Modeling Environment (SME) shall present the user with specific sets, or subsets, of tools, menu options and contextual help corresponding to the user experience level and roles defined in the specification. (Could be standardized on the 4 levels of OCSMP certification.) The modeling environment shall provide a contextual menu or iconology for setting the display properties of an object, including word wrap, text formatting, color, and visibility of attributes and compartments. The modeling environment shall provide training vignettes (animation or videos) for performing various tasks. (e.g. similar to that provided by Microsoft Office products) The modeling environment shall implement a common set of shortcuts, or "hot keys".

The modeling environment shall allow the user to record macros (generate scripts graphically). Non-Export Controlled See Slide 1 Publicly Available UC: Provide Methodology Enablement GAP: Provide/define recommended methodology(ies) Actor: Systems Engineer/Architect Driving Requirements: The SysML Specification shall present one or more methodologies to be implemented by the modeling environment. The methodology(ies) shall define a standardized project structure, or framework, optimized for each methodology. Methodology project structures shall be designed to support collaboration and configuration management.

Non-Export Controlled See Slide 1 Publicly Available UC: Provide Automated Methodology Enablement Tools GAP: Automation supporting (aligned with) methodology workflow. GAP: Lack of standard methodology overlays (as profiles, libraries, automation, etc.) GAP: Lack of automation standards (requires extra key strokes, replication of data, etc.) Actor: Systems Engineer/Architect Driving Requirements: Standardized tool automation shall be implemented to support the methodologies presented in the SysML Specification. A common "core" set of automated tasks shall be provided in the modeling environment. A standardized method for extending automated toolsets shall be adopted. Automatic model validation shall be implemented to ensure that changes made by the user to the model structure do not cause problems with automated scripts. Tool automation shall support collaboration and configuration management by providing automatic "check-out",

or locking for edit, of all elements that will be affected by execution of an automated task. The intent of this requirement is to prevent unpredictable or confusing behavior of automated scripts when all of the required model scope is not reserved for editing. Non-Export Controlled See Slide 1 Publicly Available Methodology Enablement Measures of Effectiveness Time to set up a new project. Number of steps to complete a modeling task. Percent of tasks which are automated.

Number of different methodologies supported. Percentage of coverage of documentation (and depth of coverage?) True/False: Supports a methodology with automated workflow Implements a predefined core set of automated tasks Complies with standardized method of extending automated toolsets A standardized project structure, or framework is defined for each methodology Automatic validation of user changes to model structure Non-Export Controlled See Slide 1 Publicly Available Model Analytics Use Cases Non-Export Controlled See Slide 1

Publicly Available UC: Report System Model Completeness GAP: Report on the completeness of the model to show a level of "done" GAP: Trade Studies and Analysis Actor: Systems Engineer/Architect Driving Requirements: The modeling environment shall provide a standard calculation and/or processing of completeness. This could include an evaluation of: Couplings/Relationships between model elements Fundamental principles Are all elements/artifacts consistent? The modeling environment shall provide an establishment of scoring or weighting to quantify completeness What is the denominator? This will evolve with program phase The modeling environment shall provide a manner to show completeness of requirements traceability The modeling environment shall provide a way for a subject matter expert to influence the determination of completeness (if customization is needed)

Non-Export Controlled See Slide 1 Publicly Available UC: Capture System Performance Analyses GAP: Capture performance Analyses and their ties to the system model GAP: Trade Studies and Analysis Actor: Systems Engineer/Architect Driving Requirements: The modeling environment shall provide a capability for tolerance (stack-up) analyses to show verification and validation at lower levels. The modeling environment shall provide a capability for constraint/parametric analyses to show verification and validation at lower levels. These capabilities shall be automated What semantics are needed? These capabilities shall incorporate probabilities into models for these analyses to deliver increased value. The modeling environment shall provide optimization parameters (e.g. cost, performance, complexity) The modeling environment shall provide a capability to display predicted (flow-up) performance and specified (flordown) performance for a given (instance? Configuration?) of the model.

The modeling environment shall provide a capability for governance hooks to track trade study excursion analyses. These are analyses performed in other models/tools) Non-Export Controlled See Slide 1 Publicly Available UC: Extend SysML For Impact Analysis And Analytics GAP: Extend SysML type relationships into other domains for impact analysis and analytics GAP: Trade Studies and Analysis Actor: Systems Engineer/Architect Driving Requirements: There shall be SysML constructs that address Verification and Validation concepts in the language. This should not require stereotypes that are unique to a model or project/program, etc. but are standardized in the language for consistency across the environment and in cross business use. There shall be SysML constructs that address common analytical and performance metrics to

be connected to model reporting and analyses. Examples: value types and constraints for cost, reliability, availability, risk, complexity Non-Export Controlled See Slide 1 Publicly Available UC: Model Simulation Standards Compatibility GAP: Execute SysML based models outside of the SysML tool with an execution engine that allows simulation with other domain models (i.e. FMI, Proprietary implementations/tools (Model Center, Syndeia)) Actor: Systems Engineer/Architect Driving Requirements: There shall be synchronization between the SysML and FMI standards. Non-Export Controlled See Slide 1 Publicly Available

UC: Synchronize Parametric Diagrams With External Mathematical Models GAP: The relationship between high level system (logic) modeling and mathematical model GAP: Synchronize use of Parametric Diagrams with (external) mathematical models to maintain consistency of relationships established in SysML across the models Actor: Systems Engineer/Architect Driving Requirements: The modeling environment shall provide a means to show if a requirement is being violated/contradicted and vice versa to the external link Non-Export Controlled See Slide 1 Publicly Available UC: Visualization Of Analyses And Analytics

GAP: How can the models (SysML and total digital system models) and the associated analytics on the models be better understood and represented through visualization Actor: Systems Engineer/Architect Driving Requirements: There shall be a measurement of "-ilities" included in the standard. There shall be a capability to visualize the "-ilities" in the standard. This includes cost/CAIV, reliability, availability, etc. There shall be a standard layout/formatting of models so that layout and colors are consistent between tools. Cross cutting with API There shall be a standard approach for "attached figures/files" as part of the transfer between tools Non-Export Controlled See Slide 1 Publicly Available UC: Represent MOEs GAP: Model Quality

GAP: How to represent MOEs represented in the model Actor: Systems Engineer/Architect Driving Requirements: There shall be a standard implementation for representing MOEs (KPPs, TPMs, other measures) in the language. Such as matrix views Non-Export Controlled See Slide 1 Publicly Available UC: Perform Consistency Check On Models GAP: Model Quality GAP: Notify model users of consistency check results on the models GAP: Consistency check models done for SysML relationships established to model elements outside of the SysML model (other engineering domains)

Actor: Systems Engineer/Architect Driving Requirements: There shall be synchronization between SysML compliant tools and OSLC. Tools shall implement both standards to be compliant. Non-Export Controlled See Slide 1 Publicly Available UC: Execute Scenario Analysis GAP: The ability to extract related portions of the system for subsystem analysis while maintaining connectivity to limiting factors that are not involved in the analysis, but impact possibilities Actor: Systems Engineer/Architect Driving Requirements: There shall be a standard for model analysis configuration control. This needs to be communicated, and multiple options may be necessary in the standard

Non-Export Controlled See Slide 1 Publicly Available Model Analytics Measures of Effectiveness Completeness Relationships established Consistency of elements/artifacts Inclusion of optimization/performance parameters Something else determined by a subject matter expert Compliance

Number of requirements/parametric constraints that are violated in current implementation/execution "-ilities" A way to quantify the different additional attributes of the system True/False: Implements probabilistic assessment in execution and analyses Includes V&V concepts in the standard language Synchronized with FMI Non-Export Controlled See Slide 1 Publicly Available Reporting Use Cases Non-Export Controlled See Slide 1

Publicly Available UC: Distribute Model Information In A Human Readable Format GAP: Ability for stakeholders and distributed team members to access the information in the model Driving Requirements: The System Modeling Environment (SME) shall provide easy to use mechanisms to distribute model information in a human readable format. The SME shall provide flexible, updatable and easy to use templates to generate human readable content. The SME shall provide WYSIWYG mechanisms to simplify the distribution of model information based on user definable viewpoints and views. The SME shall provide mechanisms to control access to distributed model information. Non-Export Controlled See Slide 1

Publicly Available UC: Interactively View Model Information GAP: Ability to be able to interactively view the model Driving Requirements: The SME shall provide an interactive viewing mechanism for model browsing to include Text and graphic hyperlinking across the model information Structured graphic viewing to allow easy to use pan, zoom and filtering features while maintaining human readable content Non-Export Controlled See Slide 1 Publicly Available UC: Create Report Template GAP: Easier / standardized report/document generation GAP: Ability to easily create a WYSIWYG (what you see is what you get)

report template as a more intuitive way to create and generate reports based on the model content GAP: Easily create a report template based on an intuitive rendering of the final report content Driving Requirements: The SME shall provide easy to use and standardized report generation mechanisms The SME shall provide intuitive to use WYSIWYG (what you see is what you get) report template mechanisms Non-Export Controlled See Slide 1 Publicly Available UC: Interactively View Model Content Across Geographically Distributed Team GAP: standards for visualization -- how do we make our models presentable for external stakeholders

GAP: Ability to synch up the contents of reports with the model, such that, as the model changes the corresponding report content changes GAP: Distributed team members and subcontractor to be able to interactively view the model, rather than just print outs of the diagrams Driving Requirements The SME shall provide mechanisms to support visualization standards for external stakeholders including Managers, Customers, other disciplines who may require "non-system engineering" oriented renderings of the system model information The SME shall provide mechanisms to maintain consistency between the system model and the external rendering of the model (e.g. if the model changes, the rendering changes or if the rendering is changed by an authorized stakeholder the system model is also changed. The SME shall provide change management mechanisms to manage the system model changes based on a wider range of external stakeholders Non-Export Controlled See Slide 1 Publicly Available

UC: Generate Reports For Model Dependencies And Version Differences GAP: Lack of reporting mechanisms to show differences between versions and variants of models GAP: Lack of reporting mechanisms to capture dependencies between models Driving Requirements: The SME shall provide mechanisms to visualize model dependencies. The SME shall provide mechanisms to generate reports on model dependencies The SME shall provide mechanisms to visualize model version differences The SME shall provide mechanisms to generate reports on model version differences

The SME shall provide mechanisms to visualize variants within models The SME shall provide mechanisms to generate report on variants within models. Non-Export Controlled See Slide 1 Publicly Available Reporting Measures of Effectiveness Ease of Use: Steps to complete a modeling task (reduce/minimize) Learning Curve: Assumes maturity levels.how long to get from one level to another Complexity: Length of time to generate first report (reduce/minimize)

Productivity Ease of viewing Presenting/delivering to a customer Presenting/delivering to Engineering Leadership Team Level of Automation: From zero (all manual tasks) to Full automation (easy button click) for report generation tasks Report complexity Report Quality Cost to generate report (time, resources) Schedule: Time to setup and generate report Metrics for what CDRLs can be created / completed at the current point in time Non-Export Controlled See Slide 1

Recently Viewed Presentations

  • Living Cells - Oronsay

    Living Cells - Oronsay

    Stem Cells. Stem cells are only found in animals and they are unspecialised, i.e. they have no specific function.. They can: Reproduce repeatedly by mitosis and cell division and remain unspecialised. Develop into specialised cells when required to replace damaged...
  • After studying this chapter, you should be able to:

    After studying this chapter, you should be able to:

    Title: After studying this chapter, you should be able to: Last modified by: Pc Created Date: 6/17/2002 7:15:40 PM Document presentation format: On-screen Show (4:3)
  • Chapter 5 The Skin and Dermatologic Drug Therapy

    Chapter 5 The Skin and Dermatologic Drug Therapy

    If patients have a skin problem, pharmacy technicians can get involved. Can help identify patients with likely problems. ... Are vitamin A derivatives. Mechanism of Action: increase cell turnover in follicles, which pushes clogged material of the pores.
  • Monday, October 13th, 2014

    Monday, October 13th, 2014

    What was the other reason that Iago hates Othello? Themes. Okay, first lets list what some of the main themes are in Othello. Did we get them right? Jealousy. Love or True Love. ... You also need to include 2-4...
  • Implementation of National Urban Health Mission (NUHM) Joint

    Implementation of National Urban Health Mission (NUHM) Joint

    About NUHM. National Urban Health Mission (NUHM) was approved on 1st May, 2013 as a sub-mission of National Health Mission (NHM) Aims to establish and strengthen primary healthcare delivery in urban areas with focus on slums and vulnerable population.
  • Презентация PowerPoint

    Презентация PowerPoint

    Acri.Tec GmbH, Germany Acri.Sil-oI 1000, Acri.Sil-oI 5000 Micromed, Italy PDMS 1000, PDMS 2000, PDMS 5000 Alcon, USA Silicone™ 1000
  • Course 7: Electronics

    Course 7: Electronics

    ( to be displayed when flashcard moused over) Use . 2,5mm . Norsk (2+E) cable . to supply a isolator that will allow the water heater to be supplied from. Option 2: Use . 2,5mm flat twin and earth (2+E)...
  • The Invisible Warrior - Weebly

    The Invisible Warrior - Weebly

    The Invisible Warrior The invisible warrior thought about talking to the chief. The chief had three daughters. Perhaps he could marry one of them. But the warrior had heard that the three sisters were mean. Truthfully, the two oldest sisters...