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;
49 Cards in this Set
- Front
- Back
use case |
an activity that the system performs, usually in response to a request by a user |
|
user goal technique |
a technique to identify use cases by determining what specific goals or objectives must be completed by a user |
|
event decomposition technique |
a technique to identify use cases by determining |
|
elementary business processes (EBPs) |
the most fundamental tasks in a business process, which leaves the system and data in a quiescent state; usually performed by one person in response to a business event |
|
event |
something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system |
|
external event |
an event that occurs outside the system, usually initiated by an external agent |
|
actor |
an external agent; a person or group that interacts with the system by supplying or receiving data |
|
temporal event |
an event that occurs as a result of reaching a point in time |
|
state event |
an event that occurs when something happens inside the system that triggers some process |
|
system controls |
checks or safety procedures to protect the integrity of the system and the data |
|
perfect technology assumption |
the assumption that a system runs under perfect |
|
CRUD technique |
an acronym for Create, Read/Report, Update, and Delete; a technique to validate or refine use cases |
|
brief use case description |
an often one-sentence description that provides a quick overview of a use case |
|
use case diagram |
the UML model used to graphically show use cases and their relationships to actors |
|
automation boundary |
the boundary between the computerized portion of the application and the users who operate the |
|
<>.. relationship |
a relationship between use cases in which one use case is stereotypically included within the other use case |
|
problem domain |
the specific area (or domain) of the user’s business need (or problem) that is within the scope of the new system |
|
brainstorming technique |
a technique to identify problem domain objects in which developers work with users in an open group setting |
|
noun technique |
a technique to identify problem domain objects by finding and classifying the nouns in a dialog or description |
|
attributes |
descriptive pieces of information about things or objects |
|
identifier or key |
an attribute the value of which uniquely identifies an individual thing or object |
|
compound attribute |
an attribute that consists of multiple pieces of information but is best treated in the aggregate |
|
association |
a term, in UML, that describes a naturally occurring relationship between specific things, sometimes called a relationship |
|
relationship |
a term that describes a naturally occurring association between specific things, sometimes called an association |
|
cardinality |
a measure of the number of links between one object and another object in a relationship |
|
multiplicity |
a measure, in UML, of the number of links between one object and another object in an association |
|
multiplicity constraints |
the actual numeric count of the constraints on objects allowed in an association |
|
binary associations |
associations between exactly two distinct types of things |
|
unary association |
an association between two instances of the same type of thing |
|
ternary association |
an association between exactly three distinct types of things |
|
n-ary association |
an association between n distinct types of things |
|
data entities |
the term used in an ER diagram to describe sets of things or individual things |
|
entity-relationship diagram (ERD) |
a diagram consisting of data entities (i.e., sets of |
|
semantic net |
a graphical representation of an individual data entity and its relationship with other individual data entities |
|
class |
a category or classification of a set of objects or things |
|
domain classes |
classes that describe objects from the problem domain |
|
class diagram |
a diagram consisting of classes (i.e., sets of objects) and associations among the classes |
|
domain model class diagram |
a class diagram that only includes classes from the problem domain |
|
camelback notation or camelcase notation |
when words are concatenated to form a single word and the first letter of each embedded word is capitalized |
|
association class |
an association that is also treated as a class; often required in order to capture attributes for the association |
|
generalization/specialization relationship |
a type of hierarchical relationship in which subordinate classes are subsets of objects of the superior classes; an inheritance hierarchy |
|
superclass |
the superior or more general class in a generalization/specialization relationship |
|
subclass |
the subordinate or more specialized class in a generalization/specialization relationship |
|
inheritance |
the concept that specialization classes inherit the attributes of the generalization class |
|
abstract class |
a class that describes a category or set of objects but that never includes individual objects or instances |
|
concrete class |
a class that allows individual objects or instances to exist |
|
whole-part relationship |
a relationship between classes in which one class is a part or a component portion of another class |
|
aggregation |
a type of whole-part relationship in which the component parts also exist as individual objects apart from the aggregate |
|
composition |
a type of whole-part relationship in which the component parts cannot exist as individual objects apart from the total composition |