********************************************************************************

  OO    OOO   OOO  OOOO   OOO  OOOOO    OOO      OO    O   O    O    OOO  O   O
 O  O   O  O    O  O     O       O      O  O    O  O   OO OO   O O    O   OO  O
O    O  OOO     O  OOO   O       O      O   O  O    O  O O O  OOOOO   O   O O O
 O  O   O  O    O  O     O       O      O  O    O  O   O   O  O   O   O   O  OO
  OO    OOO   OO   OOOO   OOO    O      OO       OO    O   O  O   O  OOO  O   O

********************************************************************************

 Thank you for your interest in "object domain".

 Object Domain is a object oriented design and analysis tool. It is based on the
 book: "OBJECT ORIENTED ANALYSIS AND DESIGN with Applications second edition"
 by Grady Booch.

 All diagrams are available in this version.

 INSTALLATION:
 ------------

 To install this program just run the supplied setup program. From the program
 manager select file/run  "a:\install".




 SHAREWARE:
 ---------

 This program is not public domain nor freeware. It is being distributed as
 shareware.This means that you can evaluate this program for free for a trial
 period of 30 days. Using this program after this trial period is a copy right
 violation.

 Also the shareware version of this program will print a message on the bottom
 and the header of printouts.

 If you register you will receive the latest version without these restrictions.
 You will also receive the latest version of the software.
 Registered users will also receive a 32 bit version of the program.

 See the programs help file for information on how to register
 ( from the help menu on the menubar select About, in the About dialog select
  Help).


 KNOWN PROBLEMS :
 --------------

 Typing text in diagrams which are zoomed does not work.

 KNOWN SHORTCOMMINGS :
 -------------------

 - Code generation is rather simple :
	Only information from the class,attribute,and operation templates is used.
	Module depeendencies are only generated for dependencies between bodies and
	and specifictation modules ( subsystem dependencies have no effect on the
	generated	code)

 - Referencing (importing) classes and categories in other diagrams is not
	possible.A workaround for this is to use you own naming convention for
	referencing objects.

	e.g.   @Class1 would be a reference to class A

	( Note if you do not intend to use code generation you could give both object
	 the same name)



 REPORTING PROBLEMS, ENHANCEMENT REQUESTS:
 ----------------------------------------

 - Please send me mail or email regarding problems and enhancement requests.

	For problems please send a description on how to reproduce this problem
	(if possible to reproduce)

	For enhancements please specify exactly what you want and how important this
	feature is to you. I don't promise the requested feature will be added in the
	next version but if you don't ask....
	Enhancements requested by many users will be considered first.


	Features currently on the list for planned features:
	- the known problem + shortcommings listed above

	- Reverse engineering:
		( this will also allow to keep code and diagrams up to date. )









HOW TO REACH ME :
----------------

mail:

 Dirk Vermeersch
 1397 Ridgewood Drive
 San Jose CA 95118

 email :
 dirkv@netcom.com

 or compuserve ID
 71202.2323


