| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| <!-- saved from url=(0072)http://eclipse.org/eclipse/development/eclipse_project_plan_summary.html --> |
| <!-- saved from url=(0022)http://internet.e-mail --> |
| <HTML xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns="http://www.w3.org/TR/REC-html40"><HEAD><TITLE>Eclipse Test & Performance Tools Platform (TPTP) Project Plan Summary</TITLE> |
| <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> |
| <META content="Eclipse Project PMC" name=Author> |
| <link rel="stylesheet" type="text/css" href="../default_style.css"> |
| <META content="Microsoft FrontPage 5.0" name=GENERATOR> |
| </HEAD> |
| <BODY> |
| <table border=0 cellspacing=5 cellpadding=2 width="100%" > |
| <tr> |
| <td align=left width="72%"> <font class=indextop>Test & Performance Tools Platform (TPTP) Project<BR>Plan Summary</font> <br> |
| <font class=indexsub> the open community driving the eclipse platform</font> </td> |
| <td width="28%"> |
| <img src="/images/Idea.jpg" height=86 width=120></td> |
| </tr> |
| </table> |
| |
| <P>Frozen version for the <a href="../../roadmap.html">Eclipse Roadmap v1.0</a>, last revised February 16, 2005.<br> |
| The most current version of this document is available on |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://eclipse.org/tptp/home/project_info/devplans/EclipseTPTPProjectPlanSummary_Q105.htm">the |
| TPTP website</a>.</P> |
| <h2>Executive Summary of Current Plan</h2> |
| <P>The Eclipse TPTP Project is currently working on three releases as follows:</P> |
| <table border="1" width="100%" id="table1"> |
| <tr> |
| <td width="105" bgcolor="#C0C0C0" align="center"><b>Release*</b></td> |
| <td width="139" bgcolor="#C0C0C0" align="center"><b>Target Release Date</b></td> |
| <td bgcolor="#C0C0C0"><b>Description</b></td> |
| </tr> |
| <tr> |
| <td width="105" align="center"> |
| <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_302.html">TPTP 3.0.2</a></td> |
| <td width="139" align="center">18-Mar-05</td> |
| <td> |
| <p style="margin-top: 4px; margin-bottom: 4px; text-indent:-20px; margin-left:20px"> |
| Maintenance release delivered in support of the Eclipse Platform 3.0.2 |
| maintenance release<br> |
| <i>Targeted for legacy |
| adopters of TPTP 3.0.x who require various fixes, but are unable to |
| adopt a new TPTP major/minor release in this timeframe.</i></p></td> |
| </tr> |
| <tr> |
| <td width="105" align="center"> |
| <a href="tptp_3.3_Plan_2005_01_31.htm">TPTP 3.3.0 (January 31, 2005)</a></td> |
| <td width="139" align="center">16-May-05</td> |
| <td> |
| <p style="text-indent: -20px; margin-left: 20px; margin-top: 4px; margin-bottom: 4px">Feature release based on the Eclipse Platform 3.0.x release<br> |
| <i>Targeted for legacy adopters of TPTP who require additional TPTP |
| features/fixes, but are not able to move to the Eclipse Platform 3.1 |
| release in this timeframe.</i></td> |
| </tr> |
| <tr> |
| <td width="105" align="center"> |
| <a href="tptp_4.0_Plan_2005_01_31.htm">TPTP 4.0.0 (January 31, 2005)</a></td> |
| <td width="139" align="center">27-June-05</td> |
| <td> |
| <p style="text-indent: -20px; margin-left: 20px; margin-top: 4px; margin-bottom: 4px">Feature release based on the Eclipse Platform 3.1.0 release<br> |
| <i>Targeted for new TPTP adopters and legacy adopters who require |
| additional TPTP features/fixes and are ready to move to the Eclipse |
| Platform 3.1.0 release; TPTP 4.0.0 includes TPTP 3.3.0 and prior |
| features/fixes.</i></td> |
| </tr> |
| </table> |
| <p style="margin-top: 0"><font size="1">* Follow links above for access to the |
| respective release plan summaries.</font></p> |
| <P>Our general release philosophy is to release TPTP coincident with Eclipse |
| Platform releases and provide more frequent interim releases as applicable. |
| This generally translates to an annual major release in June, quarterly minor |
| releases thereafter (September, December, March), and maintenance releases as |
| needed. </P> |
| <P>In addition to the above releases approved by the TPTP PMC and Planning |
| Group, we have recently commenced the planning cycle for our follow-on TPTP 4.1 minor |
| release targeted for September 2005 and we will publish such plan information |
| when available.</P> |
| <P>Details of the current plan(s) can be found at:</P> |
| <ul> |
| <li><span style="font-family: Arial, Helvetica, sans-serif">Planning and |
| execution information at </span> |
| <img border="0" src="../external.gif" width="20" height="16"><span style="font-family: Arial, Helvetica, sans-serif"><a href="http://www.eclipse.org/tptp/home/project_info/index.php?">TPTP D</a></span><a style="font-family: Arial, Helvetica, sans-serif; font-size: 10pt" href="http://www.eclipse.org/tptp/home/project_info/index.php?">evelopment |
| Plans</a><span style="font-family: arial, helvetica, geneva"> </span></li> |
| <li><span style="font-family: Arial, Helvetica, sans-serif">Architecture plan at</span><span style="font-family: arial, helvetica, geneva"> |
| </span> |
| <img border="0" src="../external.gif" width="20" height="16"><a href="http://www.eclipse.org/tptp/groups/Architecture/documents/arch_main.html">TPTP |
| Architecture Plan</a>.</li> |
| </ul> |
| <h2>Forward Looking Statement</h2> |
| <p>The TPTP PMC adopted and specialized the following |
| <a href="../../themes.html">Eclipse Themes and |
| Priorities</a> which |
| represent the key focus areas for TPTP enhancements in releases for the year |
| ahead:</p> |
| <ul> |
| <li> |
| <p style="MARGIN-TOP: 0px; 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: 0px; 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: 0px; 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: 0px; 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: 0px; 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: 0px; 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> |
| <p>We are tracking and supporting the following standards and projects: </p> |
| <ul> |
| <li>We support the <b>OMG UML2 Test Profile</b> and have implemented an |
| early draft of the model. We are assessing the need to change our test |
| model in a future release. Additionally, our members have participated in |
| the definition of the OMG effort to define this model. </li> |
| <li>We provide an implementation of <b>Common Base Event</b> which is |
| currently a proposed standard submission to Oasis. Once approved we will |
| implement the changes needed to comply with the specification. We also |
| provide an adaptor for the Eclipse Platform so that all Eclipse tools can |
| become producers of this logging format and leverage our analysis tooling. |
| </li> |
| <li>In a future release we intend to provide a <b>JVMTI (JSR 163)</b> |
| based data collector to replace our current <b>JVMPI</b> agent. We are |
| currently pursuing contributors to get this into our plans. This will |
| improve the install experience as well as improve our coexistence with |
| other infrastructure tooling. </li> |
| <li>We are actively working with the Eclipse Platform team support to add |
| support for logical resources and record based resources in order to |
| provide more enterprise and scalable team solutions. This is in line with |
| <b>JSR 147 </b>(logical and record resources) and <b>JSR 170 </b>(logical |
| resources). </li> |
| <li>We are also driving extension of our testing and execution frameworks |
| based on other de facto based standards that derive from <b>JUnit</b>, |
| such as <b>HTTPUnit</b> and <b>Abbot</b>.</li> |
| </ul> |
| <p style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 5px">The following illustration |
| summarizes TPTP recent releases and roadmap (TPTP Approved/Pending status refers to |
| TPTP PMC and Planning Group approval status):</p> |
| <p align="center"> |
| <img border="0" src="TPTP%20Project%20Roadmap%20-%2018-Feb-05.gif" width="644" height="396"></p> |
| <p>For more information, visit the |
| <img border="0" src="../external.gif" width="20" height="16"><a target="_top" href="http://www.eclipse.org/test-and-performance/">Eclipse Test and |
| Performance Tools Platform (TPTP) Project</a> website.</p> |
| <p> </p> |
| <p align="center"> </p> |
| <p> </p> |
| <p> </p> |
| <p> </p> |
| <p> </p> |
| <p> </p> |
| <p> </p> |
| |
| </BODY></HTML> |
