Design Note #0
Design Note #0 - KISS Principle
32 January 2007
../../webpages/FawcettHome.xml
../../Courses.xml
../../Code.xml
../../Books.xml
www.ecs.syr.edu/faculty/fawcett/handouts
../../research.xml
../../swdev.xml
../../webdev.xml
../../news.xml
../../OtherLinks.xml
../../SiteDesign.xml
../../CSE681/CSE681Code.xml
../../CSE687/CSE687Code.xml
../../CSE691/CSE691Code.xml
../../CSE775/CSE775Code.xml
../../CSE776/CSE776Code.xml
../../CSE778/CSE778Code.xml
../../CSE784/CSE784Code.xml
StudyGuideDesign.xml
Keep It Small and Simple (KISS) ==> need to partition into modules.
Divide and Conquer
Strive for High Cohesiveness in each module ==> focus on a single activity.
Public processing model should be simple even though there may be complex internal details.
Strive for loose coupling ==> refer to abstractions, not implementations.
Use Interfaces to support plug-in instances of any class derived from the interface.
The ../code/Project1HelpS06/Tokenizer.h, in
../code/Parser/ collects tokens
for analysis of grammatical constructs found in a source code file.
It supports cohesiveness by hiding complex character manipulations in a
private helper functions.
The ../code/Parser/Parser.h, in
../code/Parser/ illustrates how binding
to interfaces, Rule and Action, allows any instance of a class, derived from the interface, Rule for example,
to be plugged into an instance of Parser, modifying the way it carries out its work.