For software products developed using Plan And Document processes the

For software products developed using plan and

This preview shows page 370 - 372 out of 517 pages.

organizations use different people for Quality Assessment to do the testing and for user documentation. For software products developed using Plan-And-Document processes, the environment for maintenance is very different from the environment for development: Working software —A working software product is in the field during this whole phase, and new releases must not interfere with existing features. Customer collaboration —Rather than trying to meet a specification that is part of a negotiated contract, the goal for this phase is to work with customers to improve the product for the next release. Responding to change —Based on use of the product, customers send a stream of change requests , which can be new features as well as bug fixes. One challenge of the maintenance phase is prioritizing whether to implement a change request and in which release should it appear. Change requests are called maintenance requests in IEEE standards. Regression testing plays a much bigger role in maintenance to avoid breaking old features when developing new ones. Refactoring also plays a much bigger role, as you may need to refactor to implement a change request or simply to make the code more maintainable. There is less incentive for the extra cost and time to make the product easier to maintain in Plan-And-Document processes initially
Image of page 370
if the company developing the software is not the one that maintains it, which is one reason refactoring plays a smaller role during development. As mentioned above, change management is based on change requests made by customers and other stakeholders to fix bugs or to improve functionality (see Section 10.7 ). They typically fill out change request forms , which are tracked using a ticket tracking system so that each request is responded to and resolved. A key tool for change management is a version control system, which tracks all modifications to all objects, as we describe in Sections 10.4 and 10.5 . The prior paragraphs should sound familiar, for we are describing Agile development; in fact, the three bullets are copied from the Agile Manifesto (see Section 1.3 ). Thus, maintenance is essentially an Agile process . Change requests are like user stories; the triaging of change requests is similar to the assignment of points and using Pivotal Tracker to decide how to prioritize stories; and new releases of the software product act as Agile iterations of the working prototype. Plan-and-document maintenance even follows the same strategy of breaking a large change request into many smaller ones to make them easier to assess and implement, just as we do with user stories assigned more than eight points (see Section 7.2 ). Hence, if the same team is developing and maintaining the software, nothing changes after the first release of the product when using the Agile lifecycle. Although one paper reports successfully using an Agile process to maintain software developed using Plan-And-Document processes ( Poole and Huisman 2001 ), normally an organization that follows Plan- And-Document for development also follows it for maintenance. As we saw in earlier chapters, this
Image of page 371
Image of page 372

You've reached the end of your free preview.

Want to read all 517 pages?

  • Spring '19
  • Dr.Marcos

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes
A+ icon
Ask Expert Tutors