1 / 13

OBS - CDR

OBS - CDR. OBS3. Design of OBS3 Status of OBS3 Configuration control. OBS3 - Design of OBS3. Status of OBS version 2 - OBS2 working on AVM1 - Most of code well written only needs consolidation - A few parts need entire rewriting for optimization on AVM2

qamar
Download Presentation

OBS - CDR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OBS - CDR OBS CDR – IFSI – May 3rd 2005

  2. OBS3 Design of OBS3 Status of OBS3 Configuration control OBS CDR – IFSI – May 3rd 2005

  3. OBS3 - Design of OBS3 • Status of OBS version 2 • - OBS2 working on AVM1 • - Most of code well written only needs consolidation • - A few parts need entire rewriting for optimization on AVM2 • - Code organisation can be improved • Design of OBS version 3 • - OBS2 is working and we are short of time. • - The approach is evolutionary and not revolutionary. • - All versions run on the AVM2. OBS CDR – IFSI – May 3rd 2005

  4. OBS3 - Design of OBS3 • Tasks • - Code optimization for AVM2 • Longer FIFOs to be exploited • - Code consolidation: • Homogenization of writing style and documentation • Breaking of long functions in smaller parts OBS CDR – IFSI – May 3rd 2005

  5. OBS3 - Design of OBS3 • - Addition of missing functionalities • System monitoring • Several TC commands • Some tuning procedures and measurements OBS CDR – IFSI – May 3rd 2005

  6. OBS3 - Design of OBS3 • - Improvement of software organization • Header files reorganisation • Minimisation of use of global variables • Increased modularity • Improved correspondance between code and documentation • Detailed Design update • - Testing • Module level testing • Integration testing • Off-line testing - Emulators OBS CDR – IFSI – May 3rd 2005

  7. OBS3 - Status of OBS3 • Code optimization for AVM2 • Done. HS has been rewritten. • Code consolidation • Some 10-15% of the code has undergone cosolidation • Doxygen has been selected as standard documentation style • It is proposed to move the (file and functions) headers into the .dox files (impact on CIDL) • Addition of missing functionalities • Essential House Keeping. Error Counting. Limit checking OBS CDR – IFSI – May 3rd 2005

  8. OBS3 - Status of OBS3 • Improvement of software organisation • Code reorganization proceeds in parallel with code consolidation • The process is iterative • Organisation of header files has been revised • New detailed design is under development • Migration from task to module OBS CDR – IFSI – May 3rd 2005

  9. OBS3 - Design of OBS3 OBS CDR – IFSI – May 3rd 2005

  10. OBS3 - Status of OBS3 • Testing • Testing procedures similar to those used for OBS2 are being and will be used • The feasibility of off-line emulators has been demonstrated for a single task. • Foreseen are the following emulators: hs1, tuning, data_pack, IV_curve. OBS CDR – IFSI – May 3rd 2005

  11. OBS3 - Configuration control CVS CVS is currently being used as versioning system The file first line is being handled by CVS reporting filename, revision and date. The file last lines are being handled by CVS reporting the full file history. The modules and function headers have been moved to the .dox file which is kept under configuration. Proposal: to remove file history and use CVS directly. OBS CDR – IFSI – May 3rd 2005

  12. OBS3 - Configuration control • SRN • The following list from Luc is the basis for discussion • a) SxR solved in this release (only number + title) - Cross reference of SPR solved and modules changed • b) Open SxR's at the time the code for the release was frozen • c) Complete traceback of modules (source code, configuration tables) that are in this release (CVS filename + version numbers preferred) (CIDL?) • d) Change log of software changes for modules, copied from official CVS rep. change notes if they are maintained= enough detail to describe the changes • e) List of all commands cross referenced against command spec document, and whether they are supported or not yet • f) List of open requirements cross referenced against URD, and whether they are supported or not yet • g) version's of applicable documents on which this release is based • i) A change summary of items a)-h) where only those that have changed with respect to the previous release are repeated OBS CDR – IFSI – May 3rd 2005

  13. OBS3 - Configuration control CIDL All source (.c, .s, .h) files All MIL files (.h, .o) The following virtuoso files makefile, allnodes.h, node1.h, cflags, obs.vpf, hifi.ach, obs.nli All documentation files (.dox) The input to the VM compiler. XLS tables. Level 2 The VM compiler. OBS CDR – IFSI – May 3rd 2005

More Related