| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| <HTML><HEAD><TITLE>Eclipse |
| TPTP Project Approved 3.3 Release Plan</TITLE> |
| <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> |
| <META content="Eclipse Project PMC" name=Author> |
| <META content="Microsoft FrontPage 5.0" name=GENERATOR> |
| <META content=FrontPage.Editor.Document name=ProgId><LINK |
| href="../default_style.css" type=text/css |
| rel=stylesheet></HEAD> |
| <BODY> |
| <H1>Eclipse Test & Performance Tools Platform (TPTP) Project<BR>Approved 4.0 Plan</H1> |
| <P>Frozen version for the <a href="../../roadmap.html">Eclipse Roadmap v1.0</a>, Last revised 16:00 PST 31 January 2005 (<IMG height=12 |
| src="new.gif" width=12 border=0> marks |
| interesting changes since earlier draft)<br> |
| The most current version of this document is available on |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://www.eclipse.org/tptp/home/project_info/devplans/Eclipse%20TPTP%20Project%20Approved%204.0%20Release%20Plan.htm">the |
| TPTP website</a>.<BR><BR><I> Please send comments |
| about this plan to the </I><a href="mailto:tptp-pmc@eclipse.org">tptp-pmc@eclipse.org</a> |
| <i>PMC |
| mailing list.</i></P> |
| <P>This document lays out the feature and API set for the TPTP 4.0 release. |
| <UL> |
| <LI><A |
| href="#Deliverables">Release |
| Deliverables</A> |
| <LI><A |
| href="#Milestones">Release |
| Milestones</A> |
| <LI><A |
| href="#TargetOperatingEnvironments">Target |
| Operating Environments</A> |
| <LI><A |
| href="#Compatibility">Compatibility |
| with Previous Releases</A><LI><a href="#Themes">Themes</a></LI> |
| <LI><a href="#Projects">Projects</a></LI> |
| <LI><a href="#Features">Features</a></LI> |
| <LI><a href="#Defects">Defects</a></LI></UL> |
| <P>The first part of this plan deals with the important matters of release |
| deliverables, release milestones, target operating environments, and |
| release-to-release compatibility. These are all things that need to be clear for |
| any release, even if no features were to change. |
| <P>The remainder of the plan consists of plan items for the four projects under |
| the TPTP Top-Level Project. Each plan item covers a feature or API that is to |
| be added to TPTP, or some aspect of TPTP that is to be improved. Each plan |
| item has its own entry in the TPTP bugzilla database, with a title and a |
| concise summary (usually a single paragraph) that explains the work item at a |
| suitably high enough level so that everyone can readily understand what the work |
| item is without having to understand the nitty-gritty detail. |
| <P>Not all plan items represent the same amount of work; some may be quite |
| large, others, quite small. Some plan items may involve work that is localized |
| to a single component; others may involve coordinated changes to |
| several components; other may pervade the entire project. |
| <P>With the previous release as the starting point, this is the plan for how we |
| will enhance and improve it. Fixing bugs, improving test coverage, |
| documentation, examples, performance tuning, usability, etc. are considered |
| routine ongoing maintenance activities and are not included in this plan unless |
| they would also involve a significant change to the API or feature set, or |
| involve a significant amount of work. The intent of the plan is to account for |
| all interesting feature work. |
| <H2><A name=Deliverables></A>Release Deliverables</H2> |
| <P>The following release deliverables are provided: |
| <UL> |
| <LI>Runtime </LI> |
| <LI>Source </LI> |
| <LI>Examples </LI> |
| <LI>Component Test </LI> |
| <LI>Data Collection Engine for Windows (NT, 2000, XP) Runtime </LI> |
| <LI>Data Collection Engine for Linux x86 Runtime </LI> |
| <LI>Data Collection Engine for Linux 390 Runtime </LI> |
| <LI>Data Collection Engine for zSeries Runtime </LI> |
| <LI>Data Collection Engine for iSeries Runtime </LI> |
| <LI>Data Collection Engine for Solaris Sparc Runtime </LI> |
| <LI>Data Collection Engine for AIX PPC Runtime </LI> |
| <LI>Data Collection Engine for HP-UX Runtime </LI> |
| <LI>Native Logging Implementation (All platforms) </LI> |
| <LI>Plugin Translatability Log</LI></UL> |
| <H2><A name=Milestones></A>Release Milestones</H2> |
| <P>The TPTP 4.0 release is targeted for general availability on 27-Jun-2005. |
| All release deliverables will be available for download as soon as the release |
| has been tested and validated in the target operating configurations. |
| Interim release milestone are planned at roughly 6 week intervals to facilitate |
| coarse-grained planning and staging. </P> |
| <TABLE width=821 border=1 id="table1"> |
| <TR> |
| <TD width=793 colspan="3" bgcolor="#C0C0C0"> |
| <p align="center"><b><font size="+1">Release Milestones</font></b></TD> |
| </TR> |
| <TR> |
| <TD width=205 bgcolor="#C0C0C0"><B>Milestone</B></TD> |
| <TD width=159 bgcolor="#C0C0C0"><b>Date</b></TD> |
| <TD width=416 bgcolor="#C0C0C0"><b>Description</b></TD></TR> |
| <TR> |
| <TD width=205>Iteration 1 (4.0 i1)</TD> |
| <TD width=159>Monday, 21-Feb-05</TD> |
| <TD width=416>Stable build</TD></TR> |
| <TR> |
| <TD width=205>Iteration 2 (4.0 i2)</TD> |
| <TD width=159>Monday, 4-Apr-05</TD> |
| <TD width=416>Stable build - API / UI freeze</TD></TR> |
| <TR> |
| <TD width=205>Iteration 3 (4.0 i3)</TD> |
| <TD width=159>Monday, 16-May-05</TD> |
| <TD width=416>Stable build</TD></TR> |
| <TR> |
| <TD width=205>Iteration 4 (4.0 i4)</TD> |
| <TD width=159>Monday, 27-Jun-05</TD> |
| <TD width=416>General Availability, English and Translated</TD></TR> |
| </TABLE> |
| <H2><A name=TargetOperatingEnvironments></A>Target Operating Environments</H2> |
| <P>In order to remain current, each TPTP release targets reasonably current |
| versions of the underlying operating environments.</P> |
| <ul> |
| <li>Java runtime (JRE) or Java development kit (JDK) 1.4 |
| </li> |
| <li>Eclipse SDK 3.1.1 for |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/eclipse-SDK-3.0.1-linux-gtk.zip">Linux (GTK)</a> , |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/eclipse-SDK-3.0.1-linux-motif.zip">Linux (Motif)</a>, or |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://download.eclipse.org/downloads/drops/R-3.0.1-200409161125/eclipse-SDK-3.0.1-win32.zip">Windows</a> (<IMG height=12 |
| src="new.gif" width=12 border=0> prior TPTP releases dependent on Eclipse SDK |
| 3.0.1)</li> |
| <li>Eclipse Modeling Framework (EMF) SDK |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://download.eclipse.org/tools/emf/downloads/drops/2.0.1/R200409171617/emf-sdo-SDK-2.0.1.zip">2.0.1</a> </li> |
| <li>XML Schema Infoset Model (XSD) SDK |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://download.eclipse.org/tools/emf/downloads/drops/2.0.1/R200409171617/xsd-SDK-2.0.1.zip">2.0.1</a> </li> |
| </ul> |
| <P>Most of the TPTP SDK is "pure" Java™ code and has no direct dependence on |
| the underlying operating system. The chief dependence is therefore on the Java 2 |
| Platform itself. The TPTP 4.0 release is written and compiled |
| against version 1.4 of the Java 2 Platform APIs, and targeted to run on version |
| 1.4 of the Java 2 Runtime Environment, Standard Edition.</P> |
| <P>There are many different implementations of the Java 2 Platform running atop |
| a variety of operating systems. We focus TPTP testing on a handful of popular |
| <SPAN class=header>combinations of operating system and Java 2 Platform; these |
| are our <EM>reference platforms</EM>. TPTP undoubtedly runs fine in many |
| operating environments beyond the reference platforms we test. However, since we |
| do not systematically test them we cannot vouch for them. Problems encountered |
| when running TPTP on non-reference platforms that cannot be recreated on any |
| reference platform will be given lower priority than problems with running |
| TPTP on a reference platform.</SPAN></P> |
| <P>TPTP SDK 4.0 is tested and validated on the following reference platforms |
| (this list may be updated over the course of the release cycle):</P> |
| <TABLE width=821 border=1> |
| <TBODY> |
| <TR bgColor=#cccccc> |
| <TH colSpan=2> |
| <DIV align=center><font size="+1">TPTP</font><B><FONT size=+1> Agent |
| Controller Reference Platforms</FONT></B> |
| </DIV></TH></TR> |
| <TR> |
| <TD width=96><B>Processor architecture</B></TD> |
| <TD width=709><B>Operating system</B></TD></TR> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709> |
| Red Hat Linux v7.1, v7.2, v7.3, v8.0</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>Red Hat Linux Advanced Server v2.1</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>SuSE Linux v7.2, v7.3</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>SuSE Linux Enterprise Server (SLES) v7, v8</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>Windows 2000 Advanced Server (service pack 2)</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>Windows 2000 Professional (service pack 2)</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>Windows 2000 Server (service pack 2)</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709> |
| Windows NT 4.0 (service pack 6a)</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>Windows Server 2003</TD> |
| </tr> |
| <tr> |
| <TD width=96>Intel IA32</TD> |
| <TD width=709>Windows XP Professional</TD> |
| </tr> |
| <tr> |
| <TD width=96>iSeries</TD> |
| <TD width=709>OS/400 V5R1, V5R2</TD> |
| </tr> |
| <tr> |
| <TD width=96>Itanium</TD> |
| <TD width=709>Windows and Linux TBD</TD> |
| </tr> |
| <tr> |
| <TD width=96>PA-RISC</TD> |
| <TD width=709>HP-UX v11.0, v11i</TD> |
| </tr> |
| <TR> |
| <TD width=96>RS/6000</TD> |
| <TD width=709>AIX v4.4.0, v5.1, v5.2</TD></TR> |
| <tr> |
| <TD width=96>PowerPC</TD> |
| <TD width=709>Windows and Linux TBD</TD> |
| </tr> |
| <tr> |
| <TD width=96>SPARC</TD> |
| <TD width=709>Sun Solaris v8, v9</TD> |
| </tr> |
| <TR> |
| <TD width=96>zSeries</TD> |
| <TD width=709>z/OS v1R4, v1R5</TD></TR> |
| </TBODY></TABLE> |
| <P>Although untested, TPTP should work fine on other OSes that support the same |
| window system.</P> |
| <H4>Internationalization</H4> |
| <P>TPTP is designed as the basis for internationalized products. |
| The user interface elements provided by the TPTP SDK components, including |
| dialogs and error messages, are externalized. The English strings are provided |
| as the default resource bundles.</P> |
| <P>Latin-1 locales are supported by the TPTP SDK on all of the above |
| operating environments; DBCS locales are supported by the TPTP SDK on the |
| Windows, GTK, and Motif window systems; BIDI locales are supported by the |
| TPTP SDK only on Windows operating environments. |
| <P>The TPTP SDK supports GB 18030, the new Chinese code page standard, on |
| Windows XP and 2000, and Linux. |
| <P>German and Japanese locales are tested.</P> |
| <H2><A name=Compatibility></A>Compatibility with Previous Releases</H2> |
| <P>TPTP 4.0 will be compatible with TPTP 4.0. The following specifies |
| details of the various aspects of release compatibility.</P> |
| <ul> |
| <li> |
| <P style="margin-top: 0; margin-bottom: 5px"><B> |
| API Contract Compatibility:</B> TPTP SDK 4.0 will be upwards |
| contract-compatible with TPTP SDK 3.3. Downward contract compatibility is not supported. There is no guarantee |
| that compliance with TPTP SDK 4.0 APIs would ensure compliance with TPTP SDK 3.3 APIs. Refer to |
| <img border="0" src="../external.gif" width="20" height="16"><I><A |
| href="http://eclipse.org/eclipse/development/java-api-evolution.html">Evolving |
| Java-based APIs</A></I> for a discussion of the kinds of API changes that |
| maintain contract compatibility.</P></li> |
| <li> |
| <P style="margin-top: 0; margin-bottom: 5px"><B> |
| Binary (plug-in) Compatibility:</B> TPTP SDK 4.0 will be upwards |
| binary-compatible with TPTP SDK 4.0. Downward plug-in |
| compatibility is not supported. Plug-ins for TPTP SDK 4.0 will not be usable |
| in TPTP SDK 3.3. Refer to |
| <img border="0" src="../external.gif" width="20" height="16"><I><A |
| href="http://eclipse.org/eclipse/development/java-api-evolution.html">Evolving |
| Java-based APIs</A></I> for a discussion of the kinds of API changes that |
| maintain binary compatibility. |
| </li> |
| <li> |
| <P style="margin-top: 0; margin-bottom: 5px"><B> |
| Source Compatibility:</B> TPTP SDK 4.0 will be upwards |
| source-compatible with TPTP SDK 3.3. This means that |
| source files written to use TPTP SDK 3.3 APIs might successfully compile and |
| run against TPTP SDK 4.0 APIs, although this is not guaranteed. Downward |
| source compatibility is not supported. If source files use new TPTP SDK APIs, |
| they will not be usable with an earlier version of the TPTP SDK. </li> |
| <li> |
| <P style="margin-top: 0; margin-bottom: 5px"><B> |
| Workspace Compatibility:</B> TPTP SDK 4.0 will be upwards |
| workspace-compatible with TPTP SDK 3.3 unless noted. This means that |
| workspaces and projects created with TPTP SDK 3.3 can be successfully opened |
| by TPTP SDK 4.0 and upgraded to a 4.0 workspace. This includes both hidden |
| metadata, which is localized to a particular workspace, as well as metadata |
| files found within a workspace project (e.g., the .project file), which may |
| propagate between workspaces via file copying or team repositories. Individual |
| plug-ins developed for TPTP SDK 3.1 should provide similar upwards compatibility |
| for their hidden and visible workspace metadata created by earlier versions; |
| 4.0 plug-in developers are responsible for ensuring that their |
| plug-ins recognize earlier version metadata and process it appropriately. |
| User interface session state may be discarded when a workspace is upgraded. |
| Downward workspace compatibility is not supported. A workspace created (or |
| opened) by a product based on TPTP 4.0 will be unusable with a product based |
| an earlier version of TPTP. Visible metadata files created (or overwritten) |
| by TPTP 4.0 will generally be unusable with earlier versions of TPTP. </li> |
| <li><B>Non-compliant usage of API's</B>: All non-API methods and classes, and |
| certainly everything in a package with "internal" in its name, are considered |
| implementation details which may vary between operating environment and are |
| subject to change without notice. Client plug-ins that directly depend on |
| anything other than what is specified in the TPTP SDK API are inherently |
| unsupportable and receive no guarantees about compatibility within a single |
| release much less with an earlier releases. Refer to |
| <img border="0" src="../external.gif" width="20" height="16"><I><A |
| href="http://www.eclipse.org/articles/Article-API%20use/eclipse-api-usage-rules.html">How |
| to Use the Eclipse API</A></I> for information about how to write compliant |
| plug-ins. |
| </li> |
| </ul> |
| <H2><a name="Themes"></a>Themes</H2> |
| <P>The TPTP PMC adopted and specialized the following Eclipse themes which |
| represent the key focus areas for TPTP enhancements in the year ahead.</P> |
| <ul> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Scaling Up -</b><span lang="EN-GB"> |
| </span>TPTP will work to enhance the support of large data volumes and |
| processing rates in areas such as data collection, user interface and in |
| the persistence of trace, log and statistical models and execution |
| histories.</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Enterprise Ready </b>- |
| Hooks will be provided within the TPTP infrastructure to link testing |
| tools to requirements tracking tools and defect tracking tools, thus |
| embedding them effectively in enterprise development cycles. Changes to |
| the data collection layers will increase interoperability with |
| enterprise security infrastructure. In addition, there will be |
| progressive adoption of the TPTP tools and infrastructure as a test |
| platform for the project itself, which is in turn likely to drive |
| refinements into the tools. An increased focus on whole-project |
| integration testing will ensure effective interoperability amongst all |
| TPTP components and the rest of the Eclipse environment.</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Design for |
| Extensibility: Be a Better Platform</b> - There will be a wide range of |
| activities within TPTP to externalize APIs and define extension points, |
| making the infrastructure more flexible, and more generic in |
| application.</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Simple to Use</b> - The |
| existing TPTP tools were conceived as samples, rather than as exemplary, |
| they are deficient in many areas of usability and in some cases lacking |
| in function. The plan is that within the domains which they target they |
| will provide a high-quality user experience out of the box. We will |
| focus on ease of use through enhanced user documentation, tutorials, |
| white papers, demonstrations, and a wide range of enhancements to the |
| user interface to streamline basic processes and clarify concepts and |
| terminology.</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Enable Consistent |
| Multi-language Support</b> - In TPTP a significant effort will be |
| applied in extending coverage of the trace models to represent C/C++ |
| programs and to handle protocol activity (specifically HTTP) |
| consistently with program activity. There will also be C/C++ APIs |
| provided to the data collection and control layers.</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Appealing to the Broader |
| Community</b> - A range of initiatives will be taken to broaden the |
| community of potential and actual users of TPTP. Technically this will |
| include additional integration of open source test tool technologies |
| based on JUnit, and the various hooks to JUnit in the JDT, more data |
| collection agents – particularly focusing on open source technologies, |
| and additional operating system and hardware platforms from which data |
| can be collected. There will be additional marketing and an extensive |
| outreach program to the Eclipse community for additional contribution |
| and adoption.</li> |
| </ul> |
| <h2><a name="Projects"></a>Projects</h2> |
| <p style="margin-top: 0; margin-bottom: 0">The TPTP project is is comprised |
| of four, managed in a coordinated fashion, across which the plans items are |
| allocated. TPTP subprojects include:</p> |
| <ul> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>TPTP Platform Project </b>- |
| Provides common infrastructure in the areas of user interface, EMF based |
| data models, data collection and communications control, as well as |
| remote execution environments. Additionally, the Platform provides |
| extension points for leveraging or extending these capabilities in |
| solution specific tooling or runtimes. This includes Eclipse workbench |
| plug-ins as well as runtime plug-ins on a target and optionally remote |
| system.</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Testing Tools Project |
| </b>- Provides specializations of the TPTP Platform for testing (e.g. |
| test editors, trace/test conversion support), and exemplary extensible |
| tools for specific testing environments. Initially this includes three |
| test environments: JUnit, manual, and URL testing. These specializations |
| provide optimized editing and reporting experiences for these use cases. |
| In the cases where a unique runtime or an implementation of a |
| testability interface is required, it is also developed in the project. |
| For example, the manual test execution environment provides a remotely |
| managed user interface specifically for collecting manual test progress. |
| This manual user interface is unique from the common execution |
| environment for JUnit and URL testing. . </li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 5px"><b>Tracing & Profiling |
| Tools Project</b> - Extends the TPTP Platform with specific data |
| collection for Java and distributed applications that populate the |
| common trace model, additional language and protocol support is |
| anticipated. There are also viewers and analysis services that draw data |
| from the common trace model. Capabilities are provided to collect and |
| analyze heap and stack information as well as generic toolkits for |
| instrumenting running applications..</li> |
| <li> |
| <p style="margin-top: 0; margin-bottom: 0"><b>Monitoring Tools Project |
| </b>- Extends the TPTP Platform for collecting, analyzing, aggregating, |
| and visualizing data that can be captured in the log and statistical |
| models. The typical examples are the collection of system or application |
| resources such as CPU or memory utilization and support for the viewing, |
| aggregation, and analysis of that data. Logs can also be transformed |
| into a common format and model allowing for symptom and pattern |
| analysis. The correlation of the data in these models is of particular |
| interest when it is associated with other model instances of statistical |
| or log data as well as traces and tests.. </li> |
| </ul> |
| <h2><a name="Features"></a>Features</h2> |
| <p>Plan items targeted for this release represent the addition of new |
| features or areas where existing features will be significantly reworked or |
| enhanced. Plan items are allocated to themes and projects indicated |
| above. </p> |
| <blockquote> |
| <p style="margin-top: 0; margin-bottom: 0">See |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://dev.eclipse.org/viewcvs/indextools.cgi/~checkout~/hyades-home/docs/unapproveddrafts/project%20info/plans/3+/TPTPFeatures.html">TPTP 4.0 Features</a> for a detailed listing of plan items targeted for this |
| release.</p> |
| <p style="margin-top: 0; margin-bottom: 0">Select "4.0" tab. Items |
| with "Priority" = "P1" and "In Plan" = "Committed" represent items |
| features targeted for this release.</p> |
| </blockquote> |
| <h2><a name="Defects"></a>Defects</h2> |
| <p>In addition to the targeted features for this release, we plan to reduce the defect backlog.</p> |
| <blockquote> |
| <p style="margin-top: 0; margin-bottom: 0">See |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://dev.eclipse.org/viewcvs/indextools.cgi/~checkout~/hyades-home/docs/reports/bugs/bugreport_40.html">TPTP 4.0 Defects</a> for a listing of the |
| current defect targets and backlog.</p> |
| <p style="margin-top: 0; margin-bottom: 0">Select "4.0 [nil | i1 | i2] |
| bugs" tabs.</p> |
| </blockquote> |
| <p> </p> |
| <p> </p> |
| <p> </p> |
| <p> </p> |
| |
| </BODY></HTML> |
