UMD

Best UMD Ever!

UMD

Issues raised in the last forum

1. To be updated on the current prjects

2. To have a repository of bugs\Srs\problems that were

fixed in the past or being handeled now

3. Version managment flow - should be re-design

Suggested improvements

1. One Access - One access release which will load on

the fly the relevant dlls.

2. Less branches - unite few brunches to one (SG for

example)

3. Create a process for cross branch bugs (generic bugs

or critical bugs in CCFlow or Core)

4. Feature automatic configuration - a tool that will set all

the relevant configuration (registry & spring)

5. Configuration repository - A list of the registry

configuration. Include explanations of the main role,

use and what is their impact.

Gaps

42.195 KM

1. History knowledge

* Features (Summary report, Direct delivery, AF)

* Configuration

2. Automation and Unit tests

3. Major features should be redesign (have a lot of

problems) - S&F, fan out, locks in CCflow

4. Code review - very difficult to enforce

Improvements

1. Build

* UMD components are complied in the Jenkins

* Each developer need to have a user to the Jenkins

* 4 work days needed in order to use complile the configuration as well

2. Targeting 2012 - 5 days of Irena are needed (and

tests of course)

3. CI - new dedicated developer - need to set priorities