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;
65 Cards in this Set
- Front
- Back
systems design
|
the stage of systems development that answers the question "how will the information system solve a problem?"
|
|
logical design
|
a description of the functional requirements of a system
|
|
physical design
|
the specifications of the characteristics of the system components necessary to put the logical design into action
|
|
sign-on procedure
|
identification numbers, passwords, and other safeguards needed for someone to gain access to computer resources
|
|
menu-driven system
|
a system in which users simply pick what they want to do from a list of alternatives
|
|
help facility
|
a program that provides assistance when users want to know more about a program or feature or what type of response is expected
|
|
look up tables
|
tables containing data that computer programs can develop and use to simplify and shorten data entry
|
|
restart procedures
|
simplified processes to access an application from where it stopped
|
|
disaster recovery
|
the implementation of the disaster plan
|
|
hot site
|
a duplicate, operational hardware system or immediate access to one through a specialized vendor
|
|
cold site
|
a computer environment that includes rooms, electrical service, telecommunications links, data storage devices, and the like; also called a shell
|
|
incremental backup
|
making a backup copy of all files changed during the last few days or the last week
|
|
image log
|
a separate file that contains only changes to applications
|
|
systems control
|
rules and procedures to maintain data security
|
|
closed shops
|
IS departments in which only authorized operators can run the computers
|
|
open shops
|
IS departments in which people, such as programmers and systems analysts, are allowed to run the computers, in addition to authorized operators
|
|
deterrence controls
|
rules and procedures to prevent problems before they occur
|
|
request for proposal
|
a document that specifies in detail required resources such as hardware and software
|
|
preliminary evaluation
|
an initial assessment whose purpose is to dismiss the unwanted proposals; begins after all proposals have been submitted
|
|
final evaluation
|
a detailed investigation of the proposals offered by the vendors remaining after the preliminary evaluation
|
|
group consensus
|
decision making by a group that is appointed and given the responsibility of making the final evaluation and selection
|
|
cost/benefit analysis
|
an approach that lists the costs and benefits of each proposed system. After they are expressed in monetary terms, all the costs are compared with all the benefits
|
|
benchmark test
|
an examination that compares computer systems operating under the same conditions
|
|
point evaluation system
|
an evaluation process in which each evaluation factor is assigned a weight, in percentage points, based on importance
|
|
design report
|
the primary result of systems design, reflecting the decisions made and preparing the way for systems implementation
|
|
systems implementation
|
a stage of systems development that includes hardware acquisition, software acquisition or development, user preparation, hiring and training of personnel, site and data preparation, installation, testing, start-up, and user acceptance
|
|
make-or-buy decision
|
the decision regarding whether to obtain the necessary software from internal or external sources
|
|
chief programmer team
|
a group of skilled IS professionals who design and implement a set of programs
|
|
sequence structure
|
a programming structure in which, after starting the sequence, programming statements are executed one after another until all the statements in the sequence have been executed
|
|
decision structure
|
a programming structure that allows the computer to branch, depending on certain conditions
|
|
loop structure
|
a programming structure that allows the program to cycle or loop a certain number of times
|
|
cross-platform development
|
a development technique that allows programmers to develop programs that can run on computer systems having different hardware and operating systems, or platforms
|
|
integrated development environment
|
a development approach that combines the tools needed for programing with a programming language into one integrated package
|
|
structured walk through
|
a planned and pre announced review of the progress of a program module
|
|
technical documentation
|
written details used by computer operators to execute the program and by analysts and programmers to solve problems or modify the program
|
|
user documentation
|
written descriptions developed for people who use a program, showing users, in easy-to-understand terms, how the program can and should be used
|
|
user preparation
|
the process of readying managers, decision makers, employees, other users, and stakeholders for new system
|
|
site preparation
|
preparation of the location of a new system
|
|
data preparation, or data conversion
|
ensuring all files and databases are ready to be used with new computer software and systems
|
|
installation
|
the process of physically placing the computer equipment on the site and making it operational
|
|
unit testing
|
testing of individual programs
|
|
systems testing
|
testing the entire system of programs
|
|
volume testing
|
testing the application with a large amount of data
|
|
integration testing
|
testing all related systems together
|
|
acceptance testing
|
conducting any tests required by the user
|
|
alpha testing
|
testing an incomplete or early version of the system
|
|
beta testing
|
testing a complete and stable system by end users
|
|
start-up
|
the process of making the final tested information system fully operational
|
|
direct conversion
|
stopping the old system and starting the new system on a given date
|
|
phase-in approach
|
slowly replacing components of the old system with those of the new one. This process is repeated for each application until the new system is running every application and performing as expected
|
|
pilot start-up
|
running the new systems for one group of users rather than all users
|
|
parallel start-up
|
running both the old and new systems for a period of time and comparing the output of the new system closely with the output of the old system
|
|
user acceptance document
|
a formal agreement signed by the user that states that a phase of the installation or the complete system is approved
|
|
systems operation
|
use of a new or modified system
|
|
systems maintenance
|
a stage of systems development that involves checking, changing, and enhancing the system to make it more useful in achieving user and organizational goals
|
|
slipstream upgrade
|
a minor upgrade-typically a code adjustment or minor bug fix, not worth mentioning
|
|
patch
|
a minor change to correct a problem or make a small enhancement. It is usually an addition to an existing program
|
|
release
|
a significant program change that often requires changes in the documentation of the software
|
|
version
|
a major program change, typically encompassing many new features
|
|
request for maintenance form
|
a form authorizing modification of programs
|
|
systems review
|
the final step of systems development, involving the analysis of systems to make sure that they are operating as intended
|
|
event-driven review
|
a review triggered by a problem or opportunity such as an error, or corporate merger, or a new market for products
|
|
time-driven review
|
review performed after a specified amount of time
|
|
system performance measurement
|
monitoring the system- the number of errors encountered, the amount of memory required, the amount of processing or CPU time needed, and other problems
|
|
system performance products
|
software that measures all components of the computer-based information system, including hardware, software, database, telecommunications, and network systems
|