Home > Articles > Software Development & Management > UML

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

This chapter is from the book

Iterative and Incremental

The third fundamental tenet of the Unified Process is its iterative and incremental nature. An iteration is a mini-project that results in a version of the system that will be released internally or externally. This version is supposed to offer incremental improvement over the previous version, which is why the result of an iteration is called an increment.

The section "Iterations and Increments," which appears later in this chapter, describes how iterations and increments fit into the larger context of the overall process. Meanwhile, the following subsections describe the advantages of iterative and incremental development.

Logical Progress Toward a Robust Architecture

An earlier section, "Architecture-Centric," describes the central place of architecture in the Unified Process. The process specifies how the project team should focus on particular aspects of the architecture during each of the iterations of the system. During early iterations, the team puts together a candidate architecture that offers the beginnings of a solid foundation; later iterations find the team expanding the vision of the full architecture, which in turn influences most, and in some cases all, of the development tasks being performed as part of a given iteration. Building the architecture in an iterative and incremental fashion enables the team to make necessary major changes early in the process at considerably less cost than they would inflict later in the project.

Dealing With Ongoing Changes in Requirements

Processes based on the waterfall approach, which dictates that all of the requirements be gathered and analyzed before design starts, face what now seems to be an inevitable problem: Requirements tend to be unstable. Also, customers have difficulty envisioning a system when all they have is documentation. The Unified Process advocates breaking the system down into builds, where each build is a working version of some meaningful chunk of the full system. By focusing on bounded sets of use cases and making effective use of prototypes, the project team and the customers can negotiate requirements on an ongoing basis, thus reducing the (often very large) risk associated with trying to specify all of the requirements up front. One of the reviewers of the manuscript for this book indicated that his company practices "ruthless prioritization," which involves dealing with changing requirements by aggressively identifying priorities and eliminating lower-priority features from consideration.

Greater Flexibility to Change the Plan

Since each iteration is a mini-project, the project team addresses, to some extent, all the risks associated with the project as a whole each time it builds an increment of the system. As risks become greater, as delays occur, and as the environment becomes more unstable, the team is able to make necessary adjustments on a relatively small scale and propagate those adjustments across the entire project. During the postmortem for each iteration, the project leaders can decide whether the iteration was a success and change the iteration plan as appropriate before work proceeds with the next iteration. The goal is to isolate problems within iterations and deal with them on a relatively small scale, rather than allowing them to spread.

Continuous Integration

Each increment brings a combination of new features and improved functionality to the system. This enables all the stakeholders to measure the progress of the project toward specific goals, rather than toward more abstract and general requirements. By continually integrating new increments, the development team is also able to isolate problems that it might bring to the system and address those problems in ways that don't disrupt the integrity of the working system. This kind of setup makes it easier for the team to go as far as throwing a particular increment away and starting over, since the process gives it the ability to define iterations that take less time to perform.

Early Understanding

Each of the activities that the team performs during an iteration is straight-forwardly defined, as is the sequence of activities within each workflow and across workflows. The process is designed to enable reliance on things like ongoing mentoring, rather than forcing people to go through extensive training before becoming productive members of the team. Well-defined iterations allow room to experiment and make mistakes, because those mistakes will be isolated such that their impact on schedule and budget can be minimized. As work proceeds, the team can leverage its understanding of what it's trying to build and the associated risks, thus building momentum, which in turn enables the team to make continuous improvements in the way it goes about its tasks.

Ongoing Focus on Risk

Perhaps the most important advantage that iterative and incremental development, as defined by the Unified Process, brings to the table is the project team's ability to focus its efforts on addressing the most critical risks early in the life cycle. The team has a mandate to organize iterations based on addressing risks on an ongoing basis; the goal is to mitigate risks to the greatest extent possible during each iteration, so each iteration poses fewer risks of less importance than its predecessors.

Various people have come up with many different ways to categorize risks to software development projects. See UML Distilled (Martin Fowler with Kendall Scott; Addison-Wesley, 1999) for one view of risks. Three categories of risks useful in discussing the Unified Process are described next.

  • Technical risks are those associated with the various technologies that will come into play during the project and with issues such as performance and the "-ilities" (reliability, scalability, and so forth). For example, if the system will use Enterprise Java Beans (EJBs) in the context of the Common Object Request Broker Architecture (CORBA), the project team must solve a number of potential technical problems along the way to building a system that will perform acceptably. The process doesn't specifically address technical risks; however, the emphasis on architecture (see below) reflects the principle that the team should address technical risks early, before coding starts.

  • Architectural risks are those associated with the ability of the architecture to serve as a strong foundation of the system and also be sufficiently resilient and adaptable to the addition of features in future releases of the system. Risks associated with "make versus buy" decisions are also part of this category. The process addresses architectural risks by defining activities that involve analyzing, designing, and implementing the architecture, and by defining a number of other activities that include keeping the architecture description up to date so it can assume its place front and center within the development effort.

  • Requirements risk is the risk of not building the right system—the system that the customers are paying for—by not understanding the requirements and not using associated use cases to drive development. The process addresses requirements risk with activities specifically defined to facilitate the discovery and negotiation of requirements and with its premise that use cases should drive all aspects of development.

  • + 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