Systems Design,

Implementation, and Operation

Chapter 22

Copyright © 2015 Pearson Education, Inc.

22-1
 Learning Objectives
• Discuss the conceptual systems design process
and the activities in this phase.

• Discuss the physical systems design process and

the activities in this phase.

• Discuss the systems implementation and

conversion process and the activities in this phase.

• Discuss the systems operation and maintenance

process and the activities in this phase.
Copyright © 2015 Pearson Education, Inc.
22-2
 Phase 2: Conceptual Systems Design

Copyright © 2015 Pearson Education, Inc.

22-3
 Phase 3: Physical Systems Design

• Output design (e.g., reports)

• File and database design
• Input design (e.g., forms, computer screen
input)
• Program design
• Procedures design
• Control design

Copyright © 2015 Pearson Education, Inc.

22-4
 Program Design
• Determine user needs
• Create and document development plan
• Write the computer code
• Test the program
• Document the program
• Train users
• Install the system (including components and
hardware)
• Use and modify the system
Copyright © 2015 Pearson Education, Inc.
22-5
 Phase 4: Systems Implementation

• Implementation plan
• Select and train personnel
• Complete documentation
▫ Development documentation
▫ Operations documentation
▫ User documentation
• Testing the system
• Conversion

Copyright © 2015 Pearson Education, Inc.

22-6
 Testing the System

• Walk-throughs
▫ Step by step review
• Processing test data
▫ Test all valid transactions and error conditions
• Acceptance tests
▫ Use copies of real data

Copyright © 2015 Pearson Education, Inc.

22-7
 Conversion Approaches
• Direct conversion
▫ Terminates the old and begins with the new system
• Parallel conversion
▫ Operate old and new systems for a period of time
• Phase-in conversion
▫ Gradual replacement of old elements with new
system elements
• Pilot conversion
▫ Implement a system in a part of an organization
(e.g., a branch)
Copyright © 2015 Pearson Education, Inc.
22-8
 Phase 5: Operations and Maintenance

• Conduct post-implementation review

Copyright © 2015 Pearson Education, Inc.

22-9
 Key Terms
• Conceptual design
specifications
• Conceptual systems design
report
• Scheduled report
• Special-purpose analysis
report
• Triggered exception report
• Demand report
• Structured programming
• Debugging
• Program maintenance
• Physical systems design report
Copyright © 2015 Pearson Education, Inc.
• Systems implementation
• Implementation plan
• Walk-through
• Processing test data
• Acceptance test
• Conversion
• Direct conversion
• Parallel conversion
• Phase-in conversion
• Pilot conversion
• Post-implementation review
• Post-implementation review
report
22-10