==== IBM Rational Unified Process for Systems Engineering (RUP-SE) ==== === Overview === * Extends RUP style of concurrent design and iterative development to support SE in Model-Driven Systems Development (MDSD) * New roles, e.g., systems engineers * New artifacts & disciplines, e.g., security, training, logistics * Emphasis on business modeling, business actors and flow of events to adequately define system reqts * Viewpoints for SE, i.e., model levels and model viewpoints * Introduces concept of //locality// — Member of system partition representing generalized or abstract view of physical resources; linked by connections (M. Cantor) * Scalability enhancements where each subsystem coupled w/locality has own derived reqts * Allocated vs derived reqts — locality/subsystem is allocated if fulfilling system reqt; is derived if identifyed by studying how collaborates with other to meet system reqt * Subsystem-level flowdown activity via use-case flowdown activity and flow of events in “white-box view of system * Support for designing additional components (e.g., H/W) in addition to RUP S/W focus {{:mbse:rup_se_lifecycle.jpg?400|}} {{:mbse:rup_se_reqts_alloc_der_method.jpg?350|}} === Tool Support === * A process framework tool does exist to support RUP-SE and is available via the RUP-SE plugin for the [[http://www-01.ibm.com/software/awdtools/rmc/|Rational® Method Composer (RMC)]] product offering from IBM Rational® software. * Direct MBSE tool support is provided by IBM through its Rational® suite of tool offerings that support analysis, modeling, design, and construction, which is a collection of early IBM Rational tools plus those adapted from [[http://www-01.ibm.com/software/rational/welcome/telelogic/|IBM Rational's acquisition of the Telelogic®]] family of systems development products (e.g., DOORS®, Tau®, Rhapsody®, System Architect®). === Offering/Availability === * Given the breadth, depth, and complexity of the RUP-SE methodology, it is recommended that adoption and tailoring of the RUP-SE methodology be supported through IBM professional services. * A textbook by P. Kruchten exist for the baseline RUP® methodology that details core tenets and elements of the methodology and provides tailoring guidelines (see Resources below). Such a companion text does not yet exist for RUP-SE, at least not at the time of this survey. === Resources === * Estefan, Jeff A., “[[http://www.incose.org/ProductsPubs/pdf/techdata/MTTC/MBSE_Methodology_Survey_2008-0610_RevB-JAE2.pdf|Survey of Model-Based Systems Engineering (MBSE) Methodologies]],” Rev. B, INCOSE Technical Publication, Document No.: INCOSE-TD-2007-003-01, International Council on Systems Engineering, San Diego, CA, June 10, 2008.\\ * Cantor, Murray, “[[http://www.ibm.com/developerworks/rational/library/content/RationalEdge/aug03/f_rupse_mc.pdf|Rational Unified Process® for Systems Engineering, RUP SE® Version 2.0]],” IBM Rational Software white paper, IBM Corporation, May 8, 2003. * Balmelli, L., Brown, D., Cantor, M. and M. Mott, “[[http://ieeexplore.ieee.org/search/freesrchabstract.jsp?tp=&arnumber=5386622&queryText%3Dmodel+driven+systems+development%26openedRefinements%3D*%26searchField%3DSearch+All|Model-Driven Systems Development]],” //IBM Systems Journal//, **45**, Iss. 3, pp. 569-585, 2006. * Nolan, B., Brown, B., Balmelli, L., Bohn, T., and U. Wahli, "[[http://www.redbooks.ibm.com/abstracts/sg247368.html?Open|Model Driven Systems Development with Rational Products]]," IBM Redbook SG24-7368-00, IBM Corporation, Mar. 4, 2008. * Kruchten, Philippe, //The Rational Unified Process: An Introduction//, Third Edition, Addison-Wesley Professional: Reading, MA, 2003. ====== Return to List of MBSE Methodologies ====== [[http://www.omgwiki.org/MBSE/doku.php?id=mbse:methodology#List of MBSE Methodologies | Click Here]]