This document describes a proposed architecture for the GNUe Base Package.
This document was originally written by Neil Tiffin.
This introduction is $Revision: 1.1 $ $Date: 2003/01/05 00:00:29 $.
This version number only applies to this introduction, each module class file, and module requirements chapter have a separate version tag. Probably a bit of overkill, but this will have to suffice until we get to the stage of versioned releases.
The purpose of this document is to define the scope of the modules in the Base Package. If any terms in this document are unclear please let me know. We are working on a glossary and I will gladly add them.
The Base Package encompasses all business objects that are used by multiple packages and modules. So anything that does not fit well in its own package should go here. Normally the screens and forms to access objects defined in the base package should be part of the non-base packages and modules.
The first version of the Base Package will be a proof of concept package to stress and test the GNUe tools architecture. As such it may have limited functionality. However, with that said the modules and objects developed for the initial package should be re-usable to address larger or industry specific implementations.
Future functionality describes requirements slated for a future version of GNUe. These requirements may appear in either standard GNUe functionality or in industry packages.
Each Module definition below contains a list of Business Requirements, Business Objects, and External Objects. The Business Requirements are the general business functionality that the module will support. The Business Objects are the objects whos definition is managed and controlled by the respective module. External Objects are interfaces to objects managed and controlled by other Module definitions. No attempt has been made to create an object structure in this document. That is the responsibility of the module developers. For example the Warehouse business object may be related to a general Location Business Object. It is also assumed that the requirements stated here will change as the Modules are defined and or refactored.