Fluent Essays

Important: Please make sure you have read the attached Down Town Car Repair Business Case. After some discussion with Tim, you decided to use Agile and Agile Usage-Centered Design for determining system requirements. For your written assignment this week, write a 700-word proposal (double-spaced and in APA format) that discusses the following points with the necessary references to support your claims/statements: What are some of the advantages of using Agile methodologies to capture system requirements? Provide an overview of the Agile Usage-Centered Design approach. Outline the steps involved in the Agile Usage-Centered Design. Explain why you would apply the Agile Usage-Centered Design approach to Tim’s proposal. Assignment Guidelines: Your proposal should be a minimum of 700 words, double-spaced. Use memo format (or other professional memo formats). Click on the following hyperlink to view and/or download a memo template from MS Word: Memo Template Make sure to provide references and cite your sources (APA format) as necessary. Please make sure you are using our textbook as a source. Save it as an MS Word file (e.g., .doc or .docx). [Company Name] Memo To: [Recipient Name] From: [Your Name] cc: [Name] Date: [Click to select date] Re: [Subject] How to Use This Memo Template Select the text you would like to replace, and type your memo. Use styles such as Heading 1-3 and Body Text from the Styles and Formatting work pane from the Format menu. To save changes to this template for future use, choose Save As from the File menu. In the Save As Type box, choose Document Template. Next time you want to use it, choose New from the File menu, select General Templates from the work pane, and then double-click you template. This template is provided by Microsoft Word. You can download other templates for memos and other formats at the following address: https://templates.office.com/ 1 2 B e l l e v u e U n i v e r s i t y | 1 CIS 521 | 2 0 1 9 Down Town Car Repair Business Case Introduction Tim Smith owns a small car repair shop called Down Town Car Repair. Tim does small and large car repair jobs for individual customers only. Tim doesn’t do commercial work. Tim manages all his accounts using pen and paper. Tim has contracted you to automate his small business. Assignment You will incrementally build your proposal. Each week you will deliver a small part of the overall proposal and deliver the final proposal the last week of class. Business Case Customers will call or drop in and ask Tim to bid on a repair. If the repair is small, such as an oil change, Tim will give them a fixed bid. However, if the repair is complex and needs some time for Tim to investigate the problem, he charges a fixed amount for the initial investigation and then provides a bid on the work. Either way, Tim creates a bid for all his work. Customers can either accept the bid or reject the bid. If the customer accepts the bid, then Tim starts the work. The bid contains the start date, estimated end date, estimated materials, estimated labor cost, and total estimated cost of the repairs. Tim buys material and supplies from various suppliers. Tim has an inventory of common material, such as belts, oil, tiers, and so forth. However, when a job requires special material, such as engines or transmissions, Tim orders these special materials from various suppliers. All of Tim’s suppliers allow him to make monthly payments on the materials he purchases. It is important that Tim understands what material he is purchasing for each supplier, the total amount due to each supplier, and the monthly amount due to each supplier. Once Tim completes the work, Tim create a bill for the work done. The bill contains the same information as the bid, but the amounts are adjusted based on B e l l e v u e U n i v e r s i t y | 2 CIS 521 | 2 0 1 9 the work Tim has done. Tim will not charge over the bid amount unless he calls the customer and gets their approval. If the total amount due is less than a certain dollar amount, the customer has to pay when they pick up their vehicle. If the amount due is over a certain amount Tim allows for monthly payments. However, each payment needs to be 10% of the outstanding amount due or a minimum of 100 dollars. If a customer fails to make a payment for one month, he charges a 10% late fee. If the customer fails to make a payment for a second month, he turns the account over to a collection agency. The collection agency then tries to collect payment. If the collection agency fails to collect payment after three months, Tim doesn’t have to pay the collection agency. If the collection agents collects partial payment or full payment, the collection agency takes 30% of the amount collected. GLOBAL EDITION GLOBAL EDITION GLO B A L E D IT IO N This is a special edition of an established title widely used by colleges and universities throughout the world. Pearson published this exclusive edition for the benefit of students outside the United States and Canada. If you purchased this book within the United States or Canada, you should be aware that it has been imported without the approval of the Publisher or Author. Modern Systems Analysis and Design presents the skills, techniques, tools, and perspectives that students need to successfully develop information systems. Its expansive coverage of tools and systems development methodologies is structured along the systems development life cycle, providing students with a strong conceptual and systematic framework. Central to the book’s approach is the theme that systems development is a practical field and a profession, always rooted in an organizational basis. Focusing on the role, responsibilities, and mind-set of the systems analyst and the systems project manager, the coverage also encompasses skills such as systems documentation, project management, team management, and a variety of systems development and acquisition strategies. The ninth edition also includes the following features to prepare students for the modern systems development environment. • NEW—This edition’s expanded coverage includes a new section on Scrum and an updated section on information systems security. • UPDATED—Screen captures familiarize students with the latest versions of programming environments, Internet development environments, and user interface designs. • Three illustrative cases, each spread across several chapters, illustrate key aspects of systems development and bring chapter concepts to life. • UPDATED—Review Questions and Problems and Exercises test students’ understanding, and Field Exercises help them explore systems analysis and design in organizations. Modern Systems Analysis and Design M o dern System s A nalysis and D esign V alacich • G eo rge N IN T H E D IT IO N NINTH EDITION Joseph S. Valacich Joey F. George CVR_VALA1629_09_GE_CVR.indd 1 08/04/20 5:58 PM Modern Systems Analysis and Design Joseph S. Valacich University of Arizona Joey F. George Iowa State University N I N T H E D I T I O N G L O B A L E D I T I O N Harlow, England • London • New York • Boston • San Francisco • Toronto • Sydney • Dubai • Singapore • Hong Kong Tokyo • Seoul • Taipei • New Delhi • Cape Town • São Paulo • Mexico City • Madrid • Amsterdam • Munich • Paris • Milan A01_VALA1629_09_GE_FM.indd 1 15/04/2020 11:21 Please contact https://support.pearson.com/getsupport/s/contactsupport with any queries on this content. Microsoft and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published as part of the services for any purpose. All such documents and related graphics are provided “as is” without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all warranties and conditions of merchantability, whether express, implied or statutory, fitness for a particular purpose, title and non-infringement. In no event shall Microsoft and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from the services. The documents and related graphics contained herein could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Microsoft and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time. Partial screen shots may be viewed in full within the software version specified. Microsoft® and Windows® are registered trademarks of the Microsoft Corporation in the U.S.A. and other countries. This book is not sponsored or endorsed by or affiliated with the Microsoft Corporation. Pearson Education Limited KAO Two KAO Park Hockham Way Harlow Essex CM17 9SR United Kingdom and Associated Companies throughout the world Visit us on the World Wide Web at: www.pearsonglobaleditions.com © Pearson Education Limited, 2021 The rights of Joseph S. Valacich and Joey F. George to be identified as the authors of this work have been asserted by them in accordance with the Copyright, Designs and Patents Act 1988. Authorized adaptation from the United States edition, entitled Modern Systems Analysis and Design, 9th Edition, ISBN 978-0-13-517275-9 by Joseph S. Valacich and Joey F. George, published by Pearson Education © 2020. Acknowledgments of third-party content appear on the appropriate page within the text. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without either the prior written permission of the publisher or a license permitting restricted copying in the United Kingdom issued by the Copyright Licensing Agency Ltd, Saffron House, 6–10 Kirby Street, London EC1N 8TS. All trademarks used herein are the property of their respective owners. The use of any trademark in this text does not vest in the author or publisher any trademark ownership rights in such trademarks, nor does the use of such trademarks imply any affiliation with or endorsement of this book by such owners. For information regarding permissions, request forms, and the appropriate contacts within the Pearson Education Global Rights and Permissions department, please visit www.pearsoned.com/permissions/. This eBook is a standalone product and may or may not include all assets that were part of the print version. It also does not provide access to other Pearson digital products like MyLab and Mastering. The publisher reserves the right to remove any material in this eBook at any time. ISBN 10: 1-292-35162-4 ISBN 13: 978-1-292-35162-9 eBook ISBN 13: 978-1-292-35163-6 British Library Cataloguing-in-Publication Data A catalogue record for this book is available from the British Library Cover image: Ashalatha/Shutterstock eBook formatted by SPi Global A01_VALA1629_09_GE_FM_CR_page.indd 2 20/04/2020 21:44 https://support.pearson.com/getsupport/s/contactsupport http://www.pearsonglobaleditions.com http://www.pearsoned.com/permissions/ To my mother, Mary Valacich. You are the best! —Joe To my parents, John and Loree George. —Joey A01_VALA1629_09_GE_FM.indd 3 15/04/2020 11:21 This page intentionally left blank A01_THOM6233_05_SE_WALK.indd 9 1/13/17 6:50 PM 5 Preface 19 PART ONE Foundations for Systems Development 25 1 The Systems Development Environment 27 2 The Origins of Software 47 3 Managing the Information Systems Project 64 Appendix: Object-Oriented Analysis and Design: Project Management 98 PART TWO Planning 107 4 Identifying and Selecting Systems Development Projects 109 5 Initiating and Planning Systems Development Projects 133 PART THREE Analysis 167 6 Determining System Requirements 169 7 Structuring System Process Requirements 203 Appendix 7A: Object-Oriented Analysis and Design: Use Cases 237 Appendix 7B: Object-Oriented Analysis and Design: Activity Diagrams 252 Appendix 7C: Business Process Modeling 257 8 Structuring System Data Requirements 266 Appendix: Object-Oriented Analysis and Design: Object Modeling–Class Diagrams 301 PART FOUR Design 319 9 Designing Databases 321 10 Designing Forms and Reports 363 11 Designing Interfaces and Dialogues 391 12 Designing Distributed and Internet Systems 427 PART FIVE Implementation and Maintenance 461 13 System Implementation 463 14 Maintaining Information Systems 495 GLOSSARY OF TERMS 513 GLOSSARY OF ACRONYMS 520 INDEX 521 Brief Contents A01_VALA1629_09_GE_FM.indd 5 15/04/2020 11:21 This page intentionally left blank A01_THOM6233_05_SE_WALK.indd 9 1/13/17 6:50 PM 7 Preface 19 PART ONE Foundations for Systems Development AN OVERVIEW OF PART ONE 26 1 The Systems Development Environment 27 Learning Objectives 27 Introduction 27 A Modern Approach to Systems Analysis and Design 29 Developing Information Systems and the Systems Development Life Cycle 30 The Heart of the Systems Development Process 35 The Traditional Waterfall SDLC 36 Agile Methodologies 38 eXtreme Programming 39 Scrum 40 Agile in Practice 41 Object-Oriented Analysis and Design 42 Our Approach to Systems Development 44 Summary 45 Key Terms 45 Review Questions 45 Problems and Exercises 46 Field Exercises 46 References 46 2 The Origins of Software 47 Learning Objectives 47 Introduction 47 Systems Acquisition 47 Outsourcing 48 Sources of Software 49 Choosing Off-the-Shelf Software 55 Validating Purchased Software Information 57 Reuse 58 Summary 60 Key Terms 61 Review Questions 61 Contents A01_VALA1629_09_GE_FM.indd 7 15/04/2020 11:21 8 CONTENTS Problems and Exercises 61 Field Exercises 61 References 62 BEC CASE: THE ORIGINS OF SOFTWARE 63 Case Questions 63 3 Managing the Information Systems Project 64 Learning Objectives 64 Introduction 64 Pine Valley Furniture Company Background 64 Managing the Information Systems Project 66 Initiating a Project 70 Planning the Project 72 Executing the Project 79 Closing Down the Project 82 Representing and Scheduling Project Plans 83 Representing Project Plans 85 Calculating Expected Time Durations Using PERT 85 Constructing a Gantt Chart and Network Diagram at Pine Valley Furniture 86 Using Project Management Software 89 Establishing a Project Start Date 90 Entering Tasks and Assigning Task Relationships 90 Selecting a Scheduling Method to Review Project Reports 91 Summary 93 Key Terms 93 Review Questions 94 Problems and Exercises 94 Field Exercises 96 References 96 Appendix: Object-Oriented Analysis and Design: Project Management 98 Learning Objectives 98 Unique Characteristics of an OOSAD Project 98 Define the System as a Set of Components 98 Complete Hard Problems First 98 Using Iterations to Manage the Project 100 Don’t Plan Too Much Up Front 100 How Many and How Long Are Iterations? 102 Project Activity Focus Changes Over the Life of a Project 102 Summary 104 Review Question 104 Problems and Exercises 104 BEC CASE: MANAGING THE INFORMATION SYSTEMS PROJECT 105 Case Questions 105 PINE VALLEY FURNITURE PINE VALLEY FURNITURE PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 8 15/04/2020 11:21 CONTENTS 9 PART TWO Planning AN OVERVIEW OF PART TWO 108 4 Identifying and Selecting Systems Development Projects 109 Learning Objectives 109 Introduction 109 Identifying and Selecting Systems Development Projects 110 The Process of Identifying and Selecting IS Development Projects 111 Deliverables and Outcomes 115 Corporate and Information Systems Planning 116 Corporate Strategic Planning 117 Information Systems Planning 119 Electronic Commerce Applications: Identifying and Selecting Systems Development Projects 126 Internet Basics 126 Pine Valley Furniture WebStore 127 Summary 128 Key Terms 128 Review Questions 129 Problems and Exercises 129 Field Exercises 130 References 130 BEC CASE: IDENTIFYING AND SELECTING SYSTEMS DEVELOPMENT PROJECTS 132 Case Questions 132 5 Initiating and Planning Systems Development Projects 133 Learning Objectives 133 Introduction 133 Initiating and Planning Systems Development Projects 133 The Process of Initiating and Planning is Development Projects 134 Deliverables and Outcomes 135 Assessing Project Feasibility 136 Assessing Economic Feasibility 137 Assessing Technical Feasibility 145 Assessing Other Feasibility Concerns 148 Building and Reviewing the Baseline Project Plan 149 Building the Baseline Project Plan 149 Reviewing the Baseline Project Plan 154 Electronic Commerce Applications: Initiating and Planning Systems Development Projects 159 Initiating and Planning Systems Development Projects for Pine Valley Furniture’s WebStore 159 Summary 161 Key Terms 161 PINE VALLEY FURNITURE PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 9 15/04/2020 11:21 10 CONTENTS Review Questions 162 Problems and Exercises 162 Field Exercises 163 References 163 BEC CASE: INITIATING AND PLANNING SYSTEMS DEVELOPMENT PROJECTS 165 Case Questions 165 PART THREE Analysis AN OVERVIEW OF PART THREE 168 6 Determining System Requirements 169 Learning Objectives 169 Introduction 169 Performing Requirements Determination 169 The Process of Determining Requirements 170 Deliverables and Outcomes 171 Traditional Methods for Determining Requirements 172 Interviewing and Listening 172 Interviewing Groups 176 Directly Observing Users 177 Analyzing Procedures and Other Documents 178 Contemporary Methods for Determining System Requirements 183 Joint Application Design 184 Using Prototyping During Requirements Determination 186 Radical Methods for Determining System Requirements 188 Identifying Processes to Reengineer 189 Disruptive Technologies 190 Requirements Determination Using Agile Methodologies 191 Continual User Involvement 191 Agile Usage-Centered Design 192 The Planning Game from eXtreme Programming 192 Electronic Commerce Applications: Determining System Requirements 194 Determining System Requirements for Pine Valley Furniture’s WebStore 195 Summary 197 Key Terms 198 Review Questions 198 Problems and Exercises 199 Field Exercises 199 References 200 BEC CASE: DETERMINING SYSTEM REQUIREMENTS 201 Case Questions 202 PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 10 15/04/2020 11:21 CONTENTS 11 7 Structuring System Process Requirements 203 Learning Objectives 203 Introduction 203 Process Modeling 203 Modeling a System’s Process for Structured Analysis 204 Deliverables and Outcomes 204 Data Flow Diagramming Mechanics 205 Definitions and Symbols 205 Developing DFDs: An Example 207 Data Flow Diagramming Rules 210 Decomposition of DFDs 211 Balancing DFDs 214 An Example DFD 216 Using Data Flow Diagramming in the Analysis Process 219 Guidelines for Drawing DFDs 219 Using DFDs as Analysis Tools 221 Using DFDs in Business Process Reengineering 222 Modeling Logic with Decision Tables 223 Electronic Commerce Application: Process Modeling Using Data Flow Diagrams 227 Process Modeling for Pine Valley Furniture’s WebStore 227 Summary 229 Key Terms 229 Review Questions 230 Problems and Exercises 230 Field Exercises 236 References 236 Appendix 7A: Object-Oriented Analysis and Design: Use Cases 237 Learning Objectives 237 Introduction 237 Use Cases 237 What Is a Use Case? 237 Use Case Diagrams 238 Definitions and Symbols 239 Written Use Cases 242 Level 243 The Rest of the Template 243 Electronic Commerce Application: Process Modeling Using Use Cases 245 Writing Use Cases for Pine Valley Furniture’s WebStore 247 Summary 250 Key Terms 250 Review Questions 250 Problems and Exercises 250 Field Exercise 251 References 251 Hoosier Burger PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 11 15/04/2020 11:21 12 CONTENTS Appendix 7B: Object-Oriented Analysis and Design: Activity Diagrams 252 Learning Objectives 252 Introduction 252 When to Use an Activity Diagram 255 Problems and Exercises 255 Reference 256 Appendix 7C: Business Process Modeling 257 Learning Objective 257 Introduction 257 Basic Notation 257 Business Process Example 261 Summary 262 Key Terms 262 Review Questions 262 Problems and Exercises 262 Field Exercises 263 References 263 BEC CASE: STRUCTURING SYSTEM PROCESS REQUIREMENTS 264 Case Questions 265 8 Structuring System Data Requirements 266 Learning Objectives 266 Introduction 266 Conceptual Data Modeling 267 The Conceptual Data Modeling Process 268 Deliverables and Outcomes 269 Gathering Information for Conceptual Data Modeling 270 Introduction to E-R Modeling 272 Entities 272 Attributes 274 Candidate Keys and Identifiers 275 Other Attribute Types 276 Relationships 277 Conceptual Data Modeling and the E-R Model 278 Degree of a Relationship 279 Cardinalities in Relationships 281 Naming and Defining Relationships 282 Associative Entities 283 Summary of Conceptual Data Modeling with E-R Diagrams 285 Representing Supertypes and Subtypes 285 Business Rules 286 Domains 287 Triggering Operations 289 A01_VALA1629_09_GE_FM.indd 12 15/04/2020 11:21 CONTENTS 13 Role of Packaged Conceptual Data Models: Database Patterns 290 Universal Data Models 290 Industry-Specific Data Models 290 Benefits of Database Patterns and Packaged Data Models 290 Electronic Commerce Application: Conceptual Data Modeling 291 Conceptual Data Modeling for Pine Valley Furniture’s WebStore 291 Summary 295 Key Terms 295 Review Questions 296 Problems and Exercises 297 Field Exercises 299 References 300 Appendix: Object-Oriented Analysis and Design: Object Modeling—Class Diagrams 301 Learning Objectives 301 Introduction 301 Representing Objects and Classes 301 Types of Operations 302 Representing Associations 303 Representing Associative Classes 305 Representing Stereotypes for Attributes 306 Representing Generalization 306 Representing Aggregation 309 An Example of Conceptual Data Modeling at Hoosier Burger 310 Summary 313 Key Terms 313 Review Questions 314 Problems and Exercises 314 References 315 BEC CASE: STRUCTURING SYSTEM DATA REQUIREMENTS 316 Case Questions 317 PART FOUR Design AN OVERVIEW OF PART FOUR 320 9 Designing Databases 321 Learning Objectives 321 Introduction 321 Database Design 321 The Process of Database Design 322 Deliverables and Outcomes 324 The Relational Database Model 327 Well-Structured Relations 327 PINE VALLEY FURNITURE Hoosier Burger A01_VALA1629_09_GE_FM.indd 13 15/04/2020 11:21 14 CONTENTS Normalization 328 Rules of Normalization 329 Functional Dependence and Primary Keys 329 Second Normal Form 330 Third Normal Form 330 Transforming E-R Diagrams into Relations 331 Represent Entities 332 Represent Relationships 332 Summary of Transforming E-R Diagrams to Relations 336 Merging Relations 336 An Example of Merging Relations 336 View Integration Problems 337 Logical Database Design for Hoosier Burger 338 Physical File and Database Design 341 Designing Fields 341 Choosing Data Types 342 Controlling Data Integrity 343 Designing Physical Tables 344 Arranging Table Rows 347 Designing Controls for Files 351 Physical Database Design for Hoosier Burger 352 Electronic Commerce Application: Designing Databases 353 Designing Databases for Pine Valley Furniture’s WebStore 354 Summary 356 Key Terms 357 Review Questions 358 Problems and Exercises 358 Field Exercises 359 References 360 BEC CASE: DESIGNING DATABASES 361 Case Questions 362 10 Designing Forms and Reports 363 Learning Objectives 363 Introduction 363 Designing Forms and Reports 363 The Process of Designing Forms and Reports 365 Deliverables and Outcomes 366 Formatting Forms and Reports 370 General Formatting Guidelines 370 Highlighting Information 372 Color versus No Color 374 Displaying Text 375 Designing Tables and Lists 375 Paper versus Electronic Reports 379 Hoosier Burger Hoosier Burger PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 14 15/04/2020 11:21 CONTENTS 15 Assessing Usability 381 Usability Success Factors 381 Measures of Usability 382 Electronic Commerce Applications: Designing Forms and Reports for Pine Valley Furniture’s WebStore 383 General Guidelines 383 Designing Forms and Reports at Pine Valley Furniture 383 Lightweight Graphics 384 Forms and Data Integrity Rules 384 Stylesheet-Based HTML 385 Summary 385 Key Terms 385 Review Questions 386 Problems and Exercises 386 Field Exercises 387 References 387 BEC CASE: DESIGNING FORMS AND REPORTS 389 Case Questions 389 11 Designing Interfaces and Dialogues 391 Learning Objectives 391 Introduction 391 Designing Interfaces and Dialogues 391 The Process of Designing Interfaces and Dialogues 391 Deliverables and Outcomes 392 Interaction Methods and Devices 392 Methods of Interacting 392 Hardware Options for System Interaction 400 Designing Interfaces 402 Designing Layouts 402 Structuring Data Entry 405 Controlling Data Input 407 Providing Feedback 408 Providing Help 410 Designing Dialogues 412 Designing the Dialogue Sequence 413 Building Prototypes and Assessing Usability 415 Designing Interfaces and Dialogues in Graphical Environments 417 Graphical Interface Design Issues 417 Dialogue Design Issues in a Graphical Environment 419 Electronic Commerce Application: Designing Interfaces and Dialogues for Pine Valley Furniture’s WebStore 419 General Guidelines 420 Designing Interfaces and Dialogues at Pine Valley Furniture 421 Menu-Driven Navigation with Cookie Crumbs 421 PINE VALLEY FURNITURE PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 15 15/04/2020 11:21 16 CONTENTS Summary 422 Key Terms 422 Review Questions 423 Problems and Exercises 423 Field Exercises 424 References 424 BEC CASE: DESIGNING INTERFACES AND DIALOGUES 425 Case Questions 426 12 Designing Distributed and Internet Systems 427 Learning Objectives 427 Introduction 427 Designing Distributed and Internet Systems 427 The Process of Designing Distributed and Internet Systems 427 Deliverables and Outcomes 428 Designing LAN and Client/Server Systems 429 Designing Systems for LANs 429 Designing Systems for a Client/Server Architecture 431 Cloud Computing 435 What Is Cloud Computing? 435 Managing the Cloud 439 Service-Oriented Architecture 442 Web Services 443 Designing Internet Systems 444 Internet Design Fundamentals 445 Site Consistency 446 Design Issues Related to Site Management 448 Electronic Commerce Application: Designing a Distributed Advertisement Server for Pine Valley Furniture’s WebStore 451 Advertising on Pine Valley Furniture’s WebStore 451 Designing the Advertising Component 452 Designing the Management Reporting Component 453 Summary 454 Key Terms 454 Review Questions 456 Problems and Exercises 456 Field Exercises 457 References 458 BEC CASE: DESIGNING DISTRIBUTED AND INTERNET SYSTEMS 459 Case Questions 459 PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 16 15/04/2020 11:21 CONTENTS 17 PART FIVE Implementation and Maintenance AN OVERVIEW OF PART FIVE 462 13 System Implementation 463 Learning Objectives 463 Introduction 463 System Implementation 464 Coding, Testing, and Installation Processes 465 Deliverables and Outcomes from Coding, Testing, and Installation 465 Deliverables and Outcomes from Documenting the System, Training Users, and Supporting Users 466 Software Application Testing 467 Seven Different Types of Tests 468 The Testing Process 470 Combining Coding and Testing 472 Acceptance Testing by Users 473 Installation 474 Direct Installation 474 Parallel Installation 474 Single-Location Installation 475 Phased Installation 476 Planning Installation 476 Documenting the System 477 User Documentation 478 Training and Supporting Users 479 Training Information Systems Users 480 Supporting Information Systems Users 481 Organizational Issues in Systems Implementation 482 Why Implementation Sometimes Fails 483 Security Issues 485 Electronic Commerce Application: System Implementation and Operation for Pine Valley Furniture’s WebStore 487 Developing Test Cases for the WebStore 487 Alpha and Beta Testing the WebStore 488 WebStore Installation 489 Project Closedown 489 Summary 490 Key Terms 490 Review Questions 491 Problems and Exercises 492 Field Exercises 492 References 493 BEC CASE: SYSTEM IMPLEMENTATION 494 Case Questions 494 PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 17 15/04/2020 11:21 18 CONTENTS 14 Maintaining Information Systems 495 Learning Objectives 495 Introduction 495 Maintaining Information Systems 495 The Process of Maintaining Information Systems 496 Deliverables and Outcomes 497 Conducting Systems Maintenance 498 Types of Maintenance 498 The Cost of Maintenance 499 Managing Maintenance 501 Role of Automated Development Tools in Maintenance 506 Website Maintenance 506 Electronic Commerce Application: Maintaining an Information System for Pine Valley Furniture’s WebStore 508 Maintaining Pine Valley Furniture’s WebStore 508 Cannot Find Server 508 Summary 509 Key Terms 510 Review Questions 510 Problems and Exercises 511 Field Exercises 511 References 511 GLOSSARY OF TERMS 513 GLOSSARY OF ACRONYMS 520 INDEX 521 PINE VALLEY FURNITURE A01_VALA1629_09_GE_FM.indd 18 15/04/2020 11:21 19 Preface DESCRIPTION Modern Systems Analysis and Design, Ninth Edition, covers the concepts, skills, meth- odologies, techniques, tools, and perspectives essential for systems analysts to suc- cessfully develop information systems. The primary target audience is upper-division undergraduates in a management information systems (MIS) or computer informa- tion systems curriculum; a secondary target audience is MIS majors in MBA and MS programs. Although not explicitly written for the junior college and professional de- velopment markets, this book can also be used by these programs. We have over 60 years of combined teaching experience in systems analysis and design and have used that experience to create this newest edition of Modern Systems Analysis and Design. We provide a clear presentation of the concepts, skills, and tech- niques that students need to become effective systems analysts who work with others to create information systems for businesses. We use the systems development life cycle (SDLC) model as an organizing tool throughout the book to provide students with a strong conceptual and systematic framework. The SDLC in this edition has five phases and a circular design. With this text, we assume that students have taken an introductory course on computer systems and have experience designing programs in at least one program- ming language. We review basic system principles for those students who have not been exposed to the material on which systems development methods are based. We also assume that students have a solid background in computing literacy and a general understanding of the core elements of a business, including basic terms as- sociated with the production, marketing, finance, and accounting functions. NEW TO THE NINTH EDITION The following features are new to the Ninth Edition: • New material. To keep up with the changing environment for systems develop- ment, Chapter 1 has undergone a thorough revision, with a renewed focus on agile methodologies. While the book has long included material on eXtreme Programming, we now also include a section on Scrum. • Updated content. Throughout the book, the content in each chapter has been updated where appropriate. We have expanded our coverage of multiple topics in Chapter 2. Another example of an updated chapter is Chapter 13, where we have updated and extended the section on information systems security. Chapter 13 also includes new examples of systems implementation failure. All screenshots come from current versions of leading software prod- ucts. We have also made a special effort to update our reference lists, purging out-of-date material and including current references. Throughout the book figures, tables, and related content have been updated and refreshed. • Dropped material. In our efforts to keep the book current and to streamline it, the coverage of some things was dropped from this edition. Chapters 1, 6 and 7 no longer include computer assisted systems engineering (CASE) tools. We also made some changes in the appendices to Chapter 7. We deleted the appendix on UML sequential diagrams. Appendix 7A is still about use cases, A01_VALA1629_09_GE_FM.indd 19 15/04/2020 11:21 20 PREFACE and Appendix 7B is still about activity diagrams, but Appendix 7C is now about Business Process Management Notation. • Organization. We have retained the organization of the book first introduced in the Sixth Edition, with the only change being the deletion of the former Appendix 7C. We have 14 chapters and 5 appendices. The first appendix fol- lows Chapter 1. Three appendices follow Chapter 7. The fifth appendix follows Chapter 8. This streamlined organization worked well in the Sixth, Seventh and Eighth Editions, so we decided to continue with it and improve on it. • Approach to presentation of object-oriented material. We generally retain our approach to object-orientation (OO) from the last edition. Brief appendices related to the object-oriented approach continue to appear immediately after related chapters. The OO appendices appear as follows: Chapter 3 features a special OO section on IS project management. Chapter 7 now has two OO appendices: one on use cases and one about activity diagrams. (The third appendix to Chapter 7 is about Business Process Management Notation, which is not part of UML, although it is governed by the Object Management Group (OMG).) Chapter 8 has a special section on object-oriented database design. The rationale for this organization is the same as …