User Tools

Site Tools


mbse:telescope_mbse_sig_meetings_pasadena_april_2017

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
mbse:telescope_mbse_sig_meetings_pasadena_april_2017 [2018/06/14 19:36]
acrawford
mbse:telescope_mbse_sig_meetings_pasadena_april_2017 [2018/07/09 18:14] (current)
acrawford old revision restored (2017/04/19 18:24)
Line 1: Line 1:
 ====== Participants ====== ====== Participants ======
  
-ANU+TMT
-  * Jon Nielsen ​(jon.nielsen@anu.edu.au) +  * Jamie Nakawatase ​(jamie@tmt.org
- +  * Gelys Trancho ​(gtrancho@tmt.org
-CTA: +  * Kayla Hardie ​(khardie@tmt.org), dial-in ​
-  * Igor Oyer (igor.oyer.vellejo@desy.de+
-  * David Melkumyan ​(david.melkumyan@desy.de) +
-  * Peter Wegner (peter.wegner@desy.de)+
  
 GMT: GMT:
   * George Angeli (gangeli@gmto.org)   * George Angeli (gangeli@gmto.org)
-  * Amanda Cristina Santana ​(asantana@gmto.org) +  * Josema Filgueira ​(jmf@gmto.org) 
- +  * Brian Walls (bwalls@gmto.org) 
-Keck: +  * John Miles (jmiles@gmto.org) 
-  * Shui Hung Kwok (skwok@keck.hawaii.edu)+  * Adam Contos ​(bwalls@gmto.org) 
 +  * Oliver McIrwin (omcirwin@gmto.org) 
 +  * Rebecca Bernstein (rbernstein@gmto.org) 
 +  * Maria Hernandez (mhernandez@gmto.org) 
 +  * Leni Malherbe (lmalherbe@gmto.org) 
 +  * Ruth Paredes (rparedes@gmto.org) 
 +  * James Fanson (Project Manager)
  
 LSST: LSST:
   * Brian Selvy (BSelvy@lsst.org)   * Brian Selvy (BSelvy@lsst.org)
 +  * Michael Reuter (mareuter@lsst.org),​ dial-in
  
 JPL: JPL:
   * Robert Karban (Robert.Karban@jpl.nasa.gov)   * Robert Karban (Robert.Karban@jpl.nasa.gov)
   * Sebastian Herzig (Sebastian.J.Herzig@jpl.nasa.gov)   * Sebastian Herzig (Sebastian.J.Herzig@jpl.nasa.gov)
-  * Amanda Crawford ​(Amanda.Crawford@jpl.nasa.gov)+  * Frank Dekens ​(Frank.G.Dekens@jpl.nasa.gov)
  
 ESO: ESO:
-  * Gianluca Chiozzi (gchiozzi@eso.org) +  * Gianluca Chiozzi (gchiozzi@eso.org), dial-in
-  * Juan Carlos Gonzalez (jcgonzal@eso.org) +
-  * Giorgio Filippi (gfilippi@eso.org +
- +
-LBT: +
-  * Xianyu Zhang (xzhang@lbto.org) +
- +
-MPIA: +
-  * Martin Kulas (kulas@mpia.de)+
  
 NoMagic: NoMagic:
 +  * Saulius Pavalkis (saulius.pavalkis@nomagic.com)
   * Jason Wilson (jwilson@nomagic.com)   * Jason Wilson (jwilson@nomagic.com)
  
-STFC+NRAO
-  * Hermine Schnetler ​(hermine.schnetler@stfc.ac.uk)+  * Richard Prestage ​(rprestag@nrao.edu)  
 + 
 +Caltech: 
 +  * Solange Ramirez (solange@ipac.caltech.edu), dial-in
    
 INAF: INAF:
   * Marco Riva (marco.riva@brera.inaf.it),​ dial-in   * Marco Riva (marco.riva@brera.inaf.it),​ dial-in
 +
 +SKA:
 +  * Antonio Chrysostomou (A.Chrysostomou@skatelescope.org),​ dial-in
 +  * Daniel Hayden (D.Hayden@skatelescope.org),​ dial-in
 +
 +Mexican Telescope:
 +  * Gengis Toledo (gengis.toledo@cidesi.mx),​ dial-in
  
 ====== Agenda ====== ====== Agenda ======
  
 ^Topic^Who^ ^Topic^Who^
-Journal ​George ​+Telescope Modeling Challenge Team Activities ​Jamie & Robert ​
-Introduction ​of OpenMBEE ​| Robert | +Overview ​of GMT MBSE Efforts | Josema | 
-JPL Systems ​Environment | Robert |+| Static and Dynamic Roll-Ups (Mass, Power, etc) | Robert | 
 +Error Budget Modeling | Sebastian | 
 +| Monte Carlo Simulation and Acquisition Behaviors | Gelys | 
 +| LSST, Using Syndeia to Link Requirements & Verification Planning ​Environment ​in MagicDraw to Test Execution Environment in JIRA | Brian S. | 
 +| Consolidation of Syndeia, Datahub, OpenMBEE Graph Models | Discussion | 
 +| Cameo/​Collaborator Requirement Management Tool & CM Using NoMagic by GMT | Brian W. | 
 +| OpenMBEE Tool Infrastructure and View & Viewpoint Paradigm (e.g. Systems Reasoner, docgen, jupyter notebook) ​| Robert |
  
 ====== Agreed Actions ====== ====== Agreed Actions ======
-    * Set up communication channel for MBSE telescope ​community +    * Already received interested participants to contribute to next version of SE Cookbook, Jamie will coordinate efforts 
-    * Provide links to OpenMBEE information through Slack +    * GMT model to be shared with community ​in support of collaboration (George & Josema to follow up)  
-    * Sebastian ​and Gianluca ​to present interface research in future OpenMBEE meeting+    * High resolution spectrograph for E-ELT SysML model to be shared on public teamwork server (Marco to follow up) 
 +    * Jason and Saulius ​to follow up on MagicDraw updates; requirements and Excel synchronization 
 +    * MBSE workshops to be scheduled on regular basis, coordinated by Gelys 
  
 ====== Presentations ====== ====== Presentations ======
- + 
 +{{ :​mbse:​telescope_modeling_challenge_team_20170406.pdf | Telescope Modeling Challenge Team SE3}}\\  
 +{{ :​mbse:​mbse_at_gmt.pdf | Overview of MBSE at GMT}}\\  
 +{{ :​mbse:​mbse_telescope_workshop_-_error_budget_-_2017-04-06-001_-_os.pdf | A Model-Based Approach to Error Budgeting using SysML}}\\ ​  
 +{{ :​mbse:​wf_mbse.pdf | Analyzing the Operational Behavior of NFIRAOS LGS MCAO on the Thirty Meter Telescope using SysML }}\\  
 +{{ :​mbse:​lsst_end-to-end_verification_environment.pdf | LSST End-to-End Verification Environment}}\\  
 +{{ :​mbse:​gmto_cameotools_implementation_mbse_ii.pdf | GMTO Tools and Configuration Management Overview}}\\  
 +{{ :​mbse:​tmt_mbse_workshop-2017-04-06.pdf | ESEM & OpenMBEE Supporting SE Lifecycle Change Process – TMT Case Study}}\\  
 +DOORS to MagicDraw Sync Scenarios\\ {{:​mbse:​doors_to_magicdraw_sync_scenarios.mp4 | DOORS to MagicDraw Sync Scenarios}}\\ ​ 
  
 ====== Notes ====== ====== Notes ======
-George: Journal 
- 
-  * Support a version of the Journal for modeling, system engineering type modeling. ​ 
-  * Establish a baseline for system engineering for ground based modeling. Summarize where we are and what we did. Not necessarily one paper (one for each institute). Coordinate so they show up in the same issue. Similar papers about performance estimates. Peer review papers. 
-  * Is it worthwhile? Use exisiting materials but we have to combine these papers for a more serious paper. 
-  * Create a forum to communicate on Slack. (OpenMBEE Slack Channel). George will provide technicalities regarding the Journal. 
-  * Collect these papers as a starting point. Table of contents for all available papers in the last two years. ​ 
  
-RobertIntroduction ​of OpenMBEE+Telescope Modeling Challenge Team Activities 
 +    * MBSE pillars are SE fundamentals,​ MBSE tools, MBSE language 
 +    * Challenges include general obscurity of SE concepts, which can be resolved in models by flexible MBSE tools/​language when coupled with rigorous SE efforts and analyses; learning curve, time commitment, managerial buy-ins; limited resources; need for dominant standard to communicate 
 +    * Benefitsrigorous analysis to decompose system into underlying parts, analyze their interactions to meet objectives with requirements;​ multi-scale integration;​ enhancements and optimization of SE fundamentals;​ standardization and integration to improve communication  
 +    * TMT application to better understand complex system behaviors; the model captures requirements and scenarios, enables analysis, document production, standardized communication 
 +    * MBSE is not applied to full system, only for optimization ​of complex pieces 
 +    * Telescope Modeling Challenge Team is building on previous generation’s work to revise SE Cookbook and include TMT experiences and examples and produce TMT Case Study for SEBOK fall publication 
 +    * Other telescope teams should think about doing something similar
  
-  * Integration ​of MMSMDK, and VE +Overview ​of MBSE Effort by GMT 
-  LegacyEuropa model went full MBSE approach +    * Continuously working efforts to apply modeling to GMT 
-  Need for document generation ​and full traceabiity +    * Operational life cycle model 
-  EMS was developed ​as a result +    * Complex mission: science cases which are often open ended 
-  Open sourcedMMS (Model Management System), View Editor, Model Development Kit +    * Complex environment and life time goals 
-  ​* ​DocGen ​to define methodsquery the modeland generate PDFs.  +    * But still with these complexitiesthere’s a need to make a machine with precise functionality to deliver the mission 
-  OpenMBEE is the collection ​of institutions that contributes software models (i.e. BoeingJPLLockheedOMG) +    * Modeling playground which shows various levels, views, and processes and how MBSE can overcome these challenges 
-  Vendors pick up requirements ​from users +    Model is a representation of the system’s architectureand we need a standard language with formal semantics to decompose the system 
-  www.openmbee.orgGithubDownloads, EngHubDocumentation +    Observatory as a function; analysis should be pointed at the data to fulfill the science (performance function); also need to check efficiency ​and safety metrics 
-  NoMagic hosts the TWC. Contact Jason Wilson to create an account. +    Define observing cases with properties and hierarchical structure relevant to POV of observatory’s performance function 
-  Can use username openmbeeguest password guest for view only access to projects. Will be provided on slack channel. +    * Mapping of observing cases vs science cases to understand what science will be impacted if… 
-  SysMLv2 Working Group. Reduce metaclasses and instead create metaclasses. The kernel modeling language ​build on the modeling language. Specify the environment ​to access, query, and author them.To be submitted within ​the next 2 years. ​ +    * This mapping allows data to be managed and still usable when science cases change over lifetime of the observatory 
-  Benefits ​of the new specification?​ To make it easier ​to use. Targets on executability. Based on formalism which makes it analyzable and executable. Semantically integrate ​the diagrams.+    * Observing performance modes show system level properties that need to occur simultaneously;​ independent from design choices 
 +    * Observing case analysis block with properties ​as input and system performance output 
 +    * Analysis is representation,​ not performed in SysML model; it defines which analyses need to be performed 
 +    Observatory configurations split between nominal and non-nominal configurations 
 +    * Requirements flow down: science cases (articulates science book) → observing case (articulates science reqs) → observing performance mode (articulates observatory reqs) → observatory configuration (articulates observatory architecture)  ​→ data products and system element properties 
 +    ​Analysis performed at each step to enable science caseobserving case; enable implies that a single input can provide several outputsneed to add normalization rules 
 +       ​Set of analysis or synthesis cases 
 +    * Operation concept: performancesafety and efficiency functions all provide feedback to the observatory  
 +    * MBSE benefits: system decompositionrequirements flow downarticulating life-cycle concepts, organizing analyses; formal framework to consider correctness and truth; finds holes in specifications 
 +    Summary: 
 +    * Modeling goals 
 +       * Consistency in flow down of requirements 
 +       ​Traceability between analysis and requirements 
 +       * Support for system decomposition 
 +       * Develop observatory top-level life-cycle concepts model 
 +    * Playground 
 +       * Enterprise Level - Needs View 
 +       * Mission Level - Needs viewrequirements ViewISO Applicable Processes 
 +       ​System Level - same as above 
 +       ​System Element Level - same as above 
 +    ISO/​IEC/​IEEE 1440 
 +       * Built an architecture framework to build vocabulary ​to describe system 
 +       * They modified it. 
 +    * Stakeholder,​ Concern 
 +       * Formal semantics about the elements they use 
 +    Observatory as a function 
 +       * Performance Function 
 +       * Efficiency Function 
 +       * Safety Function - function ​of observatory case, environment = obs_safety_metrics 
 +    * Observing Cases 
 +       * Set of properties relevant ​to the astronomer that need to occur simultaneously 
 +    * Moe - name, units - quantity kind - initial value
  
-Robert: JPL Systems Environment +Static and Dynamic Roll-Ups (Mass, Power, etc.) 
-  MapleSoft MapleMBSEintuitive excel based interface. Non modelers can update the model +    Dynamic roll-ups used for operational modes (such as standbypeak operating, etc) to get a power profile and compare maximum against requirement 
-TWC becomes the means. +    State machines with constraints to describe behavior of system power 
-  ​TomSawyer Integration +    Parametric diagram exposes recursive characteristics of power roll-up patterns 
-  IncQuery for MagicDrawAd-hoc model queries. Fully integrated with MD 18.4/​5 ​and 19.0. Validation support. Incremental queries based on changes that have been made since last execution. Scalable and fast.  +    * Time analysis provides timeline of states ​and power profiles 
-IncQuery Server. Will be rolled out for production at JPL within ​the next 4 weeks. Works across heterogenous data sources.Report created upon commit.+    * Driving scenario: requirements determine constraints ​on timing, power budgets etc.; formalize requirements in SysML; analyze design wrt mass, power time in the tool; results verify if requirements are met (pass/fail) 
 +    * Mass updates; ​JPL is working on web based app to update ​the model 
 +    * Challenge is integration of SE discipline with domain specifications;​ goal is to consistently update the model to reflect updated CBEs in design
  
-  ​RobertInterface Modeling +Error Budget Modeling 
-Will discuss ​interface ​modeling in a future OpenMBEE meeting.+    ​Requirements for how accurate system performance needs to be and check against CBEs 
 +    * Challengesmass and power roll-ups can refer to PBS, but error budget is not directly linked to the PBS; need integration with system design and check requirements for accuracy 
 +    * Excel error budget 
 +       * Pro: simple ​interface 
 +       * Con: no explicit linking, verification is done by manual checking or independent model 
 +    * Accuracy of pupil measurement/​alignment to 0.03% of diameter as motivating example 
 +    * Error roll-up pattern similar to mass roll-up pattern; element with values requirement,​ CBE, and margin 
 +    * Margin = (allocated – CBE) / allocated 
 +    * Pattern application:​ 
 +       * inherit from specific error roll-up type 
 +       * subset “subError” property of ErrorRollUpPattern element 
 +       * Define default values for all “leaf”-CBEs 
 +    * Parametric diagram for linking requirements and PBS 
 +    * Parametric solver using CST (or others); result = roll-up 
 +       * formalized requirement 
 +       * automated roll-up 
 +       * automated verification of requirement 
 +    * Excel error budget vs SysML: SysML is better for linking and collaboration 
 +    * Model can produce visualizations similar to Excel (such as instance tables) 
 +    * NoMagic is working on requirements improvements;​ synchronization of Excel and SysML tables instead of one-time import; Jason & Saulius to schedule webinar to discuss this update 
 +    * New pattern needed for interfaces
  
-  ​SebastianBrittleness of excel integration,​ problems of integration,​ reliable sourcesWhat is the current state, how it can be remedied, ​and what'​s ​the right path?+DataHub – NASA JPL uses for Instance specs 
 +    ​DOORS to MagicDraw for SysML Stereotypeshttps://www.youtube.com/​watch?​v=ESZ433qbS7c 
 +    * Export Data & Scope Sync from MagicDraw to DOORS: https://​www.youtube.com/​watch?​v=SSGNzFQ6Ms8 
 +    * DOORS to MagicDraw - Map the Object Identifier: https://​www.youtube.com/​watch?​v=uqzYtcgCOPo 
 +    * DOORS to MagicDraw - Custom Stereotypes with UPDM (CV-1): https://​www.youtube.com/​watch?​v=rjgOdl_0ycM 
 +    * Moving Links to DOORS From MagicDraw ​and Back (Shows how to map in the export window.): https://​www.youtube.com/​watch?v=MstQROYt_Uo 
 +    * CDH 18.4 MagicDraw to DOORS Copy Data with Scope Sync: https://​www.youtube.com/​watch?​v=RIFNcQZj3tc 
 +    * YouTube Channel for move videos: https://​www.youtube.com/​channel/​UC4PcJ_klXcly5ga4vHjUpnw
  
-  * Unordered List ItemRobert: Excel side integration- how to write this integration?​+OpenMBEE docgen allows for documents that include updated simulations from the model
  
 +MagicDraw 19.0 early access to subset of features\\
 +Recording of session of R&D discussion on SUBSET of v19.o features: https://​youtu.be/​A5YAyumWlzE
 +    * MAIN attention is on presentation of "Final scope of Excel integration"​
 +    * Covers:
 +       * OSLC consumer use cases 
 +       * Extending the hyperlink concept ​
 +       * Final scope of Excel integration ​
 +       * Final implementation of Find in Diagrams: demo
  
mbse/telescope_mbse_sig_meetings_pasadena_april_2017.txt · Last modified: 2018/07/09 18:14 by acrawford