Use rational method composer to define a Unified Process of customization

Document options Level: elementary Xuan Jiang (jx0517@hotmail.com), software engineer at IBM China Software Development Lab February 23, 2006 This document describes how to use IBM Rational Method composer to generate and publish a custom Unified Process (RUP) through a simple but complete example ). Introduction 　　 In the traditional software development process, the development method that is often used is called waterfall development method. The development team should complete a series of project phases in strict order, including Requirement Analysis, Design, Implementation/integration, and finally testing. The advantage of this is that project management is very simple. 　　 As software development projects become increasingly large and demand becomes increasingly complex, problems arising from waterfall development methods are highlighted. In the process of software development, there are more and more problems encountered in the development process. These changes and problems may seriously affect the software release period. In addition, this development process will make the main team members idle in some development stages. To avoid these idleness, the team members have to switch between different projects. 　　 A new development method is called iterative development. It uses a parallel program development process to break down a project into several sub-projects, which can be synchronized between sub-projects that are not restricted by each other. This improvement can reduce the risks brought by later integration, at the same time, testers can get involved in testing earlier and provide more accurate project status for management personnel. Each sub-project is called an iteration. The iteration has a detailed target definition and can complete some functions of the final system. Each subsequent iteration is based on the previous iteration, and the project function is continuously added, until the final product development is complete. 　　 The iterative development method increases the difficulty of project management. IBM Rational Unified Process is implemented to manage and distribute the entire project development process. It is browser-based, A Customizable software development process platform. It focuses on the software development industry-recognized Optimization Method and manages the allocation of different elements in the development process. 　　 Generally, the default RUP can meet the needs of some users. Users can publish and use it simply by deleting and modifying it. However, for some specific projects, the default configuration of RUP cannot be competent. In this case, you need to use third-party software to define a custom RUP system, RMC is a software released for this demand. Back to Top Target readers 　　 This document is intended for project managers in software development projects. Assume that you already have a certain degree of project management basics, understanding the use of RUP and some rational products. Back to Top RMC Overview 　　 Project managers can use RMC to customize, deploy, and modify the project development process of a specific development team. It is a flexible tool platform that can be applied throughout the entire software development lifecycle, effectively assists the project team in maintaining a consistent custom development process. 　　 RMC is the next major release of IBM Rational, which is perfect for developing software development process solutions. The latest release version 7.0 has the following features: You can use RMC to maintain a consistent development process with project members through multiple channels. Eclipse-based build and release tools Provides a process library, including all the earlier versions of the RUP content and the RUP plug-in Back to Top Custom RUP 　　 Before RMC came into being, it required several steps to customize the custom RUP, which should be completed using different tools and software. RUP modeler-define custom plug-ins Rational process workbench-define Workflow RUP Organizer-extends plug-in content and exports plug-ins RUP builder-configure and release the RUP View Myrup-custom client 　　 RMC uses an interface to complete all of the above software's RUP-related functions, which allows you to easily define a brand new or changed RUP System Based on your unique needs. Back to Top RMC enhancements 　　 In addition to the customized and customized RUP functions implemented by several previous tools and software, RMC also has many extensions: Provides a customizable tool for the production, configuration, viewing, and release development processes. Real-time preview is provided in the dedicated view to allow Quick Switching of views. You do not need to master the basic skills of UML model development when using a form-based management method. A WYSIWYG text editing tool is provided to describe how to create a method. The editor allows you to use style styles, graphs, tables, hyperlinks, and directly edit HTML code. Use the category structure editor and flow chart creation process. The classification structure Editor supports multiple process views. RMC can automatically synchronize views when the process changes. Although the RMC release package contains the latest version of RUP, remember that RMC is a flexible process definition tool, not just the RUP. Enhanced reusability and scalability. Use drag-and-drop operations to quickly define the process. Fills in the gap between process and project management. Back to Top Elements in RMC (RUP) Core elements 　　 Core elements include roles, tasks, and products. Role 　　 A role is an element that can be involved in the development process. It contains an independent set of individual responsibilities, related skills, and abilities. Multiple roles can form a role set for resource usage in an iteration process. A role executes a task to generate corresponding products and other non-core elements. Task 　　 A task is defined as a refined allocable unit in a project. Each task is assigned to a specified role or role set. The task is usually refined by the number of hours to days for the assigned role, and the impact of the task on the entire project is minimized as much as possible. Generally, only one product is affected. Product 　　 A product is a general term for the input/output of tasks during software development. RMC contains three common types of products: Artifact Outcome Deliverable Non-core elements 　　 Non-core elements include checklist, concept, example, guideline, practice, report, reusable asset, road map, supporting material, template, term definition, tool mentor, and whitepaper. They interact in the middle of software development and constitute a necessary component of a unified process system. Back to Top Use RMC to build a custom RUP Create method Library 　　 Click file-New-method library to create a custom keystore library. The keystore library is used to save the newly created elements in all projects and the relationships between elements. All the content is stored in a directory. You can open or close an existing keystore library at any time during subsequent use. Create method plug-in 　　 Click file-New-method plug-in. The method plug-in needs to define the content and processing process of the method. Create content package 　　 Right-click content packages and choose new-content package. A content package is used to save all elements that may be involved in a process. New Element 　　 Right-click the element category under the content package to create the required elements, including the core element and the non-core element. In this example, roles, tasks, products, and reports are created. New category 　　 Right-click custom categories and choose new-custom category. The newly created category is used to organize all elements when the RUP is released. Therefore, the related elements (that is, those associated with this category) created in the previous step must be assigned to this category. New configuration 　　 Right-click Configuration, select new-method configuration, and enter the name of the new configuration. The Configuration Attribute contains all the method plug-ins contained in the final release file, and specifies the default view of the released RUP file, select the newly created "New Method plug-in" on the plug-in and package selection page, add the newly created "Custom category" on the view page, and set it as the default view. Configure the association relationship of Elements 　　 Now, we assume that all the elements we need have been created, and the necessary configuration files and categories have been created and saved respectively. Then, we need to set the dependencies between elements so that they can be reflected in the released version of the RUP. 　　 Open all the elements just created, and set the relationships between roles, tasks, and products based on project requirements. One role can undertake multiple tasks, and one task can be completed by multiple roles. Release RUP 　　 Save all the projects above, click Configuration-publish, select the created "New Method Configuration", and click Next. 　　 In the selection of release configuration, you can set the page topic of your own RUP, the connection to the page and receipt, and so on. Note that if you need to search for and customize the view function, You must select related options, which requires the client browser to support Java applet. 　　 After the release is complete, you can find error. log and warning. log under the logs in the release directory. Through these two files, you can check the errors and warnings generated during the release process. Post-Release custom RUP 　　 Use a browser to open the newly released version of the RUP system. If the search and custom functions are selected during the release, the browser needs Java Applet support. You can see the elements you just defined and the relationship between the elements in the RUP interface. Custom View 　　 Click the Save As icon on the toolbar of the RUP and save the newly released custom category as a client custom view. After switching to this view, you can add or delete nodes to or from the view, you can also use the drag-and-drop operation to add elements of interest to the Element Library. 　　 All custom operations are stored in the cache of the client, which does not affect the released RUP. 　　 So far, the process of a simple but complete process of customized RUP has ended. Project Members can view and view their responsibilities and define their own views of the RUP for the nodes they are interested in. 　　 You can add other necessary elements, such as tooltip, milestones, and key nodes, based on the framework structure. Any subsequent modifications must be re-released to ensure that the accessed RUP is the latest version. Back to Top Summary 　　 Through this article, we can understand that RMC is a method and process construction platform, which can effectively organize all the elements involved in the project development process, construct associations between them and create necessary containers to save these elements. The constructed notebook library can be published as an HTML document, that is, the custom RUP, which can be customized by the client through Java Applet again. 　　 RMC also supports the import and export of the square algorithm library, allowing you to easily use the element Resources in the existing pipeline Library (in fact, all the elements in the RUP released by default, stored in the default library directory of The RMC installation path). It also facilitates Resource Exchange and fully reflects the reusability of resources. References Can you get a trial version of The http://www.ibm.com/developerworks/downloads/r/rup/ from here? S_tact = 105agx28 & s_cmp = dlmain The article http://www.ibm.com/developerworks/rational/products/rup of RSA in DW Introducing http://www.ibm.com/developerworks/rational/library/nov05/kroll/ IBM Rational Method composer About the author Jiang Xuan, IBM China Software Development Lab, rational gb18030 Certification Team, software engineer, familiar with OS/2, Linux, AIX operating system/JDK DBCS testing, recently participated in the rational gb18030 certification test, understand the rational products. Thanks to Team Leader Xu Cheng and other members of the project team for their help during the writing process. Contact: Email: jx0517@hotmail.com