Hardware Reference
In-Depth Information
Based on the Conradi el al. proposal [5], we classify the defect types into: Omis-
sion (missing item), Extraneous information (information that should not be in the
model), Incorrect fact (misrepresentation of a fact), Ambiguity (unclear concept), or
Inconsistency (disagreement between representations of a concept). Thus, Defects 1,
2, 3, 4, and 7 correspond to
omissions
; Defect 5 corresponds to an
incorrect fact
; and
Defects 6 and 8 correspond to
ambiguities
.
Table 2 lists a set of rules of the OOmCFP measurement procedure that are related
to the identification of data movements. This table also indicates how the presented
rules help to find defect in the conceptual models.
Table 2.
Rules to identify the data movements of OOmCFP
OO-Method
Conceptual
Element
OOmCFP Rules
Defects
Display Pattern
Rule 10:
Identify
1X
data movement for the
client piece of software for each
display
pattern
in the interaction units that
participate in a functional process.
Defect 9:
An instance interaction unit
without display pattern.
Defect 10:
A population interaction
unit without display pattern.
Rule 11:
Identify
1E
data movement for the
client piece of software, and
1X
and
1R
data
movements for the server piece of software
for each different
class
that contributes with
attributes to the display pattern.
Defect 11:
A display pattern without
attributes.
Rule 13:
Identify
1R
data movement for the
server piece of software for each different
class
that is used in the
effect
of the
derivation formula
of derivate attributes that
appear in the display pattern.
Defect 12:
Derived attributes without a
derivation formula.
Filter Pattern
Rule 16:
Identify
1R
data movement for the
server piece of software for each different
class
that is used in the
filter formula
of the
filter patterns of the interaction units that
participate in a functional process.
Defect 13:
A filer without a filter
formula.
Service
Rule 20:
Identify
1R
data movement for the
server piece of software for each different
class
that is used in the
effect
of the
valuation
formula
of events that participate in the
interaction units contained in a functional
process.
Defect 14:
An event of a class of the
object diagram without valuations.
Rule 21:
Identify
1W
data movement for the
server piece of software for each
create
event
,
destroy event
, or
event that has
valuations
(represented by the class that
contains the service) that participate in the
interaction units contained in a functional
process.
Defect 15:
A class without a creation
event.
Rule 22:
Identify
1R
data movement for the
server piece of software for each different
class
that is used in the
service
formula
of
transactions, operations, or global services
that participate in the interaction units
contained in a functional process.
Defect 16:
Transactions without a
specification of a sequence of services
(service formula).
Defect 17:
Operations without a
specification of a sequence of services
(service formula).
Defect 18:
Global services without a
specification of a sequence of services
(service formula).
