mbse:model_management_joe_bedocs_brian_brady
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
mbse:model_management_joe_bedocs_brian_brady [2013/02/03 16:24] brianbrady |
mbse:model_management_joe_bedocs_brian_brady [2013/02/06 10:06] (current) brianbrady |
||
|---|---|---|---|
| Line 77: | Line 77: | ||
| * How do you protect competing information today? //Comment: Assuming a common truth model being shared with contractors. More the norm vs. the exception.// | * 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? | * What metadata is required for models to talk? | ||
| - | ** Data vs. Metadata -- This will require clean definitions. For now, everyting is data... | + | * 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). | + | * 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...? //Comment: See Chris Davey's multi-demissional release management view, slide 10 (add link) | + | * 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 ===== | + | ==== Resulting Actions ==== |
| The following are the actions resulting from this Model Management WG Session: | 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.1359926685.txt.gz · Last modified: 2013/02/03 16:24 by brianbrady
Page Tools
