Chapter 24 – Systems Design, Implementation, and Operation

Vocabulary flashcards cover key terms and definitions from Chapter 24, spanning conceptual design, physical design, implementation, conversion, and maintenance phases of the SDLC.

Initial SDLC phase that creates a general framework for meeting user requirements and solving problems identified during analysis.

Conceptual Systems Design

Step that compares possible system designs against objectives, user needs, economic feasibility, and pros vs. cons.

Evaluate Design Alternatives

Detailed requirements for outputs, data storage, inputs, processing procedures, and operations once a design is chosen.

Design Specifications

Document summarizing conceptual design activities and recommended system design(s) for steering-committee review.

Conceptual Systems Design Report

Group that evaluates design alternatives and selects the option that best fits organizational needs.

Steering Committee

Phase that translates broad conceptual requirements into detailed specifications used to code and test programs.

Physical Systems Design

Process of determining the nature, format, content, and timing of reports, documents, and screen displays.

Output Design

Output with prespecified content and format prepared on a regular timetable (e.g., monthly performance report).

Scheduled Report

Ad-hoc output without prespecified content or schedule, created in response to a specific management request.

Special-Purpose Analysis Report

Output with preset content produced only when abnormal conditions occur (e.g., inventory shortages).

Triggered Exception Report

Preset report generated only upon user request.

Demand Report

Activity that determines how and in what format data will be stored across the organization.

File and Database Design

Specification of data to be captured and the most efficient method for entering it into the system.

Input Design

Creation of paper or electronic documents used to capture source data.

Form Design

Layout of on-screen forms so data can be entered quickly, accurately, and with minimal errors.

Computer Screen Design

Technique that divides programs into small, well-defined modules, each with a single entry and exit point.

Structured Programming

Process of locating and removing program errors during testing.

Debugging

Flowcharts, diagrams, and narratives explaining how a program works and aiding maintenance.

Program Documentation

Modifying existing programs due to new requirements, detected errors, or hardware changes.

Program Maintenance

Instructions answering who, what, when, where, why, and how for all information-system activities.

Procedures (AIS)

Embedding measures in an AIS to minimize, detect, and correct errors, ensuring reliable information.

Controls Design

Implementation Plan

Schedule listing tasks, deadlines, costs, and responsible parties for installing the new AIS.

Physical modifications (e.g., power, air-conditioning, raised floors) required before hardware installation.

Site Preparation

Hiring or transferring employees and teaching them hardware, software, and new procedures.

Selecting and Training Personnel

Materials describing the new AIS, including system description, layouts, flowcharts, and test results.

Development Documentation

Guidelines for running the system—schedules, files accessed, security, and retention requirements.

Operations Documentation

Manuals and training materials that instruct end users how to operate the AIS.

User Documentation

Walk-Through

Step-by-step review of procedures or program logic to find errors early in design.

Using simulated valid and invalid transactions to verify a program operates as intended.

Processing Test Data

Final evaluation using real transactions; users determine if the AIS meets their criteria.

Acceptance Test

Switching from old to new system at once, with no parallel backup.

Direct Conversion

Running old and new systems simultaneously until the new one is proven reliable.

Parallel Conversion

Gradually replacing parts of the old system with the new until full changeover is complete.

Phase-In Conversion

Implementing the new system at one location, resolving issues, then rolling it out organization-wide.

Pilot Conversion

Moving, reformatting, and cleaning data files so they work with the new AIS.

Data Conversion

Evaluation conducted after installation to verify the system meets objectives and stays within budget.

Post-Implementation Review

Document analyzing whether a newly delivered system achieved its intended purpose; final user acceptance closes the SDLC.

Post-Implementation Review Report