Validation Without Requirements?
<-- ^ -->
-
Can't validate inconsistent requirements
-
Typically, no individual has knowledge
of all component/feature behaviors
-
Typically, no individual knows
the requirements of all the stakeholders
-
Things change rapidly in MSDS
Key Idea: a single stakeholder
(usually) does have a consistent, knowable set of requirements.
so change the problem:
-
From "Does the system do
the right thing?"
-
To
"Does the system do the right thing for me (now)?"
Remaining Difficulties:
-
Lack of knowledge of component
behaviors, configuration, connectivity, and relevance
-
ambiguity (NL descriptions, differing/unspecified
vocabularies and ontologies)
-
lack of detail (e.g. "TCP port
25"; interface definition only (IDL or WSDL))
-
hidden agendas
-
"Usual" software engineering
validation problems
-
theory and state explosion
-
feature interaction problem