Chapter 11 Flashcards

1
Q

International Organization for Standardization (ISO)

A

ISO standards include everything from internationally recognized symbols. ISO seeks to offer global consensus of what constitutes good management practices that can help firms deliver consistently high-quality products and services-including software. because software is so important to a company’s success, many firms seek assurance that software systems, either purchased or developed in-house, will meet rigid quality standards. in 2014, ISO updated a set of guidelines, called ISO 900-3:2014, which provided a quality assurance framework for developing maintaining software.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Application development

A

the process of constructing the programs and code modules that serve as a building blocks of the information system. structured analysis, object-oriented, analysis, and agile methods are three popular development options. regardless of the method, the objective is to translate the design into program and code modules will function properly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Flowcharts

A

a flowchart represents logical rules and interaction graphically, using a series of symbols connected by arrows . Using flowcharts, programmers can break large systems into subsystems and modules that are easier to understand and code.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Pseudocode

A

a technique for representing program logic. pseudocode is similar to structured English. pseudocode is not language-specific, so it can be used to describe a software module in plain English without requiring strict syntax rules. Using a pseudocode, a systems analyst or a programmer can describe program actions that can be implemented in any programming language.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

attributes

A

which describe the characteristics of objects in the class. examples: Number, name, address

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

methods

A

which represent program logic. place order, modify order, pay invoice.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Coding

A

the process of turning program logic into specific instructions that the computer system can execute. Working from a specific design a programmer uses a programming language to transform program logic into code statements. An individual programmer might create a small program, while larger programs typically are divided into modules that several individuals or groups can work on simultaneously

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

structured walkthrough

A

many organizations require a more formal type of desk checking called a structured walkthrough, or code review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Unit testing

A

the testing of an individual program or module is called unit testing. the 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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

test data

A

contain both correct data and erroneous data and should test all possible situations that occur.. for example, for a field that allows a range of numeric values, the test data should contain minimum values, maximum values, values outside the acceptable range, and alphanumeric characters. During testing, programmers can use software tools to determine the location and potential causes of program errors.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

stub testing

A

the programmer simulates each program outcome or result and displays a message to indicate whether or not the program executed successfully. each stub represents an entry or exit point that will be linked later to another program or data file.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

test plan

A

consists of detailed procedures that specify how and when the testing will be performed, who will participate, and what test data will be used. A comprehensive test plan should include scenarios for every possible situation the program could encounter

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

integration testing

A

testing two or more programs that depend on each other is called integration testing. For example, consider an information system with a program that checks and validates customer credit status, and a separate program that updates data in the customer master file.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

system testing

A

which involves the entire information system. a system test includes all likely processing situations and is intended to assure users, developers, and managers that the program meets all specifications and that all necessary features have been included.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

acceptance tests

A

successful completion of system testing is the key to user and management approval, which is why system tests sometimes are called acceptance tests. final acceptance tests, however, are performed during systems installation and evaluation with actual user data.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

documentation

A

describes an information system and helps the users, managers, and IT staff who must interact with it. documentation is essential for successful system operation and maintenance. in addition to supporting a system’s user, accurate documentation is essential for IT staff members who must modify the system, add a new feature, or perform maintenance documentation includes program, system, operations and user documentation.

17
Q

program documentation

A

describes the inputs, outputs, and processing logic for all program modules. the program documentation process starts in the systems analysis phase and continues during systems implementation. This documentation guides programmer, who construct modules that are well supported by internal and external comments and descriptions that can be understood and maintained easily. A systems analyst usually verifies that program documentation is complete and accurate.

18
Q

System documentation

A

describes the system’s functions and how they are implemented. system documentation includes data dictionary entries, data flow diagrams, object models, screen layouts, source documents, and the system request, that initiated the project. System documentation is necessary reference material for the programmers and analysts who must support and maintain the system.

19
Q

operations documentation

A

contains all the information needed for processing and distributing online and printed output. Typical documentation includes the following information.
operation documentation should be clear, concise and available online if possible, If the It department has an operations group, the documentation should be reviewed with them, early and often, to identify any problems.

20
Q

user documentation

A

consists of instructions and information to users who will interact with the system and includes user manuals, help screens, and online tutorials. programmers or systems analysts usually create program documentation and system documentation.

21
Q

online documentation

A

which provides immediate help when they have questions or encounter problems. Many users are accustomed to context sensitive help screens, hints, and tips, hypertext, on-screen demos, and other user-friendly features commonly found in popular software packages.

22
Q

operational environment

A

recall that an environment or platform, is a specific combination of hardware and software configurations, system utilities, and communications resources. the environment for the actual system operation is called the operational environment.

23
Q

test environment

A

the environment that analysts and programmers use to develop and maintain programs. A separate test environment is necessary to maintain system security and integrity and protect the operational environment.

24
Q

training plan

A

be considered early in the systems development process. A documentation is created, consider how to use the material in future training sessions. when the system is implemented, it is essential to provide the right training for the right people at the right time. the first step is to identify who should receive training and what training is needed.

the main groups for training are users, managers, and IT staff.

25
Q

data conversion

A

an important part of the system installation process, during data conversion, existing data is loaded into the new system. depending on the system, data conversion can be done before, during, or after the operational environment is complete. a data conversion plan should be developed as early as possible, and the conversion process should be tested when the test environment is developed

26
Q

system changeover

A

the process of putting 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, and phased operation.

27
Q

direct cutover

A

the approach causes the changeover from the old system to the new system to occur immediately when the new system becomes operational. direct cutover usually is the least expensive changeover methods because the IT group has to operate and maintain only one system at a time.
direct cutover, involves more risk than other changeover methods. regardless of how thoroughly and carefully testing and training is conducted.

28
Q

parallel operation

A

the changeover method requires that both the old and the new information systems operate fully for a specified period. Data is input into both systems, and output generated by the new system is compared with the equivalent output from the new system. when users, management, and the IT group are satisfied that the new system operates correctly, the old system is terminated.

29
Q

pilot operation

A

the changeover method involved implementing the complete new system at a selected location of the company. A new sales reporting system, for instance, might be implemented in only one branch office, or a new payroll system might be installed in only one department.

30
Q

phased operation

A

the changeover method allows the new system to be implemented in stages, or modules. for example, instead of implementing a new manufacturing system all at once the materials management subsystem is installed first, then the production control subsystem, then the job cost subsystem, and so on. each subsystem can be implemented by using any of the other three changeover methods.

31
Q

logic errors

A

produce incorrect results