Principles of Information Systems Eighth Edition Chapter 13 Systems Development: Design, Implementation, Maintenance, and Review.

Principles of Information Systems

Eighth Edition

Chapter 13

Systems Development: Design, Implementation, Maintenance, and Review

Principles of Information Systems, Eighth Edition 3

Principles and Learning Objectives

• Designing new systems or modifying existing ones should always help an organization achieve its goals– State the purpose of systems design and discuss the

differences between logical and physical systems design

– Describe some considerations in design modeling and the diagrams used during object-oriented design


Principles and Learning Objectives (continued)

• Designing new systems or modifying existing ones should always help an organization achieve its goals (continued)– Outline key considerations in interface design and

control and system security and control– Define the term RFP and discuss how this document

is used to drive the acquisition of hardware and software

– Describe the techniques used to make systems selection evaluations



• The primary emphasis of systems implementation is to make sure that the right information is delivered to the right person in the right format at the right time– State the purpose of systems implementation and

discuss the activities associated with this phase of systems development

– List the advantages and disadvantages of purchasing versus developing software

– Discuss the software development process and some of the tools used in this process, including object-oriented program development tools



• Maintenance and review add to the useful life of a system but can consume large amounts of resources; these activities can benefit from the same rigorous methods and project management techniques applied to systems development– State the importance of systems and software

maintenance and discuss the activities involved– Describe the systems review process


Why Learn About Systems Development?

• Almost every industry uses information systems

• Getting involved with systems design and implementation directly benefits employees

• Knowledge about systems development can help you:– Avoid costly errors– Recover from disasters


Systems Design

• Answers the question: how will the information system solve a problem?

• Results in a technical design– Details system outputs, inputs, and user interfaces– Specifies hardware, software, databases,

telecommunications, personnel, and procedures– Shows how these components are related


Logical and Physical Design

• Logical design: description of functional requirements of a system– Output, input, process, file, and database– Telecommunications, procedures, controls, and

security– Personnel and job requirements


Logical and Physical Design (continued)

• Physical design: specification of characteristics of system components necessary to put logical design into action– Characteristics of hardware, software, database,

telecommunications, and personnel– Procedure and control specifications


Object-Oriented Design

• Designing key objects and classes of objects in new or updated system– Considers problem domain, operating environment,

and user interface– Determines sequence of events that must happen

for the system to function correctly

• Scenario: sequence of events– Illustrated by sequence diagram


Object-Oriented Design (continued)

Figure 13.1: A Sequence Diagram to Add a New KayakItem Scenario


Interface Design and Controls

• Characteristics of how user accesses and interacts with system– Sign-on procedure– Interactive processing

• Menu-driven system

– Help facility– Lookup tables– Restart procedure– Good interactive design


Interface Design and Controls (continued)

Figure 13.2: The Levels of the Sign-On Procedure



Figure 13.3: Menu-Driven System



Table 13.1: The Elements of Good Interactive Dialogue


Design of System Security and Controls

• Preventing, detecting, and correcting errors– Enterprise-rights management software

• Disaster planning and recovery– Disaster planning: process of anticipating and

providing for disasters– Disaster recovery: implementation of disaster plan– Approaches

• Hot site• Cold site• Incremental backup• Image log


Design of System Security and Controls (continued)

• Systems controls: rules and procedures to maintain data security

• Deterrence controls: rules and procedures to prevent problems before they occur

• Closed shops: only authorized operators can run computers

• Open shops: other personnel, such as programmers and analysts, may also run computers



Table 13.2: Using Systems Controls to Enhance Security



Table 13.2: Using Systems Controls to Enhance Security (continued)


Generating Systems Design Alternatives

• Consider many factors when selecting a vendor– Reliability, stability, services, reviews, etc.

• Request for proposal (RFP): document that specifies required resources such as hardware and software in detail

• Financial options: consider scalability– Purchase– Lease– Rent


Generating Systems Design Alternatives (continued)

Figure 13.5: A Typical Table of Contents for a Request for Proposal



• Evaluating and selecting a systems design– Preliminary evaluation

• To dismiss unwanted proposals

• Begins after all proposals have been submitted

– Final evaluation• Detailed investigation of proposals remaining after

preliminary evaluation



Figure 13.6: The Stages in Preliminary and Final Evaluations


Evaluation Techniques

• Group consensus

• Cost/benefit analysis

• Benchmark tests

• Point evaluation


Evaluation Techniques (continued)

Figure 13.7: An Illustration of the Point Evaluation System


Freezing Design Specifications

• User agrees in writing that design is acceptable

Figure 13.8: Freezing Design Specifications


The Contract

• Vendors provide standard contracts to protect themselves

• Organizations often use outside consultants and legal firms to develop contracts that state:– All equipment specifications, software, training,

installation, maintenance, etc.– Deadlines for various stages– Actions that vendor will take in case of delays or

problems– Penalty clauses


The Design Report

• Primary result of systems design

• Reflects decisions made and prepares the way for systems implementation


The Design Report (continued)

Figure 13.9: A Typical Table of Contents for a Systems Design Report


Systems Implementation

Figure 13.10: Typical Steps in Systems Implementation


Acquiring Hardware from an IS Vendor

• Buying

• Leasing

• Renting

• “Pay-as-you-go,” “on-demand,” or “utility” computing”

• Purchasing used computer equipment

• Application service provider (ASP)


Acquiring Software: Make or Buy?

• Make-or-buy decision: decision regarding whether to obtain software from external or internal sources– Today, most software is purchased

• Externally acquired software– Commercial off-the-shelf (COTS) development

process


Acquiring Software: Make or Buy? (continued)

Table 13.5: Comparison of Off the Shelf and Developed Software



• In-house developed software tools and techniques– Chief programmer teams– Structured programming– CASE and object-oriented approaches– Cross-platform development– Integrated development environment– Structured walkthroughs– Documentation



Figure 13.11: Structured Walkthrough


Acquiring Database and Telecommunications Systems

• Databases are a blend of hardware and software

• Telecommunications systems require a blend of hardware and software

• Earlier discussion on acquiring hardware and software also applies to acquisition of:– Database systems– Telecommunications hardware and software


User Preparation

• Readying managers, decision makers, employees, other users, and stakeholders for new systems

• Training users


IS Personnel: Hiring and Training

• Personnel that might be needed for new system– IS manager– Systems analysts– Computer programmers– Data-entry operators

• Training programs should be conducted for IS personnel who will be using the system


Site Preparation

• Preparation of the location of a new system

• May involve:– Making room for a computer in an office– Special wiring and air conditioning– Renovation of entire room– Special floor– Additional power circuits


Data Preparation

• Also called data conversion

• Ensuring all files and databases are ready to be used with new computer software and systems


Installation

• Process of physically placing computer equipment on the site and making it operational

• Normally, manufacturer is responsible for installing computer equipment

• Someone from the organization (usually IS manager) should oversee the process


Testing

• Unit testing: testing of individual programs

• System testing: testing entire system of programs

• Volume testing: testing the application with a large amount of data

• Integration testing: testing all related systems together

• Acceptance testing: conducting any tests required by user


Testing (continued)

• Alpha testing: testing an incomplete or early version of system

• Beta testing: testing a complete and stable system by end users


Start-Up

• Process of making the final tested information system fully operational

• Approaches– Direct conversion (plunge, direct cutover) – Phase-in approach (piecemeal)– Pilot start-up– Parallel start-up


Start-Up (continued)

Figure 13.13: Start-Up Approaches


Start-Up (continued)

Figure 13.13: Start-Up Approaches (continued)


User Acceptance

• User acceptance document: formal agreement signed by user that states that a phase of installation or the complete system is approved– Legal document that removes or reduces IS vendor’s

liability


Systems Operation and Maintenance

• Systems operation: use of a new or modified system– Help desk provides support

• Systems maintenance: checking, changing, and enhancing the system to make it more useful in achieving user and organizational goals– Difficult and costly for legacy systems– Autonomic computing allows computers to manage

themselves


Reasons for Maintenance

• Changes in business processes

• New requests from stakeholders, users, and managers

• Bugs or errors in program

• Technical and hardware problems


Reasons for Maintenance (continued)

• Corporate mergers and acquisitions

• Government regulations

• Change in operating system or hardware on which the application runs

• Unexpected events


Types of Maintenance

• Slipstream upgrade: minor upgrade

• Patch: fix a problem or make small enhancement

• Release: significant program change requiring new documentation

• Version: major program change with new features


The Request for Maintenance Form

• Request for maintenance form: form authorizing modification of programs– Usually signed by a business manager

• IS group– Reviews form– Identifies programs to be changed– Determines programmer to be assigned to task– Estimates expected completion date– Develops a technical description of change


Performing Maintenance

• Approaches– Team who designs and builds the system also

performs maintenance– Separate maintenance team is responsible for

modifying, fixing, and updating existing software

• Maintenance tools and software– Example: RescueWare


The Financial Implications of Maintenance

• Total maintenance expenditures increase in time and money as programs age– For older programs, total cost of maintenance can be

up to five times greater than total cost of development

• Determining factor in decision to replace a system– Costs more to fix than replace system


The Financial Implications of Maintenance (continued)

Figure 13.14: Maintenance Costs as a Function of Age


The Relationship Between Maintenance and Design

Figure 13.15: The Value of Investment in Design

• More time and money spent on design means less time and money spent on maintenance


Systems Review

• Analysis of systems to make sure that they are operating as intended

• Often compares performance and benefits of designed system with actual performance and benefits of operational system


Types of Review Procedures

Table 13.6: Examples of Review Types


Factors to Consider During Systems Review

• Mission

• Organizational goals

• Hardware and software

• Database

• Telecommunications


Factors to Consider During Systems Review (continued)

• Information systems personnel

• Control

• Training

• Costs

• Complexity


Factors to Consider During Systems Review (continued)

• Reliability

• Efficiency

• Response time

• Documentation


System Performance Measurement

• System performance measurement: monitoring the system– Number of errors encountered– Amount of memory required– Amount of processing or CPU time needed– Other problems

• System performance products: software that measures all components of computer-based information system


Summary

• Systems design answers the question: “How will the information system solve a problem?”

• Logical design: description of functional requirements of a system

• Physical design: specification of characteristics of the system components necessary to put the logical design into action

• Object-oriented design: uses scenarios, or sequences of events


Summary (continued)

• Steps of systems implementation: hardware acquisition, software acquisition, user preparation, personnel hiring and training, site preparation, data preparation, installation, testing, start-up, and user acceptance

• Systems operation: use of a new or modified system

• Systems maintenance: checking, changing, and enhancing the system to make it more useful in achieving user and organizational goals


Summary (continued)

• Systems maintenance (continued): – For older programs, total cost of maintenance can be

up to five times greater than total cost of development

– More time and money spent on design means less time and money spent on maintenance

• Systems review: analysis of systems to make sure that they are operating as intended



Chapter Quiz

• Chapter quiz #13

• http://www.informatics.buu.ac.th/~wichai


ส วั� ส ดี�

Principles of Information Systems Eighth Edition Chapter 13 Systems Development: Design, Implementation, Maintenance, and Review.

Documents

importance of systems

purpose of systems design

right information

information systemsgetting

interface design

design modeling

physical designlogical

software development