Memorandum

 

From:	Project Manager
To:	Junior Software Engineers
Re:	class Design

Thanks for the clarity of your work on the system requirements.  Next week we’ll need to know what data must be stored inside of each object, so for each class, write a class declaration. The class declaration contains just the members/data fields and function prototypes.

Each function must have a clear, concise comment that tells what that function does. You do not need to write the full function definition for any of the functions at this time.  Specify first which functions are needed; so we don't fully implement a function that is not required.

Of course, our company policy specifies that you also need a comment at the top of every file and a comment describing each class.

Test your function calls at this point, so write a main() that calls each of the functions. Write a "stub function" definition (that is just an empty { } ) so that your program will compile and thereby allow testing. This code will compile, but it will not do any real work.

Check the use cases to see if your set of functions is sufficient to implement all of them.  Then we’ll be in good shape for implementation!