• No results found

romney_ch20.ppt

N/A
N/A
Protected

Academic year: 2020

Share "romney_ch20.ppt"

Copied!
172
0
0

Loading.... (view fulltext now)

Full text

(1)

C

HAPTER 20

Systems Design,

Implementation, and

(2)

INTRODUCTION

• Questions to be addressed in this chapter

include:

– What are the activities that take place in the

conceptual design phase of the systems development

life cycle (SDLC)?

– What activities take place in the physical systems

design phase?

– What happens during the systems implementation

and conversion process?

(3)

INTRODUCTION

• Accountants must understand the entire systems

development process, because they are

involved in several ways:

– Helping to specify their needs.

– As members of the development team.

– As auditors after the fact.

• Accountants also help keep the project on track

by:

– Evaluating and measuring benefits.

– Measuring costs.

(4)

INTRODUCTION

• Effective systems analysis and design

can ensure that developers:

(5)

INTRODUCTION

• The crucial phases of the SDLC include:

– Systems analysis to define the new systems

requirements (discussed in Chapter 18).

– The phases discussed in this chapter, which

include:

• Conceptual systems design

• Physical systems design

(6)

INTRODUCTION

• The crucial phases of the SDLC include:

– Systems analysis to define the new systems

requirements (discussed in Chapter 18).

– The phases discussed in this chapter, which

include:

Conceptual systems design

• Physical systems design

(7)

CONCEPTUAL SYSTEMS DESIGN

• In the

conceptual systems design

phase, a general framework is created for

implementing user requirements and

solving the problems identified in the

analysis phase.

• The three main steps are:

– Evaluate design alternatives.

– Prepare design specifications.

(8)
(9)
(10)

CONCEPTUAL SYSTEMS DESIGN

Evaluating design alternatives

– There are many design decisions that must be

made. For example:

• Should a document be hard-copy or sent by EDI?

• Should the company use a large centralized

mainframe or some form of distributed processing?

• What form should data entry take, e.g., keyboard,

(11)

CONCEPTUAL SYSTEMS DESIGN

• Also, there are many ways to approach the

systems development process:

– Packaged software

– In-house development

– End-user development

– Outsourcing

• The company also chooses between:

– Modifying or enhancing existing software

– Replacing existing software

(12)

CONCEPTUAL SYSTEMS DESIGN

• The design team should identify a variety of

design alternatives and evaluate each with

respect to:

– How well it meets organizational and system

objectives

– How well it meets user needs

– Whether it is economically feasible

– Its advantages and disadvantages

• The steering committee evaluates the

alternatives.

Click here

to view some of the design

(13)
(14)

CONCEPTUAL SYSTEMS DESIGN

Prepare design specifications

– Once a design has been selected, the

project team develops the

conceptual

design specifications

for the following

elements:

Output

(15)

CONCEPTUAL SYSTEMS DESIGN

Prepare design specifications

– Once a design has been selected, the

project team develops the

conceptual

design specifications

for the following

elements:

• Output

Data storage

(16)

CONCEPTUAL SYSTEMS DESIGN

Prepare design specifications

– Once a design has been selected, the

project team develops the

conceptual

design specifications

for the following

elements:

• Output

• Data storage

Input

(17)

CONCEPTUAL SYSTEMS DESIGN

Prepare design specifications

– Once a design has been selected, the

project team develops the

conceptual

design specifications

for the following

elements:

• Output

• Data storage

• Input

Processing procedures and operations

(18)

Systems

Analysis

Prepare

Design

Specifications

Physical

Design

Implementation

and

Conversion

Operation

and

Prepare

Conceptual Systems

Design Report

(19)

CONCEPTUAL SYSTEMS DESIGN

Prepare the conceptual systems design

report

– A

conceptual systems design report

is

prepared at the end of the conceptual design

phase to:

• Guide physical system design activities.

• Communicate how management and user

information needs will be met.

(20)

CONCEPTUAL SYSTEMS DESIGN

• The main component is a description of one or

more recommended system designs. This

description contains:

– The contents of each output, database, and input.

– Processing flows and the relationships among

programs, files, inputs, and outputs.

– Hardware, software, and resource requirements.

– Audit, control, and security processes and

procedures.

(21)

INTRODUCTION

• The crucial phases of the SDLC include:

– Systems analysis to define the new systems

requirements (discussed in Chapter 18).

– The phases discussed in this chapter, which

include:

• Conceptual systems design

Physical systems design

(22)

PHYSICAL SYSTEMS DESIGN

• During the physical systems design phase, the

company determines how the conceptual AIS

design is to be implemented.

– The broad, user-oriented requirements of conceptual

design are translated into detailed specifications used

to code and test computer programs.

– Phases include:

• Designing output

• Creating files and databases

• Designing input

• Writing computer programs

• Developing procedures

(23)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

(24)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

File and DB

(25)

PHYSICAL SYSTEMS DESIGN

Output design

– The objective of output design is to

determine the nature, format, content,

and timing of printed reports,

documents, and screen displays.

(26)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

Use of the output

Who will use it and why?

When is it needed?

(27)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

Output medium

Paper

Screen

Voice response

Diskette

Microfilm

(28)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

– Output medium

Output format

Should select the format that

clearly conveys the most

information.

Could be:

Table

Narrative

(29)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

– Output medium

– Output format

Pre-printed

Should paper output be on

preprinted form and/or

(30)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

– Output medium

– Output format

– Pre-printed

(31)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

– Output medium

– Output format

– Pre-printed

– Location

Access

Who should be able to

(32)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

– Output medium

– Output format

– Pre-printed

– Location

– Access

Detail

Lengthy output should be preceded by an

executive summary and a table of contents.

Headings and legends organize data and

highlight important items.

(33)

PHYSICAL SYSTEMS DESIGN

• Important design considerations include:

– Use of the output

– Output medium

– Output format

– Pre-printed

– Location

– Access

– Detail

Timeliness

(34)

PHYSICAL SYSTEMS DESIGN

• Outputs usually fit into one of the following

four categories:

Scheduled reports

Have pre-specified content and format.

Are prepared on a regular basis.

Examples:

Weekly sales analysis

(35)

PHYSICAL SYSTEMS DESIGN

• Outputs usually fit into one of the following

four categories:

– Scheduled reports

Special-purpose analysis reports

No pre-specified content and format.

Typically prepared in response to a

management request.

Example:

(36)

PHYSICAL SYSTEMS DESIGN

• Outputs usually fit into one of the following

four categories:

– Scheduled reports

– Special-purpose analysis reports

Triggered exception reports

Have pre-specified content and format.

Prepared only in response to abnormal

conditions, i.e., the “trigger.”

(37)

PHYSICAL SYSTEMS DESIGN

• Outputs usually fit into one of the following

four categories:

– Scheduled reports

– Special-purpose analysis reports

– Triggered exception reports

Demand reports

Have pre-specified content and format.

(38)

PHYSICAL SYSTEMS DESIGN

• AIS developers prepare sample outputs

and users evaluate them to ensure they

are complete, relevant, and useful.

– Modifications are made as needed to ensure

acceptability.

– Many organizations require users to sign off

on these documents before proceeding

(39)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

(40)

PHYSICAL SYSTEMS DESIGN

File and database design

– Various company segments need to store data in

compatible formats so that data can be shared across

units.

– Important file and database design considerations

include:

Storage medium

Hard drive

Disk

Diskette

CD

Tape

(41)

PHYSICAL SYSTEMS DESIGN

File and database design

– Various company segments need to store data in

compatible formats so that data can be shared across

units.

– Important file and database design considerations

include:

• Storage medium

Processing mode

Manual

Batch

(42)

PHYSICAL SYSTEMS DESIGN

File and database design

– Various company segments need to store data in

compatible formats so that data can be shared across

units.

– Important file and database design considerations

include:

• Storage medium

• Processing mode

Maintenance

What procedures are needed to

(43)

PHYSICAL SYSTEMS DESIGN

File and database design

– Various company segments need to store data in

compatible formats so that data can be shared across

units.

– Important file and database design considerations

include:

• Storage medium

• Processing mode

• Maintenance

Size

How many records and how big are they?

(44)

PHYSICAL SYSTEMS DESIGN

File and database design

– Various company segments need to store data in

compatible formats so that data can be shared across

units.

– Important file and database design considerations

include:

• Storage medium

• Processing mode

• Maintenance

• Size

Activity level

What portion of records are added or

deleted each year?

(45)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

(46)

PHYSICAL SYSTEMS DESIGN

Input design

– Systems designers must identify the

different types of data input and optimal

input methods.

– There are two principal types of data

input:

• Forms

(47)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

Input medium

Keyboard

OCR

MICR

POS terminal

EDI

(48)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

Input source

Where do data originate?

Computer

Customer

(49)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

Input format

What format captures the data with

the least effort or cost?

Source or turnaround document

Screen

(50)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

– Input format

(51)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

– Input format

– Input type

(52)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

– Input format

– Input type

– Volume

Personnel

What functions and expertise do the data

entry operators have?

(53)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

– Input format

– Input type

– Volume

– Personnel

(54)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

– Input format

– Input type

– Volume

– Personnel

– Frequency

Cost

(55)

PHYSICAL SYSTEMS DESIGN

Considerations in input design include:

– Input medium

– Input source

– Input format

– Input type

– Volume

– Personnel

– Frequency

– Cost

Error detection and correction

What errors are possible?

(56)

PHYSICAL SYSTEMS DESIGN

Forms design

– Although input is evolving toward source data

automation, forms design is still important.

– Following are important principles for

designing new forms and evaluating existing

ones:

General considerations

Preprint as much data as possible.

Use appropriate weight and grade of paper.

Use bold type, double-thick lines, and shading to

highlight different parts of the form.

Use a standard size and one that is consistent with

requirements for filing, binding, or mailing.

If mailed to external parties, position the address for

placement in a window envelope.

Have copies of the form printed in different colors to

facilitate accurate distribution.

(57)

PHYSICAL SYSTEMS DESIGN

Forms design

– Although input is evolving toward source data

automation, forms design is still important.

– Following are important principles for

designing new forms and evaluating existing

ones:

• General considerations

Introductory section of form

Place the form name at the top in bold type.

Have the forms pre-numbered

consecutively.

If distributed to external parties, have

(58)

PHYSICAL SYSTEMS DESIGN

Forms design

– Although input is evolving toward source data

automation, forms design is still important.

– Following are important principles for

designing new forms and evaluating existing

ones:

• General considerations

• Introductory section of form

Main body of form

Group together logically related information

(e.g., info about the customer, info about

the product).

Provide sufficient room to record each item.

Order the data items consistent with the

sequence in which the data is likely to be

gathered.

(59)

PHYSICAL SYSTEMS DESIGN

Forms Design

– Although input is evolving toward source data

automation, forms design is still important.

– Following are important principles for

designing new forms and evaluating existing

ones:

• General considerations

• Introductory section of form

• Main body of form

Conclusion section of form

Provide space for:

Recording final disposition of the form.

Approval signatures.

Dates of approval and final disposition.

A dollar or numeric total.

(60)

PHYSICAL SYSTEMS DESIGN

Designing computer screens

– It is more efficient to enter data directly into

the computer than to record it on paper for

subsequent entry.

(61)

PHYSICAL SYSTEMS DESIGN

• Computer screens are most effective when the following

principles are used:

Organize the screen for quick, accurate, and complete entry

of the data.

Minimize input by retrieving as much as possible from

the system.

(62)

PHYSICAL SYSTEMS DESIGN

• Computer screens are most effective when the following

principles are used:

– Organize the screen for quick, accurate, and complete entry of

the data.

(63)

PHYSICAL SYSTEMS DESIGN

• Computer screens are most effective when the following

principles are used:

– Organize the screen for quick, accurate, and complete entry of

the data.

– Enter data in the same order it appears on the document.

(64)

PHYSICAL SYSTEMS DESIGN

• Computer screens are most effective when the following

principles are used:

– Organize the screen for quick, accurate, and complete entry of

the data.

– Enter data in the same order it appears on the document.

– Complete the screen from left to right and top to bottom,

grouping logically related data together.

(65)

PHYSICAL SYSTEMS DESIGN

• Computer screens are most effective when the following

principles are used:

– Organize the screen for quick, accurate, and complete entry of

the data.

– Enter data in the same order it appears on the document.

– Complete the screen from left to right and top to bottom,

grouping logically related data together.

– Design the screen so users can jump from one data entry

location to another or use a single key to go directly to screen

locations.

Make it easy to correct mistakes.

(66)

PHYSICAL SYSTEMS DESIGN

• Computer screens are most effective when the following

principles are used:

– Organize the screen for quick, accurate, and complete entry of

the data.

– Enter data in the same order it appears on the document.

– Complete the screen from left to right and top to bottom,

grouping logically related data together.

– Design the screen so users can jump from one data entry

location to another or use a single key to go directly to screen

locations.

– Make it easy to correct mistakes.

Avoid clutter by restricting the amount of data on one

screen.

(67)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

(68)

PHYSICAL SYSTEMS DESIGN

Program design

– Program development is one of the most

time-consuming activities in the SDLC.

– A

structured programming

process should be

followed:

• With structured programming, programs should be

subdivided into small, well-defined modules to reduce

complexity and enhance reliability and modifiability.

• Modules should interact with a control module rather than

with each other.

(69)

PHYSICAL SYSTEMS DESIGN

• To improve software quality, organizations

should develop programming standards (rules

for writing programs).

– Contributes to consistency among programs.

– Makes them easier to read and maintain.

(70)

PHYSICAL SYSTEMS DESIGN

• Program preparation time may range from a few

days to a few years, depending on complexity.

• Though accountants need not be programmers,

they should understand how software is created.

• The following slides discuss the eight steps for

(71)

PHYSICAL SYSTEMS DESIGN

• STEP ONE: Determine user

needs.

– Occurs during the systems analysis

stage of the SDLC.

Systems

Analysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

(72)

PHYSICAL SYSTEMS DESIGN

• STEP TWO: Develop and

document a plan.

– Occurs during the conceptual design

phase and the beginning of physical

design.

Systems

Analysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

(73)

PHYSICAL SYSTEMS DESIGN

• STEP THREE: Write the program

code.

– Design in increasing levels of detail,

known as

hierarchical program

design

.

– Begun during systems design and

completed during systems

(74)

PHYSICAL SYSTEMS DESIGN

• STEP FOUR: Test the program code.

Debugging

is discovering and

eliminating program errors.

Desk checking

happens after a

program is coded and involves a

visual and mental review to discover

programming errors.

(75)

PHYSICAL SYSTEMS DESIGN

– Large programs are often tested

in three stages:

• Individual program modules.

• The linkages between the module

and the control module.

• The interfaces between the

(76)

PHYSICAL SYSTEMS DESIGN

– Errors need to be found as soon

as possible in the development

process.

– Errors discovered late cost 80–

1000% more to fix than those

found early.

Systems

Analysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

(77)

PHYSICAL SYSTEMS DESIGN

• STEP FIVE: Document the

program.

– Documentation explains how

programs work and helps

correct and resolve errors.

– Includes flowcharts, record

layouts, E-R diagrams, REA

data models, narrative

descriptions of the system, etc.,

organized in a manual.

(78)

PHYSICAL SYSTEMS DESIGN

• STEP SIX: Train program users.

– Often uses the program

documentation.

Systems

Analysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

(79)

PHYSICAL SYSTEMS DESIGN

• STEP SEVEN: Install the system.

-

All components are brought

together, and the company

begins to use the system.

Systems

Analysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

(80)

PHYSICAL SYSTEMS DESIGN

• STEP EIGHT: Use and modify

the system.

Program maintenance

is a

response to any factors that

require program revision.

– Includes requests for:

• New or revised reports.

• Changes in input, file content, or

values such as tax rates.

• Error detection and correction.

• Conversion to new hardware.

(81)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

(82)

PHYSICAL SYSTEMS DESIGN

Procedures design

– Individuals who interact with a newly-designed

AIS need procedures to cover:

• Input preparation

• Transaction processing

• Error detection and correction

• Controls

• Reconciliation of balances

• Database access

(83)

PHYSICAL SYSTEMS DESIGN

• Procedures may take the form of:

– System manuals

– User instruction classes

– Training materials

(84)

PHYSICAL SYSTEMS DESIGN

• The procedures may be written by:

– Development teams;

– Users; or

(85)

Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

(86)

PHYSICAL SYSTEMS DESIGN

Controls design

– Improperly controlled input, processing, and

database functions produce information of

questionable value.

– Controls must be built into an AIS to ensure

its effectiveness, efficiency, and accuracy.

These controls should:

• Minimize errors.

• Detect and correct errors when they do occur.

(87)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

(88)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

Authorization

(89)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

Accuracy

Is input verified to ensure accuracy?

(90)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

– Accuracy

Security

Is the system protected against:

Unauthorized physical and logical access to prevent

improper use, alteration, destruction, or disclosure of

information and software?

(91)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

– Accuracy

– Security

Numerical control

(92)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

– Accuracy

– Security

– Numerical control

Availability

Is the system available as set forth in agreements?

(93)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

– Accuracy

– Security

– Numerical control

– Availability

Maintainability

Can the system be modified without affecting system

availability, security, and integrity?

Are only authorized, tested, and documented changes

made to the system and data?

Are resources available to manage, schedule, document,

and communicate changes to management and

(94)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

– Accuracy

– Security

– Numerical control

– Availability

– Maintainability

Integrity

Is processing complete, accurate, timely, and

authorized?

(95)

PHYSICAL SYSTEMS DESIGN

Important control concerns that must be

addressed include:

– Validity

– Authorization

– Accuracy

– Security

– Numerical control

– Availability

– Maintainability

– Integrity

Audit trail

(96)

PHYSICAL SYSTEMS DESIGN

Physical systems design report

– At the end of the physical design phase, a

physical systems design report

is prepared,

summarizing what was accomplished.

– This report serves as the basis for

(97)

INTRODUCTION

• The crucial phases of the SDLC include:

– Systems analysis to define the new systems

requirements (discussed in Chapter 18).

– The phases discussed in this chapter, which

include:

• Conceptual systems design

• Physical systems design

Systems implementation and conversion

(98)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Systems implementation

Systems

implementation

is the process of

installing hardware and software and

getting the AIS up and running.

Phases include:

Developing a plan

Preparing the site

Installing and testing hardware and software

Selecting and training personnel

Completing documentation

(99)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

and

Prepare Site;

Install and Test

Hardware

(100)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

Prepare Site;

Install and Test

Hardware

(101)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Implementation planning

An

implementation plan

consists of:

Implementation tasks

Expected completion dates

Cost estimates

Specification of the person(s) responsible for each task

The plan specifies when the project should be

complete and operational.

The implementation team should identify risk

(102)

SYSTEMS IMPLEMENTATION AND

CONVERSION

AIS changes may require adjustments to the

company’s organizational structure,

including:

Creation of new departments.

Elimination or downsizing of existing

departments.

(103)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

and

Prepare site;

Install and Test

hardware

(104)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Site preparation

A large computer may require changes such as:

New electrical outlets

Data communications facilities

Raised floors

Humidity controls

Special lighting

Air-conditioning

Security measures, such as:

Fire protection

Emergency power supply

(105)

SYSTEMS IMPLEMENTATION AND

CONVERSION

(106)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

Prepare Site;

Install and Test

Hardware

(107)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Select and train personnel

– Employees can be hired from outside or

transferred internally.

• Hiring from within is usually more effective and

less costly, because the employees already

understand the business.

• Transferring displaced employees can enhance

loyalty and morale.

– Companies take training shortcuts because:

• Effective training is time-consuming and

expensive.

(108)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• When training is insufficient, the company will

not achieve the expected return on investment.

• The hidden cost is that users will turn to their

coworkers who have mastered the system for

help. Results in:

– Less productive coworkers

– Increased costs

• Effective training includes:

– Hardware and software skills

– Orientation to new policies and operations

(109)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Types of training include:

– Technical training from vendors

– Self-study manuals

– Computer-aided instruction

– Videotape presentations

– Role-playing

– Case studies

(110)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

Prepare site;

Install and Test

Hardware

(111)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three types of documentation must be

prepared for new systems:

Development documentation

Describes the AIS and includes:

A system description.

Copies of output, input, file, and database layouts.

Program flowcharts.

Test results.

(112)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three types of documentation must be

prepared for new systems:

– Development documentation

Operations documentation

Includes:

Operating schedules.

Files and databases accessed.

(113)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three types of documentation must be

prepared for new systems:

– Development documentation

– Operations documentation

User documentation

Teaches users how to operate the AIS.

(114)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

Prepare site;

Install and Test

Hardware

(115)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Test the system

– Inadequate system testing has contributed to the

failure of systems.

– All of the following should be given a trial run in

realistic circumstances.

• Documents and reports

• User input

• Operating and control procedures

• Processing procedures

• Computer programs

– Should also test:

• Capacity limits

(116)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three common forms of testing include:

Walk-throughs

Step-by-step reviews of procedures or program logic.

Attended by the development team and users early in system

design.

Focus is on organization:

Input

Files

Outputs

Data flows

(117)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three common forms of testing include:

– Walk-throughs

Processing test transactions

Determines whether the program operates as

designed.

Requires both valid and erroneous data.

(118)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three common forms of testing include:

– Walk-throughs

– Processing test transactions

Acceptance tests

Uses copies of real transactions and files

rather than hypothetical ones.

Users develop acceptance criteria.

(119)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Three common forms of testing include:

– Walk-throughs

– Processing test transactions

– Acceptance tests

Even software purchased from an

(120)

Systems

Analysis

Conceptual

Systems

Design

Physical

Systems

Design

Operation

Prepare site;

Install and test

hardware

(121)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Systems conversion

Conversion

is the process of changing from the old

AIS to the new.

– Many elements must be converted, including:

• Hardware

• Software

• Data files

• Procedures

(122)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Conversion approaches

– Four conversion approaches are used to

change from an old to a new system:

(123)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Conversion approaches

– Four conversion approaches are used to

change from an old to a new system:

Direct conversion

(124)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Direct conversion

– Immediately terminates the old AIS when the

new one is introduced.

– Appropriate when:

• The old AIS has no value; or

(125)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Main advantage to direct conversion:

– It’s inexpensive

• Main disadvantage:

– It provides no backup AIS.

• There is a high risk of failure unless the

new system has been very carefully

(126)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Conversion approaches

– Four conversion approaches are used to

change from an old to a new system:

• Direct conversion

Parallel conversion

(127)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Parallel conversion

– Operates the old and new systems

simultaneously for a period of time.

– You can process transactions with both

systems, compare output, reconcile

(128)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Main advantage to parallel conversion:

– It protects the company from errors.

• Main disadvantage:

– It is costly and stressful for employees to process all

transactions twice.

• Because companies often experience problems

during conversion, parallel processing has

(129)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Conversion approaches

– Four conversion approaches are used to

change from an old to a new system:

• Direct conversion

• Parallel conversion

Phase-in conversion

(130)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Phase-in conversion

– Gradually replaces elements of the old AIS with the

new one.

– The new system is often phased in a module at a

time.

– Main Advantage:

• Data processing resources can be acquired over time.

– Disadvantages:

• Costs of creating temporary interfaces between old and new

AIS.

(131)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Conversion approaches

– Four conversion approaches are used to

change from an old to a new system:

• Direct conversion

• Parallel conversion

• Phase-in conversion

(132)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Pilot conversion

– Implements a system in just one part of the

organization, e.g., a branch office or a single store.

– When problems with the system are resolved, the

new system could be implemented at the remaining

locations.

– Advantages:

• Localizes conversion problems and allows training in a live

environment.

– Disadvantages:

• Long conversion time.

(133)

SYSTEMS IMPLEMENTATION AND

CONVERSION

Data conversion

– Data conversion can be time-consuming,

tedious, and expense.

– The difficulty and magnitude is easy to

underestimate.

– Data files may need to be modified in three

ways:

• Files may be moved to a different storage medium

(e.g., tape to disk).

• Data content may be changed (e.g., fields added

or deleted).

(134)

SYSTEMS IMPLEMENTATION AND

CONVERSION

• Steps in the data conversion process:

– Decide which data files need to be converted.

– Check files for completeness and data inaccuracies,

and remove any inconsistencies.

– Do the actual data conversion.

– Validate the new files to ensure data were not lost

during conversion.

– If the file conversion is lengthy, update the new files

with transactions that occurred during data

conversion.

– After conversion and testing, monitor the system to

make sure it runs smoothly and accurately.

(135)

Systems

Analysis

Conceptual

Systems

Design

Physical

Design

Implementation

and

Conversion

Operation

and

(136)

OPERATIONS AND MAINTENANCE

• The last step in the SDLC is to operate

and maintain the new system.

• A

post-implementation review

should be

conducted to ensure the new AIS meets

(137)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

Goals and objectives

(138)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Goals and objectives

Satisfaction

Are users satisfied?

(139)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Goals and objectives

– Satisfaction

(140)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Goals and objectives

– Satisfaction

– Benefits

(141)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Goals and objectives

– Satisfaction

– Benefits

– Costs

Reliability

(142)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Goals and objectives

– Satisfaction

– Benefits

– Costs

– Reliability

Accuracy

(143)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Goals and objectives

– Satisfaction

– Benefits

– Costs

– Reliability

– Accuracy

Timeliness

(144)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

Compatibility

(145)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Compatibility

Controls and security

(146)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Compatibility

– Controls and security

Errors

(147)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Compatibility

– Controls and security

– Errors

Training

(148)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Compatibility

– Controls and security

– Errors

– Training

Communications

(149)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Compatibility

– Controls and security

– Errors

– Training

– Communications

Organization changes

Are structural changes that resulted from the system

beneficial or harmful?

(150)

OPERATIONS AND MAINTENANCE

• Factors and questions include:

– Compatibility

– Controls and security

– Errors

– Training

– Communications

– Organization changes

Documentation

(151)

OPERATIONS AND MAINTENANCE

• Any problems discovered during the

review should be brought to

management’s attention, and adjustments

should be made.

• When the review is complete, a

post-implementation review report

is

prepared.

(152)

OPERATIONS AND MAINTENANCE

• Control of the AIS is then passed to the

data processing department.

• But the work is not done.

– About 30% of the work takes place during

development.

(153)

SUMMARY AND CONCLUSIONS

• You’ve learned in more depth about the activities

that take place in the conceptual design phase of

the systems development life cycle (SDLC).

• You’ve also learned about activities that take

place in the physical systems design phase.

• You’ve explored what happens during the

systems implementation and conversion process.

• Finally, you’ve learned about the activities in the

last phase of the systems development life cycle

—the systems operation and maintenance

References

Related documents

Pipeline and electric utility ROW have many similarities with regard to siting, planning, construction methods, operational procedures, and maintenance

In John’s Gospel, Jesus speaks of the gatekeeper who opens the gate and calls for his sheep.. They respond because they know

Which of the following describes what happens to white sugar when mixed with iodized salt. White sugar can be distinguished from the

In a perceptual decision making task in which the required response was a reach toward one of two targets, specified by the stimulus, movements sometimes started towards one

An implicit group and a group of subjects using explicit strategies adapted to 20°, 40° and 60° cursor rotations, and we measured awareness and unawareness indices after

The purpose of this study was to quantify spatial and temporal gait asymmetries (assessed via an instrumented walkway) as well as transcallosal microstructural integrity of

While building upon an earlier report [ 12 ], where a robust machine learning model was developed for the classification of NPSLE patients and HCs using prespecified

Please list current therapies that you child is participating in: Occupational Therapy Services Provider:. Physical Therapy Services Provider: Speech Therapy Services Provider: