Category	Featured projects
scm	Subversion, Subclipse, TortoiseSVN, RapidSVN
issuetrack	Scarab
requirements	xmlbasedsrs
design	ArgoUML
techcomm	SubEtha, eyebrowse, midgard, cowiki
construction	antelope, scons, frameworx, build-interceptor, propel, phing
testing	maxq, aut
deployment	current
process	ReadySET
libraries	GEF, Axion, Style, SSTree
Over 500 more tools...

Subversion and IDEs
Eclipse
JDeveloper
NetBeans
Visual Studio

[ framework ] [ architecture ] [ screenshots ] [ contribution ] [ resources ] [ new Wheel ]

The Components 

The software package "Astade" consists of a lot of separate programs (components). Each will be described here:

Astade

This is the main part of the package. All model changes are done with that program. You can add and remove model elements with that component. And, of course, see all the model elements.

At the end, this component is a specialized directory viewer, because each model element will be mapped to an element in the file structure of the operating system. Elements which can contain other elements (like classes) are directories. Elements which don't contain other elements (like attributes) are files.

All files are text files in the wxWidgets .ini format.

If you'd like to see some screenshots, you'll find them here.

FeatureDialog

Every model element has a configuration dialog (feature dialog). In that dialog you can modify the features of the model element. So there are a lot of components which allow the modification of a specific model element.

That means there is a component for every model element (which actually edits the corresponding .ini file).

OMDView

The OMDView generates text files in the .dot format from any point of the model tree. These files are interpreted by graphviz and converted into object model diagrams.

CDView

The CDView generates text files in the .dot format from any point of the model tree. These files are interpreted by graphviz and converted into component diagrams.

CodeGenerator

The Code Generator takes a directory (which is actually a class from the model point of view) and all files and subdirectories with all the .ini stuff and generates a valid .cpp and .h file in it.

Because each model element has also a "comment", the CodeGenerator writes well documented and doxygen compatible source.

MakefileGenerator

There are model elements which are called "components". At the end they are lists of classes which shall exist in a certain binary (program or lib). The MakefileGenerator use these list and generates a Makefile, so that "make" will be able to generate the component (the program). 

Reporter

The Reporter reads also the model elements called "component" and generates a project file for doxygen. Because the source files are already well documented, the documentation of the program is ready too.

[ Project overview ]