Home > Articles > Software Development & Management > Rational

  • Print
  • + Share This
This chapter is from the book

The Key Principles and Your Environment

After you have completed the exercise of crafting a vision statement, you will need to begin looking just under the covers of RUP and tying in the underlying principles to a value statement for your company. RUP has been based on six best practices that have evolved into the six key principles that IBM Rational has gleaned from involvement in tens of thousands of software development projects supporting customers throughout the world, as well as within IBM itself. The evolution from the practices to the principles are in alignment with industry trends. For those of you in larger organizations, you may be working in an environment of IT governance, geographically distributed development, or SOA governance, to name just a few relevant items in a world of outsourced IT and business processes. The key principles are a wonderful evolution of a tried-and-true foundation that has served its adopter well.

The key principles are as follows:

  • Adapt the Process.
  • Balance Competing Stakeholder Priorities.
  • Collaborate Across Teams.
  • Demonstrate Value Iteratively.
  • Elevate the Level of Abstraction.
  • Focus Continuously on Quality.

The best practices are as follows:

  • Develop Iteratively.
  • Manage Requirements.
  • Use Component Architectures.
  • Model Visually.
  • Continuously Verify Quality.
  • Manage Change.

Many of the good books written on RUP that are noted in the Preface, such as The Rational Unified Process: An Introduction, Second Edition3 and The Rational Unified Process Made Easy: A Practitioner’s Guide to the RUP,4 do a great job of getting into the nuts and bolts level of detail of the best practices for project team practitioners. My goal is to arm you with information on what the six best practices and the six key principles will mean to your company and how you can clearly articulate the value they will have in your environment.

There are a lot of ways to sum up what the key principles or best practices are, both in technical terms as well as in laymen terms. I will provide some guidance for you to use in discussing both from a laymen’s perspective, a midpoint between the laymen and technical perspectives, and finally provide some thoughts on how to tie them into your environment. Generally, your executives and decision makers are going to need the laymen terms, but every once in a while, you will encounter someone who needs something deeper. Rarely have I seen the case where you will need to give a decision maker a very technical viewpoint, especially early on.

If you do take a technical deep dive into the key principles or best practices, I would recommend that you either have a current technical background and/or recent and thorough experience with RUP as well as the Rational tools. When you are just trying to float the idea of an improved process solution and set of tools, which is going to take a fundamental cultural change to be effective, being challenged early on and answering ineffectively can damage your efforts tremendously. If you don’t have the background and experience for the technical deep dive, don’t take it. I have rarely seen a lack of technical expertise be a negative when you disclose it from the beginning. Try this: Answer that you can discuss the business drivers for moving the company to the RUP and the Rational tools (which this book will provide), but for a deeper technical discussion, you would have to get one of the candidate future implementation team mentors to join the discussion. Rest assured, there are going to be the technical types that are going to challenge the idea of the RUP and Rational tools, but I have yet to see them want to continue the debate when you start discussing business drivers and returns on investment. My intention here is not to put off the technical side of the equation, as it is critically important. If you truly feel that you are qualified and will do more good than harm, then by all means press forward. However, if you don’t feel that you are qualified, rely on someone who is. To get to the future, you will have to get buy-in, funding, and momentum; often a little damage avoidance goes a long way this early in the process.

Note that it is also important when you are in the initial stages of introducing the idea of bringing in the RUP and the tools to your organization that you don’t bore people when trying to get them interested and planting the seeds for making the next steps a reality. Just as with the vision, having a well-prepared elevator speech for when a high-level response is warranted will help you clearly communicate a visual of the future based on why the person you are addressing should strive to be a part of that future you just painted.

Laymen Terms

Let’s start with the elevator speech type of guidance you can give when a high-level response is warranted. For the six key principles:

  • Adapt the process, balance competing stakeholder priorities, collaborate across teams, demonstrate value iteratively, elevate the level of abstraction, and focus continuously on quality are proven to help organizations such as ours make proper decisions for development driven by key principles. By adapting the process, we evolve the required formality over the project’s lifecycle, as uncertainties are resolved. We balance competing stakeholder priorities by taking the time to define, understand, and prioritize business and user needs and align our applications to those needs. Through collaboration across teams of business, software, and operations, we will motivate people and increase efficiency. Employing adaptive management using an iterative process, we will be able to demonstrate value iteratively. This will drive early risk reduction, reducing our project costs and increasing trust among our stakeholders. Complexity has become an issue in our software-intensive systems over time. By elevating the level of abstraction, we can reduce complexity and documentation by reusing existing assets and high-level modeling tools. By making the team responsible for the end product that will be delivered, everyone will focus on quality, which will happen continuously from the beginning to the end of our project’s lifecycle.

In an interview with Chips Magazine,5 Grady Booch6 (IBM Rational’s Chief Scientist) responded to a question on what the six best practices were. His response was one of the best I have seen:

  • Architecture [design] first, develop iteratively, test continuously, model visually, manage requirements, manage change—exist because they are proven to help an organization make the proper engineering and business decisions that balance the forces upon the software development organization. By focusing on architecture first, one intentionally attacks the highest technical risks in the system; by developing iteratively, one has the opportunity to reach closure on a regular rhythm and then make intelligent midcourse corrections relative to the current business and technical risks. Testing can then happen continuously, with each new release representing a baseline against which the emerging product can be measured relative to the current (and more deeply understood) requirements of the system. Modeling permits the team to visualize, specify, construct, and document the artifacts of a software-intensive system so as to control its architecture and reason about elements that cannot be known at the level of pure code. The management of requirements and the management of change refer to the intentional consideration of changing user needs (for the mere presence of a release will tell the user things they could not have known or asked about initially) and of the artifacts that constitute the developing product itself.

Midway Between Laymen and Technical Terms

Now let’s get a little deeper, say at the midpoint between laymen and technical. The simplest way to relate either the key principles or the best practices is to know a little about the person you are conversing with and target a key principle or best practice that relates to their role. State that RUP has a key principle that will help them and their team by taking some of the chaos out of their day-to-day work.

For example, the key principle to balance competing stakeholder priorities in RUP means that you are solving the right problem and building the right system. RUP provides discussion on how to understand and prioritize business and stakeholder needs, as well as providing prescriptive guidance on how to elicit, organize, document, and finally manage requirements. It will provide you with workflows and activities that will help you analyze the problem, understand what your users need, and help them distinguish between what is really needed and what they may only feel they need. It will show how to put boundaries around the scope of what the system and/or the specific project is going to include and manage the inevitable change and its impacts on the existing requirements.

The two most significant items that RUP and RequisitePro (the requirements management tool) will provide to you are capturing the functional (behavioral) requirements of the system with the Use Case technique, combined with a tool that facilitates the requirements management by combining both document-centric (through Microsoft Word) and database-centric (Access, SQL, DB2, etc.) methods. You will be able to organize your requirements and provide traceability and change management throughout the entire project lifecycle.

Then ask, so how are you doing it now? With email and spreadsheets? Where are your pain points?

  • + Share This
  • 🔖 Save To Your Account

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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