🚀 go-pugleaf

I'm going to give you some general opinions about your issues:

   * Select a modeling tool to obtain your operations/interfaces/components
   * Review  roles on your organization. For instance, your library of
     components needs a person to mantain and manage it.
   * Review your maintenance organization. A component doesn't belong to just
     one application any more, if a components need to be updated, all the
     application using it, must to test it again. Version control is one of
     the most important issues.
   * A common software team could develop infraestructure components, such
     as:
       1. Error and Trace Manager
       2. Notification Component
       3. Gateways between different technologies or between different
          systems (CRM, ERP, ...)

*Mariano Blaya
*mariano.blaya@airtel.net




Geert De Reu ha escrito:

> Hi,
>
> I'm looking for material or opinions about how should Component Based
> Development be organised:
> * how transform an organisation to CBD
> * what are the main difficulties of managing CBD, and how to tackle these
> issues
>
> Geert De Reu,
> geert.dereu@advalvas.be