![ian sommerville software engineering 9th test bank ian sommerville software engineering 9th test bank](https://image.slidesharecdn.com/ch-4-150605220936-lva1-app6891/95/ian-sommerville-software-engineering-9th-edition-ch-4-37-1024.jpg)
This publication is protected by copyright, and permission should be obtained from the publisher prior to any prohibited reproduction, storage in a retrieval system, or transmission in any form or by any means, electronic, mechanical, photocopying, recording, or likewise. Manufactured in the United States of America. Printer/Binder: Edwards Brothers Cover Printer: Lehigh-Phoenix Color/Hagerstown Copyright © 2011, 2006, 2005, 2001, 1996 Pearson Education, Inc., publishing as Addison-Wesley. Composition and Illustrations: GGS Higher Education Resources, a Division of PreMedia Global, Inc.
![ian sommerville software engineering 9th test bank ian sommerville software engineering 9th test bank](https://www.coursehero.com/thumb/17/fe/17fe1ccf12ad36d11447e996f3f8a102d3665cc0_180.jpg)
![ian sommerville software engineering 9th test bank ian sommerville software engineering 9th test bank](https://image.slidesharecdn.com/ch2-150605220819-lva1-app6892/85/ian-sommerville-software-engineering-9th-edition-ch2-24-638.jpg)
Problems: The process is not visible Managers need regular deliverables to measure progress System structure tends to degrade as new increments are added Unless time and money is spent on refactoring to improve the software, regular change tends to corrupt its structure.Addison-Wesley Boston Columbus Indianapolis New York San Francisco Upper Saddle River Amsterdam Cape Town Dubai London Madrid Milan Munich Paris Montreal Toronto Delhi Mexico City São Paulo Sydney Hong Kong Seoul Singapore Taipei TokyoĮditorial Director: Marcia Horton Editor in Chief: Michael Hirsch Acquisitions Editor: Matt Goldstein Editorial Assistant: Chelsea Bell Managing Editor: Jeff Holcomb Senior Production Project Manager: Marilyn Lloyd Director of Marketing: Margaret Waples Marketing Coordinator: Kathryn Ferranti Senior Manufacturing Buyer: Carol Melville Text Designer: Susan Raymond Cover Art Director: Elena Sidorova Front Cover Photograph: © Jacques Pavlovsky/Sygma/Corbis Interior Chapter Opener: © /Alamy Full-Service Project Management: Andrea Stefanowicz, GGS Higher Education Resources, a Division of PreMedia Global, Inc. Incremental development is based on the idea of developing an initial implementation, exposing this to user comment and evolving it through several versions until an adequate (acceptable) system has been developed Generally, the early increments of the system include the most important or most urgently required functionality Can be either plan-driven, agile, or a mixture of bothīenefits: The cost of accommodating changing customer requirements is reduced It is easier to get customer feedback on the development work that has been done More rapid delivery and deployment of useful software to the customer is possible Benefit? Problem: Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements Use: When the requirements are well-understood and changes will be fairly limited during the design process. Requirements analysis and definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance The result of each phase is one or more documents The following phase should not start until the previous phase has finished (in practice, they overlap)Ĩ The Waterfall Model Advantage: the process is visibleĭocumentation is produced at each phase. Products (outcomes of a process activity) Roles (responsibilities of people) Pre- and post-conditions Sometimes, software processes are categorized as either plan-driven or agile processesĪ software process model is a simplified representation of a software process Each process model represents a process from a particular perspective, and thus provides a partial information about that process Process models covered: The waterfall model Incremental development Reuse-oriented software engineeringħ The Waterfall Model Separate identified phases in the waterfall model: Incremental Development Reuse Oriented Software Engineeringģ Software Process A software process is a set of related activities that leads to the production of a software product There are many different software processes but all must include four activities: Software specification Software design and implementation Software validation Software evolutionĤ Software Process A software process may also include:
![ian sommerville software engineering 9th test bank ian sommerville software engineering 9th test bank](https://d20ohkaloyme4g.cloudfront.net/img/document_thumbnails/f2fb6a6e534fa4b8b929a1ebab05f919/thumb_300_388.png)
Software Process Models FebruSommerville, I., Software Engineering, Pearson, 9th Ed., 2010.Ģ Overview Software Process Software Process Models Waterfall Model 1 Sommerville, I., Software Engineering, Pearson, 9th Ed., 2010.