Hi everyone,
in this thread I will first be summarizing our case.
We have a large project at public sector with onshore and offshore teams. The technical designs and modeling is done onshore and the detailed implementation is being done offshore.
Technologies:
Oracle, Java,Hibernate, Spring, Richfaces
For the time being, we are using simple class diagrams with predefined uml pattern support to generate the structure of entities/components as Java code. Since we only have the corporate edition for the time being, we do not generate any behavioral code.
The project was initially not designed as a Model driven development project, so there are no predefined processes our big initial budget to book on MDD. I am integrating MDD solutions, whenever I get enough time for it. That means, we are looking for simpler solutions rather than heavy MDD designs.
I have some questions about this setting.
One problem is about forward-reverse engineering.
We first model onshore, generate the code and ship to offshore. The offshore can edit and change the code whenever necessary to get rid of some diesgn deffects or unforeseen parts.
While some technical designers are modeling the usecases (lets say usecase1), others are developing/modefiying some component (c12) for usecase2.
If that compoenent was used for the design of usecase1, the technical design of usecase1 is not fully valid anymore (because the component c1 is not aup to date.)
another case could be that the developers are modifying a component through code, where the TD's are modifying thorugh the model.
So, my question is:
How do you manage to process of forward and reverse engineering while preventing such conflicts? How do you deal with concurrent usage?
