CONTENTS PART ONE FOUNDATIONS FOR SYSTEMS DEVELOPMENT. Preface 21

Similar documents
DETERMINING SYSTEM REQUIREMENTS. Systems Analysis and Design

Modern Systems Analysis and Design Seventh Edition

Modern Systems Analysis and Design Sixth Edition. Jeffrey A. Hoffer Joey F. George Joseph S. Valacich. Chapter 14 Maintaining Information Systems

Chapter. Redesigning The Organization With Information Systems

The Systems Development Lifecycle

System Development Life Cycle Fall Introduction to Information and Communication Technologies CSD 102

Chapter 1 The Systems Development Environment

Modern Systems Analysis and Design Seventh Edition

Major attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis

Chapter 1 Systems Development in an Organization Context

INFORMATION SYSTEMS ANALYSIS AND DESIGN

Introduction to Systems Analysis and Design

Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1

CONTENTS. Part I BUSINESS PROCESSES AND INFORMATION SYSTEMS FOUNDATION 1. Part II TECHNOLOGY FOR BUSINESS PROCESSES AND INFORMATION SYSTEMS 65

The Systems Development Environment

Project Time Management

Software Engineering in the Agile World. Table of contents

Software Engineering II - Exercise

AUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT

Redesigning the Organization with Information Systems

Chapter 8. Systems Development. Ralph M. Stair George W. Reynolds

Basics of Software Engineering. Carmen Navarrete

Working Towards Lightweight Enterprise Architectures: the Process, frameworks, standards, and models

Software Engineering (CSC 4350/6350) Rao Casturi

Building Information Systems

Dr. Mounir Kehal BSc Comp. (IS Eng), MBA, MPhil, PhD AI/KM Carleton University, American University in London, Surrey University

Ali Khan < Project Name > Software Requirements Specification. Version 1.0. Group Id: F16. Supervisor Name: Sir/Miss.

Processes, Systems, and Information

Prerequisites It is recommended that the participants have a working knowledge of traditional Business Analysis tasks and techniques.

INTRODUCTION. Objectives. Unit 1: Introduction to Systems Analysis and Design. Key Ideas

1) Introduction to Information Systems

Unit 9 Information Systems

Introduction Systems development life cycle (SDLC) -a structured step-bystep approach for developing information systems.

Chapter 13. Building Information Systems

Managing Systems Development. Definitions. Opening case. Off the Shelf software. Custom software. In house system development.

KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK

4/3/2010. Objectives Overview. What is System Development? Objectives Overview. What is System Development? What is System Development?

Harry J. Rosenblatt. (2014). Systems Analysis and Design, 10 th Edition, International Edition. Course Technology, Cengage Learning.

Systems Analysis and Design 8 th Edition. Chapter 1 Introduction to Systems Analysis and Design

CS SOFTWARE ENGINEERING QUESTION BANK

Software Processes. Chapter 2. CMPT 276 Dr. B. Fraser Based on slides from Software Engineering 9 th ed, Sommerville.

Software Quality Engineering Courses Offered by The Westfall Team

Software Quality Engineering Courses Offered by The Westfall Team

System Development Life Cycle (SDLC) Project

BCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT IT PROJECT MANAGEMENT

Analysing client requirements

Office of Human Resources. IT Systems Analyst Associate - LI2213

Management Information Systems. B14. Acquiring IT Applications and Infrastructure

Information Technology Audit & Cyber Security

2068 I. Attempt any ten questions. (10x6=60)

Oracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM. An Oracle White Paper April 2012

CSCC40 Analysis and Design of Information Systems mid-term exam

System Engineering and Analysis. system environments. Lecture Objectives. System Elements. Definition of System. Information system types

Oracle Hyperion Planning for Interactive Users

6/29/ Professor Lili Saghafi

Systems Analysis for Business Analysts (3 Day)

Chapter 2 The Project Management Life Cycle

COPYRIGHTED MATERIAL. Contents

CONTENTS. Introduction to Software Engineering. Software Process and Life Cycle Models. Software Life-Cycle Model-2. Chapter 1. Chapter 2.

CS360. Business Information Systems Analysis and Modeling. Project Management, JAD, Agile. LJ Waguespack, Ph.D Unit 09: 1

Project vs Operation. Project Constraints. Pankaj Sharma, Pankaj Sharma,

Program Lifecycle Methodology Version 1.7

Processes. Object Orientated Analysis and Design. Benjamin Kenwright

PMBOK Guide 6 th Edition: What s in it for Me??? Cheryl C Allen, MS, PMP C Allen Associates

(Week 11) A06. IS Analysis & Design. Management Information Systems

Acquiring IT Applications and Infrastructure

SOCCI - Towards a Common Software Engineering Environment for Science Operations

Contents. Preface 19. digitalisiert durch: IDS Basel Bern. Information systems today 2016

Building Information Systems

Development Process and Analysis. LTOOD/OOAD - Verified Software Systems 1

Lesson 15-Planning and Costing

Chapter 1 Introduction to Systems Analysis and Design

Project Management is only a tool - it is never a substitute for effective managers.

Preface... iii Introduction... xvii Chapter 1: Introduction to Management Information System... 1

Introduction. Figure 1-1

INFORMATION TECHNOLOGY PROJECT MANAGEMENT. Fourth Edition. International Student Version. Jack T. Marchewka WILEY. John Wiley & Sons, Inc.

Lecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation

Software Engineering (CSC 4350/6350) Rao Casturi

[Name] [ ID] [Contact Number]

Project Report Template (Sem 1)

Chapter 2: Project Methodologies and Processes

Course Title: Agile for Business Analysts

Chapter 7: Quality Project Review

Requirements Engineering and Software Architecture Project Description

7. Project Management

Project Management and Testing

AGILE DEVELOPMENT AND ITS IMPACT ON PRODUCTIVITY

The Unified Software Development Process

Chapter 3. Information Systems Development. McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.

Course Title: Agile for Business Analysts

Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 21 st, Requirements Engineering

Lesson Three: Business Analysis Planning and Monitoring BANA 110 Analyzing Business Needs and Requirements Planning Gary Mesick and Shelly Lawrence,

Chapter 3 Prescriptive Process Models

Systems Analysis and Design Methods Chapter 3: Information Systems Development

Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture

7. Model based software architecture

MANAGEMENT INFORMATION SYSTEMS COURSES Student Learning Outcomes 1

MINGGU Ke 1 Analisa dan Perancangan Sistem Informasi

The Art of Agile Practice

Systems Requirements. Requirements Determination. Learning Objectives. Major part of Systems Analysis

Transcription:

CONTENTS Preface 21 PART ONE FOUNDATIONS FOR SYSTEMS DEVELOPMENT AN OVERVIEW OF PART ONE :»o SYSTEMS DEVELOPMENT IN AN ORGANIZATIONAL CONTEXT 31 Learning Objectives 31 Introduction 31 A Modern Approach to Systems Analysis and Design 34 Developing Information Systems and the Systems Development Life Cycle 35 The Heart of the Systems Development Process 40 The Traditional Waterfall SDLC 42 Different Approaches to Improving Development 43 CASE Tools 43 Rapid Application Development 45 Service-Oriented Architecture 46 Agile Methodologies 47 extreme Programming 50 Object-Oriented Analysis and Design 50 Our Approach to Systems Development 52 Summary 53 Key Terms 53 Review Questions 54 Problems and Exercises 54 Field Exercises 55 References 55 THE SOURCES OF SOFTWARE 57 Learning Objectives 57 Introduction 57 Systems Acquisition 58 Outsourcing 58 Sources of Software 60 Choosing Off-the-Shelf Software 66 Validating Purchased Software Information 67 Reuse 68 Summary 71 Key Terms 71 Hoffer, Jeffrey A. Modern systems analysis and design 2011 digitalisiert durch: IDS Basel Bern

CONTENTS Review Questions 71 Problems and Exercises 71 Field Exercises 72 References 72 3 PINE Learning Objectives 73 Introduction 73 FvkNmiRE Pine Valley Furniture Company Background 74 Managing the Information Systems Project 75 Initiating a Project 79 Planning the Project 81 Executing the Project 89 Closing Down the Project 91 Representing and Scheduling Project Plans 92 Representing Project Plans 94 Calculating Expected Time Duration Using PERT 95 Constructing a Gantt Chart and Network Diagram at Pine Valley Furniture 95 Using Project Management Software 99 Establishing a Project Starting Date 100 Entering Tasks and Assigning Task Relationships 100 Selecting a Scheduling Method to Review Project Reports 101 Summary 102 Key Terms 102 Review Questions 103 Problems and Exercises 104 Field Exercises 105 References 106 APPENDIX Learning Objectives 107 Unique Characteristics of an OOSAD Project 107 Define the System as a Set of Components 107 Complete Hard Problems First 109 Using Iterations to Manage the Project 110 Don't Plan Too Much Up Front 110 How Many and How Long Are Iterations? 111 Project Activity Focus Changes Over the Life of a Project 111 Summary 113 Review Questions 113 Problems and Exercises 113 BEC CASE: COMPANY BACKGROUND 114 Case Introduction 114 The Company 114 Company History 115 Company Organization 115 Development of Information Systems 116 Information Systems at BEC Today 117

CONTENTS In-Store Systems 118 Corporate Systems 118 Status of Systems 119 Case Summary 119 Case Questions 120 wmiwo PLANNING AN OVERVIEW OF PART TWO 122 IDENTIFYING AND SELECTING SYSTEMS DEVELOPMENT PROJECTS 123 Learning Objectives 123 Introduction 123 I PINE VALLEY FURNITURE fe Identifying and Selecting Systems Development Projects 124 The Process of Identifying and Selecting IS Development Projects 125 Deliverables and Outcomes 129 Corporate and Information Systems Planning 130 Corporate Strategie Planning 131 Information Systems Planning 133 Electronic Commerce Applications: Identifying and Selecting Systems Development Projects 140 Internet Basics 140 Pine Valley Furniture WebStore 141 Summary 142 Key Terms 142 Review Questions 143 Problems and Exercises 143 Field Exercises 144 References 144 BEC CASE: IDENTIFYING AND SELECTING THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 146 Case Introduction 146 The Idea for a New System 147 Formalizing a Project Proposal 147 Case Summary 150 Case Questions 150 5 INITIATING AND PLANNING SYSTEMS DEVELOPMENT PROJECTS 151 Learning Objectives 151 Introduction 151 Initiating and Planning Systems Development Projects 152 The Process of Initiating and Planning IS Development Projects 153 Deliverables and Outcomes 154 Assessing Project Feasibility 155 Assessing Economic Feasibility 155 Assessing Technical Feasibility 163 Assessing Other Feasibility Concerns 166 Building and Reviewing the Baseline Project Plan 168 Building the Baseline Project Plan 168 Reviewing the Baseline Project Plan 173

10 CONTENTS Asm, Electronic Commerce Applications: Initiating and Planning Systems Development Projects 177 li Initiating and Planning Systems Development Projects for Pine Valley Furniture's WebStore 178 Summary 180 Key Terms 180 Review Questions 181 Problems and Exercises 181 Field Exercises 182 References 182 BEC CASE: INITIATING AND PLANNING THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 184 Case Introduction 184 Initiating and Planning the Project 184 Developing the Baseline Project Plan 185 Case Summary 187 Case Questions 187 PART THREE ANALYSIS AN OVERVIEW OF PART THREE 190 6 DETERMINING SYSTEM REQUIREMENTS 191 Learning Objectives 191 Introduction 191 Performing Requirements Determination 192 The Process of Determining Requirements 192 Deliverables and Outcomes 193 Traditional Methods for Determining Requirements 194 Interviewing and Listening 194 Interviewing Groups 198 Directly Observing Users 199 Analyzing Procedures and Other Documents 201 Contemporary Methods for Determining System Requirements 205 Joint Application Design 206 Using Prototyping During Requirements Determination 209 Radical Methods for Determining System Requirements 211 Identifying Processes to Reengineer 212 Disruptive Technologies 212 Requirements Management Tools 213 Requirements Determination Using Agile Methodologies 214 Continual User Involvement 214 Agile Usage-Centered Design 215 The Planning Game from extreme Programming 216 rnrnnm flsäme Electronic Commerce Applications: Determining System Requirements 218 Determining System Requirements for Pine Valley Furniture's WebStore 218 Summary 221 Key Terms 221 Review Questions 222

CONTENTS 11 Problems and Exercises 222 Field Exercises 223 References 224 i BEC CASE: DETERMINING REQUIREMENTS FOR THE WEB-BASED CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 225 Case Introduction 225 Getting Started on Requirements Determination 225 Conducting Requirements Determination 225 Case Summary 226 Case Questions 227 7 ANALYZING SYSTEM PROCESS REQUIREMENTS 228 Learning Objectives 228 Introduction 228 Process Modeling 229 Modeling a System's Process for Structured Analysis 229 Deliverables and Outcomes 230 Data Flow Diagramming Mechanics 230 Definitions and Symbols 231 * Developing DFDs: An Example 233 Data Flow Diagramming Rules 235 Decomposition of DFDs 236 Balancing DFDs 239 «tö^ä An Example DFD 241 Using Data Flow Diagramming in the Analysis Process 244 Guideline for Drawings DFDs 244 Using DFDs as Analysis Tools 246 Using DFDs in Business Process Reengineering 247 Modeling Logic with Decision Tables 249 BPINE PURNITURE Electronic Commerce Application: Process Modeling Using Data Flow Diagrams 252 Process Modeling for Pine Valley Furniture's WebStore 253 Summary 254 Key Terms 255 Review Questions 256 Problems and Exercises 256 Field Exercises 262 References 262 APPENDIX 7A: OBJECT-ORiENTED ANALYSIS AND DESiGN: USE CASES 263 Learning Objectives 263 Introduction 263 Use Cases 263 What Is a Use Case? 263 Use Case Diagrams 264 Definitions and Symbols 265 Written Use Cases 268 Level 268 The Rest of the Template 269

12 CONTENTS 3 PINE 3 VALLEY ij FURNITURE Electronic Commerce Application: Process Modeling Using Use Cases 272 Writing Use Cases for Pine Valley Furniture's WebStore 272 Summary 274 Key Terms 275 Review Questions 275 Problems and Exercises 275 Field Exercise 276 References 276 APPENDIX 7B DBJECT-GRIENTED ANALYSIS AND DESIGN: ACTIViTY DIAGRAMS 277 Learning Objectives 277 Introduction 277 When to Use an Activity Diagram 277 Key term 279 Problems and Exercises 279 Reference 279 wfitä&i APPENDIX 7C OBJECT-ORIENTED ANALYSIS AND DESIGN: SEQUENCE DIAGRAMS 280 Learning Objectives 280 Introduction 280 Dynamic Modeling: Sequence Diagrams 281 Designing a Use Case with a Sequence Diagram 282 A Sequence Diagram for Hoosier Burger 286 Summary 287 Key Terms 287 Review Questions 288 Problems and Exercises 288 Field Exercise 288 References 289 BEC CASE: STRUCTURING SYSTEM PROCESS REQUIREMENTS FOR THE WEB-BASED CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 290 Case Introduction 290 Structuring the High-Level Process Findings from Requirements Determination 290 Case Summary 292 Case Questions 293 8 ANALYZING SYSTEM DATA REQUIREMENTS 294 Learning Objectives 294 Introduction 294 Conceptual Data Modeling 295 The Conceptual Data Modeling Process 296 Deliverables and Outcomes 297 Gathering Information for Conceptual Data Modeling 298

CONTENTS 13 I PINE VALLEY Introduction to E-R Modeling 300 Entities 301 Attributes 303 Candidate Keys and Identifiers 304 Other Attribute Types 305 Relationships 306 Conceptual Data Modeling and the E-R Model 307 Degree of a Relationship 307 Cardinalities in Relationships 309 Naming and Defining Relationships 311 Associative Entities 312 Summary of Conceptual Data Modeling with E-R Diagrams 313 Representing Supertypes and Subtypes 314 Business Rules 316 Domains 317 Triggering Operations 317 Role of Packaged Conceptual Data Models Database Patterns 318 Universal Data Models 319 Industry-Specific Data Models 319 Benefits of Database Patterns and Packaged Data Models 319 p&nmjw; Electronic Commerce Application: Conceptual Data Modeling 320 Conceptual Data Modeling for Pine Valley Furniture's WebStore 320 Summary 324 Key Terms 324 Review Questions 325 Problems and Exercises 326 Field Exercises 328 References 328 APPENDIX: OBJECT-ORIENTED ANALYSIS AND DESIGN: OBJECT MODELING-CLASS DIAGRAMS 329 Learning Objectives 329 Introduction 329 Representing Objects and Classes 329 Types of Operations 331 Representing Associations 331 Representing Associative Classes 333 Representing Stereotypes for Attributes 334 Representing Generalization 335 Representing Aggregation 337 An Example of Conceptual Data Modeling at Hoosier Burger 338 Summary 342 Key Terms 342 Review Questions 343 Problems and Exercises 343 References 344

14 CONTENTS BEC CASE: STRUCTURING SYSTEM REQUIREMENTS: CONCEPTUAL DATA MODELING FOR THE WEB-BASED CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 345 Case Introduction 345 Structuring the High-Level Data Modeling Findings from Requirements Determination 345 Case Summary 346 Case Questions 346 mmfwmm DESIGN \ ~. _~ ; " p ART FOUR 350 Learning Objectives 351 Introduction 351 Database Design 352 The Process of Database Design 353 Deliverables and Outcomes 354 Relational Database Model 357 Well-Structured Relations 358 Normalization 359 Rules of Normalization 359 Functional Dependence and Primary Keys 359 Second Normal Form 360 Third Normal Form 360 Transforming E-R Diagrams Into Relations 362 Represent Entities 362 Represent Relationships 363 Summary of Transforming E-R Diagrams to Relations 366 Merging Relations 366 An Example of Merging Relations 367 View Integration Problems 367»* MWr Logical Database Design for Hoosier Burger 368 Physical File and Database Design 371 Designing Fields 371 Choosing Data Types 371 Controlling Data Integrity 373 Designing Physical Tables 374 Arranging Table Rows 376 Designing Controls for Files 380 * Physical Database Design for Hoosier Burger 382 PINE FUK«TURE Electronic Commerce Application: Designing Databases 383 Designing Databases for Pine Valley Furniture's WebStore 383 Summary 385 Key Terms 386 Review Questions 387 Problems and Exercises 387 Field Exercises 389 References 389

CONTENTS 15 BEC CASE: DESIGNING THE RELATIONAL DATABASE FOR THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 390 Case Introduction 390 Identifying Relations 390 Designing the Physical Database 390 Case Summary 391 Case Questions 391 10 FORMS AND REPORTS DESIGN 392 Learning Objectives 392 Introduction 392 Designing Forms and Reports 393 The Process of Designing Forms and Reports 394 Deliverables and Outcomes 396 Formatting Forms and Reports 399 General Formatting Guidelines 399 Highlighting Information 401 Color Versus No Color 402 Displaying Text 403 Designing Tables and Lists 405 Paper Versus Electronic Reports 408 Assessing Usability 409 Usability Success Factors 410 Measures of Usability 410 HPINE FUWOTURE Electronic Commerce Applications: Designing Forms and Reports for Pine Valley Furniture's WebStore 411 General Guidelines 411 Designing Forms and Reports at Pine Valley Furniture 412 Lightweight Graphics 413 Forms and Data Integrity Rules 413 Template-Based HTML 413 Summary 414 Key Terms 414 Review Questions 414 Problems and Exercises 415 Field Exercises 415 References 416 BEC CASE: DESIGNING FORMS AND REPORTS FOR THE CUSTOMER RELATIONSHIP MANAGEMENTSYSTEM 417 Case Introduction 417 Identifying the Forms and Reports 417 Designing Forms and Reports for MyBroadway 417 Case Summary 418 Case Questions 418 11 INTERFACE AND DIALOGUE DESIGN 421 Learning Objectives 421 Introduction 421

16 CONTENTS 1PINE 3 VALLEY S M E Designing Interfaces and Dialogues 422 The Process of Designing Interfaces and Dialogues 422 Deliverables and Outcomes 422 Interaction Methods and Devices 423 Methods of Interacting 423 Hardware Options for System Interaction 431 Designing Interfaces 433 Designing Layouts 433 Structuring Data Entry 437 Controlling Data Input 438 Providing Feedback 440 Providing Help 441 Designing Dialogues 444 Designing the Dialogue Sequence 445 Building Prototypes and Assessing Usability 446 Designing Interfaces and Dialogues in Graphical Environments 447 Graphical Interface Design Issues 447 Dialogue Design Issues in a Graphical Environment 449 Electronic Commerce Application: Designing Interfaces and Dialogues for Pine Valley Furniture's WebStore 451 General Guidelines 451 Designing Interfaces and Dialogues at Pine Valley Furniture 452 Menu-Driven Navigation with Cookie Crumbs 452 Summary 453 Key Terms 454 Review Questions 454 Problems and Exercises 455 Field Exercises 455 References 456 BEC CASE: DESIGNING THE HUMAN INTERFACE FOR THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 457 Case Introduction 457 Designing the Dialogue Interface Between MyBroadway and Users 457 Case Summary 457 Case Questions 458 12 DISTRIBUTED AND INTERNET SYSTEMS DESIGN 459 Learning Objectives 459 Introduction 459 Designing Distributed and Internet Systems 460 The Process of Designing Distributed and Internet Systems 460 Deliverables and Outcomes 461 Designing Distributed Systems 462 Designing Systems for LANs 462 Designing Systems for a Client/Server Architecture 464 Alternative Designs for Distributed Systems 465 Designing Internet Systems 469 Internet Design Fundamentals 470 Site Consistency 472

a PINE 1 VALLEY Design Issues Related to Site Management 475 Managing Online Data 478 CONTENTS 17 puwnw Electronic Commerce Application: Designing a Distributed Advertisement Server for Pine Valley Furniture's WebStore 486 Advertising on Pine Valley Furniture's WebStore 486 Designing the Advertising Component 487 Designing the Management Reporting Component 487 Summary 488 Key Terms 489 Review Questions 490 Problems and Exercises 491 Field Exercises 491 References 492 BEC CASE: DESIGNING INTERNET FEATURES INTO THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 493 Case Introduction 493 Establishing Web Site Design Principles for MyBroadway 493 Case Summary 493 Case Questions 493 PART F1VE MPLEMENIATION AND MAINTENANCE AN OVERVIEW OF PART FIVE 498 13 IMPLEMENTING THE SYSTEM 499 Learning Objectives 499 Introduction 499 System Implementation 500 The Processes of Coding, Testing, and Installation 501 Deliverables and Outcomes from Coding, Testing, and Installation 501 Deliverables and Outcomes from Documenting the System, Training Users, and Supporting Users 503 Software Application Testing 503 Seven Different Types of Tests 505 The Testing Process 507 Combining Coding and Testing 509 Acceptance Testing by Users 509 Installation 510 Direct Installation 511 Parallel Installation 512 Single-Location Installation 512 Phased Installation 513 Planning Installation 513 Documenting the System 514 User Documentation 515 Training and Supporting Users 517 Training Information Systems Users 517 Supporting Information Systems Users 519 Support Issues for the Analyst to Consider 520

18 CONTENTS n PINE 1 VALLEY * FURNITURE Organizational Issues in Systems Implementation 521 Why Implementation Sometimes Fails 521 Security Issues 524 Electronic Commerce Application: System Implementation and Operation for Pine Valley Furniture's WebStore 525 Developing Test Cases for the WebStore 525 Alpha and Beta Testing the WebStore 527 WebStore Installation 527 Project Closedown 527 Summary 528 Key Terms 529 Review Questions 530 Problems and Exercises 530 Field Exercises 530 References 530 BEC CASE: DESIGNING A TESTING PLAN FOR THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 532 Case Introduction 532 Preparing the Testing Plan 532 Preparing a Test Case 533 Case Summary 534 Case Questions 534 14 IF1NE VALLEY FURNITURE MAINTAINING THE SYSTEf Learning Objectives 535 Introduction 535 535 Maintaining Information Systems 536 The Process of Maintaining Information Systems 536 Deliverables and Outcomes 537 Conducting Systems Maintenance 538 Types of Maintenance 538 The Cost of Maintenance 539 Managing Maintenance 541 Role of CASE and Automated Development Tools in Maintenance 546 Web Site Maintenance 547 Electronic Commerce Application: Maintaining an Information System for Pine Valley Furniture's WebStore 548 Maintaining Pine Valley Furniture's WebStore 548 Summary 549 Key Terms 550 Review Questions 551 Problems and Exercises 551 Field Exercises 551 References 552

CONTENTS 19 BEC CASE: DESIGNING A MAINTANENCE PLAN FOR THE CUSTOMER RELATIONSHIP MANAGEMENT SYSTEM 553 Case Introduction 553 Preparing the Maintanence Plan 553 Case Summary 553 Case Questions 553 Glossary of Terms 555 Glossary of Acronyms 564 Index 566