4620 Ch 4 & 5

Front 1

Logical model

Back 1

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

Front 2

Physical model

Back 2

model that shows how the system will actually be implemented

Front 3

System requirements

Back 3

specifications that define the functions to be provided by a system

Front 4

functional requirements

Back 4

system requirement that describes an activity or process that the system must perform

Front 5

Nonfunctional requirement

Back 5

characteristics of the system other than activities it must perform or support such as technology, performance, usability, reliability and security

Front 6

technical requirement

Back 6

system requirement that describes an operational characteristic related to an organization's environment, hardware and software

Front 7

performance requirement

Back 7

system requirement that describes an operational characteristic related to workload measures, such as throughput and response time

Front 8

usability requirement

Back 8

system requirement that describes an operational characteristic related to users, such as the user interface, work procedures, online help and documentation

Front 9

reliability requirement

Back 9

system requirement that describes the dependability of a system, such as how it handles service outages, incorrect processing, and error detection and recovery

Front 10

security and recovery

Back 10

system requirement that describes user access to certain functions and the conditions under which access is granted

Front 11

mathematical model:

Back 11

series of formulas that describe technical aspects of a system

Front 12

descriptive model:

Back 12

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

Front 13

graphical model:

Back 13

diagrams and schematic representations of some aspect of a system

Front 14

stakeholders:

Back 14

all the people who have interest in the success of a system

Front 15

transaction:

Back 15

single occurrence of a piece of work or an activity done in an organization

Front 16

workflow:

Back 16

sequence of steps to process a business transaction

Front 17

activity diagram:

Back 17

type of workflow diagram that describes the user activities and their sequential flow

Front 18

synchronization bar:

Back 18

a symbol in an activity diagram to control the splitting of uniting of sequential paths

Front 19

swimlane:

Back 19

rectangular area on an activity diagram representing the activities of a single agent

Front 20

prototype:

Back 20

preliminary working model of a larger system

Front 21

mock-up

Back 21

example of a final product that is for viewing only and is not executable

Front 22

close-ended questions

Back 22

questions that have simple, definitive answers

Front 23

open-ended questions

Back 23

questions that require discussion and do not necessarily have a simple, short answer

Front 24

joint application design (JAD)

Back 24

technique to define requirements or design a system in a single session by having all necessary people participate

Front 25

group support system (GSS)

Back 25

computer support system that enables multiple people to participate with comments at the same time each from their own computer

Front 26

structured walkthrough

Back 26

review of the findings from your investigation and of the models built based on those findings

Front 27

use case

Back 27

activity the system performs

Front 28

user goal technique

Back 28

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

Front 29

CRUD technique

Back 29

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, and delete the data

Front 30

elementary business process (EBP)

Back 30

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

Front 31

event

Back 31

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

Front 32

event decomposition

Back 32

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

Front 33

external event

Back 33

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

Front 34

temporal event

Back 34

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

Front 35

state event

Back 35

event that occurs when something happens inside the system that triggers the need for processing

Front 36

system controls

Back 36

checks for safety procedures put in place to protect the integrity of the system

Front 37

perfect technology assumption

Back 37

assumption that events should be included during analysis only if the system would be required to respond under perfect conditions

Front 38

event table

Back 38

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

Front 39

trigger

Back 39

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

Front 40

source

Back 40

external agent or actor that supplies data to the system

Front 41

response

Back 41

output, produced by the system, that goes to a destination

Front 42

destination

Back 42

external agent or actor that receives data from the system

Front 43

use case description

Back 43

description that lists the processing details for a use case

Front 44

actor

Back 44

in UML diagrams, a person who uses the system

Front 45

scenario or use case instance

Back 45

unique set of internal activities within a use case that represents a unique path through the use case

Front 46

preconditions

Back 46

conditions that must be true before a use case begins

Front 47

post conditions

Back 47

conditions that must be true upon completion of a use case

Front 48

relationship

Back 48

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

Front 49

cardinality

Back 49

number of associations that occur among specific thing, such as customer places many orders

Front 50

multiplicity

Back 50

synonym for cardinality (used with the object-oriented approach as defined by UML)

Front 51

binary relationships

Back 51

relationships between two different types of things, such as a customer and an order

Front 52

unary (recursive) relationship

Back 52

relationship among two things of the same type, such as one person being married to another

Front 53

ternary relationship

Back 53

relationship among three different types of things

Front 54

n-ary relationship

Back 54

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

Front 55

attribute

Back 55

one piece of specific information about a thing

Front 56

identifier

Back 56

an attribute that uniquely identifies a thing (key)

Front 57

compound attribute

Back 57

attribute that contains a collection of related attributes

Front 58

data entities

Back 58

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

Front 59

associative entity

Back 59

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

Front 60

generalization/specialization hierarchies

Back 60

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

Front 61

inheritance

Back 61

concept that allows subclasses to share characteristics of their superclasses

Front 62

whole-part hierarchies

Back 62

hierarchies that structure classes according to their associated components

Front 63

aggregation

Back 63

whole-part relationship between an object and its parts

Front 64

composition

Back 64

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