TERM 1
Fit Criterion
DEFINITION 1
Each functional requirement should have a fit criterion or a
test case. In any event, the fit criterion is the benchmark to
allow the tester to determine whether the implemented
product has met the requirement # A measurement of the
requirement such that it is possible to test if the solution
matches the original requirement.
TERM 2
Use Case
DEFINITION 2
# A use case in software engineering and s ystems engineering is a description of
a system-s behavior as it responds to a reque st that originates from outside of
that system. (wiki) # The respond to the bu siness event is called a business use
case (book 73) A use case (or set of use cas es) has these characteristics:
Organizes functional requirements Models th e goals of system/actor (user)
interactions Records paths (called scenarios) from trigger events to goals
Describes one main flow of events (also cal led a basic course of action), and
possibly other ones, called exceptional flows of events (also called alternate
courses of action) Is multi-level, so that one use case can use the functionality of
another one.
TERM 3
Domain Model
DEFINITION 3
# A conceptual model of a domain of interest (often referred
to as a problem domain) which describes the various entities,
their attributes and relationships, plus the constraints that
govern the integrity of the model elements comprising that
problem domain. (wiki) # Modesl that capture the essence of
a particular area of subject matters (p440)
TERM 4
Context Diagram
DEFINITION 4
A System Context Diagram (SCD) in software engineering
and systems engineering is a diagram that represents the
actors outside a system that could interact with that system.
(wiki)
TERM 5
Rationale
DEFINITION 5
Definition: A justification of the requirement
