Get Together 2007 Green

Openbravo Get TogetherTechnology DayOpenbravo Green, the new platform

Barcelona, October 28th 2007Speaker: Ismael Ciordia, Adrián Romero

Page 2PR-OB Get Together-XXX-date

What is Openbravo Green? Project goals

Current status and Roadmap

Technologies, Components & Tools

Contribute to Green

Q&A

Agenda


What is Openbravo Green?

• Green is the next generation of the Openbravo Development Platform– The aim of the Openbravo Development Platform is to provide a set of integrated products and

tools to develop applications in an efficient and productive manner during the whole life cycle.– Target to Agile Development Style – Rapid and High Quality Application Development

• Our Development Platform will always be improving (at least till IT freezes :-)

• Built on the strengths, improve current limitations

Openbravo Get Together – Openbravo Green

quality

time

resources requirements

Improve quality by improving efficiency


Project Goals

• Openness. Best of breed technology. New implementation based on first class Open Source technologies (Spring, Hibernate, ...)

• Web based rich client

• Improve MDD abstraction. Enhance current application dictionary

• Modular by design

• Easy to integrate with

• Workflow engine

• Others: Monitoring, embedded security in DAO, ...

• Gradual implementation. Backward compatible



Project Benefits

• Product benefits– Engaging User Experience– Enable “different flavours” of usability– Reliability and Performance– Optimize consultant operation

• Business benefits– Significantly improves SaaS operation (advanced support for multi-tenancy)– Openbravo Exchange

• Comunity benefits– Remove entry barriers to developers– Synergies with other communities

• Technology benefits– Database independence– High improvement in Maintenability (Platform decoupled from ERP and MVC component based)



Gradual improvements vs. Migration. Dependency Tree

• MDD architecture allows to change the implementation technology

• If possible, better go though gradual improvements– Gradual improvements provide a better User Experience.– Reduce Risk


• Dependency Tree

• Since the MVC framework is going to be refactored, it has to be the first step. This is a big step


Agenda

What is Green? Project goals



Contribute to Green

Q&A


Current status

• White paper– http://wiki.openbravo.com/wiki/index.php/Design_principles_for_Openbravo_Green

• Prototype– http://demo.openbravo.com/green/


• Resources– Starting from the beginning of

2007, best in class resources were allocated

– Last months resources have been reallocated according to priorities (2.3x and ODE)

– In a few weeks the project will be relaunched with more resources allocated


3.0(not announced)

2007

H2 H1 H2 H1

2009

2

2008

Feasibility Plan

RoadmapOpenbravo Get Together – Openbravo Green

GreenPlatform

1

This is a tentative plan. Feasibility Plan is required in order to have a clear roadmap and a schedule of the project.


Agenda




Contribute to Green

Q&A


Technologies, Components, ToolsOpenbravo Get Together – Openbravo Green

• New MVC implementation– Database independent– Hibernate/JDO/iBatis– Spring + Acegi– JSF (myFaces)

• UI components)• JSR 168

– DWR– Dojo

Ser

ver

sid

eC

lien

t si

de

Integration layer

Business layer

Services layerPresentation layer

WebBrowser

Database

DAO Objects Hibernate OR Mapping Transaction management

POJOs

Service beans

Transaction managementBusiness Objects

JSP

Jasper reports

Backing beans

DWR

Web services

XML Engine

DHTML

Jasper reports

Javascript

CSS

AJAX

Spring framework

Hibernate

Oracle / PostgreSql


Technologies, Components, Tools

• DAO Implementation– Filtering by rules (AD_Client_ID, AD_Org_ID, isActive, ...)– Tracking and audit– Data abstraction to be used at Dictionary level

• Usability requirements– Master/Detail edition– Navigation, sorting, filtering– Data grid with more than one row for each record (instead of horizontal scrolling)– Application structure based on processes instead of transactions

• Time zone support

• Workflow engine

• Monitoring

• Development environment



Technologies, Components, Tools

• MDD– Add "reporting only" fields to it at runtime without touching the backing database table– Fields as expressions (without having to be backed in a column)– Pluggable Business Rules– Extensible Dictionary– Overwrite column info in fields (parent, reference, ...)– Avoid rules by names (for example, for referential integrity)– Hide database operation to the consultant (manage database objects from application)– Add a new Administrator level for administering client rules– Remove all rules based on SQL– Allow to overwrite the behaviour depending on the “operation layer” (function, client,

organization, ..., customer)



Agenda




How to contribute to Green

Q&A


How to contribute to Green

• Do you have experience in some of these fields?– Share your experience with us. We will break the project into subprojects (DAO implementation,

WAD interpreter, Workflow engine, ...) and you could take part in some of them

• Let us know your opinion– What is meaningful for you, What are your concerns, ... Explain your opinion in our forums and

blogs

• Help us in the testing process


Let us engineer Openbravo Green in a Community Driven manner!


Agenda




Contribute to Green

Q&A


Questions and answers

Questions and Answers


Thank you!

Openbravo Get Together