Historical Document: Delphi Product Definition 3rd Draft - May 13, 1993
By: David Intersimone
Abstract: Zack Urlocker, Delphi Product Manager, wrote the product definition for Delphi version 1.0. This is the HTML version of the 3rd draft, dated May 13, 1993. Notable items include the original target dates and technical terms like "lotsa".
We will create new "Windows only" Pascal products (code name Delphi) to compete directly with Visual Basic and revitalize the Pascal market. Delphi will offer better performance, more capabilities and more tools than Visual Basic and will be targeted towards vertical market developers and departmental programmers. We will follow up six to nine months later with 32 bit versions of Pascal for DOS and Windows.
Notes: - FCS dates subject to delivery by R&D. - names and prices are tentative
This is targeted to new customers. It will have a low SRP and will be sold almost exclusively through the retail channel and positioned directly against Visual Basic. Current Pascal customers will be up sold to Delphi Pro.
This is targeted to new customers as well as upgrade customers. It will have an intermediate SDP and will be sold through both retail and direct mail. It will be positioned directly against Visual Basic Pro.
Delphi is targeted to application developers who want the highest possible productivity in creating efficient applications. This includes programmers in vertical markets (e.g. construction, health care, consulting), departmental programmers and professionals who program in order to accomplish their job (e.g. scientists, engineers, network administrators). These customers are characterized by their willingness to use whatever tool that "gets the job done". Many of these programmers are long time Pascal users on DOS.
High on their list of priorities are:
Low on their list of priorities are:
Our chief competitor is VB 3.0. We must be sure to beat VB 3.0 in some significant, but not necessarily all, areas.
Here's a list of the standard and "advanced" components we need to build. This is a tentative list and its likely that some components may move from the "advanced" area to become "standard" or vice verse depending on competitive issues with VB 3.0.
Based on current localizations and stated policies; unconfirmed with subs.
A. Doc & Help Change Volumes
We expect that both the paper doc and the online help will have to be completely retranslated from scratch for this product. New CBTs will also need to be translated from scratch. This adds up to a large volume of translation work. This is somewhat mitigated by the bonus of not having to manage updates of older materials. Simultaneous schedules probably won't be endangered by such large volumes.
B. Possible Schedule Conflicts
The translation facilities at the subs (and to a lesser extent, the international resources here in SV) could be overwhelmed if Delphi overlaps the BCW 4, TCW 4, an/or BCDOS 4 projects. In this case we'd have to work with the subs to decide which projects get the resources first, which of course would significantly decrease the possibility of simultaneous or near-simultaneous shipments of some of these projects.
Published on: 2/14/2005 10:17:53 AM
Server Response from: ETNASC04
Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.