soft eng prefinal

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/29

encourage image

There's no tags or description

Looks like no tags are added yet.

30 Terms

1
New cards

Systems design

Those system development activities that enable a person to describe in detail how the resulting information system will actually be implemented.

2
New cards

Systems analysis

Those system development activities that enable a person to understand and specify what the new system should accomplish.

3
New cards

Analysis objective

Understand and specify what the new system will accomplish.

4
New cards

Design objective

Describe in detail how the new system will be implemented.

5
New cards

Implementation objective

Build a new system that fulfills user needs.

6
New cards

Environment

Consists of two key elements for information system design: external systems and technology architecture.

7
New cards

Technology architecture

The set of computing hardware, network hardware and topology, and software employed by an organization.

8
New cards

Application component

A well-defined unit of a software that performs one or more specific tasks and hides complex details.

9
New cards

Database

An integral part of every computer information system containing the information itself, most often structured as a relational database consisting of dozens or hundreds of interacting tables.

10
New cards

Controls

Mechanisms and procedures that are built into a system to safeguard the system and the information within it.

11
New cards

Integrity controls

Controls that reject invalid data inputs, prevent unauthorized data outputs, and protect data and programs against accidental or malicious tampering.

12
New cards

Input controls

Controls that prevent invalid or erroneous data from entering the system.

13
New cards

Value limit control

Controls that check numeric data input to ensure that the value is reasonable.

14
New cards

Completeness control

Controls that ensure that all required data values describing an object or transaction are present.

15
New cards

Data validation controls

Controls that ensure that numeric fields that contain codes or identifiers are correct.

16
New cards

Field combination controls

Controls that review a combination of data inputs to ensure that the correct data are entered.

17
New cards

Output controls

Controls that ensure that output arrives at the proper destination and is accurate, current, and complete.

18
New cards

Discarded output control

Physical control of discarded printed outputs containing sensitive data (such as shredding or burning) to prevent unauthorized access.

19
New cards

Program access controls

Controls that restrict which users can access specific programs and program functions, usually via a username and password.

20
New cards

Redundancy, backup, and recovery

Procedures designed to protect software and data from hardware failure and catastrophes like fire, flood, and malicious destruction.

21
New cards

Backup procedures

Procedures that make partial or full copies of a file system (data and software) or a database to removable storage media or off-site servers.

22
New cards

Recovery procedures

Procedures that read off-site copies and replicate their contents to a server that can provide access to programs and users.

23
New cards

Fraud triangle

A model of fraud that states that opportunity, motivation, and rationalization must all exist for a fraud to occur.

24
New cards

Opportunity

The ability of a person to take actions that perpetrate a fraud.

25
New cards

Motivation

A desire or need for the results of the fraud.

26
New cards

Rationalization

An excuse for committing the fraud or an intention to "undo" the fraud in the future.

27
New cards

CRUD technique

A technique to validate a use case by verifying that all needed use cases (Create, Read/Report, Update, Delete) have been identified to maintain the data represented by a domain class.

28
New cards

CRUD

An acronym for Create, Read or Report, Update, and Delete, often used concerning database management.

29
New cards

Domain model class diagram

A primary requirements model that identifies all the domain classes required in the new system and is used to design the database.

30
New cards

Use case diagram

A primary requirements model used to capture the new system's process and get an idea of its total scope.