Copyright (c) John Wiley & Sons, Inc., 1993. All rights reserved. 
Reproduction or translation of any part of this work beyond that permitted 
in Section 117 of the 1976 United States Copyright Act without the express 
written permission of the copyright owner is unlawful. Requests for 
permission or further information should be addressed to the Permissions 
Department, John Wiley & Sons, Inc. The purchaser may make back-up copies 
for his/her own use only and not for distribution or resale. The Publisher 
assumes no responsibility for errors, omissions, or damages, caused by the 
use of these programs or from the use of the information contained herein.

There are actually four complete CASE tools on this disk. The first 
is a small DOS command line program. The other three require Microsoft 
Windows 3.1 or higher to run.

1. The first CASE tool is defined in Chapter 6. This is the code template 
generator. This can be run on any PC or MS-DOS compatible machine. It's 
been tested with DOS 5, but any version of DOS after 3.0 should work. 
Full source is included. There is also a Borland MAKE file. 

2. The second CASE tool is the Class Librarian. It keeps track of classes 
you are building or have built. It is defined in Chapters 8 - 10.  This 
requires MS Windows 3.1 or higher to run. It was tested on a 386SX with 
4 Meg of RAM. All of the source I created is included. It uses two 
commercial libraries as noted in the text of the book. There is also
a Borland MAKE file.

3. The third CASE tool is a Class Browser. It is defined in Chapter 11.  
This requires MS-Windows 3.1 or higher to run. It was tested on a 386SX 
with 4 Meg of RAM. All of the source I created is included. It uses two 
commercial libraries as noted in the text of the book. There is also 
a Borland MAKE file.
                           
4. The final CASE tool is the Graphic Designer. One of the new 
implementations of the list definitions uses some classes from the book 
"Practical Data Structures in C++" by Bryan Flamig, also published by 
John Wiley & Sons. (You can get the code by getting that book, or change 
the implementation to another list.) All of the source I created is
included. It uses two commercial libraries as noted in the text of 
the book. There is also a Borland MAKE file.

Comments and recommendations from users are invited. Please use the 
Computer Language (soon to be Software Development) Forum on Compuserve 
-- GO CLMFOR or GO SDFORUM. I will monitor that forum  for messages 
addressed to me about the book.  Unless it's a very private matter, 
feel free to make the messages public, as the discussion may help other 
readers. Suggestions for SSOOT CASE improvements or bug reports are 
especially  welcome.

If I enhance any of the CASE tools, I will make them available in the OOP 
Alley library of the Computer Language (Software Development) forum on 
Compuserve.   Use any of the following Keywords: "SSOOT", "BRUMBAUGH", 
"CASE", "OOBOOK" to find any of the files I upload.

The install program for this disk will create the following directory 
structure on the disk you choose. (This of course  assumes you install 
the whole thing.)
     \OOBOOK
     \OOBOOK\CHAP06
     \OOBOOK\CHAP08
     \OOBOOK\CHAP09
     \OOBOOK\CHAP10
     \OOBOOK\CHAP11
     \OOBOOK\CHAP12

Each of the subdirectories contains the files appropriate to the chapter 
it is named after.

The code in the CHAP08, CHAP10, CHAP11 and CHAP12 cannot be linked into a
complete program without a user-interface library and a database library. 
To link without changing the code you will need to purchase the Zinc 
User-Interface Library and the Pinnacle Relationship Engine.

I have designed the classes so you should be able to substitute your own 
user-interface library and database library without a major impact on the 
rest of the program. (This is by necessity less true with the Graphic Tool.)

The details, reasons and philosophies behind this are discussed in the 
book in section 1.4.4, 3.2.4, 7.7, and Appendix A.
