At this post I will describe my point of view about the Team Management, and in depth Software Development Teams. How we must build a team for:

• Having work rules simply to understand and accept by the team.
• Working efficient: capacity to measure the development time and take decisions to improve.
• Covering many projects at same time by the same team.
• Geographically distributed team.

Metodology necessary to schematize many stages which concludes in the final product. In y proffesional experience, agile methodologies are which do better approach to the reality . I will based on:

• Scrum agile development for any kind of product, it defines roles, and the way to reproduce measurable iterations, needed meetings,...
• eXtremeProgramming more specific methodology for applicatiions development, defines the way to automatize tests, version control, requirements, collective code,...

The methodology gives us:

• tasks to do on each stage
• Sequence to make every stages

Roles in the team (share the methodology tasks):

• Master: Watch for the fullilement of the methodology, teach it. Defines priorities, roles, projects. Orchestation. Get things for the team.
• Commercial: First contact with the client. Watch the profitability of the whole commercial proccess.
• Architect: it decides technologies, and teach them. It builds the system wich supports the Architecture.
• Quality (Tester): This decides the technologies for QA development, and teach them to the team. This builds the quality support system (CI, TDD, SVN).
• Analyst(Product Manager): This defines the user requirements, converts them to diagrams easy to understand by the programmer, prioritizes the tasks(maximizing the ROI) and makes demos for the user. Maximize the usability.
• Project manager: planning the iterations, version control, sharing the tasks. Maximize the regularity of the team and coherent tasks sharing.
• DB programmer: DB development, to minimize duplicity.
• Business programmer: This develops the business libraries, to maximize the reuse (APIs & WS)
• Front-end programmer: this develops the web screens, to maximize the usability.

The pairs Master-Commercial, Architect-Quality, Analyst-Manager can be adopted as three roles. It depends on the number of persons in the equipment and how you want to  do the things. Programmer roles are the same as technologies implies the architecture, being the enumerated the basics (Flash, design, ...). They can be joined in an alone person too:

Tools are which help to the team to work with methodology.

• System: network (ADSL), Operating system (Ubuntu: OpenOffice, browser...)
• Communications: e-mail,  Video/Chat (Skype)
• Project management: redmine+redminebacklogs. Version control (Subversion).
• Architecture: IDE (Development tools, Eclipse, DBDesigner,...), technologies dependencies (Hibernate, ADF, ZK,...)
• Quality: coverage plugins, Continous integration server, code analyzing, test tools,...

The backlog schema which represents the diary job work:

At this section I will describe my point of view about the Team Management, and in depth Software Development Teams. How we must build a team for:

• Having work rules simply to understand and accept by the team.
• Working efficient: capacity to measure the development time and take decisions to improve.
• Covering many projects at same time by the same team.
• Geographically distributed team.

Metodology necessary to schematize many stages which concludes in the final product. In y proffesional experience, agile methodologies are which do better approach to the reality . I will based on:

• Scrum agile development for any kind of product, it defines roles, and the way to reproduce measurable iterations, needed meetings,...
• eXtremeProgramming more specific methodology for applicatiions development, defines the way to automatize tests, version control, requirements, collective code,...

The methodology gives us:

• tasks to do on each stage
• Sequence to make every stages

Roles in the team (share the methodology tasks):

• Master: Watch for the fullilement of the methodology, teach it. Defines priorities, roles, projects. Orchestation. Get things for the team.
• Commercial: First contact with the client. Watch the profitability of the whole commercial proccess.
• Architect: it decides technologies, and teach them. It builds the system wich supports the Architecture.
• Quality (Tester): This decides the technologies for QA development, and teach them to the team. This builds the quality support system (CI, TDD, SVN).
• Analyst(Product Manager): This defines the user requirements, converts them to diagrams easy to understand by the programmer, prioritizes the tasks(maximizing the ROI) and makes demos for the user. Maximize the usability.
• Project manager: planning the iterations, version control, sharing the tasks. Maximize the regularity of the team and coherent tasks sharing.
• DB programmer: DB development, to minimize duplicity.
• Business programmer: This develops the business libraries, to maximize the reuse (APIs & WS)
• Front-end programmer: this develops the web screens, to maximize the usability.

The pairs Master-Commercial, Architect-Quality, Analyst-Manager can be adopted as three roles. It depends on the number of persons in the equipment and how you want to  do the things. Programmer roles are the same as technologies implies the architecture, being the enumerated the basics (Flash, design, ...). They can be joined in an alone person too:

Tools are which help to the team to work with methodology.

• System: network (ADSL), Operating system (Ubuntu: OpenOffice, browser...)
• Communications: e-mail,  Video/Chat (Skype)
• Project management: redmine+redminebacklogs. Version control (Subversion).
• Architecture: IDE (Development tools, Eclipse, DBDesigner,...), technologies dependencies (Hibernate, ADF, ZK,...)
• Quality: coverage plugins, Continous integration server, code analyzing, test tools,...

The backlog schema which represents the diary job work:

Mi pretensión al estudiar estas tecnologías es mejorar el modelado de los procesos de negocio, mezclando de una forma clara:

• Tareas humanas --> (ADF Web apps design)
• Servicios web
• Antiguas tecnologías
• Sincronizar con eventos de negocio
• Definición de Reglas de negocio

Me parece que controlando esto, y con un buen sistema de análisis, ofreces una gran herramienta para controlar los sistemas de información de un negocio, y por tanto dirigirlo muy bien. Hoy vamos a instalar toda la plataforma para desarrollar y desplegar aplicaciones SOA. Basándonos en la lista de lo necesario para crear nuestro banco de pruebas Oracle SOA 11g, instalaremos:

• Database Expres Edition XE Universal 10.2.0.1
• WebLogic Server 10.3.3 y JDeveloper 11.1.1.3.0: wls1033_win32.exe, jdevstudio11113install.jar
• Repository Creation Utility: ofm_rcu_win32_11.1.1.3.3_disk1_1of1.zip
• SOA Suite 11.1.1.2.0: ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip
• Parches SOA Suite 11.1.1.3.0: ofm_soa_generic_11.1.1.3.0_disk1_1of1.zip

RCU: Repository Creation Utility

Con esto creamos los esquemas en nuestra BBDD de todos los productos SOA. Repository Creation Utility: ofm_rcu_win32_11.1.1.3.3_disk1_1of1.zip descomprimir a C:\Oracle\rcuHome, y ejecutar BIN\rcu.bat

Ignorar cualquier aviso de incompatibilidad, y seleccionar SOA Infraestructura and BPM, se añadiran los esquemas dependientes:

Se crean los siguientes esquemas en tu BBDD:

Como contraseña de los esquemas welcome1

SOA Suite

Este paso no tiene más complicación. SOA Suite 11.1.1.2.0: ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip

1. Sobre el directorio Disk1 ejecutamos: setup -jreLoc C:\Oracle\Middleware\jdk160_18
2. Lo instalaremos en C:\Oracle\Middleware\Oracle_SOA1

Parches SOA Suite 11.1.1.3.0: ofm_soa_generic_11.1.1.3.0_disk1_1of1.zip.

1. Sobre el directorio Disk1 ejecutamos: setup -jreLoc C:\Oracle\Middleware\jdk160_18

Crear un dominio configurado para SOA

Ejecutar C:\Oracle\Middleware\Oracle_SOA1\common\bin\config.cmd Crear un nuevo dominio de Weblogic, con todos los productos SOA:

El nombre del dominio será: domain1, password para el administrador: welcome1 Seleccionamos al JVM: Sun SDK 1.6.0_18 @ C:\Oracle\Middleware\jdk160_18 Creamos la conexión a la BBDD de todos los esquemas que montamos con el RCU:

Sin añadir configuraciones opcionales, terminar la creación.

SOA Extension for JDeveloper

En JDeveloper Help > Check for Updates > Search Update Centers > Oracle Fusion Middleware Products debe estar marcado. Marcar los siguientes productos:

• Oracle BPM Studio
• Oracle SOA Composite Editor

Consolas que se pueden ver

Weblogic administration console:

Enterprise manager:

B2B console:

Business Activity Monitor (BAM) solo con IE:

Soa/composer y bpm/composer: