Systems Design Chapter 05 Flashcards

1
Q

Binary Relationships

A

Relationship between two different types of things - i.e. customer and an order

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

Unary Relationship (recursive)

A

Relationship among two things of the same type - such as one person married to another person

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

Ternary Relationship

A

Relationship among three different types of things

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

n-ary Relationship

A

Relationship among n (any number of) different types of things

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
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
6
Q

identifier key

A

an attribute that uniquely identifies a thing - (primary key in db)

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

compound attribute

A

attribute that contains a collection of related attributes

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

multiplicity

A

a synonym for cardinality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
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
10
Q

Data Entities

A

things about which the system needs to store information in the traditional approach to information systems

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
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
12
Q

Associative Entity

A

A data entity that represents a many-to-many relationship between two other data entities

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

Generalization/Specialization hierarchies

A

hierarchies that structure or rank classes from the more general superclass to the more specialized subclasses; sometimes called inheritance hierarchies

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

inheritance

A

a concept that allows subclasses to share characteristics of their superclasses

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

whole-part hierarchies

A

hierarchies that structure classes according to their components

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

aggregation

A

whole-part relationship between an object and its parts

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

composition

A

whole-part relationship in which the parts cannot be dissociated from the object

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

use case

A

an activity the system performs

19
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

20
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

21
Q

Elementary business process EBP

A

A task that is performed by one person - in one place - in response to a business event; it adds measureable business value and leaves the system and its data in a consistent state

22
Q

Event

A

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

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

24
Q

External Event

A

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

25
Temporal Event
an event that occurs as a result of reaching a point in time
26
state event
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
27
System controls
checks or safety procedures put in place to protect the integrity of the system
28
perfect technology assumption
the assumption that events should be included during analysis only if the system would be required to respond under perfect conditions.
29
Event table
a catalog of use cases that lists events in rows and key pieces of information about each event in columns. Event/Trigger/Source/Use Case/Response/Destination
30
Trigger
a signal that tells the system that an event has occurred - either the arrival of data needing processing or a point in time
31
Source
an external agent or actor that supplies data to the system
32
response
an output produced by the system that goes to a destination
33
destination
an external agent or actor that receives the data from the system
34
use case description
a description that lists the processing details for a use case
35
actor
in UML diagrams a person who uses the system
36
Scenario or use case instance
a unique set of internal activities within a use case that represents a unique path through the use case
37
Brief Description
short paragraph of the use case
38
Intermediate Description
Title - main flow & exception conditions
39
Fully developed description
Contains use case name-scenario-triggering event-brief description-actors-related use cases - stakeholders -preconditions -postconditions -flow of activities - exception conditions.
40
pre-conditions
conditions that must be true before a use case begins
41
postconditions
conditions that must be true upon completion of the use case
42
things
tangible - roles - organizational - devices - sites/locations - incidents/events/or interactions
43
relationship
a naturally occurring association among specific things such as an order is placed by a customer and an employee works in a department