User Tools

Site Tools


mbse:model_management_joe_bedocs_brian_brady

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mbse:model_management_joe_bedocs_brian_brady [2013/02/03 15:36]
brianbrady
mbse:model_management_joe_bedocs_brian_brady [2013/02/06 10:06] (current)
brianbrady
Line 48: Line 48:
 {{:​mbse:​mmwg-discussion.png|}} {{:​mbse:​mmwg-discussion.png|}}
  
-Notes and Action resulting ​form the Working Group session:+Notes form the Working Group (WG) session ​(thanks for Mark Sampson): 
 + 
 +** What is product truth...?​** 
 +   * Consonance Agreement: Models should be truth but documents/​views will be required. 
 +   * Approach: Treat each model as a view of the super model  
 +   * Challenge: No configuration control of a super model  
 +   * Challenge: For every model/​datum,​ someone is going to have to decide what is truth about a that particular piece of information 
 +   * Challenge: Model is truth and that’s what under configuration,​ but a document needs to go with it -- supporting approval, V&V and legal sign-off. ​ This becomes critivcally important in a prime/​subcontractor "​shared model" environments. 
 +   * Challenge: Since we can’t manage the whole, we need to control "​our"​ domain. ​ Need to validate against "our model" relitive to the federated collection.  
 +   * Approach: Could validating at the interface level. ​ Believe more validate beyond the I/F will be required. 
 +   * Approach: Looking at total system model might not useful, taking view of a model is what’s useful. 
 +   * Apporach: Parts of the truth will be configuration modeled in different ways 
 +   * Approach: Early in the lifecycle small systems are manageable, but eventually you have to break it up as we move through the lifecycle and systems get bigger. ​ This will require an understanding of interfaces/​partitions. 
 +   * Approach: Documentation generation has moved from whole documentation to parts of documents 
 +   * Approach: From a model perspective,​ you need to manage objects and interfaces; a federated model; an interface management type of problem 
 +   * Approach: Dependency management will be required (in addition to just interface management). ​ Comment: In moving to a federated set of models, the connection/​touch-points must be fully explored -- with identified exchange patterns. 
 +   * Challenge: Everything is dependent on everything, so you will need to prioritize dependencies 
 +   * Challenge: How do you divide up the model/​partition it.. 
 + 
 +**Summary:​**  
 +   * Challenge: Super model is not configurable -- models in many different tools. 
 + 
 +**Interesting Investigations:​ ** 
 +   * How do we manage documents and manufacturing models today? 
 +   * How do they do it in Software? ​ Other engineering displines?​ 
 +   * CMII model  
 +   * How is concurrent development managed today?  
 +   * How do you protect competing information today? //Comment: Assuming a common truth model being shared with contractors. ​ More the norm vs. the exception.//​  
 +   * What metadata is required for models to talk?  
 +      * Data vs. Metadata -- This will require clean definitions. ​ For now, everyting is data... 
 +      * Challenge: How to extend the data associated with a component without changing it (i.e., a new varient of an object is created in the version tracking system). 
 +   * What are the dimensions of model? ​ Dependencies,​ version, variant...?​ 
 +      * Below is Chris Davey'​s multi-demissional release management view (slide 11 from his {{:​mbse:​03-2013_incose_mbse_workshop-ford_automotive_complexity_v4.0-davey.pdf|Systems and Software Modeling at Ford - Chris Davey}} brief. 
 +{{:​mbse:​ford-relmgmt-2013-0126.png?​800|}} 
 + 
 +==== Resulting Actions ==== 
 +The following are the actions resulting from this Model Management WG Session: 
 + 
 +** Plan:** 
 +   * Start/Focus on simple scenario of model-A(v1) and model-B(v1) that have corresponding dependency. ​ Move to new versions, A(v2) and B(v2). ​ What happens to the dependencies? ​ How are the models managed? 
 +   * **Fundamental functions of Model Management** 
 +      - Access control 
 +      - Version/​configuration management 
 +      - Interface management—including dependencies,​ 
 +   * Identify next step? 
 +   * Produce a whitepaper on model management:​ 
 +      * Fundamentals 
 +      * Challenges 
 +      * Integration Patterns/​Scenarios 
 +      * Technology Gaps 
 +   * Set up a Model Management group collaboration 
 +      * Planning on using Google Group + Share documents (Google Drive?) 
 +      * Issue invites upon setup 
 + 
 + 
mbse/model_management_joe_bedocs_brian_brady.1359923813.txt.gz · Last modified: 2013/02/03 15:36 by brianbrady