From: Bob Lechner <lechner@cs.uml.edu>
Subject: BDE Rev. Eng. FYInfo (thank you JingTan)
To: lechner@cs.uml.edu (Bob Lechner)
Date: Fri, 18 Nov 2005 17:41:00 -0500 (EST)
Cc: ralmonte@cs.uml.edu (Almonte), mandava_s@yahoo.com, smandava@cs.uml.edu, jtan@cs.uml.edu, jingyoko@hotmail.com, uguntu@cs.uml.edu (Guntu), kpatel1@cs.uml.edu (Patel), lechner@cs.uml.edu (Bob Lechner)

To class - 
I will extract these into $PH/COOL-BDE. Perhaps the .zip file also.

Forwarded message:
> From jingyoko@hotmail.com  Fri Nov 18 11:01:21 2005
> From: "jingyoko@hotmail.com Tan" <jingyoko@hotmail.com>
> Subject: RE: how and why BDE came from and its structurea
> 
> Thank you for your detail explanation. It's very helpful.
> 
> In order to understand the structure of BDE, I used MagicDraw to reverse BDE 
> source codes into the following 6 diagrams in the zip file.
> 
> Hierarchy diagram of graphobject.jpg*
> Hierarchy diagram of text.jpg*
> Overview diagram of package include.jpg*
> Overview diagram of package pr_util.jpg*
> Overview of Dependency Diagram.jpg*
> bde_classes.jpg*
> 
> Since they are generated by machine, I have no way to control them, 
> somewhere maybe look ugly and some of them may be duplicated with 
> ralmonte's, but I hope they are useful for analyzing these codes.
> 
> Thanks,
> Jing
> 
> >From: Bob Lechner <lechner@cs.uml.edu>
> >To: jingyoko@hotmail.com (jingyoko@hotmail.com Tan)
> >CC: 05f523
> >Subject: how and why BDE came from and its structurea
> >
> >RJLRef: $PH/05f523/week13/GenBdeLcpEvolution.051118
> >COOL Framework Component Evolution and Motivation
> >
> > > From jingyoko@hotmail.com  Thu Nov 17 12:01:46 2005
> > > ... my question asked for documentation written by a designer
> > > before starting writing code, NOT schema declarations. The reason I 
> >asked is
> > > that I want to understand how and why the BDE came from and its 
> >structure.
> >
> >In response to Jing's question, here are some more BDE sources
> >(for the Why, more than the How):
> >[Don't look here for BDE's GUI code design.
> >Look for a vision of an evolving code generation framework
> >with automatic code generation and protoype evaluation goals.]
> >
> >R Lechner
> >===================================================
> > [cut]