On Tuesday, January 24, 2017 at 4:43:50 PM UTC, Peter Damoc wrote: > > Parnas' Principles >> These ideas were captured by computer scientist David Parnas in a pair of >> rules, which are known as Parnas' Principles: >> The developer of a software component must provide the intended user with >> all the information needed to make effective use of the services provided >> by the component, and should provide no other information. >> The implementor of a software component must be provided with all the >> information necessary to carry out the given responsibilities assigned to >> the component, and should be provided with no other information. > > Yes. Sometimes they are described as maximizing coherence and minimizing coupling. A 'coherent' component groups similar functionality together. A pair of components are 'coupled' by their interactions.
-- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
