• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/40

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

40 Cards in this Set

  • Front
  • Back

Seven major activities ofSystemImplementation and Operation

›Coding


›Testing


›Installation


›Documentation


›Training


›Support


›Maintenance

Coding

›Physicaldesign specifications are turned into working computer code

Testing

›Testsare performed using various strategies›Testingcan be performed in parallel with coding

Installation

›Processduring which the current system is replaced by the new system

Two audiences for documentation

›The information systems personnel whowill maintain the system throughout its productive life


›The people who will use the system aspart of their daily lives

Deliverables



›Documentation


System documentation


User documentation


›User training plan


Classes


Tutorials


›User training modules


Training materials


Computer-based training aids


›User support plan


Help desk


On-line help


Bulletinboards and other support

Inspection

›A testing technique in which participantsexamine program code for predictable language-specific errors

Walkthrough

›A peer group review of any productcreated during the systems development process; also called a structured walkthrough

Desk Checking

›A testing technique in which the programcode is sequentially executed manually by the reviewer

UnitTesting

›Eachmodule is tested alone in an attempt to discover any errors in its code, alsocalled module testing

IntegrationTesting

›Theprocess of bringing together all of the modules that a program comprises fortesting purposes; modules are typically integrated in a top-down, incrementalfashion

SystemTesting

›Thebringing together of all the programs that a system comprises for testingpurposes; programs are typically integrated in a top-down, incremental fashion

StubTesting

›Atechnique used in testing, especially where modules are written and tested in atop-down fashion, where a few lines of code are used to substitute forsubordinate modules

Test Case

›A specific scenario of transactions,queries, or navigation paths that represent a typical, critical, or abnormaluse of the system

Alpha Testing

›User testing of a completed informationsystem using simulated data

›Recovery testing

Forces the software (or environment) tofail in order to verify that recovery is properly performed

›Security testing

Verifies that protection mechanisms builtinto the system will protect it from improper penetration

›Stress testing

Tries to break the system

>BetaTesting

›Usertesting of a completed information system using real data in the real userenvironment

›Direct Installation

Changing over from the old informationsystem to a new one by turning off the old system when the new one is turned on

›Parallel Installation

Running the old information system andthe new one at the same time until management decides the old system can beturned off

›Single location installation

Trying out an information system at onesite and using the experience to decide if and how the new system should bedeployed throughout the organization

›Phased Installation

Changing from the old information systemto the new one incrementally, starting with one or a few functional componentsand then gradually extending the installation to cover the whole new system

>SystemDocumentation

›Detailedinformation about a system’s design specifications, its internal workings, andits functionality

›Internaldocumentation

Systemdocumentation that is part of the program source code or is generated atcompile time

›Externaldocumentation

Systemdocumentation that includes the outcome of structured diagramming techniquessuch as data-flow and entity-relationship diagrams

>UserDocumentation

›Written, or other visual information,about an application system, how it works, and how to use it

PreparingUser Documentation

›Traditional source has been informationsystems department


›Application-oriented documentation is nowoften supplied by vendors and users themselves

PotentialTraining Topics

›Useof the system


›Generalcomputer concepts


›Informationsystem concepts


›Organizationalconcepts


›Systemmanagement


›Systeminstallation

TrainingMethods

›Resident expert


›Computer-aided instruction


›Formal courses


›Software help components


›Tutorials


›Interactive training manuals


›External sources, such as vendors

Electronicperformance support system (EPSS)

›Componentof a software package or application in which training and educationalinformation is embedded

Corrective maintenance

›Changes made to a system to repair flawsin its design, coding, or implementation

Adaptive maintenance

›Changes made to a system to evolve itsfunctionality to changing business needs or technologies

Perfective maintenance

›Changes made to a system to add newfeatures or to improve performance

Preventive maintenance

›Changes made to a system to avoidpossible future problems

MeanTime between Failures (MTBF)

›Ameasurement of error occurrences that can be tracked over time to indicate thequality of a system

ConfigurationManagement

The process of assuring that onlyauthorized changes are made to the system

Baseline Modules

›Software modules that have been tested,documented, and approved to be included in the most recently created version ofa system

System Librarian

›A person responsible for controlling thechecking out and checking in of baseline modules when a system is beingdeveloped or maintained

Build Routines

›Guidelines that list the instructions toconstruct an executable system from the baseline source code