Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

IT261 Systems Design - Illinois State University > chapter-4-5-6-10-examreviews > Flashcards

chapter-4-5-6-10-examreviews Flashcards

1
Q

use case

A

an activity the system performs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

user goal technique

A

an approach for identifying use cases in which an analyst talks to all users to get them to describe their goals in using the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Event

A

an occurrence at a specific time and place that can be described and is worth remembering by the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

CRUD technique

A

Create - Read/Report - Update - Delete an approach in which an analyst looks at each type of data and includes use cases that create the data - read or report on the data - updates the data - delete the data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Event Decomposition

A

an analysis technique that focuses on identifying the events to which a system must respond and then determining how the system must respond.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

External Event

A

An event that occurs outside the system - usually initiated by an external agent or actor

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Temporal Event

A

an event that occurs as a result of reaching a point in time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

state event

A

an event that occurs when something happens inside the system that triggers the need for processing. (internal events)i.e. sale of an item results in low stock - inventory reorder must take place

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Event table

A

a catalog of use cases that lists events in roes and key pieces of information about each event in columns

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Trigger

A

a signal that tells the system that an event has occurred - either the arrival of data needing processing or a point in time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Source

A

an external agent or actor that supplies data to the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

response

A

an output produced by the system that goes to a destination

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

destination

A

an external agent or actor that receives the data from the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

use case description

A

a description that lists the processing details for a use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Brief Description

A

short paragraph of the use case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Intermediate Description

A

Title - main flow & exception conditions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Fully developed description

A

Contains use case name-scenario-triggering event-brief description-actors-related use cases - stakeholders -preconditions -postconditions -flow of activities - exception conditions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

things

A

tangible - roles - organizational - devices - sites/locations - incidents/events/or interactions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

relationship

A

a naturally occurring association among specific things such as an order is placed by a customer and an employee works in a department

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Attribute

A

one piece of specific information about a thing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

cardinality

A

the number of associations that occur among specific things - 1:1 - 1:M - M:M

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Entity Relationship Diagram ERD

A

The squares with the zero/one to many lines

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Analysis Activities

A

Gather info - Define Sys Req - Prioritize Requirements - Prototype for Feasibility & discovery - Generate & evaluation alternatives - Review recommendations with Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Gathering Info

A

interviewing users - watching users - review planning docs - review policy statements - study documentation from existing system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Define System Requirements

A

Uses modeling to help define system requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Prioritize Requirements

A

Identify the most essential requirements of the new system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Prototype for Feasibility and Discovery

A

used to better understand the user’s needs. Checks the feasibility of certain approaches to the business need.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Generate and Evaluate Alternatives

A

Many alternatives exist that will need to be evaluated for the best match

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Review Recommendations with Management

A

When all other analysis activities are complete the review with management will happen to decide if best to proceed or not

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Functional Requirements

A

a system requirement that describes and activity or process that the system must perform

31
Q

Non-functional requirement

A

other than activities -such as technology-performance - usability - reliability and security

32
Q

Models

A

representation of some aspect of the system being built

33
Q

Mathematical Model

A

series of formulas that describe technical aspects of a system.

34
Q

Descriptive Models

A

narrative memos - reports or lists that describe some aspect of a system.

35
Q

Graphical Model

A

diagrams and schematic representations of some aspect of a system

36
Q

Logical Model

A

Any model that shows what the system is required to do without committing to any one technology

37
Q

Physical Model

A

Any model that shows how the system will actually be implemented

38
Q

Stakeholders

A

all the people who have an interest in the success of a new systemthe usersthe clients (paying for it)the technical staff

39
Q

Information Gathering Techniques

A

questionnaires - interview users - review existing documentation - observe business processes - research vendor solutions - conduct JAD sessions

40
Q

Traditional approach

A

System of processes, processes interact with data entities, processes accept inputs and produce outputs.

41
Q

OO approach

A

System is collection of interacting object, objects interact with people and each other, objects send and respond to messages.

42
Q

Data flow diagram DFD

A

Represents sys requirements as processes, external agents, data flows, and data stores

43
Q

Level of abstraction

A

Any modeling technique that breaks the system down into a hierarchical set of increasingly more detailed models.

44
Q

DFD fragment

A

A DFD that represents the system response to one event withina single process symbol

45
Q

Physical and logical DFDs

A

DFDs can be either physical system model, a logical system model or a combination of both.

46
Q

Black hole

A

Process or data store with a data input that is never used to produce a data output.

47
Q

Miracle

A

Process or data store with a data element that is created out of nothing.

48
Q

Rule 7+-2

A

Modeling rule that limits the number of components or connections to no more than nine

49
Q

Minimization of interfaces

A

Simplicity by limiting the number of of connections between model components.

50
Q

Structured English

A

Writing process specifications that combines structured programming techniques with narrative English.

51
Q

Decision table

A

A table representation of processing logic containing decision variables, decision variable values and actions or formulas

52
Q

Decision tree

A

A graphical description of process logic that uses lines organized like branches of a tree.

53
Q

Data flow definition

A

Text description of a data flows content and internal structure.

54
Q

Data store definitions

A

Data store on the DFD represents a data entity on the ERD no separate definition iOS usually needed. If no ERD link analyst defines data store as a collection of elements.

55
Q

Data element definitions

A

Describes a data type such as string, integer, floating point, or Boolean.

56
Q

Activity-location matrix

A

A table that describes the relationship between processes and the locations in which they are performed.

57
Q

Activity data matrix

A

A table that describes stored data entities the locations of which they are accessed, and the nature of the accesses.

58
Q

Automation System Boundary

A

partitions the data flow diagram processes into manual processes and those that are to be included in the computer system

59
Q

System Flow Chart

A

Representation of various computer programs, files, databases, and associated manual procedures that make up a complete system.

60
Q

Structure Chart

A

hierarchical diagram showing the relationships between the modules of a computer program

61
Q

Data Couples

A

the individual data items that are passed between modules in a program call.

62
Q

Transaction Analysis

A

the development of a structure chart based on a DFD that describes the processing for several types of transactions

63
Q

Transform Analysis

A

the development of a structure chart based on a DFD that describes the input-process-output data flow

64
Q

Module coupling

A

the manner in which modules relate to each other; the preferred method is data coupling

65
Q

Automation System Boundary

A

partitions the data flow diagram processes into manual processes and those that are to be included in the computer system

66
Q

Module Cohesion

A

a measure of the internal strength of a module

67
Q

Flowcharting

A

is a visual method that uses boxes and lines to describe the flow of logic in a program.

68
Q

Structured English

A

describes the structure of the program in regular english

69
Q

pseudocode

A

closer to programming language

70
Q

three layer design

A

division of application software into the view, business logic and data access layers

71
Q

viewer layer

A

executing on a client workstation, the user’s view

72
Q

business logic layer

A

java server side components

73
Q

data layer

A

oracle dbms - talks to the databases

IT261 Systems Design - Illinois State University (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions