Difference between revisions of "Console UI Core Classes - OOP344 20111"

From CDOT Wiki
Jump to: navigation, search
m (moved Basic BIO Encapsulating Classes to Basic Encapsulating Classes - OOP344 20111: Wrong name, didn't have subject and semester tags)
Line 1: Line 1:
 
Under Construction!
 
Under Construction!
 +
=Basic (BIO) Encapsulating Classes=
 +
 +
Your objective at this stage is to create series core of classes designed to interact with the user. These '''Core Classes''' then can be used in development of any interactive application.
 +
 +
Please note that the class definitions here are minimum requirement for the Core Classes and you are free to add any enhancements or features you find useful. However make sure that you discuss these enhancements with your professor to make sure they are feasible before implementation.
 +
 +
It is highly recommended to develop the classes in the order they are stated here. You must create your won tester programs fore each class (if possible); However, close to due date of each release, a tester program is provided to help you verify the functionality of your classes. Executables of the test programs are available on matrix to show you how it is supposed to run.
 +
 +
Start by creating mock-up classes (class declaration and definition with empty methods that only compiles and don't do anything).
 +
Each class MUST have its own header file to hold its declaration and "cpp" file to hold its implementation. To make sure you do not do circular includes follow these simple guidelines:
 +
* Add recompilation safeguards to all your header files.
 +
* Always use forward declaration if possible instead of including a class header-file.
 +
* Use includes only in files in which the actual header file code is used.
 +
* '''Avoid "just in case" includes.'''

Revision as of 12:56, 7 February 2011

Under Construction!

Basic (BIO) Encapsulating Classes

Your objective at this stage is to create series core of classes designed to interact with the user. These Core Classes then can be used in development of any interactive application.

Please note that the class definitions here are minimum requirement for the Core Classes and you are free to add any enhancements or features you find useful. However make sure that you discuss these enhancements with your professor to make sure they are feasible before implementation.

It is highly recommended to develop the classes in the order they are stated here. You must create your won tester programs fore each class (if possible); However, close to due date of each release, a tester program is provided to help you verify the functionality of your classes. Executables of the test programs are available on matrix to show you how it is supposed to run.

Start by creating mock-up classes (class declaration and definition with empty methods that only compiles and don't do anything). Each class MUST have its own header file to hold its declaration and "cpp" file to hold its implementation. To make sure you do not do circular includes follow these simple guidelines:

  • Add recompilation safeguards to all your header files.
  • Always use forward declaration if possible instead of including a class header-file.
  • Use includes only in files in which the actual header file code is used.
  • Avoid "just in case" includes.