Introduction
OHT Boca and Arrow Charts
•
•
•
•
•
•
•
The Boca and Arrow charts are required for every project every quarter.
The purpose of the Boca chart is to have a similar information structure which can
convey the activities of the project for the next quarter. A similar structure enables many
projects to communicate quickly and efficiently.
The purpose of the Arrow chart is to provide a rolling 1 year forecast of what is coming.
This enables the other projects to understand the coming highlights so dependencies,
integration, PR plans etc can be developed.
The Boca and Arrow also enable organizations and individuals to conduce a gap
analysis. This will help with fulfilling requirements, dependencies and enable
commercial companies to build products and to create collaborative niches.
The Boca and Arrow will be part of the OHT web site and will be public.
Please note that all activities within OHT are defined as projects. Thus there is an
example of a partner program which follows the same format of the Boca and Arrow
structure.
The term Boca and Arrow charts are for the purpose of communication. The terms
“Boca” and “Arrow” are designed to be value free. We have deliberately not called these
plan charts because of the negative connotations associate with publishing unrealistic
plans and the associated accountability. We are absolutely seeking total honesty in the
creation and communication of the content of the Boca and Arrow.
Example
Boca Chart
Template
Pressures
OHT Project QQ/YYY
Boca Chart
Content
Added
Deleted & Changed
Dependencies
Packaging Editions
.
Statistics
.
Milestones
12 Month Rolling Plan
Template Major Dates and Deliverables
Arrow Chart
1Q2002
1Q03
4Q02
3Q02
2Q02
1Q02
Example
Boca Chart Eclipse SDK
Technical plan
Pressures:
Plan Content:
•Footprint
•Startup performance
•I18N on non-windows
•Non-local files
•Integrated web browser on
non-windows
•Swing/SWT integration
•More linux versions
•RPM install
•Torn off views
Dependencies:
•Solaris, AIX, HP – Rational
•Linux testing – Red Hat,
SuSE
•General testing - All
•Core development – OTI/IBM
•JDK 1.4.x (for hot code
replace) – only VM is from
Sun
•GB18030 support requires
GB18030-enabled JDK e.g.
Sun 1.4.1 or IBM 1.4.0 or
IBM 1.3.1sr1 (there are
known limitations in these
vms)
•NL testing – IBM
2.1 – Mar 2003
•Performance work, including improve
startup time
•Allow user customizable key bindings
•More flexible project layout
•Support building projects with circular
dependencies
•Support multi-JAR system libraries
•Improve update manager
•Add new refactorings
•Add workbench editor navigation
history
•Support double byte character sets on
Linux/GTK
•Improve Ant support
Added:
Deleted/Changed:
Configurations:
•Win32, linux-motif, linux-gtk, solarismotif, aix-motif, hpux-motif, qnx-photon,
mac-carbon (early access)
Milestones:
•Mar 7, 2003 – RC2
•Mar 14, 2003 – RC3
•March 28, 2003 – 2.1
Example
Eclipse SDK Release Roadmap
Arrow Chart
2.1.1
2Q 2003
Guiding Principles:
•Stable 2.0 code base actively maintained
•Accumulate requirements for major upgrades
before starting 3.0
2.0.1
Sep 2002
2.0
June 2002
1.0
Nov 2001
2.1
Mar 2003
2.0.2
Nov 2002
2.2
Development Begins
After 2.1
Example
Boca Chart
Partner program
Pressures/Exposures
- education / training
Partner Program
Q3 2000 Boca Chart
Content
Added
- Conceptual framework for partners
program
- Legal documents and process
- Competitive Positioning (VM,
Tools & Programs)
- Partner Program life cycle & Plan
- Minimum of 3 Partner’s signed
each quarter
Deleted & Changed
- Wireless Value-Chain analysis
Dependencies
Packaging Editions
Partner’s Web Portal
Partner Program Plan (internal /
external presentations)
Milestones
12 Month Rolling Plan
Example
Arrow Chart
Partner Program
Partner program Roll Out Dates and Deliverables
1Q01 Partner List Prioritized
Top 3 Partners Closed
15 – 20 Active Partner Negotiations
Support Closed Partners (training, sales assistance, etc)
Sep00
4q00 Partner List Prioritized
9/00 - Partner Portal Available
Top 3 Partners Closed
9/00 VAME Partner Program Announced
15 – 20 Active Partner Negotiations
9/00 VAME Partner Event @ ESC West
Support Closed Partners (training, sales assistance, etc)
8/00 - Partner Training Plan & Sales Kit Complete
Jun00
3q00 Partner List Prioritized
15 – 20 Active Partner Negotiations
Mar00
5/00 - Partner Program Plan Complete
Example
Boca Chart
Technical plan
Eclipse SDK 2.0 - Spring 2002
Pressures:
•Footprint
•Java Editor – performance,
configurability
•I18N on non-windows
•Non-local files
•Integrated web browser on
non-windows
•Swing/SWT integration
•More linux versions
•RPM install
Dependencies:
•Solaris, AIX, HP – Rational
•Linux testing – Red Hat,
SuSE
•General testing - All
•Core development – OTI/IBM
•JDK 1.4.0 (for hot code
replace) – only VM is from
Sun – IBM date?
•GB18030 support requires
GB18030-enabled JDK e.g.
Sun 1.4.0 or IBM 1.4.0 or
IBM 1.3.1sr1 (with
limitations)
•NL testing – IBM
Plan Content:
•Performance – startup, text editor,
perspective switching, build
•Footprint reduction – Java Builder
•Hot code replace (JDK 1.4 and J9)
•VCM – new team story
•Install/update – plugin delivery
•True unicode (windows only)
•GB18030 chinese code page
•Accessibility – section 508
•Improved usability – losing context
(editor management), editor/view
interaction (menu/toolbar)
•Improve performance and appearance
on Motif
•VCM – validate edit/save
•Non-versioning webdav support
•Simplify help definition mechanism
•Live help,Help servers,Standalone help
•Debug – stable API, launch configs
•JDT – improved code assist (args/var
names), search, 1.4 compiler, new
refactoring,externalization wizard
Configurations:
•Win32, linux-motif, linux-gtk, solarismotif, aix-motif, hpux-motif, qnx-photon,
mac-carbon (early port)
Added:
•GTK 2.0 support
•I18N - Latin 1 – all Motif
•Team - Move/Ren/Del, Unmanaged
resources
•Drag&Drop on Motif
•Lucene Help Search (english stems)
•Javadoc generation
•Improved CVS – better interop with
cmd line CVS, integrated patch maker
•JDT – Java Editor – error clueing
(red wavy lines), line/col #’s, key
bindings
•JDT – API for Abstract Syntax Trees
•JDT Debug – field watchpoints
•JDT – Integrated Junit support
Deleted/Changed:
•Experimental Scripting support
•Build your own eclipse SDK
•Proj Natures – improved usability
Milestones:
•March 15, 2002 – M4
•April 16, 2002 – M5
•May 21, 2002 – F1 (Freeze 1)
•Late June – Golden Code
•Early July – Golden Code + Final Doc
12 Month Rolling Plan
Example
Arrow Chart Eclipse SDK Release Roadmap
(proposed)
Guiding Principles:
•Stable 2.0 code base actively maintained
2.3
May 2003
•Long cycle for 3.0 to allow major upgrades
2.2
Jan 2003
2.1
Sep 2002
2.0
May 2002
1.0
Nov 2001
3.0
Development Begins
Fall/Winter 2002
3.0
Concept Work Begins
Summer 2002
3.0
Fall 2003
Example
Boca Chart
Technical plan
Eclipse SDK 2.0 - Spring 2002
Pressures:
•Footprint
•Java Editor – performance,
configurability
•I18N on non-windows
•Non-local files
•Integrated web browser on
non-windows
•Swing/SWT integration
•More linux versions
•RPM install
Dependencies:
•Solaris, AIX, HP – Rational
•Linux testing – Red Hat,
SuSE
•General testing - All
•Core development – OTI/IBM
•JDK 1.4.0 (for hot code
replace) – only VM is from
Sun – IBM date?
•GB18030 support requires
GB18030-enabled JDK e.g.
Sun 1.4.0 or IBM 1.4.0 or
IBM 1.3.1sr1 (with
limitations)
•NL testing – IBM
Plan Content:
•Performance – startup, text editor,
perspective switching, build
•Footprint reduction – Java Builder
•Hot code replace (JDK 1.4 and J9)
•VCM – new team story
•Install/update – plugin delivery
•True unicode (windows only)
•GB18030 chinese code page
•Accessibility – section 508
•Improved usability – losing context
(editor management), editor/view
interaction (menu/toolbar)
•Improve performance and appearance
on Motif
•VCM – validate edit/save
•Non-versioning webdav support
•Simplify help definition mechanism
•Live help,Help servers,Standalone help
•Debug – stable API, launch configs
•JDT – improved code assist (args/var
names), search, 1.4 compiler, new
refactoring,externalization wizard
Configurations:
•Win32, linux-motif, linux-gtk, solarismotif, aix-motif, hpux-motif, qnx-photon,
mac-carbon (early port)
Added:
•GTK 2.0 support
•I18N - Latin 1 – all Motif
•Team - Move/Ren/Del, Unmanaged
resources
•Drag&Drop on Motif
•Lucene Help Search (english stems)
•Javadoc generation
•Improved CVS – better interop with
cmd line CVS, integrated patch maker
•JDT – Java Editor – error clueing
(red wavy lines), line/col #’s, key
bindings
•JDT – API for Abstract Syntax Trees
•JDT Debug – field watchpoints
•JDT – Integrated Junit support
Deleted/Changed:
•Experimental Scripting support
•Build your own eclipse SDK
•Proj Natures – improved usability
Milestones:
•March 15, 2002 – M4
•April 16, 2002 – M5
•May 21, 2002 – F1 (Freeze 1)
•Late June – Golden Code
•Early July – Golden Code + Final Doc
Example Eclipse SDK Release Roadmap
Arrow Chart
(proposed)
Guiding Principles:
•Stable 2.0 code base actively maintained
2.3
May 2003
•Long cycle for 3.0 to allow major upgrades
2.2
Jan 2003
2.1
Sep 2002
2.0
May 2002
1.0
Nov 2001
3.0
Development Begins
Fall/Winter 2002
3.0
Concept Work Begins
Summer 2002
3.0
Fall 2003