Software Development And Systems Analysis And Design

Front 1

use case

Back 1

an activity that the system performs, usually in response to a request by a user

Front 2

user goal technique

Back 2

a technique to identify use cases by determining what specific goals or objectives must be completed by a user

Front 3

event decomposition technique

Back 3

a technique to identify use cases by determining
the external business events to which the system must respond

Front 4

elementary business processes (EBPs)

Back 4

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

Front 5

event

Back 5

something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system

Front 6

external event

Back 6

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

Front 7

actor

Back 7

an external agent; a person or group that interacts with the system by supplying or receiving data

Front 8

temporal event

Back 8

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

Front 9

state event

Back 9

an event that occurs when something happens inside the system that triggers some process

Front 10

system controls

Back 10

checks or safety procedures to protect the integrity of the system and the data

Front 11

perfect technology assumption

Back 11

the assumption that a system runs under perfect
operating and technological conditions

Front 12

CRUD technique

Back 12

an acronym for Create, Read/Report, Update, and Delete; a technique to validate or refine use cases

Front 13

brief use case description

Back 13

an often one-sentence description that provides a quick overview of a use case

Front 14

use case diagram

Back 14

the UML model used to graphically show use cases and their relationships to actors

Front 15

automation boundary

Back 15

the boundary between the computerized portion of the application and the users who operate the
application but are part of the total system

Front 16

<>.. relationship

Back 16

a relationship between use cases in which one use case is stereotypically included within the other use case

Front 17

problem domain

Back 17

the specific area (or domain) of the user’s business need (or problem) that is within the scope of the new system

Front 18

brainstorming technique

Back 18

a technique to identify problem domain objects in which developers work with users in an open group setting

Front 19

noun technique

Back 19

a technique to identify problem domain objects by finding and classifying the nouns in a dialog or description

Front 20

attributes

Back 20

descriptive pieces of information about things or objects

Front 21

identifier or key

Back 21

an attribute the value of which uniquely identifies an individual thing or object

Front 22

compound attribute

Back 22

an attribute that consists of multiple pieces of information but is best treated in the aggregate

Front 23

association

Back 23

a term, in UML, that describes a naturally occurring relationship between specific things, sometimes called a relationship

Front 24

relationship

Back 24

a term that describes a naturally occurring association between specific things, sometimes called an association

Front 25

cardinality

Back 25

a measure of the number of links between one object and another object in a relationship

Front 26

multiplicity

Back 26

a measure, in UML, of the number of links between one object and another object in an association

Front 27

multiplicity constraints

Back 27

the actual numeric count of the constraints on objects allowed in an association

Front 28

binary associations

Back 28

associations between exactly two distinct types of things

Front 29

unary association

Back 29

an association between two instances of the same type of thing

Front 30

ternary association

Back 30

an association between exactly three distinct types of things

Front 31

n-ary association

Back 31

an association between n distinct types of things

Front 32

data entities

Back 32

the term used in an ER diagram to describe sets of things or individual things

Front 33

entity-relationship diagram (ERD)

Back 33

a diagram consisting of data entities (i.e., sets of
things) and their relationships

Front 34

semantic net

Back 34

a graphical representation of an individual data entity and its relationship with other individual data entities

Front 35

class

Back 35

a category or classification of a set of objects or things

Front 36

domain classes

Back 36

classes that describe objects from the problem domain

Front 37

class diagram

Back 37

a diagram consisting of classes (i.e., sets of objects) and associations among the classes

Front 38

domain model class diagram

Back 38

a class diagram that only includes classes from the problem domain

Front 39

camelback notation or camelcase notation

Back 39

when words are concatenated to form a single word and the first letter of each embedded word is capitalized

Front 40

association class

Back 40

an association that is also treated as a class; often required in order to capture attributes for the association

Front 41

generalization/specialization relationship

Back 41

a type of hierarchical relationship in which subordinate classes are subsets of objects of the superior classes; an inheritance hierarchy

Front 42

superclass

Back 42

the superior or more general class in a generalization/specialization relationship

Front 43

subclass

Back 43

the subordinate or more specialized class in a generalization/specialization relationship

Front 44

inheritance

Back 44

the concept that specialization classes inherit the attributes of the generalization class

Front 45

abstract class

Back 45

a class that describes a category or set of objects but that never includes individual objects or instances

Front 46

concrete class

Back 46

a class that allows individual objects or instances to exist

Front 47

whole-part relationship

Back 47

a relationship between classes in which one class is a part or a component portion of another class

Front 48

aggregation

Back 48

a type of whole-part relationship in which the component parts also exist as individual objects apart from the aggregate

Front 49

composition

Back 49

a type of whole-part relationship in which the component parts cannot exist as individual objects apart from the total composition