Warning: Can't synchronize with repository "(default)" (/disks/svn_mcs/repos/neams-ibm does not appear to be a Subversion repository.). Look in the Trac log for more information.

Changes between Version 2 and Version 3 of mda


Ignore:
Timestamp:
01/31/09 14:18:57 (14 years ago)
Author:
bernhold
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • mda

    v2 v3  
    55 * UML, http://www.omg.org/technology/documents/formal/uml.htm 
    66 
    7 == Links from IBM Rational == 
     7== IBM Links == 
    88 * MDSD Redbook, https://www.redbooks.ibm.com/redbooks.nsf/e9abd4a2a3406a7f852569de005c909f/b5c3d2738cc022e18525720400642e80?OpenDocument 
    99   * Abstract: This IBMA(R) RedbooksA(R) publication describes the basic principles of the RationalA(R) Unified ProcessA(R) for Systems Engineering, which is IBM Rationala**s instantiation of model-driven systems development (MDSD). MDSD consists of a set of transformations that progressively refine knowledge, requirements, and design of complex systems. MDSD begins with activities and artifacts meant to promote an understanding of the system's context. Requirements problems often arise from a lack of understanding of context, which, in MDSD, means understanding the interaction of the system with entities external to it (actors), understanding the services required of the system, and understanding what gets exchanged between the system and its actors. Managing context explicitly means being aware of the shifts in context as you go from one model or decomposition level to the next. MDSD suggests that a breadth-first collaboration based approach across multiple viewpoints is more effective than a traditional depth-first functional decomposition in creating an architecture that will not only meet requirements, but will prove to be more resilient in the face of inevitable change. MDSD also seeks to provide an effective distribution of responsibilities across resources. Joint realization and abstractions such as localities provide an effective and elegant way of accomplishing this.  Finally, the ability to attach attributes and values to modeling entities and the parametric capabilities of SysML provide a basis for doing simulations or other models to meet cost, risk, and other concerns. 
     
    2121 * A Practical Guide to SysML: The Systems Modeling Language, http://www.amazon.com/Practical-Guide-SysML-Modeling-Language/dp/0123743796/ref=sr_1_1?ie=UTF8&s=books&qid=1229364540&sr=1-1 
    2222 * http://www.omgsysml.org/SysML-Tutorial-Baseline-to-INCOSE-060524-low_res.pdf 
    23  * http://eislab.gatech.edu/pubs/conferences/2007-incose-is-1-peak-primer/ 
     23 * RS Peak, RM Burkhart, SA Friedenthal, MW Wilson, M Bajaj, I Kim (2007) Simulation-Based Design Using SysML—Part 1: A Parametrics Primer. INCOSE Intl. Symposium, San Diego. http://eislab.gatech.edu/pubs/conferences/2007-incose-is-1-peak-primer/