next up previous
Next: 3.1 Non-Functional Attributes Up: The Convenience for a Previous: 2.3 Design Principles

3 A Proposal: NoFun

In this section, we present the main issues of a notation called NoFun following the design principles enumerated in the last section. We classify non-functional information into three kinds: The set of NF-attributes that characterise a component, together with their relationships (stated as NF-requirements), are declared in a NF-specification module , which is bound to the component specification. The NF-behaviour of an implementation is stated in a NF-behaviour module , bound to the implementation. Also, NF-behaviour modules will usually include NF-requirements for the software components imported by the implementation. Keeping non-functional information in separate modules gives full independence from the particular specification and programming languages used in the system.

 
next up previous
Next: 3.1 Non-Functional Attributes Up: The Convenience for a Previous: 2.3 Design Principles

Xavier Franch
Sept. 2, 1997