Reading...
Play button
Play button
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;
25 Cards in this Set
- Front
- Back
|
Logical design
|
a description of the function requirements of a system. conceptualizes what the system will do to solve the problems and identified through earlier analysis
|
|
|
Physical design
|
the specification of the characteristics of the system components necessary to put the logical design into action
|
|
|
group consensus
|
a committee evaluates and chooses the best design and makes the final evaluation and selection
|
|
|
Cost/benefit analysis
|
lists costs and benefits on each system
-compare monetary costs to monetary benefits |
|
|
Benchmark tests
|
examination that compares computer systems operating under the same conditions
|
|
|
point evaluation
|
evaluation factor is assigned a weight and the system with the greatest total score is selected
-used to evaluate which software matches a company's business |
|
|
Usability testing
|
how systems supports the end user in their task
|
|
|
Hardware acquisition
|
get the hardware
|
|
|
software acquisition
|
make or buy software
|
|
|
user preparation
|
user training
|
|
|
Unit testing
|
testing of indv programs within the system
|
|
|
system 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 user
|
|
|
alpha testing
|
testing early or incomplete version (often with limited/fake data)
|
|
|
beta testing
|
testing real system with real users
|
|
|
Direct strategy for system implementation
|
stopping the old system and starting the new system on the given date. the lease desirable approach
|
|
|
Phase in approach strategy for system implementation
|
one part of the system at a time. slowly replacing components of the old system with those of the new system. preferred by many org.
|
|
|
Pilot startup strategy for system implementation
|
running the new system for one group of users rather than all users
|
|
|
Parallel strategy for system implementation
|
running both new and old systems for a period of time and comparing the outputs
|
|
|
Slipstream upgrade
|
minor upgrade to fix bug
|
|
|
Patch upgrade
|
a minor change to correct a problem or make small enchancement. usually an addition to an existing program
|
|
|
Release upgrade
|
a significant program chance that often required changes in the documentation of the software.
-Major enhancements to existing features. -ex: 1.2 to 1.3 |
|
|
Version upgrade
|
a major program chance, typically encompassing many new features
-ex: 1.0 to 2.0 |
