CISM 11 Final

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/83

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

84 Terms

1
New cards

Tangible Costs

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

2
New cards

Intangible Costs

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

3
New cards

SWOT Analysis

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

4
New cards

Business Profile

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

5
New cards

Business Model

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

6
New cards

Logical Model

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

7
New cards

Physical Model

A model that describes how a system will be constructed.

8
New cards

Process Model

is a formal representation of the steps, stages, or activities in a process, often used to analyze, design, implement, or optimize workflows

9
New cards

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. (9.5.2)

10
New cards

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. (9.5.2)

11
New cards

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. (9.5.2)

12
New cards

Data Normalization

the process by which analysts identify and correct inherent problems and complexities in their record designs.(9.6)

13
New cards

1NF

A record is said to be in 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).(9.6.2)

14
New cards

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.(9.6.3)

15
New cards

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.(9.6.4)

16
New cards

DBMS

Database Management System: A collection of tools, features, and interfaces that enables users to add, update, manage, access, and analyze data in a database. (9.1.3)

17
New cards

Data Warehouse

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

18
New cards

data repository

A database that serves as a central storage location for all information about a system being developed.

19
New cards

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.(9.8.1)

20
New cards

Data Structures

A framework for organizing, storing, and managing data. (9.1.1)

21
New cards

File oriented System

Also called a file processing system, stores and manages data in one or more separate files.

22
New cards

Relational Database

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

23
New cards

Sequence Diagram

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

24
New cards

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.

25
New cards

UML notations

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.(4.7.3)

26
New cards

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. (7.2)

27
New cards

Network Models

A network allows the sharing of hardware, software, and data resources in order to reduce expenses and provide more capability to users.

28
New cards

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.(10.7.2)

29
New cards

Physical Topology

The connection structure of an actual network's cabling.(10.7.2)

30
New cards

Logical topology

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

31
New cards

Hierarchical 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.

32
New cards

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.

33
New cards

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.

34
New cards

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.

35
New cards

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.

36
New cards

Benchmark Testing

A measure of the time a package takes to process a certain number of transactions. (7.8-Step 3)

37
New cards

Corrective Maintenance

Changes to the system to fix errors

38
New cards

Adaptive Maintenance

Adds new capability and enhancements to an existing system.

39
New cards

Perfective Maintenance

Changes to a system to improve efficiency

40
New cards

Preventive Maintenance

41
New cards

Physical Security

Concerns the physical environment including IT resources and people throughout the company. Special attention must be paid to critical equipment located in operations centers, where servers, network hardware, and related equipment operate.

42
New cards

Network Security

To provide security for network traffic, data can be encrypted, which refers to a process of encoding the data so it cannot be accessed without authorization.

43
New cards

Application Security

Security to protect all server-based applications. Requires an understanding of services, hardening, application permissions, input validation techniques, software patches and updates, and software logs.

44
New cards

File Security

Computer configuration settings, users' personal information, and other sensitive data are stored in files.

45
New cards

User Security

User security involves the identification of system users and consideration of user-related security issues.

46
New cards

Procedural Security

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

47
New cards

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.

48
New cards

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.

49
New cards

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.

50
New cards

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.

51
New cards

Maintenance Activities

Include changing programs, procedures, or documentation to ensure correct system performance. Adapting the system to changing requirements, and making the system operate more efficiently. Those needs are met by corrective, adaptive, perfective, and preventive maintenance.

52
New cards

System Administrator

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

53
New cards

System Analyst:

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

54
New cards

Programmers

A designation for positions that require a combination of systems analysis and programming skills.

55
New cards

Thin Client

A design that locates all or most of the processing logic at the server. (10.3.1)

56
New cards

Thick Client

A system design that locates most or all of the application processing logic at the client. (10.3.1)

57
New cards

Structure Charts

A top-down representation of business functions, and processes. Also called an FDD (11.3.1)

58
New cards

Data Processing Center

A central location where physical data was delivered ro 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.

59
New cards

Mainframes

A system design where the server performs all the processing.

60
New cards

Software Development

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

61
New cards

DFD

Graphical representation of the system, showing it stores, processes, and transforms data into useful information.

62
New cards

FDD : Functional Decomposition Diagram

a top-down representation of business functions and processes. Also called a structure chart.(4.7.2)

63
New cards

ERD (Entity Relationship Diagram)

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

64
New cards

Open Systems Interconnection Model

Describes how 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.

65
New cards

Preliminary investigation reports

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

66
New cards

Gigabits per second

: A bandwidth or throughput measurement. (10.8.1)

67
New cards

Bandwidth

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

68
New cards

System Planning

During this phase, the systems project gets started. The project proposal is evaluated to determine its feasibility. (1.7.1)

69
New cards

System Analysis

The purpose of this phase is to build a logical model of the new system. (1.7.1)

70
New cards

Systems Design

The purpose of [THIS] 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. (1.7.1)

71
New cards

Systems Implementation

During this phase, the new system is constructed—programs are written, tested, and documented, and the system is installed. (1.7.1)

72
New cards

Systems Security and Support

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

73
New cards

Primary Key

is a field or combination of fields that uniquely and minimally identifies a particular member of an entity (9.4.2)

74
New cards

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. (9.4.2)

75
New cards

Composite Key

Sometimes it is necessary for a primary key to consist of a combination of fields. (9.4.2)

76
New cards

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 [THIS] (9.4.2)

77
New cards

Feasibility Study

An initial investigation to clearly identify the nature and scope of the business opportunity or problem. Also called the Preliminary investigation.(1.7.1)

78
New cards

Middleware

[THIS] is sometimes called glueware because it is used to connect two or more software components in a federated system architecture. (10.3.3). Software that connects dissimilar applications and enables them to communicate and exchange data. For example, [THIS] can link a departmental database to a Web server that can be accessed by client computers via the Internet or a company intranet. (7.1.2)

79
New cards

80
New cards

Data Manipulation Language

[THIS] controls database operations, including storing, retrieving, updating, and deleting data. (9.2.1)

81
New cards

Schema

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

82
New cards

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. (9.2.2)

83
New cards

Client/Server

Generally refers to systems that divide processing between one or more networked clients and a central server. (10.3)

84
New cards

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. (10.3)