Software Development Teams
Oct 16, 10 by Juan Lebrijo about management, blog
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:
mngmt.png 27.4 KB
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:
redminebacklogs.thumbnail.png 4.66 KB
MGMT
Oct 14, 10 by Juan Lebrijo about blog
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:
mngmt.png 27.4 KB
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:
redminebacklogs.thumbnail.png 4.66 KB
Installing Oracle SOA Suite 11g
Sep 20, 10 by Juan Lebrijo about SOA, weblogic, JDeveloper, blog
My desires when I study this technologies is improving the business proccess modeling, mixing in a clean way:
  • Human tasks --> (ADF Web apps design)
  • Web Services
  • Legacy technologies
  • Synchronize with business events
  • Define business rules
I think that controlling all this points, and with a good analysis system, you can get a great tool to manage the business information system, and so, managing good. Today we will install all the platform to develop and deploy SOA applications. Based in the needed list to creat our Oracle SOA 11g test bank, we will install:

RCU: Repository Creation Utility

On this step we will create all the DB schemas needed to allocate all the SOA products. Repository Creation Utility: ofm_rcu_win32_11.1.1.3.3_disk1_1of1.zip Unzip to C:\Oracle\rcuHome, and execute BIN\rcu.bat
image003.png 105 KB
Ignore every incompatibility warning, and select SOA Infraestructura and BPM, it will add the dependent schemas:
image005.png 139 KB
We will create the following schemas in your DB:
pantallazo-1.png 103 KB
I put as schema passwords welcome1

SOA Suite

This is a very easy step (next-next installation). SOA Suite 11.1.1.2.0: ofm_soa_generic_11.1.1.2.0_disk1_1of1.zip
  1. On the Disk1 directory, execute: setup -jreLoc C:\Oracle\Middleware\jdk160_18
  2. Install it on C:\Oracle\Middleware\Oracle_SOA1
SOA Suite patches 11.1.1.3.0: ofm_soa_generic_11.1.1.3.0_disk1_1of1.zip.
  1. On the Disk1 directory execute: setup -jreLoc C:\Oracle\Middleware\jdk160_18

Creating a Weblogic domain for SOA

Execute C:\Oracle\Middleware\Oracle_SOA1\common\bin\config.cmd Create a ne Weblogic domain with all SOA products:
image008.jpg 29.5 KB
The domain name will be: domain1, and the admin password: welcome1 Select JVM: Sun SDK 1.6.0_18 @ C:\Oracle\Middleware\jdk160_18 Create the DB conecction to the schemas created with RCU:
image010.jpg 38.2 KB
Terminate the creation without optional config.

SOA Extension for JDeveloper

In JDeveloper Help > Check for Updates > Search Update Centers > Oracle Fusion Middleware Products must be checked. Check the following products:
  • Oracle BPM Studio
  • Oracle SOA Composite Editor

Management consoles

Weblogic administration console:
image011.png 222 KB
Enterprise manager:
image013.png 200 KB
B2B console:
image015.png 139 KB
Business Activity Monitor (BAM) only through IE:
image017.png 128 KB
Soa/composer and bpm/composer:
image021.png 75.1 KB
image019.png 67.2 KB