plan

Plan

Tasks Dependency Chart

In theory, the dependencies are not very strict, e.g. most parts can be started simultaneous, but this make things risky and complex.
Since the changes for B4PHT will propagate to the whole tempo and there are many trivial thing, which make it complex and hard to arrange, it's proposed that we split the whole project into serveral steps, according to the task dependency and priorty.

Step 1: TMS
As shown in above, the most fixed thing is the specification, which defines all tasks operations.
As a result, the TMS task including web service implementation and marshaller/unmarshaller is the first task we can start
, since it only depends on the spec. All call to security, persistence, TAS... etc could be dummy interface. This also means, TMS will decide how TAS/Security/Comments Service/Persistence is called.

step 2: TAS/Security/Comments Service/Persistence.
After step 1 finished, we can goto TAS/Security/Comments Service/Persistence, because at that time, it will be fixed that how TMS call them.

Step 3: TMP/UI/XFORM
The 3 parts are highly coupled, we should implement them at the same time.

Step 4: Migration Tools/Designer/WDS
After all, we should consider the 3 parts, to allow user use new tempo really.

Project Status(September 2009)

Step1: implemented
Step2: implemented, but no security integration with current tempo's security component. One should use WS-security.
Step3: TMP was dropped in the b4p branch, so no work. Any UI is left to user's implementation.
Step4: No migration tool available.

Time Schedule

All tasks already includes unit test.
Phase 1: Design write interface/framewo

Tasks	Time Estimated
architecture design	10 days
new Service interface(wsdl,server.xml, new requestProcessor, interface of new TMSServer)	10 days
marshaller/unmarsheller interface	5 days
db schema(mysql) + entity class interface	5 days
first integration test upon interface/dummy implementation	10 days
Total	40 manday

Phase 2:

Tasks	Time Estimated
Implements TMSClient/TMSServer for all operations ( will call security/marshaller/jpa ...)	50 days
Implements marshaller/unmarsheller	12 days
Implement entity class(persistence layer)	6 days
Security	7 days
Implements comments service	5 days
Attachements handling	8 days
UI & xform manager & TMP changes implemenation changes	18 days
Deployment service	8 days
Migration tools/testing	15 days
Designer	16 days
True integration Test & bug/defects fix	30 days
Total	175 mandays

Total Efforts: 215 mandays /3 month for 3 people