Key Terms - Part 1

Question 1

Abstract Class

Answer 1

A class that describes a category or set of objects, but never includes individual objects or instances. It exists so subclasses can inherit from it.

Question 2

Activity Diagrams

Answer 2

A UML diagram that describes user (or system) activities, the person who does each activity, and the sequential flow of these activities.

Question 3

Predictive Approach to the SDLC

Answer 3

An approach that assumes the project can be planned in advance, and that the new information system can be developed according to that plan.

Question 4

Adaptive Approach to the SDLC

Answer 4

An approach that assumes that the project must be more flexible and adapt to changing needs as the project progresses.

Question 5

Alpha Version

Answer 5

A test version that is incomplete, but ready for some level of rigorous integration or usability testing.

Question 6

Beta Version

Answer 6

A test version that is stable enough to be tested by end users over an extended period of time.

Question 7

Client-Server Architecture

Answer 7

A computer network configuration with users’ computers and a central computer that provide common services.

Question 8

Component Diagram

Answer 8

A UML implementation diagram that shows the overall system architecture and the logical components within it. It identifies the logical, reusable, and transportable system components that define the system architecture.

Question 9

Communication Diagram

Answer 9

A UML interaction diagram that emphasizes the objects that send and receive messages for a specific use case.

Question 10

Data Access Class

Answer 10

A class that is used to retrieve data from and send data to a database. It is used to implement the bridge between data stored in program objects, and the data existing in the relational database.

Question 11

Database Normalization

Answer 11

A formal technique for evaluating and improving the quality of a relational database schema. It determines whether a database is flexible, and whether it contains “wrong” kinds of redundancy.

Question 12

Database Management System (DBMS)

Answer 12

A system software component that manages and controls one or more databases.

Question 13

Deployment

Answer 13

The final phase of the SDLC, in which the solution, either a system or a subsystem, is put into operation.

Question 14

Design Pattern

Answer 14

Standard design techniques and templates that are widely recognized as good practice. They were identified by the Gang of Four (GoF) and are used in object-oriented programming.

Question 15

Dialog Metaphor

Answer 15

A metaphor for human-computer interaction, in which user and computer accomplish a task by engaging in a conversation or dialog via text voice, or tools such as labeled buttons.

Question 16

Digital Signature

Answer 16

A technique in which a document is encrypted by using a private key to verify who wrote the document.

Question 17

Encryption

Answer 17

The process of altering data so unauthorized users can’t view them.

Question 18

Decryption

Answer 18

The process of converting encrypted data back to their original state.

Question 19

End Users

Answer 19

Individuals or groups of individuals who use an information system to accomplish specific tasks or goals. They interact directly with the system and use it to carry out their work or activities.

Question 20

Event

Answer 20

Something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system.

Question 21

Human-Computer Interaction (HCI)

Answer 21

The field of study that focuses on optimizing how users and computers interact by designing interactive computer interfaces that satisfy users’ needs.

Question 22

Integrity Control

Answer 22

A control that rejects invalid data inputs, prevents unauthorized data outputs, and protects data and programs against accidental or malicious tampering.

Question 23

Object

Answer 23

A “thing” in an information system that responds to messages by executing functions or methods.

Question 24

Object-Oriented Design (OOD)

Answer 24

Process by which a set of detailed object-oriented design models are built and then used by the programmers to write and test the new system.

Question 25

Model

Answer 25

Representation of some aspect of a system.

Question 26

Pair Programming

Answer 26

Extreme Programming (XP) practice in which two programmers work together on designing, coding, and testing software.

Question 27

Perfect Technology Assumption

Answer 27

The assumption that a system runs under perfect operating and technological conditions.

Question 28

Project

Answer 28

A planned undertaking that has a beginning and an end, that produces some definite result.

Question 29

Relational Database

Answer 29

A database that stores information in tables or relations, with rows representing unique records and columns representing data elements.

Question 30

Requirements

Answer 30

In a system, the activities that the system must perform or support, and the constraints that the system must meet.

Question 31

Requirements Determination

Answer 31

The process of identifying, analyzing, and documenting the needs and constraints of stakeholders for a new or improved system.

Question 32

Scrum

Answer 32

An adaptive software development methodology of which the objective is to be quick, agile, intense, and go the entire distance.

Question 33

Systems Development Life Cycle (SDLC)

Answer 33

The entire process consisting of all activities required to build, launch, and maintain an information system.

Question 34

Security Controls

Answer 34

The controls that protect the assets of an organization from all threats, with a primary focus on external threats.

Question 35

Stakeholders

Answer 35

Individuals who have an interest in the successful implementation of the system.

Question 36

System

Answer 36

An information system is a set of interrelated computer components that collects, processes, stores, and provides as output the information needed to complete business tasks.

Question 37

System Interface

Answer 37

Input or output that requires minimal human interaction.

Question 38

System Vision Document

Answer 38

A document to help define the scope of a new system.

Question 39

System Development Methodology

Answer 39

A set of comprehensive guidelines for the SDLC that includes specific models, tools, and techniques.

Question 40

Top-Down Development

Answer 40

A development order that implements top-level modules first.

Question 41

Botton-Up Development

Answer 41

A development that implements low-level detailed modules first.

Question 42

Three-Layer Architecture

Answer 42

A client-server architecture that divides an application into a view layer, a business logic layer, and a data layer.

Question 43

Unified Modeling Language (UML)

Answer 43

Standard set of model constructs and notations defined by the Object Management Group.

Question 44

Unified Process (UP)

Answer 44

Object-oriented system development methodology that uses UML for system models and describes a new, adaptive SDLC.

Question 45

Unit Testing

Answer 45

Test of an individual method, class, or component before it is integrated with other software.

Question 46

Usability Test

Answer 46

A test to determine whether a method, class, subsystem, or system meets user requirements.

Question 47

Use Case

Answer 47

An activity that the system performs, usually in response to a request by a user.

Question 48

Use Case Realization

Answer 48

The process of elaborating the detailed design with interaction diagrams for a particular use case.

Question 49

User Goal Technique

Answer 49

A technique to identify use cases by determining what specific goals or objectives must be completed by a user.

Question 50

User Interface

Answer 50

System interfaces (inputs and outputs) that more directly involve a system user.