05 Apr Read the information below, then complete the designated tasks with your team. In the previous milestone, you conducted a preliminary inves
Instructions
Read the information below, then complete the designated tasks with your team.
In the previous milestone, you conducted a preliminary investigation into Millennium request for a business support system and a medical practice support system. After discussing your recommendations, Dr. Johnson and the partners decided to move forward with the Business Support System project and want you to describe the next steps.
To ensure the quality, cost, and timeliness of the new system, you suggested that Millennium Health use a project management approach. Dr. Johnson agreed, and he wants you briefly describe project management concepts and benefits. You realize that most of the partners do not have project management experience, and it is important to deliver a clear, informative overview.
Tasks:
1. Create a Microsoft Word document to include the following points:
- Explain project management concepts and benefits.
- Explain how project management will be used by your team to manage the Millennium Health Project.
2. To illustrate the PM process, refer to table 3.39 of textbook and complete the following tasks:
- Create a two-column table with column titles Tasks and Expected Time. List activities A through J in the Tasks column.
- Calculate the Expected Time for each task and enter into this table.
- Refer to table 3.40. Based on the activities listed complete the following three steps:
- Convert the activity times to days (multiply the number of weeks by 7)
- Construct a Gantt Chart
- Copy/paste the Gantt chart into a Word document.
- I have attached milestone 1 document
Running Head: MILLENNIUM HEALTH 2
MILLENNIUM HEALTH 2
Millennium Health
Name
Institution
Date
Millennium Health
Business Profile for Millennium Health
Business Address and Details (Summary)
Company Name: Millennium Health Care Limited
Form of Business: Millennium Hospital
Trading Sector: Private Hospital
Trading Name: Health Sector
Registration No: 657598
Date Registered: 23rd December 2014
Company TIN No: 5464-5456-4646
Email Address: [email protected]
Website: [email protected]
Company Office Manager
Sheila Logan
Organizational Chart
Figure 1: Organizational Chart
Six Business Processes that Millennium Health Performs and the Personnel Responsible
I. Recruitment and management of employees based on the need within the organization and facilitation of employee benefits based on their duties. These duties are undertaken by Fred Brown, the human resource manager.
II. Preparation and management of payrolls, reporting taxes and distribution, and disbursement of the profits that have been earned by the organization. (Ricky Flemings)
III. Maintenance of all medical records of patients and by extension, the records of their visits to the hospital. (Aisha Fox)
IV. Management of account receivables. (Zane Ricardo)
V. Medical insurance and billing processes. (Deb Baldwin)
VI. Management of Patient Appointment. (Min-Ji Park)
Systems Development Method
The system development method to be adopted is the prototyping model. According to Lytvyn et al., (2019), the prototyping model is a method in which “ a prototype is built, tested and then reworked as necessary until an acceptable outcome is achieved from which the complete system or product can be developed.” Although there exist four major types of prototyping methods that can be applied in system development, that is throw away, incremental extreme, and evolutionary, the project will focus on the broader prototype model. This implies that more than one type of prototype can be used in ensuring that everything goes on well. In this research methodology, the team’s main focus is producing an early version of the system, which is aimed at replacing the existing system. “ This prototype won’t have full functionality or be thoroughly tested, but it will give external customers a sense of what’s to come. Then, feedback can be gathered and implemented throughout the rest of the SDLC phases.” The method was arrived at because it works well for emerging industries or organizations that require technology in operations. In general, the projects which require revision, user feedback, and recommendation highly go well with this type of model. The method can directly determine the direction that a certain project ought to take. Successful identifiers are important in pointing out problems before they negatively impact finished projects. The figure below depicts a sketch of how the processes will be undertaken.
Figure 2:Typical prototype model
Pros
Enhanced and involved user involvement: A good number of customers tend to have the feeling that they have been engaged in any activity that is taking place in the organization and which can impact them in one way or the other. Prototyping calls for user involvement so they can be able to interact with the working model that is yet to be implemented. The user engagement will also create the opportunity of receiving reviews about the model before launching it fully.
Reduced time and costs: Prototyping can enhance the quality of the specifications that have been mentioned. In the absence of prototyping, a number of customers anticipate for high costs. But with the model, the costs are minimized and the quality is enhanced. There is nothing that makes customers happier than a project that is completed on time. This is because they are able to meet their needs on time and the changeover process remains smooth
Cons
Possible User Confusion: The worst possible scenario that can arise with this method in place is a customer mistaking it for a completed project. Some customers, after they have access to the rough prototype might not understand that it is rough. Some customers can also wrongly perceive the prototype. This way, it makes it difficult to attain the set objectives.
Insufficient analysis: Having a focus on a limited prototype is dangerous. This is due to its capabilities of distracting the work of developers. This will hinder the potential results that might be obtained. Further, this can make the intended goals and solutions be overlooked.
Possible Developer Misunderstandings: “For every project to be successful, developers and customers must be on the same page and share the same project objectives”( Lytvyn et al., 2019) There can be proposed features that might lead to mission conflicts.
Date and Time of the Meeting
References
Lytvyn, V., Vysotska, V., Mykhailyshyn, V., Rzheuskyi, A., & Semianchuk, S. (2019, May). System development for video stream data analyzing. In International Scientific Conference “Intellectual Systems of Decision Making and Problem of Computational Intelligence” (pp. 315-331). Springer, Cham. http://ceur-ws.org/Vol-2362/paper12.pdf
Sheila Logan
Office Manager
Fred Brown
HR and Employee
Benefits
Ricky Fleming
Payroll Management
Aisha Fox
Registrar
Zane Ricardo
Accountat
Deb Baldwin
Billing and Insurince
Laboratory Technician
Min-ji Park
,
Modern Systems Analysis and Design
8th Edition
Joseph S. Valacich University of Arizona
Joey F. George Iowa State University
Boston Columbus Indianapolis New York San Francisco Amsterdam Cape Town Dubai London Madrid Milan Munich Paris Montréal Toronto
Delhi Mexico City São Paulo Sydney Hong Kong Seoul Singapore Taipei Tokyo
Vice President, Business Publishing: Donna Battista Editor-in-Chief: Stephanie Wall Senior Sponsoring Editor: Neera Bhalla Acquisitions Editor: Samantha Lewis Program Manager: Emily Biberger Editorial Assistants: Olivia Vignone, Michael Campbell Vice President, Product Marketing: Maggie Moylan Director of Marketing, Digital Services and Products: Jeanette Koskinas Executive Field Marketing Manager: Adam Goldstein Field Marketing Manager: Lenny Ann Raper Product Marketing Assistant: Jessica Quazza Team Lead, Program Management: Ashley Santora Team Lead, Project Management: Jeff Holcomb
Project Manager: Ilene Kahn Operations Specialist: Diane Peirano Creative Director: Blair Brown Art Director: Janet Slowik Vice President, Director of Digital Strategy and Assessment: Paul Gentile Manager of Learning Applications: Paul DeLuca Full-Service Project Management and Composition: George Jacob/Integra Interior Designer: Integra Software Services, Inc. Cover Designer: Integra Software Services, Inc. Cover Art: hunthomas/123rf Printer/Binder: RR Donnelley/Roanoke Cover Printer: Phoenix Color/Hagerstown
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.
Copyright © 2017, 2014, 2011 by Pearson Education, Inc. or its affiliates. All Rights Reserved. Manufactured in the United States of America. 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 otherwise. 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/.
Acknowledgments of third-party content appear on the appropriate page within the text.
PEARSON and ALWAYS LEARNING are exclusive trademarks owned by Pearson Education, Inc. or its affiliates in the U.S. and/or other countries.
Unless otherwise indicated herein, any third-party trademarks, logos, or icons that may appear in this work are the property of their respective owners, and any references to third-party trademarks, logos, icons, or other trade dress are for demonstrative or descriptive purposes only. Such references are not intended to imply any sponsorship, endorsement, authorization, or promotion of Pearson’s products by the owners of such marks, or any relationship between the owner and Pearson Education, Inc., or its affiliates, authors, licensees, or distributors.
Library of Congress Cataloging-in-Publication Data Hoffer, Jeffrey A. Modern systems analysis and design/Jeffrey A. Hoffer, University of Dayton, Joey F. George, Iowa State University, Joseph S. Valacich, University of Arizona.-—Eighth edition. pages cm Includes bibliographical references and index. ISBN-13: 978-0-13-420492-5 ISBN-10: 0-13-420492-1 1. System design. 2. System analysis. I. George, Joey F. II. Valacich, Joseph S., 1959– III. Title. QA76.9.S88H6197 2015 003—dc23
2015013648
10 9 8 7 6 5 4 3 2 1
ISBN 10: 0-13-420492-1 ISBN 13: 978-0-13-420492-5
To my mother, Mary Valacich. You are the best! —Joe
To my mother, Loree George —Joey
This page intentionally left blank
v
Preface xix
Part One Foundations For systems development 1 1 the Systems Development environment 3 2 the Origins of Software 26 3 Managing the Information Systems Project 44
appendix: object-oriented analysis and design: project management 78
Part twO planning 85 4 Identifying and Selecting Systems Development Projects 87 5 Initiating and Planning Systems Development Projects 111
Part three analysis 145 6 Determining System requirements 147 7 Structuring System Process requirements 182
appendix 7a: object-oriented analysis and design: use Cases 217
appendix 7B: object-oriented analysis and design: activity diagrams 232
appendix 7C: object-oriented analysis and design: sequence
diagrams 237
appendix 7D: Business process modeling 246
8 Structuring System Data requirements 255 appendix: object-oriented analysis and design: object modeling–Class
diagrams 290
Part FOur design 309 9 Designing Databases 311 10 Designing Forms and reports 353 11 Designing Interfaces and Dialogues 381 12 Designing Distributed and Internet Systems 417
Part FIve implementation and maintenanCe 451 13 System Implementation 453 14 Maintaining Information Systems 486
glossary oF terms 504
glossary oF aCronyms 511
index 512
Brief Contents
This page intentionally left blank
vii
Preface xix
Part One Foundations For systems development
An Overview Of PArt One 2
1 the Systems Development environment 3 Learning Objectives 3
Introduction 3
A Modern Approach to Systems Analysis and Design 5
Developing Information Systems and the Systems Development Life Cycle 6
A Specialized Systems Development Life Cycle 12
The Heart of the Systems Development Process 13 The Traditional Waterfall SDLC 15
Different Approaches to Improving Development 16 Case Tools 16
Agile Methodologies 17 eXtreme Programming 19
Object-Oriented Analysis and Design 20
Our Approach to Systems Development 22
Summary 23
Key Terms 23
Review Questions 24
Problems and Exercises 24
Field Exercises 25
References 25
2 the Origins of Software 26 Learning Objectives 26
Introduction 26
Systems Acquisition 26 Outsourcing 27 Sources of Software 28 Choosing Off-the-Shelf Software 34 Validating Purchased Software Information 37
Reuse 37
Summary 40
Key Terms 40
Contents
viii Contents
Review Questions 41
Problems and Exercises 41
Field Exercises 41
References 41
BeC Case: the origins oF soFtware 43 Case Questions 43
3 Managing the Information Systems Project 44 Learning Objectives 44
Introduction 44
Pine Valley Furniture Company Background 44
Managing the Information Systems Project 46 Initiating a Project 50 Planning the Project 53 Executing the Project 58 Closing Down the Project 62
Representing and Scheduling Project Plans 63 Representing Project Plans 64 Calculating Expected Time Durations Using PERT 65 Constructing a Gantt Chart and Network Diagram at Pine Valley Furniture 66
Using Project Management Software 69 Establishing a Project Start Date 70 Entering Tasks and Assigning Task Relationships 70 Selecting a Scheduling Method to Review Project Reports 71
Summary 72
Key Terms 73
Review Questions 74
Problems and Exercises 74
Field Exercises 76
References 76
appendix: object-oriented analysis and design 78 Learning Objectives 78 Unique Characteristics of an OOSAD Project 78 Define the System as a Set of Components 78
Complete Hard Problems First 78 Using Iterations to Manage the Project 80 Don’t Plan Too Much Up Front 80 How Many and How Long Are Iterations? 81 Project Activity Focus Changes Over the Life of a Project 83
Summary 83
Review Question 83
Problems and Exercises 83
BeC Case: managing the inFormation systems 84 Case Questions 84
Contents ix
Part twO planning
An Overview Of PArt twO 86
4 Identifying and Selecting Systems Development Projects 87 Learning Objectives 87
Introduction 87
Identifying and Selecting Systems Development Projects 88 The Process of Identifying and Selecting IS Development Projects 89 Deliverables and Outcomes 93
Corporate and Information Systems Planning 94 Corporate Strategic Planning 95 Information Systems Planning 97
Electronic Commerce Applications: Identifying and Selecting Systems Development Projects 104
Internet Basics 104 Pine Valley Furniture WebStore 105
Summary 106
Key Terms 106
Review Questions 107
Problems and Exercises 107
Field Exercises 108
References 108
BeC Case: identiFying and seleCting systems development projeCts 110 Case Questions 110
5 Initiating and Planning Systems Development Projects 111 Learning Objectives 111
Introduction 111
Initiating and Planning Systems Development Projects 111
The Process of Initiating and Planning Is Development Projects 112 Deliverables and Outcomes 113
Assessing Project Feasibility 114 Assessing Economic Feasibility 115 Assessing Technical Feasibility 123 Assessing Other Feasibility Concerns 126
Building and Reviewing the Baseline Project Plan 127 Building the Baseline Project Plan 127 Reviewing the Baseline Project Plan 132
Electronic Commerce Applications: Initiating and Planning Systems Development Projects 137
Initiating and Planning Systems Development Projects for Pine Valley Furniture’s WebStore 137
Summary 139
Key Terms 139
x Contents
Review Questions 140
Problems and Exercises 140
Field Exercises 141
References 141
BeC Case: initiating and planning systems development projeCts 143 Case Questions 143
Part three analysis
An Overview Of PArt three 146
6 Determining System requirements 147 Learning Objectives 147
Introduction 147
Performing Requirements Determination 147 The Process of Determining Requirements 148 Deliverables and Outcomes 149
Traditional Methods for Determining Requirements 150 Interviewing and Listening 150 Interviewing Groups 154 Directly Observing Users 155 Analyzing Procedures and Other Documents 156
Contemporary Methods for Determining System Requirements 161
Joint Application Design 162 Using Prototyping During Requirements Determination 165
Radical Methods for Determining System Requirements 167 Identifying Processes to Reengineer 168 Disruptive Technologies 168
Requirements Determination Using Agile Methodologies 169 Continual User Involvement 169 Agile Usage-Centered Design 170 The Planning Game from eXtreme Programming 171
Electronic Commerce Applications: Determining System Requirements 173
Determining System Requirements for Pine Valley Furniture’s WebStore 173
Summary 176
Key Terms 176
Review Questions 177
Problems and Exercises 177
Field Exercises 178
References 179
BeC Case: determining system requirements 180 Case Questions 181
Contents xi
7 Structuring System Process requirements 182 Learning Objectives 182
Introduction 182
Process Modeling 182 Modeling a System’s Process for Structured Analysis 183 Deliverables and Outcomes 183
Data Flow Diagramming Mechanics 184 Definitions and Symbols 184 Developing DFDs: An Example 186 Data Flow Diagramming Rules 189 Decomposition of DFDs 190 Balancing DFDs 193
An Example DFD 195
Using Data Flow Diagramming in the Analysis Process 198 Guidelines for Drawing DFDs 198 Using DFDs as Analysis Tools 200 Using DFDs in Business Process Reengineering 201
Modeling Logic With Decision Tables 203
Electronic Commerce Application: Process Modeling Using Data Flow Diagrams 206 Process Modeling for Pine Valley Furniture’s WebStore 207
Summary 208
Key Terms 209
Review Questions 210
Problems and Exercises 210
Field Exercises 216
References 216
appendix 7a object-oriented analysis and design: use Cases 217 Learning Objectives 217 Introduction 217 Use Cases 217
What Is a Use Case? 217 Use Case Diagrams 218 Definitions and Symbols 219
Written Use Cases 222 Level 223 The Rest of the Template 223
Electronic Commerce Application: Process Modeling Using Use Cases 225 Writing Use Cases for Pine Valley Furniture’s Webstore 227
Summary 230
Key Terms 230
Review Questions 230
Problems and Exercises 230
Field Exercise 231
References 231
HOOSIER BURGER
xii Contents
appendix 7B: object-oriented analysis and design: activity diagrams 232 Learning Objectives 232 Introduction 232 When to Use an Activity Diagram 235 Problems and Exercises 235 Reference 236
appendix 7C: object-oriented analysis and design 237 Learning Objectives 237 Introduction 237 Dynamic Modeling: Sequence Diagrams 237 Designing a Use Case with a Sequence Diagram 239 A Sequence Diagram for Hoosier Burger 242 Summary 244 Key Terms 244 Review Questions 244 Problems and Exercises 244 Field Exercise 245 References 245
appendix 7D: Business process modeling 246 Learning Objective 246 Introduction 246 Basic Notation 246 Business Process Example 250 Summary 251 Key Terms 251 Review Questions 251 Problems and Exercises 251 Field Exercises 252 References 252
BeC Case: struCturing system proCess requirements 253 Case Questions 254
8 Structuring System Data requirements 255 Learning Objectives 255
Introduction 255
Conceptual Data Modeling 256 The Conceptual Data Modeling Process 257 Deliverables and Outcomes 258
Gathering Information for Conceptual Data Modeling 259
Contents xiii
Introduction to E-R Modeling 261 Entities 261 Attributes 263 Candidate Keys and Identifiers 264 Other Attribute Types 265 Relationships 266
Conceptual Data Modeling and the E-R Model 267 Degree of a Relationship 268 Cardinalities in Relationships 270 Naming and Defining Relationships 271 Associative Entities 272 Summary of Conceptual Data Modeling with E-R Diagrams 274
Representing Supertypes and Subtypes 274
Business Rules 275 Domains 276 Triggering Operations 278
Role of Packaged Conceptual Data Models: Database Patterns 279 Universal Data Models 279 Industry-Specific Data Models 279 Benefits of Database Patterns and Packaged Data Models 279
Electronic Commerce Application: Conceptual Data Modeling 280
Conceptual Data Modeling for Pine Valley Furniture’s WebStore 280
Summary 284
Key Terms 284
Review Questions 285
Problems and Exercises 286
Field Exercises 288
References 289
appendix: object-oriented analysis and design: object modelling—Class diagrams 290 Learning Objectives 290 Introduction 290 Representing Objects and Classes 290 Types of Operations 291 Representing Associations 292 Representing Associative Classes 294 Representing Stereotypes for Attributes 295 Representing Generalization 295 Representing Aggregation 298 An Example of Conceptual Data Modeling at Hoosier Burger 299 Summary 302 Key Terms 302
xiv Contents
Review Questions 303 Problems and Exercises 303 References 304
BeC Case: struCturing system data requirements 305 Case Questions 306
Part FOur design
An Overview Of PArt fOur 310
9 Designing Databases 311 Learning Objectives 311
Introduction 311
Database Design 311 The Process of Database Design 312 Deliverables and Outcomes 314 The Relational Database Model 317 Well-Structured Relations 317
Normalization 318 Rules of Normalization 319 Functional Dependence and Primary Keys 319 Second Normal Form 320 Third Normal Form 320
Transforming E-R Diagrams Into Relations 321 Represent Entities 322 Represent Relationships 322 Summary of Transforming E-R Diagrams to Relations 326
Merging Relations 326 An Example of Merging Relations 326 View Integration Problems 327
Logical Database Design for Hoosier Burger 328
Physical File and Database Design 331 Designing Fields 331 Choosing Data Types 332 Controlling Data Integrity 333 Designing Physical Tables 334 Arranging Table Rows 337 Designing Controls for Files 341
Physical Database Design for Hoosier Burger 342
Electronic Commerce Application: Designing Databases 343 Designing Databases for Pine Valley Furniture’s WebStore 344
Summary 346
Key Terms 347
Review Questions 348
Problems and Exercises 348
Field Exercises 349
HOOSIER BURGER
HOOSIER BURGER
Contents xv
References 350
BeC Case: designing dataBases 351 Case Questions 352
10 Designing Forms and reports 353 Learning Objectives 353
Introduction 353
Designing Forms and Reports 353 The Process of Designing Forms and Reports 355 Deliverables and Outcomes 356
Formatting Forms and Reports 360 General Formatting Guidelines 360 Highlighting Information 362 Color versus No Color 364 Displaying Text 365 Designing Tables and Lists 365 Paper versus Electronic Reports 369
Assessing Usability 371 Usability Success Factors 371 Measures of Usability 372
Electronic Commerce Applications: Designing Forms and Reports for Pine Valley Furniture’s Webstore 373
General Guidelines 373 Designing Forms and Reports at Pine Valley Furniture 373 Lightweight Graphics 374 Forms and Data Integrity Rules 374 Stylesheet-Based HTML 375
Summary 375
Key Terms 376
Review Questions 376
Problems and Exercises 377
Field Exercises 377
References 378
BeC Case: designing Forms and reports 379 Case Questions 379
11 Designing Interfaces and Dialogues 381 Learning Objectives 381
Introduction 381
Designing Interfaces and Dialogues 381 The Process of Designing Interfaces and Dialogues 381 Deliverables and Outcomes 382
Interaction Methods and Devices 382 Methods of Interacting 382 Hardware Options for System Interaction 390
xvi Contents
Designing Interfaces 392 Designing Layouts 392 Structuring Data Entry 395 Controlling Data Input 397 Providing Feedback 398 Providing Help 400
Designing Dialogues 403 Designing the Dialogue Sequence 404 Building Prototypes and Assessing Usability 405
Designing Interfaces and Dialogues in Graphical Environments 407 Graphical Interface Design Issues 407 Dialogue Design Issues in a Graphical Environment 409
Electronic Commerce Application: Designing Interfaces and Dialogues for Pine Valley Furniture’s Webstore 409
General Guidelines 410 Designing Interfaces and Dialogues at Pine Valley Furniture 411 Menu-Driven Navigation with Cookie Crumbs 411
Summary 412
Key Terms 412
Review Questions 413
Problems and Exercises 413
Field Exercises 414
References 414
BeC Case: designing interFaCes and dialogues 415 Case Questions 416
12 Designing Distributed and Internet Systems 417 Learning Objectives 417
Introduction 417
Designing Distributed and Internet Systems 417 The Process of Designing Distributed and Internet Systems 417 Deliverables and Outcomes 418
Designing LAN and Client/Server Systems 419 Designing Systems for LANs 419 Designing Systems for a Client/Server Architecture 421
Cloud Computing 425 What Is Cloud Computing? 425 Managing the Cloud 429 Service-Oriented Architecture 432 Web Services 433
Designing Internet Systems 434 Internet Design Fundamentals 435 Site Consistency 436 Design Issues Related to Site Management 438
Contents xvii
Electronic Commerce Application: Designing a Distributed Advertisement Server for Pine Valley Furniture’s Webstore 441
Advertising on Pine Valley Furniture’s WebStore 441 Designing the Advertising Component 442 Designing the Management Reporting Component 443
Summary 444
Key Terms 444
Review Questions 446
Problems and Exercises 446
Field Exercises 447
References 448
BeC Case: designing distriButed and internet systems 449 Case Questions 449
Part FIve implementation and maintenanCe
An Overview Of PArt five 452
13 System Implementation 453 Learning Objectives 453
Introduction 453
System Implementation 454 Coding, Testing, and Installation Processes 455 Deliverables and Outcomes from Coding, Testing,
and Installation 455 Deliverables and Outcomes from Documenting the System, Training Users,
and Supporting Users 457
Software Application Testing 457 Seven Different Types of Tests 458 The Testing Process 461 Combining Coding and Testing 463 Acceptance Testing by Users 463
Installation 464 Direct Installation 464 Parallel Installation 465 Single-Location Installation 466 Phased Installation 466 Planning Installation 467
Documenting the System 468 User Documentation 468
Training and Supporting Users 470 Training Information Systems Users 470 Supporting Information Systems Users 471 Support Issues for the Analyst to Consider 473
xviii Contents
Organizational Issues in Systems Implementation 474 Why Implementation Sometimes Fails 475 Security Issues 477
Electronic Commerce Application: System Implementation and Operation for Pine Valley Furniture’s Webstore 478
Developing Test Cases for the WebStore 478 Alpha and Beta Testing the WebStore 480 WebStore Installation 480
Project Closedown 481
Summary 481
Key Terms 482
Review Questions 483
Problems and Exercises 483
Field Exercises 484
References 484
BeC Case: system implementation 485 Case Questions 485
14 Maintaining Information Systems 486 Learning Objectives 486
Introduction 486
Maintaining Information Systems 486 The Process of Maintaining Information Systems 487 Deliverables and Outcomes 488
Conducting Systems Maintenance 489 Types of Maintenance 489 The Cost of Maintenance 490 Managing Maintenance 492 Role of Automated Development Tools in Maintenance 497
Website Maintenance 497
Electronic Commerce Application: Maintaining an Information System for Pine Valley Furniture’s Webstore 499
Maintaining Pine Valley Furniture’s WebStore 499 Cannot Find Server 499
Summa
Our website has a team of professional writers who can help you write any of your homework. They will write your papers from scratch. We also have a team of editors just to make sure all papers are of HIGH QUALITY & PLAGIARISM FREE. To make an Order you only need to click Ask A Question and we will direct you to our Order Page at WriteEdu. Then fill Our Order Form with all your assignment instructions. Select your deadline and pay for your paper. You will get it few hours before your set deadline.
Fill in all the assignment paper details that are required in the order form with the standard information being the page count, deadline, academic level and type of paper. It is advisable to have this information at hand so that you can quickly fill in the necessary information needed in the form for the essay writer to be immediately assigned to your writing project. Make payment for the custom essay order to enable us to assign a suitable writer to your order. Payments are made through Paypal on a secured billing page. Finally, sit back and relax.
Do you need help with this question?
Get assignment help from WriteEdu.com Paper Writing Website and forget about your problems.
WriteEdu provides custom & cheap essay writing 100% original, plagiarism free essays, assignments & dissertations.
With an exceptional team of professional academic experts in a wide range of subjects, we can guarantee you an unrivaled quality of custom-written papers.
Chat with us today! We are always waiting to answer all your questions.