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;
32 Cards in this Set
- Front
- Back
|
What does managing systems implementation involve? |
• Application development • Testing • Documentation • Training • Data conversion • System changeover • Post-implementation review |
|
|
What is the main objective of quality assurance? |
To avoid problems or to identify them as soon as possible. |
|
|
Where does QA happen? |
During the entire system development life cycle. |
|
|
Where does Software QC happen? |
During the construction and testing phase. |
|
|
What is application construction? |
It is the process of constructing the programs and code modules that serve as the building blocks of the information system. The objective is to translate the design into program and code modules that will function properly |
|
|
What is cohesion? |
Cohesion measures a module’s scope and processing characteristics • A module that performs a single function or task has a high degree of cohesion, which is desirable because it focuses on a single task and is much easier to code and reuse |
|
|
What is coupling? |
• Coupling describes the degree of interdependence among modules • Modules that are independent are loosely coupled, which is desirable • Loosely coupled modules are easier to maintain and modify, because the logic in one module does not affect other modules • Tightly coupled modules have one module linked to internal logic contained in another module |
|
|
What is unit testing? |
The testing of an individual program or module • Test data should contain both correct data and erroneous data and should test all possible situations that could occur • Programs that interact with other programs and files are tested individually, before they are integrated into the system • Objective is to identify and eliminate execution errors that could cause the program to terminate abnormally, and logic errors that could have been missed during desk checking |
|
|
What is Integration Testing? |
• Testing two or more programs that depend on each other to make sure that the programs work together properly |
|
|
What is involved in system testing?
|
• Perform a final test of all programs • Verify that the system will handle valid and invalid data properly • Ensure that the IT staff has the documentation and instructions needed to operate the system properly and that backup and restart capabilities of the system are adequate Demonstrate that users can interact with the system successfully • Verify that all system components are integrated properly and that actual processing situations will be handled correctly • Confirm that the information system can handle predicted volumes of data in a timely and efficient manner |
|
|
What is a systems acceptance test |
A test performed on the final system wherein users conduct a verification, validation, and audit test. ◦ Uses real data over an extended time period ◦ Extensive test that addresses: verification testing, validation testing, and audit testing. |
|
|
What is verification testing? |
Runs the system in a simulated environment using simulated data. ◦ Alpha testing ◦ Simulated environment using simulated data ◦ Checks for errors and omissions regarding end-use and design specifications |
|
|
What is validation testing? |
Runs the system in a live environment using real data. ◦ Beta testing ◦ Live environment using real data ◦ Testing: Systems performance (throughput and response time) Peak workload performance Human engineering Methods and procedures Backup and recovery |
|
|
What is audit testing? |
Certifies that the system is free of errors and is ready to be placed into operation. |
|
|
What is program documentation? |
• Program documentation describes the inputs, outputs, and processing logic for all program modules • Process starts in the systems analysis phase and continues during systems implementation • Systems analysts prepare overall documentation, such as process descriptions and report layouts, early in the SDLC • This documentation guides programmers, who construct modules that are well supported by internal and external comments and descriptions that can be understood and maintained easily |
|
|
What is system documentation? |
• Describes the system’s functions and how they are implemented • Includes data dictionary entries, data flow diagrams, object models, screen layouts, source documents, and the systems request that initiated the project |
|
|
What is operation documentation? |
Operations documentation contains all the information needed for processing and distributing online and printed output |
|
|
What is user documentation? |
Consists of instructions and information to users who will interact with the system and includes user manuals, Help screens, and tutorials |
|
|
Describe data conversion strategies. |
• When a new system replaces an existing system, you should automate the data conversion process • The old system might be capable of exporting data in an acceptable format for the new system • ODBC. ODBC (Open Database Connectivity) is an industry-standard protocol that allows DBMSs from various vendors to interact and exchange data • Middleware connects dissimilar applications and enables them to communicate |
|
|
Describe data conversion security and controls |
• Maintain strict input controls during the conversion process • Ensure that all system control measures are in place and operational to protect data from unauthorized access and to help prevent erroneous input |
|
|
Describe system changeover. |
System changeover is the process of putting the new information system online and retiring the old system Changeover can be rapid or slow, depending on the method The four changeover methods are: ◦ Direct cutover ◦ Parallel operation ◦ Pilot operation ◦ Phased operation |
|
|
Describe Direct Cutover? |
◦ Causes the changeover from the old system to the new system to occur immediately when the new system becomes operational ◦ Usually is the least expensive changeover method because the IT group has to operate and maintain only one system at a time |
|
|
Describe Parallel Operation. |
◦ Requires that both the old and the new information systems operate fully for a specified period ◦ Obvious advantage of parallel operation is lower risk ◦ Company can use the old system as a backup ◦ Most costly changeover method |
|
|
Describe Pilot Operation. |
◦ Implementing the complete new system at a selected location of the company ◦ The old system continues to operate for the entire organization, including the pilot site ◦ Restricting the implementation to a pilot site reduces the risk of system failure ◦ Less expensive than a parallel operation for the entire company |
|
|
Describe Phased Operation. |
◦ Implement the new system in stages, or modules ◦ Combines direct cutover and parallel operation to reduce risks and costs ◦ Give a part of the system to all users, while pilot operation ◦ Risk of errors or failures is limited to the implemented module only ◦ Less expensive than full parallel operation because you have to work with only one part of the system at a time |
|
|
Describe Post-Implementation Evaluation. |
◦ A post-implementation evaluation assesses the overall quality of the information system Accuracy, completeness, and timeliness of information system outputUser satisfaction System reliability and maintainability Adequacy of system controls and security measures Hardware efficiency and platform performance Effectiveness of database implementation Performance of the IT team Completeness and quality of documentation Quality and effectiveness of training Accuracy of cost-benefit estimates and development schedules When evaluating a system, you should: ◦ Interview members of management and key users ◦ Observe users and computer operations personnel actually working with the new information system ◦ Read all documentation and training materials ◦ Examine all source documents, output reports, and screen displays ◦ Use questionnaires to gather information and opinions from a large number of users ◦ Analyze maintenance and help desk logs |
|
|
List the main tasks that are performed during systems implementation. |
· Application Development · Testing · Installation · Evaluation |
|
|
Describe Application Development. |
o Determine the overall design strategy and work withprogrammers to complete design, coding, testing and documentation. |
|
|
Describe Testing |
o Quality assurance testing o Desk checking, code review, and unit testing o Integration testing o Systems testing |
|
|
Describe Installation |
o Establish an operational, or production, environment forthe new information system that is completely separate from the testenvironment. o Contains live data and is accessible only by authorizedusers. o Data conversion o Training users o System changeover |
|
|
Describe evaluation. |
o A post-implementation evaluation assesses and reports onthe quality of the new system and the work done by the project team. o The final report to management includes the final systemdocumentation, describes any future system enhancements that already have beenidentified, and details the project costs. |
|
|
Whatis the difference between an operational environment and a test environment? |
The operational environment is the environment where theactual system is operating, using live data.The test environment is the environment that analysts and programmersuse to develop and maintain programs. |
