XERP Module Architecture


Consensus on how to approach the management of XAF modules for XERP.

Should all BOs be in single module or split up.

This task will involve research (with a written deliverable) to understand how OpenERP / Python manages modules and how XAF can best match the functionality or improve upon it.

This task will manage discussions to arrive at a consensus and a deliverable.

file attachments


julianpaulozzi wrote Sep 28, 2009 at 2:38 AM

Here is a small conceptual model of ERP XAF for analysis.

mgpetryk wrote Sep 28, 2009 at 3:53 PM

With all BOs in a single file, would that not make it harder to divide this project up and allow multiple developers work simultaneously? I would suggest at least breaking them down to HR / Account / IR / MRP / Process / Product / PO / RES / Stock , WKF .

Also, in reviewing the current BO file, is it the intent to duplicate the file structure of OpenERP exactly? or was this just the standard result from creating the objects when pointing to a db. I would suggest that the file structure we use be optimized for use with XAF, initially just looking at the INT keys to be replaced with GUID.

mgpetryk wrote Sep 28, 2009 at 4:07 PM

Attached is a potential XERP Base object.

garthhenderson wrote Sep 28, 2009 at 9:36 PM


The consensus that Oscar, Emilio and I had on Saturday (our first conference to help organize the project) was to create a folder for each module based on the OpenERP table module name and have a separate file for each BO.

We are starting to do this by module.

Does this seem reasonable?

FYI: It seems that we are forced by CodePlex to manually identify the name of the file attached with a comment as are abiguously listed at the top.

NOTE: Our highest concern is how to remove bottle necks so that everyone can freely move forward in an organized yet somewhat independent way based on our work and family schedules.

Yes, we are going to optimize the BOs for XAF.