Purdue CNIT 180 Final Exam

Pataasin ang iyong marka sa homework at exams ngayon gamit ang Quizwiz!

Change Control (CC)

A process for controlling changes in system requirements during software development; also an important tool for managing system changes and costs after a system becomes operational.

System Requirement

A characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users.

Information System

A combination of information technology, people, and data to support business requirements. The five key components are hardware, software, data, processes, and people.

Data Structure

A meaningful combination of related data elements that is included in a data flow or retained in a data store. A framework for organizing and storing data.

Security Policy

A plan that addresses the three main elements of system security: confidentiality, integrity, and availability.

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.

Code

A set of letters or numbers that represents a data item. Codes can be used to simplify output, input, and data formats.

Structure Chart

A top-down representation of business functions and processes. Also called an FDD.

Pretexting

Obtaining personal information under false pretenses.

Limit Check

Occurs when a validation check involves a minimum or a maximum value, but not both. Checking that a payment amount is greater than zero, but not specifying a maximum value, is an example of a limit check.

Iteration

The completion of a process step that is repeated until a specific condition changes.

Character-Based Report

A report created using a single mono-spaced character set.

Data Warehouse

An integrated collection of data that can support management analysis and decision making.

Social Engineering

An intruder uses social interaction to gain access to a computer system.

Four-Model Approach

A physical model of the current system, a logical model of the current system, a logical model of the new system, and a physical model of the new system are all developed.

Physical Design

A plan for the actual implementation of the system.

Asset

Hardware, software, data, networks, people, or procedures that provide tangible or intangible benefit to an organization.

Software

A program run by computers for a specific function or task.

System

A set of related components that produces specific results.

Information Technology (IT)

A combination of hardware, software, and telecommunications systems that support business operations, improve productivity, and help managers make decisions.

802.11

A family of wireless network specifications developed by the IEEE.

Node

A physical device, wired or wireless, that can send, receive, or manage network data.

Public Key Encryption (PKE)

A common encryption technique. Each user on the network has a pair of keys: a public key and a private key. The public key encrypts data that can be decrypted with the private key.

Foreign Key

A field in one table that must match a primary key value in another table in order to establish the relationship between the two tables.

Wireless Local Area Network (WLAN)

A wireless network that is relatively inexpensive to install and is well-suited to workgroups and users who are not anchored to a specific desk or location.

Multiple Input/Multiple Output (MIMO)

A wireless networking technology incorporated in the IEEE 802.11n and 802.11ac standards that uses multiple data streams and multiple antennas to achieve higher transmission speeds and substantially increase wireless range over earlier standards.

WPA2

A wireless security standard based on 802.11i that provides a significant increase in protection over WEP and WPA.

Request for Proposal (RFP)

A written list of features and specifications given to prospective vendors before a specific product or package has been selected.

Identify Management

Controls and procedures necessary to identify legitimate users and system components.

Agile Methods

systems development methods that attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements. Related to adaptive methods.

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.

Identify Theft

The stealing of personally identifying information online.

Archived

The storage of previous version of a system when a new version is installed.

Requirements Engineering

Used in the systems planning phase of the SDLC. It involves using various fact-finding techniques, such as interviews, surveys, observation, and sampling, to describe the current system and identify the requirements for the new system.

Design Review

See structured walk-through.

Testing Review

See structured walk-through.

Malware

Malicious software that might jeopardize the system's security or privacy.

Sequence Diagram

A diagram that shows the timing of transactions between objects as they occur.

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.

Software License

A legal agreement that gives users the right to use the software under certain terms and conditions.

Tangible Costs

Expenses that have a specific dollar value. Examples include employee salaries and hardware purchases.

Credentials

Formal qualifications that include degrees, diplomas, or certificates granted by learning institutions to show that a certain level of education has been achieved.

Requirements Elicitation

The process of gathering requirements. See fact-finding.

Fact-Finding

The process of gathering requirements. See requirements elucidation.

Strategic Planning

The process of identifying long-term organizational goals, strategies, and resource.

Risk Management

The process of identifying, evaluating, tracking, and controlling risks to minimize their impact.

Project Management

The process of planning, scheduling, monitoring, controlling, and reporting upon the development of an information system.

System Chageover

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

Recovery

The process of restoring data and restarting a system after an interruption.

Desk Checking

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

Perfective Maintenance

Changes to a system to improve efficiency.

Corrective Maintenance

Changes to the system to fix errors.

Private Network

A dedicated connection, similar to a leased telephone line.

Risk

An event that could affect the project negatively.

Work-Case Estimate

The most pessimistic outcome.

Full Backup

A complete backup of every file on the system.

Bit

The smallest unit of data is one binary bit.

Gateway

(1) In business processing modeling notation, a fork in the process, allowing the flow to go one way or another. (2) A router or other network device used to connect to a larger, dissimilar type of network, such as the Internet.

B2B (business-to-business)

A commercial exchange (e.g., products or services) between businesses, typically enabled by the Internet or electronic means.

Toolbar

A GUI element that contains icons or buttons that represent shortcuts for executing common commands.

Toggle Button

A GUI element used to represent on or off status. Clicking the toggle button switches to the other status.

Network Diagram

A PERT chart also is referred to as a network diagram.

Sequence Diagram

A UML diagram that shows the timing of transactions between objects as they occur during system execution.

Task Name

A brief descriptive name for a task, which does not have to be unique in the project. For example, a task named Conduct Interviews might appear in several phases of the project.

Empowerment

A business practice that places more responsibility and accountability throughout all levels of an organization.

Calendar Control

A calendar control allows the user to select a date that the system will display and store as a field value.

Tamper-Evident Case

A case designed to show any attempt to open or unlock the case.

Data Processing Center

A central location where physical data was delivered or transmitted in some manner and entered into the system. Users in the organization had no input or output capability, except for printed reports that were distributed by a corporate IT department.

Task Box

A component of a PERT/CPM chart that contains important scheduling and duration information about a task. Each task in a project is represented by its own task box in the PERT/CPM chart.

Online Data Entry

A data entry method used for most business activity. The online method offers major advantages, including the immediate validation and availability of data.

Diverging Data Flow

A data flow in which the same data travels to two or more different locations.

Relational Database

A database in which tables are related by common fields, creating a unified data structure that provides improved data quality and access.

Requirements Specification

A description of the system requirements from the analyst or engineering team's point of view.

Secondary Key

A field or combination of fields that can be used to access or retrieve records. Secondary key values are not unique. For example, to access records for only those customers in a specific postal code, the postal code field could be used as a secondary key.

Primary Key

A field or combination of fields that uniquely and minimally identifies a particular member of an entity. For example, in a customer table the customer number is a unique primary key because no two customers can have the same customer number. That key also is minimal because it contains no information beyond what is needed to identify the customer.

File-Oriented System

A file-oriented system, also called a file processing system, stores and manages data in one or more separate files.

Benchmark Testing

A form of testing used by companies to measure system performance.

Binary Storage Format

A format that offers efficient storage of numeric data. For example, when numeric data types are specified using Microsoft Access, there are a variety of storage formats choices, including integer and long integer, among others.

Subclass

A further division of objects in a class. Subclasses are more specific categories within a class.

Batch

A group of data, usually inputted into an information system at the same time.

Query by Example (QBE)

A language allows the user to provide an example of the data requested.

Data Center

A large concentration of networked computers working together.

Logical Record

A logical record contains field values that describe a single person, place, thing, or event. Application programs see a logical record as a set of fields, regardless of how or where the data is stored physically.

Superuser Account

A login account that allows essentially unrestricted access to the application.

Unicode

A relatively recent coding method that represents characters as integers. Unlike EBCDIC and ASCII, which use eight bits for each character, Unicode requires 16 bits per character, which allows it to represent more than 65,000 unique characters.

Pseudocode

A technique for representing program logic in semi-structured prose.

Wiki

A web-based repository of information that anyone can access, contribute to, or modify.

Switch

Central networking device in a star network, which manages the network and acts as a conduit for all network traffic.

Systems Development Life Cycle (SDLC)

Activities and functions that systems developers typically perform, regardless of how those activities and functions fit into a particular methodology. The SDLC model includes five phases: (1) Systems planning, (2)Systems analysis, (3) Systems design, (4) Systems implementation, and (5) Systems support and security.

Application Lifecycle Management (ALM)

Activities that cover the entire SDLC, including requirements, design, development, testing, and deployment and management of software applications.

Adaptive Maintenance

Adds new capability and enhancements to an existing system.

Abbreviation Code

Alphabetic abbreviation. For example, standard state codes include NY for New York, ME for Maine, and MN for Minnesota.

Message

An O-O command that tells you an object to perform a certain method.

SWOT Analysis

An examination of a company's strengths (S), weaknesses (W), opportunities (O), and threats (T).

Report Header

Appears at the beginning of a report and identifies the report as well as the report title, date, and other necessary information.

Page Footer

Appears at the bottom of the page and is used to display the name of the report and the page number.

Retention Period

Backups are stored for a specific retention period after which they are either destroyed or the backup media is reused.

Uninterruptible Power Supply (UPS)

Battery-powered backup power source that enables operations to continue during short-term power outages and surges.

Radio Button

Buttons that represent groups of options. The user can select only one option at a time; a selected option contains a black dot. See also option button.

Universal Security Slot (USS)

Can be fastened to a cable lock or laptop alarm.

Maintenance Activities

Changing programs, procedures, or documentation to ensure correct system per - formance. Adapting the system to changing requirements; and making the system operate more effi- ciently. Those needs are met by corrective, adaptive, perfective, and preventive maintenance.

Significant Digit Code

Cipher that distinguishes items by using a series of subgroups of digits. U.S. Postal Service zip codes, for example, are significant digit codes.

Range-of-Response Questions

Closed-ended questions that ask the person to evaluate something by providing limited answers to specific responses or on a numeric scale.

Cardinality Notation

Code that shows relationships between entities.

Derivation Code

Combining data from different item attributes, or characteristics, to build the code. Most magazine subscription codes are derivation codes.

Soft Skills

Communications, interpersonal skills, perceptive abilities, and critical thinking are soft skills. It professionals must have soft skills as well as technical skills.

Maintenance Expenses

Costs that vary significantly during the system's operational life and include spend- ing to support maintenance activities.

Security Hole

Created by a combination of one or more improperly configured services.

Design Prototyping

Creating a prototype of user requirements, after which the prototype is discarded and implementation continues. Also called throwaway prototyping.

Method

Defines specific tasks that an object must perform. Describes what and how an object does something.

Backup Media

Data storage options, including tape, hard drives, optical storage, and online storage.

Information

Data that has been changed into a useful form of output.

Usability Metrics

Data that interface designers can obtain by using software that can record and measure user interactions with the system.

Unencrypted

Data that is not encrypted.

NoSQL Databases

Database systems that use a flat, nontabular (nonrelational) structure to store and process large-scale datasets.

Open Systems Interconnection (OSI) Model

Describes how the data actually moves from an application on one computer to an application on another networked computer. The OSI consists of seven layers, and each layer performs a specific function.

Object Model

Describes objects, which combine data and processes. Object models are the end product of O-O analysis.

Product Baseline

Describes the system at the beginning of operation. The product baseline incorporates any changes made since the allocated baseline and includes the results of performance and acceptance tests for the operational system.

Backup Policy

Detailed instructions and procedures for all backups.

Risk Control

Develops safeguards that reduce the likelihood and impact of risks.

Internet-of-Things (IOT)

Devices connected to one another over a computer network.

Data Flow Diagram (DFD)

Diagram that shows how the system stores, processes, and transforms data into useful information.

Systems Support and Security Phase

During the systems support and security phase of the SDLC, the IT staff maintains, enhances, and protects the system.

File

Each file or table contains data about people, places, things, or events that interact with the information system.

Table

Each file or table contains data about people, places, things, or events that interact with the information system.

Successor Task

Each of the concurrent tasks of a predecessor task.

Operational Costs

Expenses that are incurred after a system is implemented and continue while the system is in use. Examples include system maintenance, supplies, equipment rental, and annual software license fees.

Relationships

Enable objects to communicate and interact as they perform the business functions and transactions required by a system. Relationships describe what objects needs to know about each other, how objects respond to changes in other objects, and the effects of membership in classes, superclasses, and subclasses.

Automatic Update Service

Enables an application to contact the vendor's server and check for a needed patch.

Qualitative Risk Analysis

Evaluating risk by estimating the probability that it will occur and the degree of impact.

Quantitative Risk Analysis

Evaluating risk in terms of the actual impact in terms of dollars, time, project scope, or quality.

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.

Big Data

Extremely large datasets (e.g., petabytes) requiring nontraditional approaches to deal with them. Sometimes characterized by three terms: volume, variety, and velocity.

Wireless Fidelity (Wi-Fi)

Family of popular IEEE LAN wireless networking standards, also known as 802.11, including 802.11a, b, g, and n. 802.11n is the most recent standard. 802.11ac and 802.11ad are proposed new standards.

Brooke's Law

Frederick Brooks, an IBM engineer, observed that adding more manpower to a late software project only makes it later.

Project Monitoring

Guiding, supervising, and coordinating the project team's workload.

Online System

Handling transactions when and where they occur and providing output directly to users. Because it is interactive, online processing avoids delays and allows a constant dialog between the user and the system.

Project Planning

Identifying project tasks and estimating completion time and costs.

Totals Zone

If a form has data totals, they will appear in this section of the form.

Tightly Coupled

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

Process 0

In a DFD, process 0 (zero) represents the entire information system but does not show the internal workings.

Swim Lanes

In a business process diagram, the overall diagram is called a pool and the designated customer areas are called swim lanes.

Methods

In a class diagram, methods represent program logic.

Control Field Order

In a control break report, the records are arranged or sorted in the same order as the control fields.

Pilot Site

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

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.

Scroll Bar

In user interface design, a scroll bar allows the user to move through the available choices for an input field.

Action Code

Indicates what action is to be taken with an associated item. For example, a student records program might prompt a user to enter or click an action code such as D (to display the student's record), A (to add a record), and X (to exit the program).

Inference Rules

Instructions that direct a knowledge management system to identify data patterns and relationships.

Intangible Costs

Items that are difficult to measure in dollar terms, such as employee dissatisfaction.

Risk Identification

Listing each risk and assessing the likelihood that it could affect a project.

Data Mining

Looking for meaningful patterns and relationships among data. For example, data mining software could help a consumer products firm identify potential customers based on their prior purchases.

Hardening

Making a system more secure by removing unnecessary accounts, services, and features.

Biometric Scanning Systems

Mapping an individual's facial features, handprint, or eye characteristics for identification purposes.

Hash Controls

Not meaningful numbers themselves but are useful for comparison purposes. Also known as batch control totals.

Sequence Code

Numbers or letters assigned in a specific order. Sequence codes contain no additional information other than an indication of order of entry into a system

Acceptance

One of four risk control strategies. In acceptance, the risk is accepted and nothing is done. Risk is usually accepted only if protection from risk is clearly not worth the expense.

Avoidance

One of four risk control strategies. In avoidance, adding protective safeguards eliminates the risk.

Command Button

Onscreen button that initiates an action such as printing a form or requesting Help.

Transaction Processing (TP) Systems

Operational systems used to process day-to-day recurring business transactions such as customer billing.

Turnaround Document

Output document that is later entered back into the same or another information system. A telephone or utility bill, for example, might be a turnaround document printed by the company's billing system. When the bill is returned with payment, it is scanned into the company's accounts receivable system to record the payment accurately.

Customer

Primary user of a system, service or product.

Process

Procedure or task that users, managers, and IT staff members perform. Also, the logical rules of a system that are applied to transform data into meaningful information. In DFDs, a process receives input data and produces output that has a different content, form, or both.

Open-Ended Questions

Queries that allow for a range of answers. They encourage spontaneous and unstructured responses and are useful in understanding a larger process.

Closed-Ended Questions

Queries that limit or restrict the range of responses. Used in the interview process when specific information or fact verification is desired.

Leading Questions

Queries that suggest or favor a particular reply.

Audit Log Files

Record details of all accesses and changes to a file or database and can be used to recover changes made since the last backup.

Log

Record typically kept by operating systems and applications that documents all events, including dates, times, and other specific information. Logs can be important in understanding past attacks and preventing future intrusions.

Extensibility

Refers to a system's ability to expand, change, or downsize easily to meet the changing needs of a business enterprise. Also known as scalability.

Records Retention Policy

Rules designed to meet all legal requirements and business needs for keeping records.

Business Logic

Rules reflecting the operational requirements of the business that determine how a system handles data and produces useful information. Examples include adding the proper amount of sales tax to invoices, calculating customer balances and finance charges, and determining whether a customer is eligible for a volume-based discount.

Business Logic

Rules to determine how a system handles data and produces useful information, reflecting the operational requirements of the business. Examples include adding the proper amount of sales tax to invoices, calculating customer balances and finance charges, and determining whether a customer is eligible for a volume-based discount. Also called business rules.

Incremental Backup

Saving a copy of only the files that have changed since the last full backup.

One-to-One Relationship

See 1:1.

One-to-Many Relationship

See 1:M.

Computer-Aided Systems Engineering (CASE)

See Computer-aided software engineering (CASE).

Many-to-Many Relationship

See M:N.

Program Evaluation Review Technique (PERT)

See PERT/CPM.

Product Lifecycle Management (PLM)

See application lifecycle management (ALM).

Faxback

See automated fax.

Business Rules

See business logic.

Control Structure

Serve as building blocks for a process. Control structures have one entry and exit point. They may be completed in sequential order, as the result of a test or condition, or repeated until a specific condition changes. Also called logical structure.

State Transition Diagram

Shows how an object changes from one state to another, depending on the events that affect the object.

Logical Model

Shows what a system must do, regardless of how it will be implemented physically.

System Boundary

Shows what is included and excluded from a system. Depicted by a shaded rectangle in use case diagrams.

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.

Technical Support

Technical support is necessary to support the wide variety of IT systems and users. It includes six main functions: application development, systems support, user support, database administration, network administration, and web support. These functions overlap considerably and often have different names in different companies.

Electronic Product Code (EPC)

Technology that uses RFID tags to identify and monitor the movement of each individual product, from the factory floor to the retail checkout counter.

Radio Frequency Identification (RFID)

Technology that uses high-frequency radio waves to track physical objects.

Input Mask

Template or pattern that makes it easier for users to enter data. Often used in automated forms to guide an unfamiliar user.

Scalable

The ability of a system to expand to meet new business requirements and volumes.

Duration

The amount of time it will take to complete a task.

Artificial Intelligence

The attempt to recreate natural intelligence through software in machines.

Schema

The complete definition of a database, including descriptions of all fields, records, and relationships.

Sequence

The completion of steps in sequential order, one after another.

Finish Day/Date

The day or date when a task is scheduled to be finished.

Start Day/Date

The day or date when a task is scheduled to begin.

Logical Design

The definition of an information system's functions and features, and the relationships among its components.

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.

Systems Planning Phase

The first phase of the SDLC. During this phase the systems project gets started. The project proposal is evaluated to determine its feasibility. The project management plan is formulated, with the help of CASE tools where appropriate.

Coding

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

Process Improvement

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

Strategic Plans

The long-range plans that define the corporate mission and goals. Typically defined by top management, with input from all levels.

Child Diagram

The lower-level diagram in an exploded DFD.

Firewall

The main line of defense between a local network, or intranet, and the Internet.

Probable-Case Eatimate

The most likely outcome is called a probable-case estimate.

Data

The raw material or basic facts used by information systems.

Data Frames

Traffic on a computer network.

E-commerce (electronic commerce)

Transactions (e.g., buying and selling of goods and information) that occur on the Internet. Includes both business-to-consumer and business-to-business.

Network

Two or more devices that are connected for the purpose of sending, receiving, and sharing data.

Cipher Codes

Use a keyword to encode a number. A retail store, for example, may use a 10-letter word, such as CAMPGROUND, to code wholesale prices, where the letter C represents 1, A represents 2, and so on. Thus, the code, GRAND, would indicate that the store paid $562.90 for the item.

Request for Quotation (RFQ)

Used to obtain a price quotation or bid on a specific product or package.

Check Box

Used to select one or more choices from a group. A check mark, or an X, represents selected options.

Critical Success Factors

Vital objectives that must be achieved for the enterprise to fulfill its mission.

Mock-Up

When designing a report, a sample report is prepared, which is a mock-up, or prototype, for users to review. The sample should include typical field values and contain enough records to show all the design features.

Stand-Alone

When personal computers first appeared in large numbers in the 1990, users found that they could run their own word processing, spreadsheet, and database applications, without assistance from the IT group, in a mode called stand-alone computing.

Discretionary Projects

Where management has a choice in implementing a project, they are called discretionary. For example, creating a new report for a user is an example of a discretionary project.

Nondiscretionary Projects

Where management has no choice in implementing a project, they are called nondiscretionary. For example, adding a report required by a new federal law.

Metrics

Workload measurements, also called metrics, include the number of lines printed, the number of records accessed, and the number of transactions processed in a given time period.

Object-Oriented (O-O) Analysis

describes an information system by identifying things called objects. An object represents a real person, place, event, or transaction. O-O analysis is a popular approach that sees a system from the viewpoint of the objects themselves as they function and interact with the system.

Risk Management Plan

includes a review of the project's scope, stakeholders, budget, schedule, and any other internal or external factors that might affect the project. The plan should define project roles and responsibilities, risk management methods and procedures, categories of risks, and contingency plans.

Looping

refers to a process step that is repeated until a specific condition changes. For example, a process that continues to print paychecks until it reaches the end of the payroll file is looping. Also known as repetition.

ASCII

stands for American Standard Code for Information Interchange, a data storage coding method used on most personal computers and workstations.

Terminator

A DFD symbol that indicates a data origin or final destination. Also called an external entity.

Data Manipulation Language (DML)

A DML controls database operations, including storing, retrieving, updating, and deleting data. Most commercial DBMSs, such as Oracle and IBM's DB2, use a DML.

Redundant Array of Independent Disks (RAID)

A RAID system may be part of an organization's backup and recovery plans. A RAID system mirrors the data while processing continues. RAID systems are called fault-tolerant, because a failure of any one disk does not disable the system.

Differential Backup

A backup that includes only the files that have changed since the last full backup.

Gigabits per Second (GBps)

A bandwidth or throughput measurement.

Gigabits per second (GBps)

A bandwidth or throughput measurement.

Kbps (Kilobits Per Second)

A bandwidth or throughput measurement.

Megabits per Second (MBps)

A bandwidth or throughput measurement.

Megabits per second (MBps)

A bandwidth or throughput measurement.

Horizontal System

A basic system, such as an inventory or payroll package, that is commonly used by a variety of companies.

Data Dictionary

A central storehouse of information about a system's data.

Access Point

A central wireless device that provides network services to wireless clients.

Wireless Access Point (WAP)

A central wireless device that provides network services to wireless clients. Also called an access point.

Help Desk

A centralized resource staffed by IT professionals that provides users with the support they need to do their jobs. A help desk has three main objectives: to show people how to use system resources more effectively, to provide answers to technical or operational questions, and to make users more productive by teaching them how to meet their own information needs.

Service Desk

A centralized resource staffed by IT professionals that provides users with the support they need to do their jobs. Also called help desk.

Scalability

A characteristic implying the system can be expanded, modified, or downsized easily to meet the rapidly changing needs of a business enterprise.

Scalability

A characteristic implying the system can be expanded, modified, or downsized to meet the rapidly changing needs of a business enterprise.

Scalability

A characteristic of a system, implying that the system can be expanded, modified, or downsized easily to meet the rapidly changing needs of a business enterprise.

Build or Buy

A choice between developing in-house software and purchasing software, often called a build or buy, or make or buy, decision.

Data Management System (DBMS)

A collection of tools, features, and interfaces that enables users to add, update, manage, access, and analyze data in a database.

Network Interface

A combination of hardware and software that allows the computer to interact with the network.

B2C (business-to-consumer)

A commercial exchange (e.g., products or services) between businesses and consumers conducted over the Internet.

Private Key Encryption

A common encryption technology called public key encryption (PKE). The private key is one of a pair of keys, and it decrypts data that has been encrypted with the second part of the pair, the public key.

Wi-Fi Protected Access (WPA)

A common method used to secure a wireless network. This approach requires each wireless client be configured manually to use a special, pre-shared key, rather than key pairs. The most recent and more secure version is WPA2.

Histogram

A common tool for showing the distribution of questionnaire or sampling results. It takes the form of a vertical bar graph.

Service-Oriented

A company that primarily offers information or services, or sells goods produced by others.

Application Server

A computer acting as "middlemen" between customers and an organization's databases and applications. Often used to facilitate complex business transactions.

Bus Network

A computer network where a single communication path connects the mainframe computer, server, workstations, and peripheral devices. Information is transmitted in either direction from any workstation to another workstation, and any message can be directed to a specific device.

Management Information Systems (MIS)

A computer-based information system used in business planning, control, decision making, and problem solving.

Cardinality

A concept that describes how instances of one entity relate to instances of another entity. Described in ERDs by notation that indicates combinations that include zero or one-to-many, one-to-one, and many-to-many.

Cardinality

A concept that describes how instances of one entity relate to instances of another entity. Described in entity-relationship diagrams by notation that indicates combinations that include zero or one-to-many, one-to-one, and many-to-many.

Control Break

A control break usually causes specific actions to occur, such as printing subtotal a for a group of records.

Selection

A control structure in modular design, it is the completion of two or more process steps based on the results of a test or condition.

Certification

A credential an individual earns by demonstrating a certain level of knowledge and skill on a standardized test.

Business Profile

A definition of a company's overall functions, processes, organization, products, services, customers, suppliers, competitors, constraints, and future direction.

Use Case Description

A description in UML that documents the name of the use case, the actor, a description of the use case, a step-by-step list of the tasks required for successful completion, and other key descriptions and assumptions.

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, DFDs, object models, screen layouts, source documents, and the systems request that initiated the project.

Business Process

A description of specific events, tasks, and desired results.

Human-Computer Interaction (HCI)

A description of the relationship between computers and the people who use them to perform business-related tasks. HCI concepts apply to everything from a PC desktop to the main menu for a global network.

Requirements Definitions

A description of the system requirements from the user's point of view.

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 is also called partitioning.

Modular Design

A design that can be broken down into logical blocks. Also known as partitioning or top-down design.

Programmer/Analyst

A designation for positions that require a combination of systems analysis and pro- gramming skills.

Detail Report

A detail report produces one or more lines of output for each record processed.

Control Break Report

A detail report that focuses on control breaks.

Class Diagram

A detailed view of a single use case, showing the classes that participate in the use case and documenting the relationship among the classes.

Payback Analysis

A determination of how long it takes an information system to pay for itself through reduced costs and increased benefits.

Spiral Model

A development model with a series of iterations, or revisions, based on user feedback.

Keystroke Logger

A device that can be inserted between a keyboard and a computer to record keystrokes.

Router

A device that connects network segments, determines the most efficient data path, and guides the flow of data.

Diagram 0

A diagram depicting the first level of detail below the initial context diagram. Diagram 0 (zero) zooms in on the context diagram and shows major processes, data flows, and data stores, as well as repeating the external entities and data flows that appear in the context diagram.

Exploding

A diagram is said to be exploded if it "drills down" to a more detailed or expanded view.

Activity Diagram

A diagram that resembles a horizontal flowchart that shows the actions and events as they occur. Activity diagrams show the order in which actions take place and identify the outcome.

SysML

A dialect of UML 2, used for representing requirements (and other things), primarily in MBSE applications.

Net-Centric Computing

A distributed environment where applications and data are downloaded from servers and exchanged with peers across a network on an as-needed basis.

Blockchain

A distributed ledger system. The technology underlying Bitcoin.

Survey

A document containing a number of standard questions that can be sent to many individuals. Also called a questionnaire.

Questionnaire

A document containing a number of standard questions that can be sent to many individuals. Also called a survey.

Exception Report

A document displaying only those records that meet a specific condition or conditions. Exception reports are useful when the user wants information only on records that might require action, but does not need to know the details.

Mission Statement

A document or statement that describes the company for its stakeholders and briefly states the company's overall purpose, products, services, and values.

System Requirements Document

A document that contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management. It is the end product of the systems analysis phase.

System Design Specification

A document that presents the complete design for the new information system, along with detailed costs, staffing, and scheduling for completing the next SDLC phase, systems implementation. Also called the technical design specification or the detailed design specification.

Process Description

A documentation of a functional primitive's details, which represents a specific set of processing steps and business logic.

Disaster Recovery Plan

A documented procedure consisting of an overall backup and recovery plan.

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 the month, quarter, or year, in their simulations.

Brainstorming

A fact-finding technique for gaining information through the use of a small group discussion of a specific problem, opportunity, or issue.

Observation

A fact-finding technique where an analyst sees a system in action. Observation allows the verification of statements made in interviews.

What-If Analysis

A feature of business support systems that allow analysis to define and account for a wide variety of issues (including issues not completely defined).

Content-Sensitive

A feature that is sensitive to the current conditions when it is invoked. For example, content-sensitive help offers assistance for a task in progress.

Application Service Provider (ASP)

A firm that delivers a software application, or access to an application, by charging a usage or subscription fee.

Value-Added Reseller (VAR)

A firm that enhances a commercial package by adding custom features and configuring it for a particular industry.

Service Provider

A firm that offers outsourcing solutions. Two popular outsourcing options involve application service providers (ASPs) and firms that offer Internet business services (IBSs).

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 out- puts 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.

Bluetooth

A form of wireless transmission very popular for short-distance wireless communication that does not require high power.

Source Document

A form used to request and collect input data, trigger or authorize an input action, and provide a record of the original transaction. During the input design stage, you develop source documents that are easy to complete and inexpensive.

Systems Request

A formal appeal to the IT department that describes problems or desired changes in an information system or business process. It might propose enhancements for an existing system, the correction of problems, or the development of an entirely new system.

Baseline

A formal reference point that measures system characteristics at a specific time. Systems analysts use baselines as yardsticks to document features and performance during the systems development process.

Maintenance Release

A formal release of a new system version that contains a number of changes.

Systems Request

A formal request to the IT department that describes problems or desired changes in an information system or business process. It might propose enhancements for an existing system, the correction of problems, or the development of an entirely new system.

Entity-Relationship Diagram (ERD)

A graphical model of the information system that depicts the relationships among system entities.

Business Model

A graphical representation of business functions that consist of business processes, such as sales, accounting, and purchasing.

Business Process Model (BPM)

A graphical representation of one or more business processes.

Decision Tree

A graphical representation of the conditions, actions, and rules found in a decision table.

Unstructured Brainstorming

A group discussion where any participant can speak at any time.

Structured Brainstorming

A group discussion where each participant speaks when it is his or her turn or passes.

Byte

A group of eight bits is called a byte, or a character. A set of bytes forms a field, which is an individual fact about a person, a place, a thing, or an event.

Character

A group of eight bits is called a character, or a byte. A set of bytes forms a field, which is an individual fact about a person, a place, a thing, or an event.

Computer Resources Committee

A group of key managers and users responsible for evaluating systems requests. The term "systems review committee" is also used.

Systems Review Committee

A group of key managers and users responsible for evaluating systems requests. The term computer resources committee is sometimes also used.

Evaluation and Selection Team

A group of people involved in selecting hardware and software. The group includes systems analysts and users. A team approach ensures that critical factors are not overlooked and that a sound choice is made.

Gantt Chart

A horizontal bar chart that illustrates a schedule. Developed many years ago by Henry L. Gantt as a production control technique. Still are in common use today.

Attack

A hostile act that targets an information system, or an organization itself.

Task Pattern

A logical sequence of tasks in a work breakdown structure (WBS). Can involve sequential tasks, multiple successor tasks, and multiple predecessor tasks.

Subordinate Module

A lower-level module in a structure chart.

Service Pack

A maintenance release supplied by commercial software suppliers.

Turnaround Time

A measure applied to centralized batch processing operations, such as customer billing or credit card statement processing. Turnaround time measures the time between submitting a request for information and the fulfillment of the request. Turnaround time can also be used to measure the quality of IT support or services by measuring the time from a user request for help to the resolution of the problem.

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.

Throughput

A measurement of actual system performance under specific circumstances and is affected by network loads and hardware efficiency. Throughput, like bandwidth, is expressed as a data transfer rate, such as Kbps, Mbps, or Gbps.

Benchmark

A measures of the time a package takes to process a certain number of transactions.

Data Validation Rule

A mechanism to improve input quality by testing the data and rejecting any entry that fails to meet specified conditions.

Biometric Devices

A mechanism used to uniquely identify a person by a retina scan or by mapping a facial pattern.

Black Box

A metaphor for a process or action that produces results in a non-transparent or non-observable manner. In DFD's, a process appears as a black box where the inputs, outputs, and general function of the process are known, but the underlying details are not shown.

Bottom-Up Technique

A method for analyzing a large, complex project as a series of individual tasks, called project tasks.

Capability Maturity Model (CMM)

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

Software as a Service (SaaS)

A model of software delivery in which functionality is delivered on-demand as a network-accessible service, rather than as a traditional software application that is downloaded and installed on the customer's computer.

Physical Model

A model that describes how a system will be constructed.

Relational Model

A model used in relational databases. The relational model was introduced during the 1970s and became popular because it was flexible and powerful.

Module

A module consists of related program code that organized into small units that are easy to understand and maintain. A complex program could have hundreds or even thousands of modules.

Superclass

A more generalized category to which objects may belong (e.g., a NOVEL class might belong to a superclass called BOOK).

N-Tier Design

A multilevel design or architecture. For example, three-tier designs are also called n-tier designs, to indicate that some designs use more than one intermediate layer.

Mesh Network

A network design in which each node connects to every other node. While this design is very reliable, it is also expensive to install and maintain.

Local Area Network (LAN)

A network design that allows the sharing of data and hardware, such as printers and scanners. Advances in data communication technology have made it possible to create powerful networks that use satellite links, high-speed fiber-optic lines, or the Internet to share data.

Fat Client

A network design that locates all or most of the application processing logic at the client. Also called a thick client design.

Multipath Design

A network design that relies on multiple data paths to increase bandwidth and range, using MIMO (multiple input/multiple output) technology.

Hierarchal Network

A network design where one computer (typically a mainframe) controls the entire network. Satellite computers or servers control lower levels of processing and network devices.

Two-Tier Design

A network design where the user interface resides on the client, all data resides on the server, and the application logic can run either on the server or on the client, or be divided between the client and the server.

Star Network

A network design with a central device and one or more workstations connected to it in a way that forms a star pattern.

Transparent

A network is transparent if a user sees the data as if it were stored on his or her own workstation.

International Organization for Standardization (ISO)

A network of national standard institutes from over a hundred countries working in partnership with international organizations, governments, industries, and business and consumer representatives. The ISO acts as a bridge between public and private sectors.

Ring Network

A network resembling a circle of computers that communicate with each other. A ring network often is used when processing is performed at local sites rather than at a central location.

Wide Area Network (WAN)

A network spanning long distances that can link users who are continents apart.

Diskless Workstation

A network terminal that supports a full-featured user interface, but limits the printing or copying of data, except to certain network resources that can be monitored and controlled more easily.

Proxy Server

A networking device that provides Internet connectivity for internal LAN users.

Enhancement

A new feature or capability.

Wi-Fi Alliance

A nonprofit international association formed in 1999 to certify interoperability of wireless network products based on IEEE 802.11 specifications.

Task ID

A number or code that uniquely identifies a task.

Total Cost of Ownership (TCO)

A number used in assessing costs, which includes ongoing support and maintenance costs, as well as acquisition costs.

Webcast

A one-way transmission of information or training materials, such as a Webinar session, available on demand or for a specific period to online participants.

Case for Action

A part of the preliminary investigation report to management that summarizes project requests and makes specific recommendations.

Boot-Level Password

A password that must be entered before the computer can be started. It prevents an unauthorized person from booting a computer by using a USB device or a CD-ROM. Also called a power-on password or a BIOS-level password.

BIOS-Level Password

A password that must be entered before the computer can be started. It prevents an unauthorized person from booting a computer by using a USB device or a CD-ROM. Also called a power-on password or a boot-level password.

Power-On Password

A password that must be entered before the computer can be started. It prevents an unauthorized person from booting a computer by using a USB device or a CD-ROM. Also called a power-on password or a boot-level password.

Data Flow

A path for data to move from one part of the information system to another.

Return on Investment (ROI)

A percentage rate that measures profitability by comparing the total net benefits (the return) received from a project to the total costs (the investment) of the project. ROI = (total benefits - total costs)/total costs.

Knee of the Curve

A performance characteristic of a client/server computing environment. Client/server response times tend to increase gradually and then rise dramatically as the system nears its capacity. The point where response times increase dramatically.

Systems Programmer

A person who concentrates on operating system software and utilities.

Database Programmer

A person who focuses on creating and supporting large-scale database systems.

System Administrator

A person who is responsible for the configuration management (CM) and maintenance of an organization's computer networks.

Systems Analyst

A person who plans, analyzes, and implements information systems. He or she may work internally within a company's IT department, or be hired by a company as an independent consultant.

Applications Programmer

A person who works on new systems development and maintenance.

Entity

A person, a place, a thing, or an event for which data is collected and maintained. For example, an online sales system may include entities named CUSTOMER, ORDER, PRODUCT, and SUPPLIER.

Requirements Planning Phase

A phase that combines elements of the systems planning and systems analysis phases of the SDLC.

Construction Phase

A phase that focuses on program and application development tasks similar to the SDLC.

Cutover Phase

A phase that resembles the final tasks in the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training.

Hawthorne Effect

A phenomenon where employees who know they are being observed are more productive.

Security Token

A physical device that authenticates a legitimate user, such as a smart card or keychain device.

Test Plan

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

Business Continuity Plan (BCP)

A plan that defines how critical business functions can continue in the event of a major disruption.

Interview

A planned meeting during which information is obtained from another person.

Deliverable

A polished, final product, suitable for its intended use. End products or deliverables often coincide with the completion of each SDLC phase.

Source Data Automation

A popular online input method that combines online data entry and automated data capture using input devices such as magnetic data strips, or swipe scanners.

Game and Sarson

A popular symbol set used in DFD's. Processes, data flows, data stores, and external entities all have a unique symbol.

knowledge Base

A popular systems development technique that uses a group of users, managers and IT professionals that work together to gather information, discuss business needs, and define the new system requirements.

Scrum

A popular technique for agile project management. Derived from a rugby term. In Scrum, team members play specific roles and interact in intense sessions.

Port

A positive integer that is used for routing incoming traffic to the correct application on a computer.

Pair Programming

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

Moore's Law

A prediction that computing power would double every 18 to 24 months due to increased miniaturization of electronic components.

Risk Response Plan

A proactive effort to anticipate a risk and describe an action plan to deal with it. An effective risk response plan can help reduce the overall impact by triggering a timely and appropriate action.

Y2K Issues

A problem faced by many firms in the year 2000 because their computer systems used only two digits to represent the year; most dates now use a four-digit format for the year (YYYYMMDD).

Normalization

A process by which analysts identify and correct inherent problems and complexities in their record designs.

Configuration Management (CM)

A process for controlling changes in system requirements during the development phases of the SDLC. Configuration management also is an important tool for managing system changes and costs after a system becomes operational.

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.

Roaming

A process that allows wireless clients to move from one access point to another, automatically associating with the stronger access point and allowing for uninterrupted service.

Enterprise Resource Planning (ERP)

A process that establishes an enterprise-wide strategy for IT resources. ERP defines a specific architecture, including standards for data, processing, network, and user interface design.

Black Hole

A process that has no output.

Electronic Data Interchange (EDI)

A process that involves the computer-to-computer transfer of data between companies. Is the exchange of business documents between computers using a standard electronic format.

Capacity Planning

A process that monitors current activity and performance levels, anticipates future activity, and forecasts the resources needed to provide desired levels of service.

Modeling

A process that produces a graphical representation of a concept or process that systems developers can analyze, test, and modify.

Balancing

A process used to maintain consistency among an entire series of diagrams, including input and output data flows, data definition, and process descriptions.

Sampling

A process where an analyst collects examples of actual documents, which could include records, reports, or various forms.

Batch Input

A process where data entry is performed on a specified time schedule, such as daily, weekly, monthly, or longer. For example, batch inputs occur when a payroll department collects time cards at the end of the week and enters the data as a batch.

Encryption

A process where data is coded (converted into unreadable characters) so that only those with the required authorization an access the data (usually via decoding software).

Encryption

A process where data is coded (converted into unreadable characters) so that only those with the required authorization can access the data (usually via decoding software).

Gray Hole

A process with an input obviously insufficient to generate the shown output.

Institute of Electrical and Electronics Engineers (IEEE)

A professional organization that establishes standards for telecommunications.

Personal Digital Assistant

A program that responds to user requests through a natural interface, such as regular speech, to provide assistance to general-purpose queries. Often embedded in devices such as Internet-connected speakers and smartphones.

Work Breakdown Structure (WBS)

A project broken down into a series of smaller tasks. See also Gantt chart; PERT/CPM chart.

Schedule Feasibility

A project can be implemented in an acceptable time frame.

Structured Query Language (SQL)

A query language that allows PC users to communicate with servers and mainframe computers.

Continuous Backup

A real-time streaming backup method that records all system activity as it occurs.

Second Normal Form (2NF)

A record design is in 2NF if it is in 1NF and if all fields that are not part of the primary key are dependent on the entire primary key. If any field in a 1NF record depends on only one of the fields in a combination primary key, then the record is not in 2NF. A 1NF record with a primary key that is a single field is automatically in 2NF.

Third Normal Form (3NF)

A record design is in 3NF if it is in 2NF and if no nonkey field is dependent on another nonkey field. A nonkey field is a field that is not a candidate key for the primary key.

First Normal Form (1NF)

A record is said to be in first normal form (1NF) if it does not contain a repeating group (a set of data items that can occur any number of times in a single record).

Audit Trail

A record of the source of each data item and when it entered a system. In addition to recording the original source, an audit trail must show how and when data is accessed or changed, and by whom. All these actions must be logged in an audit trail file and monitored carefully.

Unnormalized

A record that contains a repeating group, which means that a single record has multiple occurrences of a particular field, with each occurrence having different values.

Milestone

A reference point that marks a major occurrence. Used to monitor progress and manage a project. See also event.

Event

A reference point that marks a major occurrence. Used to monitor progress and manage a project. See also milestone.

Summary Report

A report used by individuals at higher levels in the organization that includes less detail than reports used by lower-level employees.

Standard notation Format

A representation that makes designing tables easier as it clearly shows a table's structure, fields, and primary key.

Constraint

A requirement or a condition that the system must satisfy or an outcome that the system must achieve.

Code Review

A review of a project team member's work by other members of the team to spot logic errors. Generally, systems analysts review the work of other systems analysts, and programmers review the work of other programmers, as a form of peer review. Structured walk-throughs should take place throughout the SDLC and are called requirements reviews, design reviews, code reviews, or testing reviews, depending on the phase in which they occur. Also known as a structured walk-through.

Structured Walk-Through

A review of a project team member's work by other members of the team. Generally, systems analysts review the work of other systems analysts, and programmers review the work of other programmers, as a form of peer review. Should take place throughout the SDLC and are called requirement reviews, design reviews, code reviews, or testing reviews, depending on the phase in which they occur.

Document Review

A review of baseline documentation. A useful fact-finding technique that helps an analyst understand how the current system is supposed to work.

Systematic Sample

A sample that occurs at a predetermined periodicity. For example, every tenth customer record might be selected as a systematic sample for review.

Web 2.0

A second generation of the web that enables people to collaborate, interact, and share information much more dynamically, based on continuously available user applications rather than static HTML web pages. Interactive experience is a hallmark of Web 2.0.

Tunnel

A secure network connection established between the client and the access point of the local intranet.

IEEE 802.11i

A security standard for Wi-Fi wireless networks that uses the WPA2 protocol, currently the most secure encryption method for Wi-Fi networks.

Vulnerability

A security weakness or soft spot.

Random Sample

A selection taken in a random, unplanned manner. For example, a random sample might be a sample that selects any 20 customers.

Hot Site

A separate IT location, which might be in another state or even another country, that can support critical business systems in the event of a power outage, system crash, or physical catastrophe.

Critical Path

A series of events and activities with no slack time. If any activity along the critical path falls behind schedule, the entire project schedule is similarly delayed. As the name implies, a critical path includes all activities that are vital to the project schedule.

Tutorial

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

Distributed Denial of Service (DDOS)

A service attack involving multiple attacking computers that can synchronize DOS attacks on a server.

Fixed Fee Model

A service model that charges a set fee based on a specified level of service and user support.

Subscription Model

A service model that charges a variable fee for an application based on the number of users or workstations that have access to the application.

Transaction Model

A service model that charges a variable fee for an application based on the volume of transactions or operations performed by the application. Also called a usage model.

Design Walk-Through

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.

Stratified Sample

A set metric is collected across functional areas. For example, a certain percentage of transactions from every work shift, or five customers from each of four zip codes, could be a stratified sample.

Corporate Culture

A set of beliefs, rules, traditions, values, and attitudes that define a company and influence its way of doing business.

Repeating Group

A set of one or more fields that can occur any number of times in a single record, with each occurrence having different values.

Record

A set of related fields that describes one instance, or member of an entity, such as one customer, one order, or one product. A record might have one or dozens of fields, depending on what information is needed. Also called a tuple.

Menu Bar

A set of user-selectable software application options, usually located across the top of the screen.

Data Element

A single characteristic or fact about an entity. A data element, field, or attribute is the smallest piece of data that has meaning within an information system. For example, a Social Security number or company name could be examples of a data element. Also called data item.

Field

A single characteristic or fact about an entity. A field, or attribute, is the smallest piece of data that has meaning within an information system. For example, a Social Security number or company name could be examples of a field. The terms data element, data item, and field are used interchangeably.

Attribute

A single characteristic or fact about an entity. An attribute, or field, is the smallest piece of data that has meaning within an information system. For example, a SocialSecurity number or company name could be examples of an attribute. In O-O analysis, an attribute is part of a class diagram that describes the characteristics of objects in the class. Also known as a data element.

Functional Primitive

A single function that is not exploded further. The logic for functional primitives is documented in a data dictionary process description.

Predecessor Task

A single prior task upon which two or more concurrent tasks depend.

App

A software application that runs on a mobile device, such as a smartphone or tablet.

Software Engineering

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

Natural Language

A software feature that allows users to type commands or requests in normal English (or other language) phrases.

Horizontal Application

A software package that can be used by many different types of organizations.

Vertical Application

A software package that has been developed to handle information requirements for a specific type of business.

Data Mart

A specialized database designed to serve the needs of a specific department, such as sales, marketing, or finance. Each data mart includes only the data that users in that department require to perform their jobs.

Project Scope

A specific determination of a project's boundaries or extent.

Platform

A specific hardware and software configuration that supports IT business goals such as hardware connectivity and easy integration of future applications. Also called an environment.

Instance

A specific member of a class.

Maintenance Agreement

A specification of the conditions, charges, and time frame for users to contact the vendor for assistance when they have system problems or questions.

Condition

A specified action or state in a structure chart.

Business Process Modeling Notation (BPMN)

A standard set of shapes and symbols used to represent events, processes, and workflows in computer-based modeling tools.

Java Database Connectivity (JDBC)

A standard that enables Java applications to exchange data with any database that uses SQL statements and is ODBC-compliant.

Non-Functional Requirements

A statement of operational system constraints.

Functional Requirement

A statement of the services a system provides.

Web-Centric

A strategy or approach that emphasizes a high degree of integration with other web-based components. A web-centric architecture follows Internet design protocols and enables a company to integrate the new application into its ecommerce strategy.

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.

Structured English

A subset of standard English that describes logical processes clearly and accurately.

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.

Electronic Proof of Delivery (EPOD)

A supplier uses RFID tags on each crate, case, or shipping unit to create a digital shipping list to verify receipt of goods.

Data Repository

A symbol used in data flow diagrams to represent a situation in which a system must retain data because one or more processes need to use that stored data at a later time. Used interchangeably with the term data store.

Thick Client

A system design that locates most or all of the application processing logic at the client. Also called a fat client design.

Thin Client

A system design that locates most or all of the processing logic at the server.

Mainframe Architecture

A system design where the server performs all the processing.

Vertical System

A system designed to meet the unique requirements of a specific business or industry, such as a web-based retailer or auto-supply store.

Distributed Database Management System (DDBMS)

A system for managing data stored at more than one location. Using DDBMS offers several advantages: Data stored closer to users can reduce network traffic; the system is scalable, so new data sites can be added without reworking the system design; and with data stored in various locations, the system is less likely to experience a catastrophic failure. A potential disadvantage of distributed data storage involves data security. It can be more difficult to maintain controls and standards when data is stored in various locations.

Maintenance Release Methodology

A system of numbered releases used by organizations (especially software vendors) that helps organize maintenance changes and updates.

Fault Tolerant

A system or application is said to be fault tolerant if the failure of one component does not disable the rest of the system or application.

Automated Fax

A system that allows a customer to request a fax using email, the company website, or a telephone. The response is transmitted in a matter of seconds back to the user's fax machine. See faxback.

Operational Feasibility

A system that will be used effectively after it has been developed.

Joint Application Development (JAD)

A systems development technique that uses a task force of users, managers, and IT professionals who work together to gather information, discuss business needs, and define the new system requirements.

Decision Table

A table that shows a logical structure, with all possible combinations of conditions and resulting actions.

Dependent Task

A task is said to be dependent when it has to be completed in a serial sequence.

Concurrent Task

A task that can be completed at the same time as (in parallel with) another task.

Task Group

A task that represents several activities.

Rapid Application Development (RAD)

A team-based technique that speeds up information systems development and produces a functioning information system. RAD is similar in concept to JAD but goes further by including all phases of the SDLC.

Pseudocode

A technique for representing program logic.

Evaluation Model

A technique that uses a common yardstick to measure and compare vendor ratings.

Computer-Aided Software Engineering (CASE)

A technique that uses powerful programs called CASE tools to provide an overall framework for systems development. The tools support a wide variety of design methodologies, including structured analysis and object-oriented analysis. Also referred to as computer-aided systems engineering.

Fill-In Form

A template used to collect data on the Internet or a company intranet.

User-Centered

A term that indicates the primary focus is upon the user. In a user-centered system, the distinction blurs between input, output, and the interface itself.

Class

A term used in object-oriented modeling to indicate a collection is similar objects.

Alias

A term used in various data dictionaries to indicate an alternate name, or a name other than the standard data element name, that is used to describe the same data element.

Personal Information Manager (PLM)

A tool that helps manage tasks and schedules. Many handheld devices also include this function.

XY Chart

A tool used by system analysts to graphically show the correlation between two variables. Also called a scatter diagram.

Scatter Diagram

A tool used by system analysts to graphically show the correlation between two variables. Also called an XY chart.

Functional Decomposition Diagram (FDD)

A top-down representation of business functions and processes. Also called a structure chart.

Context Diagram

A top-level view of an information system that shows the boundaries and scope.

Batch Control

A total used to verify batch input. Batch controls might check data items such as record counts and numeric field totals. For example, before entering a batch of orders, a user might calculate the total number of orders and the sum of all the order quantities. When the batch of orders is entered, the order system also calculates the same two totals. If the system totals do not match the input totals, then a data entry error has occurred.

Structured Analysis

A traditional systems development technique that uses phases to plan, analyze, design, implement, and support an information system. Processes and data are treated as separate components.

Supply Chain

A traditional systems development technique that uses phases to plan, analyze, design, implement, and support an information system. Processes and data are treated as separate components.

Outsourcing

A transfer of information systems development, operation, or maintenance to an outside firm that provides these services, for a fee, on a temporary or long-term basis.

System Architecture

A translation of the logical design of an information system into a physical structure that includes hardware, software, network support, and processing methods.

Site Visit

A trip to a physical location to observe a system in use at another location.

Tuple

A tuple (rhymes with couple), or record, is a set of related fields that describes one instance, or member of an entity, such as one customer, one order, or one product. A tuple might have one or dozens of fields, depending on what information is needed.

Market Basket Analysis

A type of analysis that can detect patterns and trends in large amounts of data.

Crow's Foot Notation

A type of cardinality notation. It is called crow's foot notation because of the shapes, which include circles, bars, and symbols, that indicate various possibilities. A single bar indicates one, a double bar indicates one and only one, a circle indicates zero, and a crow's foot indicates many.

Reasonableness Check

A type of data validation check that identifies values that are questionable, but not necessarily wrong. For example, input payment values of $0.05 and $5,000,000.00 both pass a simple limit check for a payment value greater than zero, and yet both values could be errors.

Combination Check

A type of data validation check that is performed on two or more fields to ensure that they are consistent or reasonable when considered together. Even though all the fields involved in a combination check might pass their individual validation checks, the combination of the field values might be inconsistent or unreasonable.

Combination Key

A type of data validation check that is performed on two or more fields to ensure that they are consistent or reasonable when considered together. Even though all the fields involved in a combination check might pass their individual validation checks, the combination of the field values might be inconsistent or unreasonable.

Validity Check

A type of data validation check that is used for data items that must have certain values. For example, if an inventory system has 20 valid item classes, then any input item that does not match one of the valid classes will fail the check.

Existence Check

A type of data validation check that is used for mandatory data items. For example, if an employee record requires a Social Security number, an existence check would not allow the user to save the record until he or she enters a suitable value in the SSN field.

Data Type Check

A type of data validation check that is used to ensure that a data item fits the required data type. For example, a numeric field must have only numbers or numeric symbols, and an alphabetic field can contain only the characters A through Z or the characters a through z.

Sequence Check

A type of data validation check that is used when the data must be in some predetermined sequence. If the user must enter work orders in numerical sequence, for example, then an out-of-sequence order number indicates an error. If the user must enter transactions chronologically, then a transaction with an out-of-sequence date indicates an error.

Range Check

A type of data validation check that tests data items to verify that they fall between a specified minimum and maximum value. The daily hours worked on by an employee, for example, must fall within the range of 0 to 24.

M:N

A type of entity relationship. A many-to-many relationship, abbreviated M:N, exists when one instance of the first entity can be related to many instances of the second entity, and one instance of the second entity can be related to many instances of the first entity.

1:M

A type of entity relationship. A one-to-many relationship, abbreviated 1:M, exists when one occurrence of the first entity can be related to many occurrences of the second entity, but each occurrence of the second entity can be associated with only one occurrence of the first entity.

1:1

A type of entity relationship. A one-to-one relationship, abbreviated 1:1, exists when exactly one of the second entity occurs for each instance of the first entity.

Inheritance

A type of object relationship. Inheritance enables an object to derive one or more of its attributes from another object (e.g., an INSTRUCTOR object may inherit many traits from the EMPLOYEE object, such as hire date).

Yourdon

A type of symbol set that is used in DFDs. Processes, data flows, data stores, and external entities each have a unique symbol in the Yourdon symbol set.

Referential Integrity

A type of validity check. Referential integrity is a set of rules that avoids data inconsistency and quality problems.

Transparent Interface

A user interface that users don't really notice—a user-friendly interface that does not distract the user and calls no attention to itself.

Default Value

A value that a system displays automatically.

Pareto Chart

A vertical bar graph named for a nineteenth-century economist. The bars, which represent various causes of a problem, are arranged in descending order, so the team can focus on the most important causes.

Form Filling

A very effective method of online data entry where a blank form that duplicates or resembles the source document is completed on the screen. The user enters the data and then moves to the next field.

Logical Topology

A view of a network that describes the way the components interact, rather than the actual network cabling and connections.

Subschema

A view of the database used by one or more systems or users. A subschema defines only those portions of the database that a particular system or user needs or is allowed to access.

Use Case Diagram

A visual representation that illustrates the interaction between users and the information system in UML.

Use Case Diagram

A visual representation that represents the interaction between users and the information system in UML.

Podcast

A web-based broadcast that allows a user to receive audio or multimedia files using music player software such as iTunes, and listen to them on a PC or download them to a portable MP3 player or smartphone.

Corporate Portal

A website that provides various tools and features for an organization's customers, employees, suppliers, and the public.

Unified Modeling Language (UML)

A widely used method of visualizing and documenting software systems design. UML uses O-O design concepts, but it is independent of any specific programming language and can be used to describe business processes and requirements generally.

Unified Modeling Language (UML)

A widely used method of visualizing and documenting software systems design. UML uses object-oriented design concepts, but it is independent of any specific programming language and can be used to describe business processes and requirements generally.

Infrastructure Mode

A wireless network configuration in which a central wireless device called an access point is used to serve all wireless clients; also called Basic Service Set (BSS).

Basic Service Set (BSS)

A wireless network configuration in which a central wireless device called an access point is used to serve all wireless clients; also called infrastructure mode.

Extended Service Set (ESS)

A wireless network configuration made up of two or more Basic Service Set (BSS) networks, which allows wireless clients to roam from BSS to BSS.

Economic Feasibility

Achieved if the projected benefits of the proposed system outweigh the estimated costs involved in acquiring, installing, and operating it.

Dialog Box

Allows a user to enter information about a task that a system will perform.

Query Language

Allows a user to specify a task without specifying how it will be accomplished. Some query languages use natural language commands that resemble ordinary English sentences.

802.11n

An IEEE wireless network specification adopted in 2009 that uses multiple input/multiple output (MIMO) technology to achieve speeds of 200+ Mbps while increasing the wireless range, and is backward-compatible with 802.11 a, b, and g.

802.11b

An IEEE wireless network specification introduced in 1999, based on a frequency of 2.4 GHz, and maximum bandwidth of 11 Mbps. Replaced by 802.11g.

802.11g

An IEEE wireless network specification introduced in 2003 based on a frequency of 2.4 GHz and maximum bandwidth of 54 Mbps; compatible with and replaced 802.11b, and has been superseded by the 802.11n standard.

802.11ac

An IEEE wireless network specification, approved in 2014, that uses expanded multiple input/multiple output (MIMO) technology to achieve theoretical speeds of nearly 7 Gbps while increasing the wireless range, and is backward-compatible with 802.11 a, b, g, and n.

Webinar

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

Capability Maturity Model Integration (CMMI)

An SEI-developed process to improve quality, reduce development time, and cut costs. A CMM tracks an organization's software development goals and practices, using five maturity levels, from Level 1 (relatively unstable, ineffective software) to Level 5 (software that is refined, efficient, and reliable).

Test-Driven Development(TDD)

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

Administrator Account

An account that allows essentially unrestricted access to the application.

Iterative

An adaptive method typically uses a spiral development model, which builds on a series of iterations.

State

An adjective that describes an object's current status (e.g., a student could be a CURRENT, FUTURE, or PAST student).

Iteration Cycle

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

Fishbone Diagram

An analysis tool that represents the possible causes of a problem as a graphical outline. Also called an Ishikawa diagram.

Integrated Development Environments (IDE)

An application for building other software applications. Typically includes a visual code editor, an integrated compiler, a debugger, a configuration management system, and test framework.

Machine Learning

An application of computer science and artificial intelligence that uses automated approaches to pattern recognition and predictive analytics based on large datasets.

Third-Party Software

An application that is not developed in-house.

Service

An application that monitors, or listens on, a particular port.

Model-Based Systems Engineering (MBSE)

An approach to systems engineering that relies on domain models, rather than traditional documents, to design large-scale systems and convey information between engineers.

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.

Exploit

An attack that takes advantage of of a system vulnerability, often due to a combination of one or more improperly configured services.

Port Scan

An attempt to detect the services running on a computer by trying to connect to various ports and recording the ports on which a connection was accepted.

Common Field

An attribute that appears in more than one entity. Common fields can be used to link entities in various types of relationships.

Prototype

An early, rapidly constructed working version of the proposed information system.

Electronic Health Record (EHR)

An electronic record of a patient's health information generated as the patient encounters various health-care providers and shared among multiple facilities and agencies.

Associative Entity

An entity that has its own set of attributes and characteristics. Associative entities are used to link between many-to-many (M:N) relationships.

Portal

An entrance to a multifunction website. After entering a portal, a user can navigate to a destination, using various tools and features provided by the portal designer.

Bring Your Own Device (BYOD)

An equipment management model where employees are in charge of their devices (e.g., computers, tablets, smartphones) at work, not the IT department. This includes device selection and setup, program installation and updating, and network connectivity (including security).

Semantic Web

An evolution of the web where the documents shared on the Internet have semantics (meaning) and not just syntax (HTML markup). Sometimes called Web 3.0.

Sink

An external entity that receives data from an information system.

Source

An external entity that supplies data to an information system.

Actor

An external entity with a specific role. In a use case model, actors are used to model interaction with the system.

Research

An important fact-finding technique that includes the review of journals, periodicals, and books to obtain background information, technical material, and news about industry trends and development.

Weight

An important multiplier that manages factor into estimates so they can be analyzed.

Open Database Connectivity (ODBC)

An industry-standard protocol that makes it possible for software from different vendors to interact and exchange data.

In-House Software

An information center or help desk within the IT department responsible for providing user support and offering services such as hotline assistance, training, and guidance to users who need technical help.

Mission-Critical System

An information system that is vital to a company's operations.

Preliminary Investigation

An initial analysis to clearly identify the nature and scope of the business opportunity or problem. Also called a feasibility study.

Feasibility Study

An initial investigation to clearly identify the nature and scope of the business opportunity or problem. Also called a preliminary investigation.

Radio Frequency Identification (RFID) Tag

An input device used in source data automation.

Legacy System

An older system that is typically less technologically advanced than currently available systems.

Denial of Service (DOS)

An online attack that occurs when an attacking computer makes repeated requests to a service or services running on certain ports.

Forum

An online discussion on a particular topic, where people meet, offer support, and exchange ideas.

Blog

An online journal. The term is a contraction of "web log."

Cloud Computing

An online software and data environment in which applications and services are accessed and used through an Internet connection rather than on a local computer; refers to the cloud symbol for the Internet.

Managed Hosting

An operation is managed by the outside firm, or host. Another term for Internet business services (IBS).

Informal Structure

An organization based on interpersonal relationships, which can develop from previous work assignments, physical proximity, unofficial procedures, or personal relationships.

List Box

An output mechanism that displays a list of choices that the user can select.

Orphan

An unassociated or unrelated record or field. An orphan could be created if a customer order was interned in an order table where that customer did not already exist in the customer table. Referential integrity would prevent the creation of this orphan.

Privilege Escalation Attack

An unauthorized attempt to increase permission levels.

Spontaneous Generation

An unexplained generation of data or information. With respect to DFDs, processes cannot spontaneously generate data flows—they must have an input to have an output.

Decomposing

Another way of conveying a process or system that has been broken down from a general, top-level view to more detail. The terms exploded and partitioned can also be used.

Nonkey Field

Any field that is not a primary key or a candidate key is called a nonkey field.

Activity

Any work that has a beginning and an end and requires the use of company resources including people, time and/or money. Examples include conducting a series of interviews, designing a report, selecting software, waiting for the delivery of equipment, and training users. See also task.

Task

Any work that has a beginning and an end and requires the use of company resources including people, time, and/or money. Examples include conducting a series of interviews, designing a report, selecting software, waiting for the delivery of equipment, and training users. See also activity.

Stakeholder

Anyone who is affected by the company's performance, such as customers, employees, suppliers, stockholders, and members of the community.

Report Footer

Appears at the end of the report, can include grand totals for numeric fields and other end-of-report information.

Page Header

Appears at the top of the page and includes the column headings that identify the data.

User Productivity Systems

Application that provides employees of all levels a wide array of tools to improve job performance. Examples include email, word processing, graphics, and company intranets.

Productivity Software

Applications such as word processing, spreadsheet, database management, and presentation graphics programs.

Remote Control Software

Applications that allow IT staff to take over a user's workstation and provide support and troubleshooting.

Preventive Maintenance

Changes made to a system to avoid possible future problems.

Validity Rules

Checks that are applied to data elements when data is entered to ensure that the value entered is valid. For example, a validity rule might require that an employee's salary number be within the employer's predefined range for that position.

Block Sequence Code

Cipher that uses blocks of numbers for different classifications.

Category Codes

Ciphers that identify a group of related items. For example, a local department store may use a two-character category code to identify the department in which a product is sold.

Mnemonic Code

Ciphers using a specific combination of letters that are easy to remember. Many three-character airport codes are mnemonic codes. For example, LAX represents Los Angeles.

Product-Oriented

Companies that manufacture computers, routers, or microchips.

Software Vendor

Company that develops software for sale.

Enterprise Applications

Company-wide applications, such as order processing systems, payroll systems, and company communications networks.

Distributed System

Company-wide system that connects one or more LANs or WANs. The capabilities of a distributed system depend on the power and capacity of the underlying data communication network.

Sever

Computer in a client/server design that supplies data, processing, and services to client workstations.

Procedural Security

Concerned with managerial policies and controls that ensure secure operations. Also called operational security.

Operational Security

Concerned with managerial policies and controls that ensure secure operations. Also called procedural security.

Operations Documentation

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

Plain Text

Data that is not encrypted.

Allocated Baseline

Documents the system at the end of the design phase and identifies any changes since the functional baseline. The allocated baseline includes testing and verification of all system requirements and features.

Functionally Dependent

Functional dependence is an important concept for understanding the 2NF. The field X is said to be functionally dependent on the field Y if the value of X depends on the value of Y. For example, an order date is dependent on an order number; for a particular order number, there is only one value for the order date. In contrast, the product description is not dependent on the order number. For a particular order number, there might be several product descriptions, one for each item ordered.

Client/Server Architecture

Generally refers to systems that divide processing between one or more networked clients and a central server. In a typical client/server system, the client handles the entire user interface, including data entry, data query, and screen presentation logic. The server stores the data and provides data access and database management functions. Application logic is divided in some manner between the server and the clients.

Security

Hardware, software, and procedural controls that safeguard and protect a system and its data from internal or external threats.

Wi-Max

IEEE 802.16 specifications, which are expected to enable wireless multimedia applications with a range of up to 30 miles.

Focus

In a sequence diagram, a focus indicates when an object sends or receives a message. It is indicated by a narrow vertical rectangle that covers the lifeline.

Lifeline

In a sequence diagram, a lifeline is used to represent the time during which the object above it is able to interact with the other objects in the use case. An X marks the end of a lifeline.

Control Couple

In a structure chart, a control couple shows a message, also called a flag, which one module sends to another.

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.

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.

Three-Tier Design

In a three-tier design, the user interface runs on the client and the data is stored on the server, just as in a two-tier design. A three-tier design also has a middle layer between the client and server that processes the client requests and translates them into data access commands that can be understood and carried out by the server.

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.

Scenarios

In an agile project, a real-world example of how users will interact with the system.

User Stories

In an agile project, a set of more refined requirements derived from features.

Storyboard

In an agile project, a simple graphic organizer that helps systems analysts visualize the status of a project.

Feature

In an agile project, a simple, high-level statement of a requirement. See epic.

Epic

In an agile project, a simple, high-level statement of a requirement. See feature.

Child

In inheritance, a child is the object that derives one or more attributes from another object, called the parent.

Parent

In inheritance, a parent is the object from which the other object, the child, derives one or more attributes.

Data Replication

In normal operating conditions, any transaction that occurs on the primary system must automatically propagate to the hot site.

Properties

In object-oriented (O-O) analysis, characteristics that objects inherit from their class or possess on their own.

Threat

In risk management, an internal or external or external entity that could endanger an asset.

Status Flag

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

User Design Phase

In this phase, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs.

Usability

In user interface design, includes user satisfaction, support for business functions, and system effectiveness.

User Interface

Includes screens, commands, controls, and features that enable users to interact more effectively with an application. See also graphical user interface (GUI).

Physical Storage

Information storage mechanism that is strictly hardware related, because it involves the process of reading and writing binary data to physical media, such as a hard drive, flash drive, or DVD.

Enterprise Computing

Information systems that support company-wide data management requirements, such as airline reservations or credit card billing systems.

User Documentation

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

Data Science

Interdisciplinary field that blends Computer Science, math and statistics, and business methods to analyze large datasets. Involves artificial intelligence, machine learning and predictive analytics, and visualization techniques.

Customer Relationship Management (CRM)

Many companies implement systems to integrate all customer-related events and transactions including marketing, sales, and customer service activities.

Documentation

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

Coupling

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

Risk Assessment

Measures the likelihood and impact of risks.

Output Control

Methods to maintain output integrity and security. For example, every report should include an appropriate title, report number or code, printing date, and time period covered. Reports should have pages that are numbered consecutively, identified as Page xx of xx, and the end of the report should be labeled clearly.

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.

Transference

One of four risk control strategies. In transference, risk is shifted to another asset or party, such as an insurance company.

Mitigation

One of four risk control strategies. Mitigation reduces the impact of a risk by carefully planning and preparation. For example, a company can prepare a disaster recovery plan to mitigate the effects of a natural disaster should one occur.

Wired Equivalent Privacy (WEP)

One of the earliest methods used to secure a wireless network, super - seded by WPA and WPA2.

Availability

One of the three main elements of system security: confidentiality, integrity, and availability (CIA). Availability ensures that authorized users have timely and reliable access to necessary information.

Confidentiality

One of the three main elements of system security: confidentiality, integrity, and availability (CIA). Confidentiality protects information from unauthorized discloser and safeguards privacy.

Integrity

One of the three main elements of system security: confidentiality, integrity, and availability (CIA). Integrity prevents unauthorized users from creating, modifying, or deleting information.

Maintenance Team

One or more systems analysts and programmers working on product maintenance issues together.

Output Security

Output security protects privacy rights and shields the organization's proprietary data from theft or unauthorized access.

Authorization Zone

Part of a form that contains any required signatures.

Internet Operating System

Part of the Web 2.0 model, an online computing environment created by online communities and services, based on layers of shared information that can contain text, sound bytes, images, and video clips.

Application

Part of the information system, an application handles the input, manages the processing logic, and provides the required output.

Intangible Benefits

Positive outcomes that are difficult to measure in dollars. However, intangible benefits can be very important in the calculation of economic feasibility. An example of an intangible benefit might be a new website that improves a company's image.

Tangible Benefits

Positive outcomes that can be measured in dollars. They can result from a decrease in expenses, an increase in revenues, or both.

CASE Tools

Powerful software used in computer-aided systems engineering (CASE) to help systems analysts develop and maintain information systems.

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.

Recovery Procedure

Process for restoring data and restarting a system after an interruption. Recovery procedures can be used to restore a file or database to its current state at the time of the last backup.

System Prototyping

Producing a full-featured, working model of the information system being developed.

Syntax Error

Programming language Grammer error.

Groupware

Programs that run on a network that enable users to share data, collaborate on projects, and work in teams. Also called workgroup software.

System Software

Programs that that control the computer, including the operating system, device drivers that communicate with hardware, and low-level utilities.

User Application

Programs that utilize standard business software, such as Microsoft Office, which has been configured in a specific manner to enhance user productivity.

Data Security

Protection of data from loss or damage and recovers data when it is lost or damaged.

Online Documentation

Provides immediate help when users have questions or encounter problems.

Business Support Systems

Provides job-related information support to users at all levels of a company.

Project Reporting

Providing regular progress reports to management, users, and the project team itself.

Option Button

Radio buttons that represent groups of options. The user can select only one option at a time; a selected option contains a black dot. See also radio button.

Dumpster Diving

Raiding desks or trash bins for valuable information.

Clickstream Storage

Recording web visitor behavior and traffic trends for later data mining use.

Logical Storage

Refers to information as seen through a user's eyes, regardless of how or where that information is organized or stored.

Business Case

Refers to the reasons, or justification, for a proposal.

Module

Related program code organized into small units that are easy to understand and maintain. A complex program could have hundreds or even thousands of modules.

Patch

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

Object

Represents a real person, place, event, or transaction.

Use Case

Represents the steps in a specific business function or process in UML.

Concatenated Key

See composite key.

Logical Structure

See control structure.

Data Item

See data element.

Data Store

See data repository.

Throwaway Prototyping

See design prototyping.

Glueware

See middleware.

Quality Attributes

See non-functional requirements.

Offshoring

See offshore outsourcing.

Code Review

See structured walk-through.

Usage Model

See transaction model.

Internet Business Services (IBSs)

Services that provide powerful web-based support for transactions such as order processing, billing, and customer relationship management.

Critical Path Method (CPM)

Shows a project as a network diagram. The activities are shown as vectors, and the events are displayed graphically as nodes. Although CPM developed separately from the Program Evaluation Review Technique (PERT), the two methods are essentially identical. See also PERT/CPM.

Storyboard

Sketches used during prototyping to show the general screen layout and design.

Mobile Device

Smartphones, tablets, and other computing devices that are not permanently tethered to a desk. They connect to the network wirelessly.

Application Software

Software programs, such as email, word processors, spreadsheets, and graphics packages, used by employees in typical office scenarios.

Middleware

Software that connects dissimilar applications and enables them to communicate and exchange data. For example, middleware can link a departmental database to a Web server that can be accessed by client computers via the Internet or a company intranet. See also glueware.

Middleware

Software that connects dissimilar applications and enables them to communicate and exchange data. For example, middleware can link a departmental database to a web server that can be accessed by client computers via the Internet or a company intranet.

Software Package

Software that is purchased or leased from another firm. A commercially produced software product, or family of products.

Open Source

Software that is supported by a large group of users and developers. The source code is made freely available.

Network Intrusion Detection System (NIDS)

Software that monitors network traffic to detect attempted intrusions or suspicious network traffic patterns, and sends alerts to network administrators. Can be helpful in documenting the efforts of attackers and analyzing network performance.

Data Administrator (DBA)

Someone who manages a DBMS. The DBA assesses overall requirements and maintains the database for the benefit of the entire organization rather than a single department or user.

Composite Key

Sometimes it is necessary for a primary key to consist of a combination of fields. In that case, the primary key is called a combination key, composite key, concatenated key, or multivalued key.

Multivalued Key

Sometimes it is necessary for a primary key to consist of a combination of fields. In that case, the primary key is called a combination key, composite key, concatenated key, or multivalued key.

Candidate Key

Sometimes it is possible to have a choice of fields or field combinations to use as the primary key. Any field that could serve as a primary key is called a candidate key.

Audit Fields

Special fields within data records to provide additional control or security information. Typical audit fields include the date the record was created or modified, the name of the user who performed the action, and the number of times the record has been accessed.

Table Design

Specifies fields and identifies the primary key in a particular table or file

Users

Stakeholders inside and outside the company who will interact with the system.

EBCDIC

Stands for Extended Binary Coded Decimal Interchange Code, a coding method used on mainframe computers and some high-capacity servers.

Legacy System

Term used to describe older systems that are typically less technologically advanced than currently available systems.

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.

PERT/CPM

The Program Evaluation Review Technique (PERT) was developed by the U.S. Navy to manage very complex projects, such as the construction of nuclear submarines. At approximately the same time, the Critical Path Method (CPM) was developed by private industry to meet similar project management needs. The important distinctions between the two methods have disappeared over time, and today the technique is called either PERT, CPM, or PERT/CPM.

Critical Thinking Skills

The ability to compare, classify, evaluate, recognize patterns, analyze cause and effect, and apply logic. Such skills are valued in the IT industry.

Traceability

The ability to follow a requirement backward to its origins and forward through the SDLC to link design documents, code fragments, and test artifacts.

Scaling on Demand

The ability to match network resources to needs at any given time; a feature of cloud computing. For example, during peak loads, additional cloud servers might come on line to automatically to support increased workloads.

Engaged Listening

The ability to really concentrate on what someone is saying and avoid the temptation to hear what is expected. Also includes noticing nonverbal communication.

Bandwidth

The amount of data that the system can handle in a fixed time period. Bandwidth requirements are expressed in bits per second (bps).

Slack Time

The amount of time by which an event can be late without delaying the project. The difference between latest completion time (LCT) and earliest completion time (ECT).

Person-Day

The amount of work that one person can complete in one day.

Clicks to Close

The average number of page views to accomplish a purchase or obtain desired information.

Partitioning

The breaking down of overall objectives into subsystems and modules.

Hub

The center of a star network. Switches in modern networks have largely replaced hubs.

Make or Buy

The choice between developing in-house software and purchasing software often is called a make or buy, or build or buy, decision.

Polymorphism

The concept that a message gives different meanings to different objects (e.g., a GOOD NIGHT message might produce different results depending if it is received by a child or the family dog).

Garbage In, Garbage Out (GIGO)

The concept that the quality of the output is only as good as the quality of the input.

Functional Baseline

The configuration of the system documented at the beginning of the project. It consists of all the necessary system requirements and design constraints.

Physical Topology

The connection structure of an actual network's cabling.

Supply Chain Management (SCM)

The coordination, integration, and management of materials, information, and finances as they move from suppliers to customers, both within and between companies. In a totally integrated supply chain, a customer order could cause a production planning system to schedule a work order, which in turn could trigger a call for certain parts from one or more suppliers.

Project Scheduling

The creation of a specific timetable to facilitate completion of a project. Also involves selecting and staffing the project team and assigning specific tasks to team members.

Legacy Data

The data associated with an older, less technologically advanced legacy system.

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.

Just-in-Time (JIT)

The exchange or delivery of information when and where it is needed. For example, just-in-time inventory systems rely on computer-to-computer data exchange to minimize unnecessary inventory.

Systems Implementation Phase

The fourth phase of SDLC. During this phase the new system is constructed, programs are written, tested, and documented, and the system is installed.

Parent Diagram

The higher or more top-level diagram in an exploded DFD.

Encapsulation

The idea that all data and methods are self-contained, as in a black box.

Economy of Scale

The inherent efficiency of high-volume processing on larger computers. Database design allows better utilization of hardware. If a company maintains an enterprise-wide database, processing is less expensive using a powerful mainframe server instead of using several smaller computers.

User Training Package

The main objective of a user training package is to show users how the system can help them perform their jobs.

User Interface (UI)

The mechanism through which the user interacts with the system. The user interface can be graphical, textual, aural, or a combination of different modes of interaction.

Prototyping

The method by which a prototype is developed. It involves a repetitive sequence of analysis, design, modeling, and testing. It is a common technique that can be used to design anything from a new home to a computer network.

Best-Case Estimate

The most optimistic outcome.

Input Control

The necessary measures to ensure that input data is correct, complete, and secure. A systems analyst must focus on input control during every phase of input design, starting with source documents that promote data accuracy and quality.

Business Process Outsourcing (BPO)

The outsourcing of a basic business process. See also outsourcing.

Pool

The overall diagram in BPMN.

Response Time

The overall time between a request for system activity and delivery of the response. In the typical online environment, response time is measured from the instant the user presses the ENTER key or clicks a mouse button until the requested screen display appears or printed output is ready.

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.

Point-of-Scale (POS)

The part of an information system that handles daily sales transactions and maintains the online inventory file.

Project Leader

The person charged with leading a project from a technical perspective.

Project Manager

The person charged with managing a project from an administrative perspective.

Project Coordinator

The person who handles administrative responsibilities for the development team and negotiates with users who might have conflicting requirements or want changes that would require additional time or expense.

Phased Operation

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

Form Layout

The physical appearance and placement of data on a form. Form layout makes the form easy to complete and provides enough space, both vertically and horizontally, for users to enter the data.

Hardware

The physical layer of the information system, to include computers, networks, communications equipment, and other technology-based infrastructure.

Pilot Operation

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

Global Outsourcing

The practice of shifting IT development, support, and operations to other countries.

Offshore Outsourcing

The practice of shifting IT development, support, and operations to other countries.

Offsiting

The practice of storing backup media away from the main business location, in order to mitigate the risk of a catastrophic disaster such as a flood, fire, or earthquake.

Project Creep

The process by which projects with very general scope definitions expand gradually, without specific authorization.

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 Analysis and Design

The process of developing information systems that effectively use hardware, software, data, processes, and people to support the company's business objectives.

Leveling

The process of drawing a series of increasingly detailed diagrams to reach the desired level of detail.

Backup

The process of saving a series of file or data copies to be retained for a specified period of time. Data can be backed up continuously, or at prescribed intervals.

Version Control

The process of tracking system release.

Object-Oriented Development (OOD)

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

Systems Analysis Phase

The second SDLC phase. The purpose of this phase is to build a logical model of the new system.

HTTP/2

The second major version of the network protocol used by the web. Released as a standard in 2015.

Domain

The set of values permitted for a data element.

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 of two or more programs that depend on each other.

Systems Design Phase

The third SDLC phase. The purpose of systems design is to create a blueprint for the new system that will satisfy all documented requirements, whether the system is being developed in-house or purchased as a package.

CIA Triangle

The three main elements of system security: confidentiality, integrity, and availability.

Project Triangle

The three major components of a project: cost, scope, and time. A project manager tries to find the optimal balance among these factors.

Fault Management

The timely detection and resolution of operational problems. Fault management includes monitoring a system for signs of trouble, logging all system failures, diagnosing the problem, and applying corrective action.

Absolute Date

The total number of days from some specific base date. To calculate the number of days between two absolute dates, subtract one date from the other. For example, using a base date of January 1, 1900, September 27, 2012, has an absolute data value of 41179 and July 13, 2011, has an absolute date of 40737. If the earlier date value is subtracted from the later one, the result is 442 days.

Net Present Value (NPV)

The total value of the benefits minus the total value of the costs, with both the costs and benefits being adjusted to reflect the point in time at which they occur.

Waterfall Model

The traditional model of software development. A graph that depicts the result of each SDLC phase flowing down into the next phase.

Application Logic

The underlying business rules or logic for an application.

Switchboard

The use of command buttons in a user interface to enable users to navigate a system and select from groups of related tasks.

Graphical User Interface (GUI)

The use of graphical objects and techniques allowing users to communicate with a system. A well-designed GUI can help users learn a new system rapidly and work with the system effectively.

Network Topology

The way a network is configured. LAN and WAN networks typically are arranged in one of four common patterns: hierarchical, bus, star, and ring.

Key Fields

Used during the systems design phase to organize, access, and maintain data structures. The four types of key fields are primary keys, candidate keys, foreign keys, and secondary keys.

Requirements Engineering

Used in the systems planning phase of the SDLC. It involves fact-finding to describe the current system and identify the requirements for the new system.

User Rights

User-specific privileges that determine the type of access a user has to a database, file, or direc- tory. Also called permissions.

Permissions

User-specific privileges that determine the type of access a user has to a database, file, or directory. Also called user rights.

Virtual Private Network (VPN)

Uses a public network to connect remote users securely. Allows a remote client to use a special key exchange that must be authenticated by the VPN.

Alphabetic Code

Uses alphabet letters to distinguish one item from another based on a category, an abbreviation, or an easy-to-remember value, called a mnemonic code.

Software Reengineering

Uses analytical techniques to identify potential quality and performance improvements in an information system.

Technical Feasibility

When an organization has the resources to develop or purchase, install, and operate the system.

Critical Risk

When risks are categorized and prioritized, critical risks (those with the highest vulnerability and impact ratings) head the list.

Client

Workstation that users interact within a client/server design. These workstations, or computers, are supplied data, processing services, or other support from other computers, called servers.


Kaugnay na mga set ng pag-aaral

Yoder-Wise Ch 3 Legal/Ethical Issues

View Set

Pharmacology, Ch. 3: Toxic Effects of Drugs

View Set

Chapter: Basic Insurance Concepts and Principles

View Set

Chapter 16 Control Systems and Quality Management: Techniques for Enhancing Organizational Effectiveness

View Set

NX BASIC DESIGN KNOWLEDGE CHECKS

View Set