Taco Information

Entering EVO#3

EVO#3

• CDR converter
• File receiver
• Optimizations
  • Testing (How much are we capable of processing
• Handle the comments that Europolitan gave us, i.e the changes in the database design
• User documentation
• QMG rework of the old quality documents.

---

Committments

• What about receiving CDR files via FTP? (req. F332) Esping
• What about the unknown CDR's, i.e roaming calls? (req. F336) Esping
• Responsible for the optimizations, see to that there will be better performance Esping,Dan Andersson, 20 May, Monday, 08.15, start
• Take care of the rewrite of the requirements specification and the contract Young, 20 May Monday 08.15 (start)
• Responsible for the FileReceiver Esping, 20 May, Monday, 08.15, ready and working
• Responsible for the CDR converter Dan Andersson, 20 May, Monday, 08.15, ready and working
• User documentation ready, Marcus Helgesson, finnished, 22 May, , afternoon
• Test specification ready, Marcus Helgesson, finnished, 17 May, Friday, afternoon
• The intermediate code has to be documented, Wigge, 22 May Wednesday, written and ready to print
• Make a specification of what's to be included in the last delivery, included an attribute spec., Tobias Eriksson, May 15, Wednesday, 08.15
• Make a WBS/top level design specification, Tobias Eriksson, May 15, Wednesday, 08.15
• Make a subrequirements specification, Tobias Eriksson, May 20, Monday, 16.00, ready
• Check the changes made to the Database design.
• Fill in the tags for the requirements in the design documents, concerns everybody.
• Testdata has to be made, this includes all areas, i.e CDR's, CDR-mapping file, Intermediate code etc. Responsibles are Dan Andersson CDR-Mapping, Esping CDR's, Wigge 4G HCL.

General Information

• Information about number analysis, resp. Young, document describing this
• Survey about Threads, which we decided not to use, see ..., Wigge
• CDR information can be found here -> , Esping, 26 April ready and working

General schedule (this is a preliminary schedule)

Week 21
Monday Implementation and filuring kring optimeringar
Tuesday Implementation finnished, Optimizations
Wednesday Optimizations and Final Integration
Thursday Testing
Friday Final Delivery
Saturday
Sunday