CSE687 - Object Oriented Design

Design Note #6
Executive Control Flow Narrative

Revised: 4/28/2011
Home Courses Code Handouts CoreTech Books Articles Math Research Masters Projects SWDev WebDev News OtherLinks SiteDesign Graduates AllPages Office Hours Notices

CSE681-SWMAA CSE686-IP CSE687-OOD CSE775-DO CSE776-DP CSE778-AWP CSE784-SWS

Note #01 Note #02 Note #03 Note #04 Note #05 Note #06 Note #07
Note #08 Note #09 Note #10 Note #11 Note #12 Note #13 Note #14
Note #15 Note #16 Note #17 Note #18 Note #19 Note #20 Note #21
Note #22 Note #23 Note #24 Note #25 Note #26 Note #27 Note #28
Design Notes

Syllabus SG - Design SG - Templates SG - Class Relationships

Design Note #6:

Most applications are structured to have an Executive package that is responsible for carrying out all the tasks for the application. It does this through a set of helper packages where often each helper is responsible for one of the major tasks.

The Executive is responsible for creating and activating the helper objects. If we name the helper packages and classes effectively, the text of the Executive is simply a narrative description of its activities, making learning and maintaining the application much easier than it might otherwise be.

Conclusions:

Code is read more often than compiled:
  1. Make your code self describing so it can easily be reused and understood by others who need to use it.
  2. You do that by naming classes and their member functions to support a model or metaphor and the text of the user simply can describe the processing needed in the language you provide.