| The RMC product comes with a set of out-of-the-box processes. |
The RMC product comes with a set of out-of-the-box processes, or delivery processes. These describe an end-to-end process, including a suggested order of activities, such as what phases to plan for and typical iteration patterns. These can be used out of the box, or as a starting point for further customizations. New delivery processes are added and made available via the DeveloperWorks Web site.[3] At the time of publishing, the following processes are available: [3] See www.ibm.com/developerworks.
RUP for small projects. This process guides small and collocated teams in how to develop new software or make major improvements to existing software. RUP for medium-sized projects. This process guides distributed and medium-sized teams in how to develop new software or make major improvements to existing software. RUP for large projects (classic RUP). This process guides distributed and large-scale teams in how to develop or refine business models, how to develop new software, and how to make major improvements to existing software to support an evolving business. This process is most appropriate for organizations working to meet industry or regulatory compliance guidelines, such as Sarbanes-Oxley, SEI CMMI, Basel, and ISO 9001. RUP for COTS or packaged application development. This process describes how to choose the right components for reuse and how to make the right trade-offs among reuse, addressing requirements, programmatic risk, and marketplace concerns. The process addresses how to incorporate one or several smaller components, as well as how to customize large packages to your needs (see Figure B.1). Figure B.1. RUP for COTS/Packaged Application Development.
RUP for COTS or packaged application development describes how to balance trade-offs among stakeholders, availability of commercial components, architectural concerns, and program risks as you develop applications using COTS or implement packaged applications.  RUP for systems engineering. This process describes how to develop systems that consist of a combination of software, hardware, and people, addressing the common problems these resources present through effective, unified collaboration. This process is used in a variety of projects, from large-scale defense and communications projects to embedded software projects in the automobile industry. RUP for service-oriented architecture. This process describes how to define business processes and couple them with services (see Figure B.2). It provides a variety of approaches for identifying the appropriate business elements to expose as service components by analyzing current assets and data structures. The approach includes specific guidance on how to leverage J2EE and other technologies to implement Web services effectively. Figure B.2. RUP for Service-Oriented Architecture.
RUP for service-oriented architecture describes how to define and simulate business processes; how to identify services from business processes, use cases, existing data, and legacy components; how to couple services to business processes to allow close coupling between business needs and IT assets; and how to implement services and service components.  RUP for maintenance. This process describes how to take a set of defects and change requests and drive an incremental release of an existing product. SUMMIT systems delivery. This process describes how to develop an application using traditional structured systems development techniques.
| RMC provides specialized content to support a variety of domains and technologies. |
RMC also provides specialized content to support a variety of domains and technologies that can be used to augment or alter the delivery processes listed above, or to build completely new delivery processes. This content is packaged as downloadable "plug-ins," which can be added to your processes library at any time. IBM and partners continuously develop new plug-ins. Following are some key content areas covered by these plug-ins: J2EE development. This includes guidance on architectural patterns, designs targeting various deployment environments, and effective use of tools to develop J2EE applications. .NET development. This includes guidance on distribution patterns, application design, .NET platform elements, architectural layering, and effective use of tools to develop .NET applications. User-centered engineering. This includes user experience modeling, navigation maps, storyboards, wire frames, usability testing, and user-centered design. Tool-specific guidance. This includes how to leverage IBM Rational software development tools, as well as partner tools, effectively.
|
