GVCS Lifecycle Analysis: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
== Approach == | == Approach == | ||
The systems engineering method makes use of many tools. In the above analysis, significant use was made of the [http://www.omgsysml.org/ OMG Systems Modeling Language]. The initial [[CAD:SysML]] model for the GVCS is linked above, while the paper and presentation include rendered images of the model. | The systems engineering method makes use of many tools. In the above analysis, significant use was made of the [http://www.omgsysml.org/ OMG Systems Modeling Language]. The initial [[CAD:SysML]] model for the GVCS is linked above, while the paper and presentation include rendered images of the model. | ||
[[File:Sysml_bdd_gvcs.svg]] | |||
[[Category:Systems Analysis]] | [[Category:Systems Analysis]] | ||
Revision as of 23:06, 13 February 2012
Links to External Files
- Web Presentation (press Right and Left to navigate)
- Paper
- SysML Model
A system-of-systems analysis of GVCS development
This analysis looks at the needs and approach for:
- the system of GVCS tools in a GVCS Village (the system of interest),
- the system of the contributors and processes being used to develop the system of interest, and
- the global system of all contributors and users of the GVCS
Emergent Behaviors
Large, complex, loosely coupled systems begin to display effects not intended by the creator. An example: sharing open code spawns other efforts adopting tools for different uses. The analysis identifies some of the areas where GVCS is likely to display emergent behaviors in design, community processes and business.
Approach
The systems engineering method makes use of many tools. In the above analysis, significant use was made of the OMG Systems Modeling Language. The initial CAD:SysML model for the GVCS is linked above, while the paper and presentation include rendered images of the model.
