FAQ for JBuilder Roadmap Announcement

By: Anders Ohlsson

Abstract: More details on this morning's press release

External FAQ for JBuilder Roadmap Announcement

May 31, 2005

Top Questions

Q:  What are you announcing today? Whats new?

A:  Were announcing new details around Borlands long-term product roadmap for JBuilder, and our ongoing investment in developers. This roadmap introduces two new JBuilder products that will be available within the next 12 months  JBuilder 2006 and project Peloton. The roadmap announcement also provides insight into the direction these products will take. Finally, were clarifying our plans utilize Eclipse as the underlying framework for future JBuilder and ALM products, clearing up some of the questions customers have had around our investments in Eclipse.

Q:  What does the future look like for JBuilder? Whats the roadmap?

A:  Since JBuilders introduction in 1997, Borland has offered enterprise Java developers a way to simplify and harness the latest technologies and Java standards to build better software, faster. The next generation of JBuilder will continue this tradition, while also addressing the growing challenges of managing distributed teams, larger projects and the expanding role developers are playing in the software delivery process.

Specifically, JBuilder will continue to evolve into a more collaborative development environment that will:

Make individual developers more productive

Provide developers with the ability to manage larger, more complex projects

Improve team collaboration  including collaboration across geographic boundaries

Enable teams to better leverage new technologies, standards and open frameworks

Provide developers with more visibility and control over the various areas of development process which they specifically impact (or are impacted by)

Provide developers with a clear path to Core SDP and Core::Developer

Q:  What will be in JBuilder 2006? When will it be available?

A: JBuilder 2006 exemplifies JBuilders continued evolution into a more collaborative developer environment. Already, JBuilder 2005 includes features such as distributed refactoring to help developers easily propagate changes across projects. JBuilder 2006 will include these and other new collaboration features, such as shared code editor views and joint debugging that will enable developers across the world to communicate and work together as if they were sitting at the same workstation. Additional enhancements include updates to Web services support and enhanced J2EE application server support.

     JBuilder 2006 will ship before the end of the year.

Q:  What is Peloton? When is it available? What does the code name Peloton mean?

A: Peloton is the code name for the first commercial JBuilder product built atop the Eclipse platform, which will be available in the first half of 2006. Peloton will combine the best of JBuilder and Eclipse, incorporating JBuilders trademark usability, advanced collaboration features, ALM integrations and enterprise-class support, with the flexibility and cost efficiencies of utilizing an open platform. It will provide the same level of quality, innovation, enterprise support and investment protection that customers expect from Borland and JBuilder. Its important to note that it will also respect the characteristics of the Eclipse platform which developers love, such as its customizability and its ability to easily integrate third-party plug-ins from the Eclipse community.

     Peloton is a cycling term. It is the group of individual riders that work better together as a team to reach their goal faster and with less effort.

Q:  How does JBuilder utilize Eclipse? How are you going to add value to Eclipse?

A: We will be utilizing Eclipse as an underlying integration framework  or the plumbing  for future JBuilder products. By utilizing Eclipse as a framework for future ALM and development products, Borland can better serve both existing customers and the wider Eclipse community. It will allow Borland to focus our talent on building out new, innovative capabilities that provide higher value to developers and development teams, rather than constantly spending our time retooling the base IDE functionality that changes for each new epoch of software development.

We are also adding value to Eclipse in a number of ways. On a community level, we are a Strategic Developer on Eclipses board and are contributing both monetary and development resources. We are also leading a modeling project within Eclipse, creating a new graphical modeling framework that would build upon, bridge and extend the existing modeling technology within the Eclipse platform.

On a product level, we are building high-value, enterprise-strength developer and ALM solutions that leverage Borlands 22 years of experience in software development and Eclipses flexibility and cost efficiencies. They will also offer enterprise customers the high level of quality, support and investment protection they expect from a trusted name like Borland.

Q: Give me an example of the kind of enterprise-class functionality from JBuilder that we can expect to see in Peloton or future Eclipse-based products.

A: Some examples include two-way visual designers, deep code insight and error insight, and a consistent method and development environment for multi-server deployment. More details to come closer to the launch of Peleton.

Q:  What is developers role in your SDO vision?

A: Developers have played an important role in Borlands past success, and they will play just as important of a role in Borlands future. Our mission is to maximize the business value of software, and we cant do that without serving the artists that create and deliver that software.

But the role of developers has changed over the years. Today, developers must not only enhance their individual art but their contributions within a larger team - a team that often spans organizational roles, geographies and time zones. Now more than ever, the successful delivery of software depends on teamwork, communication, agility and efficiency. JBuilder and our Core Software Delivery Platform (SDP) will evolve to help individuals, teams and organizations as a whole manage the pressures of this new era of software and thrive in it.

Q:  How do JBuilder and Core SDP (Core::Developer) relate to each other?

A: JBuilder provides individual productivity features as well as innovative collaboration features that allow distributed developers and development teams to work more effectively together. Core::Developer includes all of the capabilities of JBuilder and adds ALM, workflow, and process capabilities to improve collaboration across various roles in the software delivery lifecycle (business analyst, architect, developer, tester, etc.) The developer collaboration features in JBuilder provide developers with an on-ramp to the broader cross-role and cross-lifecycle capabilities in Borland Core SDP.

Q:  Why should I renew my JBuilder support/maintenance now?

A: Customers who renew their support and maintenance contracts can ensure uninterrupted enterprise-class support as well as free upgrades to the latest versions of JBuilder, including JBuilder 2006 and the first version of JBuilder on Eclipse, code named Peloton. Customers are free to use any combination of JBuilder versions up to the total number of seats licensed.

Q:  How will Borlands transition to the Eclipse framework impact existing JBuilder customers? How will you protect their investments in JBuilder?

A: Eclipse is simply the plumbing. A change in the integration framework for JBuilder should impact customers very little, but to ease the transition from previous versions of JBuilder to future versions based on Eclipse, Borland will offer free migration tools. Because JBuilder 2006 and Peloton are the next versions of JBuilder, customers on JBuilder support and maintenance will be entitled to both products once they are released.

Miscellaneous Eclipse Questions

Q:  How else are you investing in Eclipse beyond JBuilder?

A:  Borland is playing a leadership role in the Eclipse community by sitting on the Eclipse Board of Directors. Part of this investment includes dedicating at least 8 full-time developers to expand the Eclipse platform.

Also, to help drive ALM advancements within Eclipse, we will be leading a new graphical modeling framework project that will build upon, bridge and extend the existing modeling technology within the Eclipse community. Our strong expertise in modeling and our ongoing leadership in OMGs Model Driven Architecture (MDA) standards make Borland a perfect fit for this role.

We will also be expanding our use of Eclipse, along with Microsoft Visual Studio, across our ALM product line.


Server Response from: ETNASC04