changed based on MAS#35 discussion.
Showing with 1 addition and 1 deletion
|...||...||@@ -185,7 +185,7 @@ The advantage of identifying a subset of generic *ModuleClasses*, described belo|
|Every [Device](#Device) can then be described by a collection of *Modules* (functionality). In the simplest examples, where there are no extensions needed, each *ModuleClass* has exactly one "child" Module ... in such cases the software developer can consider the two terms to be the same.|
|The relationship between a *ModuleClass* and a *Module* is very similar to the specification of a superclass and a subclass in an object oriented programming language.|
|The relationship between a *ModuleClass* and a *Module* is very similar to the specification of a superclass and a class in an object oriented programming language.|