Having only a single possible meaning, and therefore not
susceptible to multiple conflicting interpretations. Clear
and certain, without being obscure or vague.
the smallest software component that can be treated as a
relatively independent blackbox module. A unit is typically
identified in the design and the subject of unit testing. A
unit is also typically the smallest software configuration
item.
For example, a software unit could be an
object-oriented programming language class or interface, a
procedural programming language function, or an HTML
webpage.
a CASE tool that primarily deals with work products at a
higher level of abstraction than software components.
Examples include requirements engineering tools, design
tools, modeling tools, and documentation tools.
(1) a user-oriented
securityquality
requirement specifying the degree to which an
application or
component (e.g., user
interface, help facilities) and its documentation shall
enable a specified set of users to easily and efficiently:
Learn and remember how to use it.
Perform a specified set of their tasks while making a
minimum number of errors (e.g., create and inputs, obtain
and understand outputs).
(2) a quality factor measuring the degree to which an
application or component actually enable users to easily and
effectively use it.
a testing work product consisting of an organized list of
questions that is used to obtain the test participants’
observations, opinions, preferences, and recommendations
concerning the work product under test.
the fourth phase, during which minor updates and
corrections to the new version of the application are made
while it is in use by the user organizations.
a completely specific way of using a blackbox business
orapplication that traverses a
use case path through a
use case.
Note that usage scenarios are test cases for testing
use case paths.
a general way of using a blackbox business, application,
component, or framework to achieve a goal of some
external, primarily
specified in terms of its normal and exceptional
use case paths.
Contrast withusage scenario and
use case path.
Contrast withchange case and
misuse case.
For example, the use cases for an automatic teller
machine application could include customer deposits funds,
customer withdraws funds, customer obtains account balances,
customer transfers funds, and customer makes payment.
Note that a use case is a single, complete
functional abstraction.
a large index card used during the requirements
elicitation task to informally capture the cohesive set of
operational requirements associated with a single use
case.
a semi-specific way of using a blackbox business or
application, specified in terms of its preconditions, logical
interactions that capture the externals’ intentions and
the businesses’ or application’s requirements,
and required postconditions.
See alsoexceptional
path and
normal path.
Contrast withusage scenario and
use case.
For example, the use case paths for the withdraw
funds use case of an automatic teller machine application
could include the fast cash and successfully withdraw a
specific amount normal paths as well as the account overdrawn
and over daily cash limit exceptional paths.
Note that use case paths determine equivalence sets
of usage scenarios.
Note that the preconditions determine which path is
traversed.
Note that different paths often have different sets
of interactions and postconditions.
1) the requirements task during which the users of an
application are profiled and analyzed.
2)the requirements work product produced during business
(re)engineering that documents the results of the analysis of
the user organization that uses the customer organization’s
applications.
Contrast withcustomer
analysis and
market
analysis.
a user support work product that documents how to use an
application in terms of the tasks to be performed by
different kinds of users and the workflows to be performed
multiple collaborating roles using the application.
