Chapter 11 Flashcards
International Organization for Standardization (ISO)
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.
Application development
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.
Flowcharts
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.
Pseudocode
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.
attributes
which describe the characteristics of objects in the class. examples: Number, name, address
methods
which represent program logic. place order, modify order, pay invoice.
Coding
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
structured walkthrough
many organizations require a more formal type of desk checking called a structured walkthrough, or code review
Unit testing
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
test data
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.
stub testing
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.
test plan
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
integration testing
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.
system testing
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.
acceptance tests
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.