Home > Articles > Software Development & Management > UML

Strategic Reuse Management and the Rational Unified Process (RUP)

📄 Contents

  1. Strategic Reuse Management and the Rational Unified Process (RUP)
  2. References and Recommended Reading
RUP doesn't have much to say when it comes to reuse. Scott Ambler explains that by thinking outside of the RUP box you can easily tailor a strategic reuse management process into the RUP. You can have your process cake and eat it, too.
This article appeared originally on Flashline.com.
Like this article? We recommend

Many organizations have adopted, or are in the process of adopting, the Rational Unified Process (RUP) (Kruchten 2000). There's a good reason for this: the RUP is a very good, rigorous software process, arguably the defacto standard within the IT industry. But these days organizations are eager to do more than adopt a new software process. They're just as eager to increase the level of reuse on software projects to both reduce overall cost and time to delivery. The problem is that the RUP doesn't have much to say when it comes to reuse. I suspect this is because reuse is a cross-system issue whereas the RUP focuses on the development of a single system. In this article I'll show that by thinking outside of the RUP box you can easily tailor a strategic reuse management process into the RUP. You can have your process cake and eat it, too.

I define strategic reuse management as "the identification, generalization and/or development of, and support of potentially reusable artifacts" (Ambler and Constantine 2000b). Strategic reuse management is a complex endeavor, one that spans all of the projects within your organization. Your development teams should strive to identify and reuse existing artifacts wherever possible, to buy instead of build where that makes sense, and to produce high-quality artifacts that can potentially be generalized for reuse when that makes sense.

If strategic reuse management requires a cross-project effort, yet the RUP only focuses on the development of a single system, what do you do? Extend the RUP, of course. This is exactly what the Enterprise Unified Process (EUP) does by adding a new discipline called Infrastructure Management (Ambler 2002). Figure 1 depicts the lifecycle for the RUP and Figure 2 the lifecycle for the EUP - you can see how the EUP extends the RUP with two new disciplines (Infrastructure Management and Operations and Support) and one new phase (Production). The focus of this article is on strategic reuse management, one of several critical cross-project issues encompassed by the Infrastructure Management discipline. Other cross-project issues include portfolio management (also called program management), enterprise configuration management, enterprise architecture, enterprise requirements modeling, enterprise process management, and enterprise administration. The bottom line is that practice shows that in order to achieve economies of scale in developing software, to increase the consistency and quality of the software that you develop, and to increase reuse between projects, you must effectively manage your common infrastructure -- you need the EUP's Infrastructure Management discipline.

Figure 1Figure 1. The lifecycle for the Rational Unified Process (RUP).

Figure 2Figure 2. The lifecycle for the Enterprise Unified Process (EUP).

In my experience the most effective way to define a strategic reuse management process is to begin by defining its philosophical foundation. These philosophies should be brainstormed and then debated by a representational group within your organization, thus ensuring the widest acceptance. As a starting point you should consider the following philosophies:

  1. Quality, not quantity, is the goal. You are far better off developing ten high-quality items that people actually need than one hundred low-quality items of interest to no one. High-quality items will help to build the reputation of your reuse program, motivating developers to submit more high-quality items over time. Success breeds success.

  2. Building reusable items is difficult. Reusable items must be of high quality, but they also must be sufficiently general in nature so as to be useful across the widest range of purposes. They also require accompanying documentation, examples, and configuration strategies. This is a significant amount of work that must be performed by experienced people. Steve Adolph (1999) shows this concept well in his implementation of a simple class to simulate dice. He masterfully shows that building something to make it reusable is significantly harder than building it to meet your specific needs at the time. The point is that you shouldn't underestimate the effort to make something reusable.

  3. You can reuse more than just code. A fundamental concept in reuse management is that there are a wide variety of things that you can reuse on a software project, and that different types of reuse offer varying levels of value to your overall effort. My experience (1998) is that there are eight categories of reuse...

    • artifact reuse
    • code reuse
    • component reuse
    • domain-component reuse
    • framework reuse
    • inheritance reuse
    • pattern reuse
    • and template reuse

    ...that you may apply on your software projects. It is important to understand each category: different people apply each type of reuse in a different manner to different aspects of your overall development efforts. For example, your programmers typically apply code and component reuse, whereas pattern reuse is typically applied by modelers. It is interesting to note that several of the most effective forms of reuse, such as domain-component reuse and framework reuse, require other infrastructure management efforts, such as enterprise architectural modeling, in order to be successful.

  4. A reuse repository is a good start, but only a start. Over the years I have found that a common mistake that organizations make is that they believe that all they need to do is purchase a reuse repository and they'll automatically improve their levels of reuse, an anti-pattern that I call Repository-Driven Reuse (Ambler 2000). There is more to strategic reuse management than just a good tool — your process and culture must also reflect your reuse strategy. Remember, it's people, process, and tools not just tools.

  5. An asset is reusable only after it has been reused. A good rule of thumb is that you truly know that something is reusable only when three different project teams have reused. Many strategic reuse management programs flounder when the owners of a reuse repository fill it with items that developers aren't interested in. Reuse is in the eye of the beholder - something isn't reusable simply because you declare it to be so.

  6. Reuse isn't free. Reusability has an ongoing cost beyond its initial price of acquisition - you must also manage your reusable assets and support the people using them. Assets must evolve, or be retired when they are no longer viable.

  7. Beware reward systems. I do not believe in rewarding people for reuse. My philosophy is that developing and reusing high-quality artifacts is a fundamental aspect of a software developer's job. Having said that, many organizations decide to embark on a reward program anyway. If this is the case for your organization it is important to explore effective incentives. Roland Racko (1996) believes that a reward program can be useful to help kick-start a reuse program, but you must be prepared to dismantle your reward system as reuse becomes a permanent aspect of your software culture. In short, be smart about how you use rewards.

Many organizations succeed at strategic reuse management, but that's because they go into it with their eyes wide open. You can implement a reuse program within the RUP if you choose to, but to do so you'll have to think outside of the box a bit. Success, after all, is a choice.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020