Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
64 Cards in this Set
- Front
- Back
Logical model
|
any model that shows what the system is required to do without committing to any one technology
|
|
Physical model
|
model that shows how the system will actually be implemented
|
|
System requirements
|
specifications that define the functions to be provided by a system
|
|
functional requirements
|
system requirement that describes an activity or process that the system must perform
|
|
Nonfunctional requirement
|
characteristics of the system other than activities it must perform or support such as technology, performance, usability, reliability and security
|
|
technical requirement
|
system requirement that describes an operational characteristic related to an organization's environment, hardware and software
|
|
performance requirement
|
system requirement that describes an operational characteristic related to workload measures, such as throughput and response time
|
|
usability requirement
|
system requirement that describes an operational characteristic related to users, such as the user interface, work procedures, online help and documentation
|
|
reliability requirement
|
system requirement that describes the dependability of a system, such as how it handles service outages, incorrect processing, and error detection and recovery
|
|
security and recovery
|
system requirement that describes user access to certain functions and the conditions under which access is granted
|
|
mathematical model:
|
series of formulas that describe technical aspects of a system
|
|
descriptive model:
|
narrative memos, reports, or lists that describe some aspect of a system
|
|
graphical model:
|
diagrams and schematic representations of some aspect of a system
|
|
stakeholders:
|
all the people who have interest in the success of a system
|
|
transaction:
|
single occurrence of a piece of work or an activity done in an organization
|
|
workflow:
|
sequence of steps to process a business transaction
|
|
activity diagram:
|
type of workflow diagram that describes the user activities and their sequential flow
|
|
synchronization bar:
|
a symbol in an activity diagram to control the splitting of uniting of sequential paths
|
|
swimlane:
|
rectangular area on an activity diagram representing the activities of a single agent
|
|
prototype:
|
preliminary working model of a larger system
|
|
mock-up
|
example of a final product that is for viewing only and is not executable
|
|
close-ended questions
|
questions that have simple, definitive answers
|
|
open-ended questions
|
questions that require discussion and do not necessarily have a simple, short answer
|
|
joint application design (JAD)
|
technique to define requirements or design a system in a single session by having all necessary people participate
|
|
group support system (GSS)
|
computer support system that enables multiple people to participate with comments at the same time each from their own computer
|
|
structured walkthrough
|
review of the findings from your investigation and of the models built based on those findings
|
|
use case
|
activity the system performs
|
|
user goal technique
|
approach for identifying use cases in which an analyst talks to all users to get their goals in using the system
|
|
CRUD technique
|
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
|
|
elementary business process (EBP)
|
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
|
|
event
|
an occurrence at a specific time and place that can be described and is worth remembering
|
|
event decomposition
|
analysis technique that focuses on identifying the events to which a system must respond and then determining how the system must respond
|
|
external event
|
event that occurs outside the system, usually initiated by an external agent or actor
|
|
temporal event
|
an event that occurs as a result of reaching a point in time
|
|
state event
|
event that occurs when something happens inside the system that triggers the need for processing
|
|
system controls
|
checks for safety procedures put in place to protect the integrity of the system
|
|
perfect technology assumption
|
assumption that events should be included during analysis only if the system would be required to respond under perfect conditions
|
|
event table
|
catalog of use cases that lists events in rows and key pieces of information about each event in columns
|
|
trigger
|
signal that tells the system that an event has occurred, either the arrival of data needing processing or a point in time
|
|
source
|
external agent or actor that supplies data to the system
|
|
response
|
output, produced by the system, that goes to a destination
|
|
destination
|
external agent or actor that receives data from the system
|
|
use case description
|
description that lists the processing details for a use case
|
|
actor
|
in UML diagrams, a person who uses the system
|
|
scenario or use case instance
|
unique set of internal activities within a use case that represents a unique path through the use case
|
|
preconditions
|
conditions that must be true before a use case begins
|
|
post conditions
|
conditions that must be true upon completion of a use case
|
|
relationship
|
naturally occurring association among specific things such as an order is placed by a customer and an employee works in a department
|
|
cardinality
|
number of associations that occur among specific thing, such as customer places many orders
|
|
multiplicity
|
synonym for cardinality (used with the object-oriented approach as defined by UML)
|
|
binary relationships
|
relationships between two different types of things, such as a customer and an order
|
|
unary (recursive) relationship
|
relationship among two things of the same type, such as one person being married to another
|
|
ternary relationship
|
relationship among three different types of things
|
|
n-ary relationship
|
relationship among n (any number of) different types of things
|
|
attribute
|
one piece of specific information about a thing
|
|
identifier
|
an attribute that uniquely identifies a thing (key)
|
|
compound attribute
|
attribute that contains a collection of related attributes
|
|
data entities
|
things about which the system needs to store information in the traditional approach to information systems
|
|
associative entity
|
data entity that represents a many-to-many relationship between two other data activities
|
|
generalization/specialization hierarchies
|
hierarchies that structure or rank classes from the more general superclasses to the more specialized subclasses; sometimes called inheritance hierarchies
|
|
inheritance
|
concept that allows subclasses to share characteristics of their superclasses
|
|
whole-part hierarchies
|
hierarchies that structure classes according to their associated components
|
|
aggregation
|
whole-part relationship between an object and its parts
|
|
composition
|
whole-part relationship in which the parts cannot be dissociated from the object
|