next up previous
Next: 3.3 Non-Functional Requirements Up: 3 A Proposal: NoFun Previous: 3.1 Non-Functional Attributes

3.2 Non-Functional Behaviour

Once a component specification (both functional and non-functional parts) has been built, implementations for the component may be written. Each implementation for a given software component D should state its NF-behaviour with respect to the basic NF-attributes characterising D ; values of derived NF-attributes are automatically computed. This assignment of values is encapsulated in a NF-behaviour module. In order for the implementation to be considered as correct, its NF-behaviour must fulfil all the requirements stated at the NF-specification (see next subsection).

In the general case, a component will be used in different software systems. In these systems, the NF-attributes characterising the component could be different. This situation requires multiple NF-behaviour modules to exist, each of them describing the NF-behaviour of the component in its corresponding context.


Xavier Franch
Sept. 2, 1997