Welcome to the IoT-A Uniﬁed Requirements list!
PreambleRequirements in IoT-A are mainly targeted at supporting and validating the work onthe Architectural Reference Model (ARM). While requirement work within the projecttries to follow requirement best practices (by using as much as possible Voleremethodology, by using input from both potential end-users and developers),producing and exploiting requirements on a Reference Architecture (and Model) levelis somewhat different than for a concrete system (for which the state of the artmethodology is largely targeted). This results in a number of speciﬁcs that the readershould keep in mind:
Prioritization of requirements for the ARM is largely inapplicable – while it islargely considered best practice in concrete system speciﬁcation.
Formulation (description ﬁeld) of requirements expressed by external or internalstakeholder may sometimes refer directly to the ARM, but in most cases they applyto a concrete system. In that latter case, they express characteristics on the systemthat the ARM should enable to specify.
Mapping to perspective/views/functional groups and components is done on alowest common denominator basis – e.g. it indicates which aspect is deﬁnitelyimpacted by a given requirement, but the reader should keep in mind that in certain(concrete system) speciﬁc cases, other components may need to be considered.