Systems Analysis and Design | Chapter 11

bug tracking software

System developers use defect tracking software, sometimes called bug tracking software, to document and track program defects, code changes, and replacement code, called patches.

defect tracking software

System developers use defect tracking software, sometimes called bug tracking software, to document and track program defects, code changes, and replacement code, called patches.

operations documentation

Contains all the information needed for processing and distributing online and printed output.

structure chart

During application development, what can be used to show the program modules and the relationships among them, and consists of rectangles that represent the program modules?

data conversion

Existing data is loaded into the new system, transformed as needed. Depending on the system, data conversion can be done before, during, or after the operational environment is complete.

user story

In agile development, a short, simple requirements definition provided by the customer. Programmers use user stories to determine a project's requirements, priorities, and scope.

status flag

In structured application development, an indicator that allows one module to send a message to another module.

user documentation

Instructions and information to users who will interact with the system. Includes user manuals, help screens, and tutorials.

code review

Many organization identify a peer group that will be used to identify errors, apply quality standards, and verify that the program meets the requirements of the system design specification. What is this process known as?

documentation

Material that explains a system, helps people interact with it, and includes program documentation, system documentation, operations documentation, and user documentation.

coupling

Measures relationships and interdependence among modules. The opposite of cohesion.

logic error

Mistakes in the underlying logic that produce incorrect results.

loosely coupled

Modules that are relatively independent. Loosely coupled modules are easier to maintain and modify, because the logic in one module does not affect other modules.

phased operation

The phased operation method allows a new system to be implemented in stages, or modules.

pilot operation

The pilot operation changeover method involves implementing the complete new system at a selected location of the company.

application development

The process of constructing the programs and code modules that are the building blocks of an information system. Application development is handled by an application development group within a traditional IT department that is composed of systems analysts and programmers who handle information system design, development, and implementation.

system changeover

The process of putting the new information system online and retiring the old system. Changeover can be rapid or slow, depending on the method.

desk checking

The process of reviewing the program code to spot logic errors, which produce incorrect results.

object-oriented development (OOD)

The process of translating an object model directly into an object-oriented programming language.

coding

The process of turning program logic into specific instructions that a computer system can execute.

unit testing

The testing of an individual program or module. 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.

integration testing

The testing two or more programs that depend on each other.

direct cutover

Which changeover method is usually considered the least expensive changeover method because the IT group has to operate and maintain only one system at a time?

agile development

Which systems development method focuses on small teams, intense communication, and rapid development iterations?

application development

process of constructing the programs and code modules that serve as building blocks of the information system

review all data flow diagrams for accuracy and completeness

the first step that should be followed when creating a structure chart

system testing

users enter data, perform queries, and produce reports to simulate actual operating conditions

simulation

A dress rehearsal for users and IT support staff. Organizations typically include all procedures, such as those that they execute only at the end of a month, quarter, or year, in their simulations.

system documentation

A description of a system's functions and how they are implemented. The analyst prepares most of the system documentation during the systems analysis and systems design phases. System documentation includes data dictionary entries, data flow diagrams, object models, screen layouts, source documents, and the systems request that initiated the project.

top-down approach

A design approach, also called modular design, where the systems analyst defines the overall objectives of the system, and then breaks them down into subsystems and modules. This breaking-down process also is called partitioning.

flowchart

A diagram used to describe program logic that represents logical rules and interaction graphically using a series of symbols connected by arrows. Flowcharts can be useful in visualizing modular program designs.

system testing

A form of testing involving an entire information system and includes all typical processing situations. During a system test, users enter data, including samples of actual, or live data, perform queries, and produce reports to simulate actual operating conditions. All processing options and outputs are verified by users and the IT project development team to ensure that the system functions correctly.

stub testing

A form of testing where 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.

subordinate module

A lower-level module in a structure chart.

cohesion

A measure of 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.

Capability Maturity Model (CMM)

A model developed by SEI that integrates software and systems development into a process improvement framework.

test plan

A plan designed by a systems analyst that includes test steps and test data for integration testing and system testing.

pair programming

A practice in Extreme Programming in which two programmers work on the same task on the same computer; one drives (programs) while the other navigates (watches).

quality assurance (QA)

A process or procedure for minimizing errors and ensuring quality in products. Poor quality can result from inaccurate requirements, design problems, coding errors, faulty documentation, and ineffective testing. A quality assurance (QA) team reviews and tests all applications and systems changes to verify specifications and software quality standards.

tutorial

A series of online interactive lessons that present material and provide a dialog with users.

design walkthrough

A session with users to review the interface with a cross-section of people who will work with the new system. This is a continuation of the modeling and prototyping effort that began early in the systems development process.

ISO 9000-3:2014

A set of guidelines established and updated by the International Organization for Standardization (ISO) to provide a quality assurance framework for developing and maintaining software.

software engineering

A software development process that stresses solid design, effective structure, accurate documentation, and careful testing.

condition

A specified action or state in a structure chart. A line with a diamond on one end represents which of the following in a structure chart

train-the-trainer

A strategy where one group of users has been trained and can assist others. Users often learn more quickly from coworkers who share common experience and job responsibilities.

training plan

A successful information system requires training for users, managers, and IT staff members. The entire systems development effort can depend on whether or not people understand the system and know how to use it effectively. The training plan is a document that details these requirements.

integrated development environment (IDE)

A suite of integrated tools to make it easier to plan, construct, and maintain a specific software product. An IDE is designed to allow the easy integration of system components with less time being spent on developing code for interactive modules.

test-driven development (TDD)

An Extreme Programming (XP) concept that unit tests are designed before code is written, focusing on end results and preventing programmers from straying from their goals.

webinar

An Internet-based training session that provides an interactive experience. The word "webinar" combines the words "web" and "seminar."

iteration cycle

An agile development cycle that includes planning, designing, coding, and testing one or more features based on user stories. 1

post-implementation evaluation

An assessment of the overall quality of the information system. The evaluation verifies that the new system meets specified requirements, complies with user objectives, and achieves the anticipated benefits. In addition, by providing feedback to the development team, the evaluation also helps improve IT development practices for future projects.

tightly coupled

If modules are tightly coupled, one module refers to internal logic contained in another module.

methods

In a class diagram, methods represent program logic.

pilot site

In a pilot operation, the group that uses the new system first is called the pilot site.

control couple

In a structure chart, a control couple shows a message, also called a flag, which one module sends to another. An arrow with a filled circle represents a control couple

control module

In a structure chart, a control module is a higher-level module that directs lower-level modules, called subordinate modules.

data couple

In a structure chart, a data couple shows data that one module passes to another. An arrow with an empty circle represents a data couple

library module

In a structure chart, a library module is a module that is reusable and can be invoked from more than one point in the chart.

loop

In a structure chart, a loop indicates that one or more modules are repeated. A curved arrow represents a loop.

iteration planning meeting

In agile development, a meeting held at the beginning of each iteration cycle to break down user stories into specific tasks that are assigned to team members.

release plan

In agile development, a plan that specifies when user stories will be implemented and the timing of the releases. Releases are relatively frequent, and each release is treated as a system prototype that can be tested and modified as needed.

program documentation

Preparation of program documentation 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. Programmers provide documentation by constructing modules that are well supported by internal and external comments and descriptions that can be understood and maintained easily.

customer

Primary user of a system, service, or product.

syntax error

Programming language grammar error.

online documentation

Provides immediate help when users have questions or encounter problems.

patch

Replacement code that is applied to fix bugs or security holes in software.

acceptance test

Testing involves the entire information system, including all typical processing situations. During an acceptance test, users enter data, including samples of actual, or live data, perform queries, and produce reports to simulate actual operating conditions. All processing options and outputs are verified by users and the IT project development team to ensure that the system functions correctly. Sometimes known as a system test.

test data

The data used in unit testing. Test data should contain both correct data and erroneous data and should test all possible situations that could occur.

direct cutover

The direct cutover approach causes the changeover from the old system to the new system to occur immediately when the new system becomes operational.

production environment

The environment for the actual system operation. It includes hardware and software configurations, system utilities, and communications resources. Also called the operational environment.

operational environment

The environment for the actual system operation. It includes hardware and software configurations, system utilities, and communications resources. Also called the production environment.

test environment

The environment that analysts and programmers use to develop and maintain programs.

process improvement

The framework used to integrate software and systems development by a new SEI model, Capability Maturity Model Integration (CMMI).

parallel operation

The parallel operation 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 old system.