scope:
Not really a “plan”, time planning is done on a “EMI release” granularity level 
Not really “technical” compared to the area workplans
Not intended to be directly used by developers as a “development” plan
Main goal is to set “project direction”, capture high-level objectives based on collected requirements and to present some vision.
Also serves as the source for EMI component  and PT definition

TOC of DNA1.3.2
Absract
1. INTRODUCTION 
1.1. PURPOSE
1.2. DOCUMENT ORGANISATION 
1.3. REFERENCES
1.4. DOCUMENT AMENDMENT PROCEDURE 
1.5. TERMINOLOGY 
2. EXECUTIVE SUMMARY 
3. REQUIREMENTS
4. EMI COMPONENTS AND PRODUCT TEAMS 
5. TECHNICAL OBJECTIVES
5.1. HIGH LEVEL VIEW
5.2. Invetory of OBJECTIVES 
6.CONCLUSIONS
APPENDIX (EMI package list)






-- Main.FloridaEstrella - 15-Apr-2011
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2011-05-05 - BalazsKonya
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback