MySpace Iteration3 Plan and Forecast

Plan:

• Enhancement and Consolidation of Iteration2: start + 3Weeks(01/07/03 -- 25/07/03)
  • Code revise and UML reflect current code in place: done
  • Test environment set up:Tomcat/Axis,TogetherSoft(optional): ACD will try to use grendel12 to perform ServerSide^? Test.
  • JUnit test in place: Week2: almost done
  • Web Services Up and Running: done
  • External Interface in place: done
  • Refactoring including jConfig Message/Error Logs -- Week2+Week3: still need to be completed
  • Bug Fixing and Unit Testing: All through Consolidation Period. ACD and CLQ: on going
  • Study Registry and find out similarity between Registry and MySpaceRegistry: not nessesary for Iteration 3.
  • get certificate from e-science ACD and CLQ
  • Building stubs and (dummy)MySpaceManager Service stubs and delegates for other WG to access: done

• New Functions in Iteration3: 04/08/03 -- 15/09/03
  • ACD:
    • Upload/download(including Ftp transferring or http transferring investigation)
    • CreateUser
    • DeleteUser
    • ChangeOwner
    • StructureMySpace
    • Backup Registry file
  • BKM:
    • Integrating Dave's MSExplore and emelfm' look and feel - Before 18th Aug 2003)
    • Adding new functionalities and Authorise(Working with CLQ) - after 5th Sep 2003
  • CLQ:
    • UML plan
    • ServerToServer use case
    • Authorise (Working with Brian)
    • Extend Lease
    • Publish

• • Holidays:
    • BKM: 18th Aug to 5th Sep
    • ACD: 18th Aug to 29th Aug
  • Booked time for other activities:
    • CLQ: 18th Aug to 29th Aug - prepare All-hands E-Science meeting talk in Nottingham
    • CLQ: 2nd Sep to 4th Sep All-hands E-Science meeting in Nottingham
    • ACD: 11th Aug
    • BKM: basicly being devided between Community and MySpace so half time.
  • Useable Time for Iteration 3 from 4th Aug till 15th Sep(Code freeze)
    • CLQ: 4.5 weeks
    • ACD: 4 weeks
    • BKM: 1.5 weeks
    • TOTAL: 10 weeks

Quality control:

• Should have Continuous integration testing throughout It3.
• Should integrate with portal/community asap.
• Developers check code into CVS /devel at least once everyday.
• Workgroup leader update UML Model and stable code into CVS /release every week(every Friday)
• Training: AstroGrid will be setting up a support/training page.
• Unit test! Write Unit test while coding.
• Using Ant build while deploying.
• Communication within team: dayly question/anwser via email/telephone; weekly teleconf(every Monday afternoon); monthly face-to-face meeting.
• Communication between workgroups!
• Code freeze by 15/09/03

-- CatherineQin - 01 Aug 2003