RUP SE is a useful tool to help manage and organise todays software organisations. To find out how RUP can be used to manage your project, read this article today.
Organizing RUP SE Projects - A Final Word: How Hard is This? (Page 5 of 5 )
As we mentioned above, using architecture rather than requirements to organize systems development may, at first, seem overly complex and difficult to put into practice. However, the complexity of the organization scales with the complexity and size of the effort. For smaller, simpler projects, you can combine roles and teams so that the organization is more streamlined. Even for larger teams, the difficulty is more perceived than real.
For these projects, with their inherent diseconomies of scale, the RUP SE management approach tames the nonlinear growth in interteam communications, yielding productivity increases. For very large projects, applying RUP SE at several levels simplifies the management process, and synchronizing the plans from these various levels validates overall system planning. At every level, the teams have clear roles, areas of concern, and responsibility. In the end, process adoption can proceed smoothly, allowing all teams to focus on the system, and not on the process itself.
Notes
1 The RUP SE architecture framework can be found in the RUP SE extension to the RUP available on RDN. This framework is further explained in the draft whitepaper "The Rational Unified Process for System Engineering 2.0" (in press) by Murray Cantor, and available from the author.
2 RUP SE relies on a way to express logical decomposition. UML 1.4 characterizes the elements of the logical decomposition of the system as subsystems. At this writing, the UML 2.0 drafts use different semantics to express the logical elements. When UML 2.0 is adopted, we will change the semantic representation of logical elements to reflect the current standard.
4 Available through Rational Developer Network (http://www.rational.net); authorization required.
5 Fred Brooks, The Mythical Man Month, Addison Wesley, 1997.
6 Barry Boehm et al., Software Cost Estimation with COCOMO II, Prentice Hall, 2000.
7 See notes 3 and 4.
8 See notes 3 and 4.
9 Very High Speed Integrated Circuit (VHSIC) Hardware Description Language
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.
Development Cycles 
/ 10 
The Ten Essentials of RUP
