Romney Ch20 slide

8/10/2019 Romney Ch20 slide

1/153

2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 1 of 173

C HAPTER 20

Systems Design,

Implementation, and

Operation


2/153


INTRODUCTION

Questions to be addressed in this chapter

include:

What are the activities that take place in the

conceptual design phase of the systems developmentlife cycle (SDLC)?

What activities take place in the physical systems

design phase?

What happens during the systems implementationand conversion process?

What activities occur in the systems operation and

maintenance process?


3/153


INTRODUCTION

Accountants must understand the entire systemsdevelopment process, because they areinvolved 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.

Ensuring the project stays on schedule.


4/153


INTRODUCTION

Effective systems analysis and design

can ensure that developers:

Correctly define the business problem. Design the appropriate solution.


5/153


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

Operation and maintenance


6/153


INTRODUCTION





include:





7/153 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart 7 of 173

CONCEPTUAL SYSTEMS DESIGN

In the conceptual sys tems designphase, a general framework is created forimplementing user requirements and

solving the problems identified in theanalysis phase.

The three main steps are:

Evaluate design alternatives. Prepare design specifications.

Prepare the conceptual systems designreport.



Systems

Analysis

Prepare

Design

Specifications

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance

Prepare

Conceptual Systems

Design Report

Evaluate

Design

Alternatives

Conceptual

Systems

Design


9/153




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,

optical character recognition, POS devices?




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

Reengineering its business processes




The design team should identify a variety ofdesign alternatives and evaluate each withrespect 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 thealternatives.

Click hereto view some of the designconsiderations and alternatives from Table 20-1in your textbook.

Design Considerations



Systems

Analysis

Prepare

Design

Specifications

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance

Prepare

Conceptual Systems

Design Report

Evaluate

Design

Alternatives




Prepare design specifications

Once a design has been selected, the

project team develops the conceptualdesign speci f icat ionsfor the following

elements:

Output

Because output is what goes to the user and the

system must be designed to meet user needs, the

output specifications are prepared first.







elements:

Output

Data storage

How will data be stored to produce the desired

outputs?







elements:

Output

Data storage

Input What types of data must be entered to produce the

desired outputs?





Once a design has been selected, theproject team develops the conceptual

design speci f icat ionsfor the followingelements:

Output

Data storage Input

Processing procedures and operations

How will data be processed and in what sequenceto produce the desired outputs?



Systems

Analysis

Prepare

Design

Specifications

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance

Prepare

Conceptual Systems

Design Report

Evaluate

Design

Alternatives




Prepare the conceptual systems design

report

A conceptual systems design repor tis

prepared at the end of the conceptual designphase to:

Guide physical system design activities.

Communicate how management and userinformation needs will be met.

Help the steering committee assess system

feasibility.




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 andprocedures.

A discussion of assumptions or unresolved problems

that might affect the final design.



INTRODUCTION





include:






PHYSICAL SYSTEMS DESIGN

During the physical systems design phase, thecompany determines how the conceptual AISdesign is to be implemented. The broad, user-oriented requirements of conceptual

design are translated into detailed specifications usedto code and test computer programs.

Phases include: Designing output

Creating files and databases

Designing input Writing computer programs

Developing procedures

Building in controls



Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

Design

Input

Design

Program

Design

Proce-dures

Design

Controls

Design

Physical

Systems

Design



Systems

Analysis

Conceptual

Systems

Design

Output

Design

Implementation

and

Conversion

Operation

and

Maintenance

File and DB

Design

Input

Design

Program

Design

Proce-dures

Design

Controls

Design


25/153



Output design

The objective of output design is to

determine the nature, format, content,and timing of printed reports,

documents, and screen displays.

Requires cooperation between users and

designers.


26/153



Important design considerations include:

Use of the output

Who will use it and why?

When is it needed?

What decisions will it facilitate?


27/153




Use of the output

Output medium

Paper

Screen

Voice response

Diskette

Microfilm

Other


28/153




Use of the output

Output medium

Output format Should select the format thatclearly conveys the most

information.

Could be:

Table Narrative

Graphic


29/153




Use of the output

Output medium

Output format

Pre-printed Should paper output be onpreprinted form and/or

turnaround document?


30/153




Use of the output

Output medium

Output format

Pre-printed

Location Where is the output to be

sent?


31/153




Use of the output

Output medium

Output format

Pre-printed

Location

Access Who should be able toaccess hard-copy and

screen output?


32/153




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.

Detailed info goes in an appendix.


33/153


34/153



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

Monthly financial statements


35/153




four categories:

Scheduled reports

Special-purpose analysis reports

No pre-specified content and format.

Typically prepared in response to a

management request. Example:

Analysis of impact of a government

mandate on profitability


36/153




four categories:

Scheduled reports


Triggered exception reports


Prepared only in response to abnormalconditions, i.e., the trigger.

Example:

Cost overruns


37/153




four categories:

Scheduled reports


Triggered exception reports

Demand reports


Prepared only on request.


38/153



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 proceedingthrough the SDLC.


39/153


Systems

Analysis

Conceptual

Systems

Design

OutputDesign

Implementation

and

Conversion

Operation

and

Maintenance

File and DBDesign

InputDesign

ProgramDesign

Proce-dures

Design

ControlsDesign


40/153



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

Paper


41/153






units.


include:

Storage medium

Processing mode Manual

Batch Real time


42/153






units.


include:

Storage medium

Processing mode

Maintenance What procedures are needed to

effectively maintain the data?


43/153






units.


include:

Storage medium

Processing mode

Maintenance

Size How many records and how big are they?

How fast are they expected to grow?


44/153






units.


include:

Storage medium

Processing mode

Maintenance

Size

Activity level

What portion of records are added or

deleted each year? What portion needs to be updated?


45/153


46/153



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

Computer screens


47/153



Considerations in input design include:

Input medium Keyboard

OCR

MICR

POS terminal

EDI

Voice input


48/153




Input medium

Input source

Where do data originate?

Computer

Customer

Remote location


49/153




Input medium

Input source

Input format What format captures the data with

the least effort or cost?

Source or turnaround document

Screen

Source data automation


50/153




Input medium

Input source

Input format Input type What is the nature of the data?


51/153




Input medium

Input source

Input format Input type

Volume How much data are to be entered?


52/153




Input medium

Input source


Volume

Personnel

What functions and expertise do the dataentry operators have?

Is additional training necessary?


53/153




Input medium

Input source


Volume

Personnel

Frequency How often is data to be entered?


54/153




Input medium

Input source


Volume

Personnel

Frequency

Cost

How can costs be minimized withoutadversely affecting efficiency and

accuracy?


55/153




Input medium

Input source


Volume

Personnel

Frequency

Cost

Error detection and correction

What errors are possible? How can they be detected and corrected?


56/153



Forms design

Although input is evolving toward source data

automation, forms design is still important.

Following are important principles fordesigning 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.

Include clear instructions for completing the form.


57/153



Forms design




ones:


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

company name and address pre-printed on

the form.


58/153



Forms design




ones:



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.

Use codes and check-offs in places where

standardized explanations are likely.


59/153



Forms Design




ones:



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.

Clearly indicate the distribution of

each form.


60/153



Designing computer screens

It is more efficient to enter data directly into

the computer than to record it on paper for

subsequent entry. Therefore, its important to design computer

screens for input as well as output.


61/153



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 fromthe system.

Example: If the customer number is entered, retrieve his

name/address data from the system.


62/153



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.


63/153



Computer screens are most effective when the followingprinciples are used:


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.


64/153





the data.



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.


65/153





the data.




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

locations. Make it easy to correct mistakes.

Use clear and explicit error messages that are consistent

on all screens.

Provide a help feature for online assistance.


66/153





the data.




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.

Limit the number of menu options on a single screen.


67/153


Systems

Analysis

Conceptual

Systems

Design

OutputDesign

Implementation

and

Conversion

Operation

and

Maintenance

File and DBDesign

InputDesign

ProgramDesign

Proce-dures

Design

ControlsDesign


68/153



Program design

Program development is one of the most time-

consuming activities in the SDLC.

A struc tured prog ramm ingprocess 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 thanwith each other.

To facilitate testing and modification, each module should

have only one entry and exit point.


69/153



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.

Consider doing structured program walk-

throughs to find incorrect logic, errors,

omissions, or other problems.


70/153



Program preparation time may range from a fewdays 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

developing software and where these steps take

place in the SDLC.


71/153



STEP ONE: Determine userneeds.

Occurs during the systems analysis

stage of the SDLC.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


72/153



STEP TWO: Develop anddocument a plan.

Occurs during the conceptual design

phase and the beginning of physical

design.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


73/153



STEP THREE: Write the programcode.

Design in increasing levels of detail,

known as hierarchical p rogram

design.

Begun during systems design and

completed during systems

implementation.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


74/153



STEP FOUR: Test the program code.

Debuggingis discovering and

eliminating program errors.

Desk checkinghappens after a

program is coded and involves avisual and mental review to discover

programming errors.

Programs are tested for logic errors

using test data that simulates bothvalid transactions and all possible

error conditions.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


75/153



Large programs are often testedin three stages:

Individual program modules.

The linkages between the moduleand the control module.

The interfaces between the

program being tested and other

application programs.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


76/153



Errors need to be found as soonas possible in the development

process.

Errors discovered late cost 801000% more to fix than those

found early.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


77/153



STEP FIVE: Document theprogram.

Documentation explains how

programs work and helpscorrect and resolve errors.

Includes flowcharts, record

layouts, E-R diagrams, REA

data models, narrativedescriptions of the system, etc.,

organized in a manual.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


78/153



STEP SIX: Train program users.

Often uses the program

documentation.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


79/153


80/153



STEP EIGHT: Use and modifythe system.

Prog ram maintenanceis a

response to any factors thatrequire program revision.

Includes requests for: New or revised reports.

Changes in input, file content, orvalues such as tax rates.

Error detection and correction.

Conversion to new hardware.

SystemsAnalysis

Conceptual

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


81/153


Systems

Analysis

Conceptual

Systems

Design

OutputDesign

Implementation

and

Conversion

Operation

and

Maintenance

File and DBDesign

InputDesign

ProgramDesign

Proce-

dures

Design

ControlsDesign

S C S S S S G


82/153



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

Output preparation and distribution

Computer operator instructions



83/153



Procedures may take the form of:

System manuals

User instruction classes

Training materials

Online help screens



84/153



The procedures may be written by:

Development teams;

Users; or

Teams representing both groups.


85/153


Systems

Analysis

Conceptual

Systems

Design

OutputDesign

Implementation

and

Conversion

Operation

and

Maintenance

File and DBDesign

InputDesign

ProgramDesign

Proce-

dures

Design

ControlsDesign



86/153



Controls design Improperly controlled input, processing, and

database functions produce information ofquestionable value.

Controls must be built into an AIS to ensureits effectiveness, efficiency, and accuracy.These controls should: Minimize errors.

Detect and correct errors when they do occur.

Accountants play a vital role in this area.


87/153



88/153



Important control concerns that must beaddressed include:

Validity

Authorization

Are input, processing, storage, and

output activities authorized by the

appropriate managers?



89/153




Validity

Authorization

Accuracy Is input verified to ensure accuracy?

What controls ensure that data is not

lost when passing between processing

activities?



90/153




Validity

Authorization

Accuracy

Security

Is the system protected against:

Unauthorized physical and logical access to preventimproper use, alteration, destruction, or disclosure of

information and software?

Theft of system resources?



91/153




Validity

Authorization

Accuracy

Security

Numerical control

Are documents pre-numbered to prevent errors orintentional misuse and to detect when documents are

missing or stolen?



92/153




Validity

Authorization

Accuracy

Security

Numerical control

Availability Is the system available as set forth in agreements?

Can users enter, update, and retrieve data during those

times?



93/153




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

authorized users?



94/153




Validity

Authorization

Accuracy

Security

Numerical control

Availability Maintainability

Integrity

Is processing complete, accurate, timely, and

authorized?

Is it free from unauthorized or inadvertentmanipulations?



95/153



Important control concerns that must beaddressed include: Validity

Authorization

Accuracy Security

Numerical control

Availability

Maintainability Integrity

Audit trail

Can data be traced from source to output and viceversa?


96/153

INTRODUCTION


97/153


INTRODUCTION

The crucial phases of the SDLC include: Systems analysis to define the new systems


The phases discussed in this chapter, whichinclude:


Physical systems design

Systems implementation and conversion


SYSTEMS IMPLEMENTATION AND


98/153


CONVERSION

Systems implementation Systemsimplementat ionis the process of

installing hardware and software andgetting 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

Testing the system

Systems

Analysis


99/153


Conceptual

SystemsDesign

Physical

Systems

Design

Operation

and

Maintenance

Prepare Site;

Install and Test

Hardware

Select and TrainPersonnel

System

Implementation

and

Conversion

Implementation

Planning

Complete

Documentation

TestSystem

Conversion

Systems

Analysis


100/153


Conceptual

SystemsDesign

Physical

Systems

Design

Operation

and

Maintenance

Prepare Site;

Install and Test

Hardware


Implementation

Planning

Complete

Documentation

TestSystem

Conversion



101/153


CONVERSION

Implementation planning An imp lementat ion planconsists of:

Implementation tasks

Expected completion dates

Cost estimates Specification of the person(s) responsible for each task

The plan specifies when the project should becomplete and operational.

The implementation team should identify risk

factors that decrease the likelihood of successfulimplementation, and the plan should contain astrategy for coping with each of the risks.


102/153

Systems

Analysis


103/153


Conceptual

SystemsDesign

Physical

Systems

Design

Operation

and

Maintenance

Prepare site;

Install and Test

hardware


Implementation

Planning

Complete

Documentation

TestSystem

Conversion


104/153



105/153


CONVERSION

Site preparation is a lengthy process andshould begin well ahead of the installation

date.

Systems

Analysis


106/153


Conceptual

SystemsDesign

Physical

Systems

Design

Operation

and

Maintenance

Prepare Site;

Install and Test

Hardware


Implementation

Planning

Complete

Documentation

TestSystem

Conversion



107/153


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 alreadyunderstand the business.

Transferring displaced employees can enhanceloyalty and morale.

Companies take training shortcuts because:

Effective training is time-consuming andexpensive.

Those who understand the system are maintainingand upgrading it.



108/153


CONVERSION

When training is insufficient, the company willnot achieve the expected return on investment.

The hidden cost is that users will turn to theircoworkers 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

The training should be scheduled just beforesystems testing and conversion.



109/153


CONVERSION

Types of training include: Technical training from vendors

Self-study manuals

Computer-aided instruction Videotape presentations

Role-playing

Case studies Experimenting with the AIS under the

guidance of experienced users


110/153



111/153


CONVERSION

Three types of documentation must beprepared 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.

User acceptance forms.


CO S O


112/153


CONVERSION


Operations documentation

Includes:

Operating schedules.

Files and databases accessed.

Equipment, security, and file retention requirements


CONVERSION


113/153


CONVERSION


Operations documentation User documentation

Teaches users how to operate the AIS.

Includes a procedures manual and training materials.


114/153


CONVERSION


115/153


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

Backup and recovery procedures


CONVERSION


116/153


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 systemdesign.

Focus is on organization:

Input

Files

Outputs

Data flows

Subsequent walk-throughs are attended by programmers.

Address logical and structural aspects of program code.


117/153


118/153


CONVERSION


119/153


CONVERSION

Three common forms of testing include: Walk-throughs

Processing test transactions

Acceptance tests

Even software purchased from an

outside vendor must be tested

thoroughly before installation.


120/153


CONVERSION


121/153


CONVERSION

Systems conversion Convers ionis the process of changing from the old

AIS to the new.

Many elements must be converted, including:

Hardware

Software

Data files

Procedures

The process is complete when the new AIS hasbecome a routine, ongoing part of the system.


122/153


CONVERSION


123/153


CONVERSION

Conversion approaches Four conversion approaches are used to

change from an old to a new system:

Direct conversion Parallel conversion

Phase-in conversion

Pilot conversion


CONVERSION


124/153


CONVERSION

Direct conversion Immediately terminates the old AIS when the

new one is introduced.

Appropriate when: The old AIS has no value; or

The new AIS is so different that comparisons

between the two are meaningless.


CONVERSION


125/153


CONVERSION

Main advantage to direct conversion: Its inexpensive

Main disadvantage:

It provides no backup AIS.

There is a high risk of failure unless the

new system has been very carefully

developed and tested.


CONVERSION


126/153


CONVERSION




Phase-in conversion

Pilot conversion


CONVERSION


127/153


CONVERSION

Parallel conversion Operates the old and new systems

simultaneously for a period of time.

You can process transactions with bothsystems, compare output, reconcile

differences, and make corrections to the new

AIS.


CONVERSION


128/153


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

gained widespread popularity.


CONVERSION


129/153


CONVERSION




Phase-in conversion

Pilot conversion


CONVERSION


130/153


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 newAIS.

Time required to make the complete conversion.


CONVERSION


131/153


CONVERSION




Phase-in conversion

Pilot conversion


CONVERSION


132/153


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 remaininglocations.

Advantages: Localizes conversion problems and allows training in a live

environment.

Disadvantages: Long conversion time.

Need for interfaces between old and new systems.


CONVERSION


133/153


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 addedor deleted).

A file or database format may be changed.


CONVERSION


134/153


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 lostduring conversion.

If the file conversion is lengthy, update the new fileswith transactions that occurred during dataconversion.

After conversion and testing, monitor the system tomake sure it runs smoothly and accurately.

Document the conversion activities.

Systems

Analysis


135/153


Analysis

Conceptual

Systems

Design

Physical

Design

Implementation

and

Conversion

Operation

and

Maintenance


136/153

OPERATIONS AND MAINTENANCE


137/153


Factors and questions include: Goals and objectives

Does the system help the organization meet its goals,

objectives, and overall mission?


138/153



139/153



Satisfaction

Benefits Were the expected benefits achieved?



140/153



Satisfaction

Benefits

Costs Are actual costs in line with expected costs?



141/153



Satisfaction

Benefits

Costs

Reliability Has the system failed, and if so, why?



142/153



Satisfaction

Benefits

Costs

Reliability

Accuracy

Does the system produce accurate and complete

data?



143/153



Satisfaction

Benefits

Costs

Reliability

Accuracy

Timeliness

Does the system produce timely information?



144/153


Factors and questions include: Compatibility

Are hardware, software, data, and procedures

compatible with existing systems?



145/153



Controls and security

Are there safeguards against unintentional errors,

fraud, and intrusion?



146/153




Errors Are there adequate error-handling procedures?


147/153



148/153




Errors

Training

Communications Is the communications system adequate?



149/153




Errors

Training

Communications

Organization changes

Are structural changes that resulted from the system

beneficial or harmful?

If harmful, how can they be resolved?



150/153




Errors

Training

Communications

Organization changes

Documentation

Is documentation complete and accurate?



151/153


Any problems discovered during thereview should be brought to

managements attention, and adjustments

should be made. When the review is complete, a post -

implementation review repo rtis

prepared. User acceptance of that report is the final

activity in systems development.


152/153

SUMMARY AND CONCLUSIONS


153/153

Youve learned in more depth about the activitiesthat take place in the conceptual design phase ofthe systems development life cycle (SDLC).

Youve also learned about activities that takeplace in the physical systems design phase.

Youve explored what happens during thesystems implementation and conversionprocess.

Finally, youve learned about the activities in thelast phase of the systems development life

Romney Ch20 slide

Documents

Transcript of Romney Ch20 slide