|
>Subject: WebSphere Studio tools - como
cham�-los ?
>Date: Wed, 24 Apr 2002 09:11:06 -0300 > >Recebi esta nota do pessoal de software da IBM e achei interessante >repassar > > >******************************************************************************************************************************************************** >N�o usar mais o nome WSAD, como fazemos frequentemente... > > > ------------------------------------------------------------------------------------ > > Marketing the WebSphere Studio Name > ------------------------------------------------------------------------------------ > > > > > >This came from marketing: > > > >I would appreciate your help in setting an example for the rest of IBM in >how we communicate WebSphere Studio to the market - customers, partners, >analysts, and the press. We are working to drive home the significant >value Studio adds to the WebSphere Platform AND a much higher level of AD >penetration than we have ever had by setting the bar at "ONE powerful yet >easy to use development environment for the entire development team." We >dimisih our message when we refer to Studio as a "tool" and when we focus >attention on a particular configuration without first putting it in context >of the greater Studio message. We also hinder execution of our strategy by >focusing only on WS Studio AD - reinforces the idea that this is only about >a Java IDE. > >Some basics > We should never be saying or writing "WSAD" - if you need to short hand > it, please use "Studio" > Studio is a comprehensive and integrated development environment that > contains tools. It is not "a tool" > What makes Studio comprehensive are the IBM and partner extensions. > They are part of WebSphere Studio in this context. We don't say Studio > does some great things then partner and other IBM plug-ins make it > better. We say Studio - including the extension - is the single, > comprehensive IDE. > ONE development environment - offered in multiple configurations that > deliver the right set of tools for each developer role on the team > (e.g., Web, Device/J2ME, Application/J2EE, Enterprise (J2EE, COBOL, PL/1 > etc.)) > Refer to the" ____ configuration of WebSphere Studio" to set the stage > when necessary then just speak to WebSphere Studio. (or "Studio" for > short) (e.g., "in this demonstration I will be using the Application > Developer configuration of WebSphere Studio...... Studio provides the > tools to ...") Unless you are in a detailed discussion with a customer > explaining differences among configurations - you do not need to be > precise. Reinforce the message that "Studio" does it all. > Not necessary to refer to WebSphere Studio family - just say WebSphere > Studio > The eclipse community has settled on the "Eclipse Platform" - please > replace Eclipse Workbench in your written and verbal communication. We > like this, too, as it reinforces "open platform for AD" message. > >And for extra credit: The English word "tooling" is an informal verb that >means driving around in a vehicle. At least in public communication, >please drop the made up use of "tooling" and use the English word for tools >- "tools." >
|
- [java-list] WSAD WSAD WSAD ==== Re: RES:... Orbitall 1 Centro de Competencia
- RES: [java-list] WSAD WSAD WSAD ===... Marcio Alves Marinho
- Re: [java-list] WSAD WSAD WSAD ... Leucir Marin Junior
- Re: [java-list] WSAD WSAD W... Dormevilly N. Tertius
- Re: [java-list] WSAD WS... Sven van �t Veer
- RES: [java-list] W... Fl�vio Leite
- Re: [java-list] WSAD WSAD W... Marcelo Alves
- Re: [java-list] WSAD WSAD W... Marco Antonio
- RE: [java-list] WSAD WSAD WSAD ====... Leandro Gruarin Abite - (DYNAMIC)
- Re: [java-list] WSAD WSAD WSAD ... Sven van �t Veer
- Re: [java-list] WSAD WSAD W... Carmilton
- Re: [java-list] WSAD WSAD WSAD ====... Orbitall 1 Centro de Competencia
- Re: [java-list] WSAD WSAD WSAD ... Sven van �t Veer
- Re: [java-list] WSAD WSAD W... Gilvan Marques
- Re: [java-list] WSAD WS... sven van �t veer
- [java-list] VR/Hora Curso Igor
- Re: [java-list] VR/Hora Cur... Luiz Reginaldo
