Premium
7.3.1 SUGGESTIONS FOR REQUIREMENTS MODEL ROBUSTNESS
Author(s) -
DeFoe Joseph C.,
Sheard Sarah A.
Publication year - 1995
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1995.tb01908.x
Subject(s) - rotation formalisms in three dimensions , computer science , requirements analysis , robustness (evolution) , set (abstract data type) , system requirements , process (computing) , requirements management , systems engineering , synchronization (alternating current) , non functional requirement , risk analysis (engineering) , engineering , software system , software , computer network , channel (broadcasting) , gene , programming language , operating system , medicine , biochemistry , chemistry , geometry , mathematics , software construction
The behavior implied by a set of requirements must be modeled to ensure that a system built as specified will meet user needs and expectations. Requirements modeling explores possible operational scenarios to establish which capabilities the system must have to be effective. Requirements modeling can be done either implicitly, in the heads and on the white boards of the team producing the requirements, or explicitly, using any number of formalisms and tools. In either case, specific strategies and ground rules must be employed if the model is to properly explore the operationally necessary, externally observable behaviors of the system. This paper presents a set of such strategies to consider when developing a requirements model. Strategies that lead to a robust model help ensure the final system will be operationally suitable. Examples of systems for which the requirements seem to have been insufficiently modeled are used to illustrate the need for a process that accounts for varied external behaviors, perceived concurrencies, synchronization lags, real world objects, and expresses what the system must do, not how it is do it.