Java术语介绍

JavaPlan发展

JavaPlan应用

JavaPlan英文原文

Java术语介绍

术语名称：JavaPlan

术语解释：面向的设计和编程工具，用Java语言编写。

JavaPlan发展

JavaPlan推出

Java语言和Java小程序已在互联网掀起风暴，收益率在以前从未见过的方式网页互动性。迄今为止，然而，Java并没有被应用到更大规模的发展问题，一个基于Java的前端努力专注的结果，但很少通过后端的方式。从Sun公司新的收购是列出来改变这种状况。

凭借其旗舰JavaPlan，灯塔设计已展开令人信服的先进开发者Java的准备黄金开发大型应用程序的时间。

灯塔设计的JavaPlan是第一个软件开发工具，专门用于企业Java，可为建筑和大型编程任务解构图形平台，在沿着与代码生成，现有的Java源代码，自动化的文件和项目报告逆向工程 - 所有多用户环境。 JavaPlan需要的图形，高度重复的软件设计方法 - “战略”的应用组件开发其中的商业目标，过程和参数必须在开始编码表示。

在更大意义上说，JavaPlan凝聚成一个有凝聚力的努力，两个角度及模具他们点。它鼓励，给予开发工具和角度去实现它“好”的设计。它也给传统的遗留系统开发团队的一个易于使用的工具，鼓励逐步参与，而不是火的“洗礼组曲”通常与技能的转让。程序开发人员可以通过图形分解开始与JavaPlan申请，并着手对使用这些工具的实际执行的步骤。

通过简化和正式的软件设计战略的一部分，JavaPlan大幅降低时间和定制开发和部署企业应用的费用。此外，它使企业能够重用的软件设计和部件 - 一个极为承诺，但很少交付能力，大大减少了应用程序设计的长期成本。

JavaPlan应用

电子“白板”美国国家设计与编程

在传统的定制软件开发，应用的建筑师和设计师们日复一日集思广益，充满了“strawman”白板设计和办法。随着时间的推移，他们在白板上修改的涂鸦，添加和改变他们的设计。如果他们要讨论或与其他开发人员共享的变化，大家聚集在一起，他们必须在白板前面。在大多数情况下，白板材料多数是永远失去了。 JavaPlan保留非正式和自由的形式表达的物理白板。开发人员可以尝试新的想法，没有什么清除工作，添加到什么是现成的，一起脑力激荡有关指示或细节。而且，JavaPlan也保持这一进程的记录。

值得注意的是，管理者可以使用JavaPlan争取到应用程序开发过程的角度，而不是简单地希望他们的开发人员正在对申请的权利与1件，考虑到共同的目标。正如开发人员可以“检查白板”从任何地方和任何时间，管理人员可以使用JavaPlan看到了他们所做的，是谁并在这一进程的发展方向。

JavaPlan英文原文

What JavaPlan Delivers

The Java language and Java applets have taken the Internet by storm, yielding interactivity on Web pages in ways previously never seen. To date, however, Java has not been applied to larger scale development problems, a result of a concentration of effort on Java front-ends, but little by way of back ends. A new acquisition from Sun Microsystems is setting out to change that.

With its flagship JavaPlan, Lighthouse Design has embarked upon convincing sophisticated developers that Java's ready for prime-time in large applications development.

Lighthouse Design's JavaPlan is the first software development tool devoted to enterprise Java, providing a graphical platform for the architecture and deconstruction of large programming tasks, along with code generation, reverse engineering of existing Java source code, automated documentation and project reporting - all within a multi-user environment. JavaPlan takes a graphical, highly iterative approach to software design -- the "strategic" component of applications development wherein business goals, processes and parameters must be expressed before coding begins.

In a larger sense, JavaPlan unites two points of view and molds them into a cohesive effort. It encourages "good" design by giving developers the tools and perspective to attain it. It also gives teams of traditional legacy system developers a suite of easy-to-use tools that encourage progressive involvement, as opposed to a "baptism by fire" normally associated with skills transfer. Procedural developers can begin by graphically decomposing an application with JavaPlan, and proceed in steps toward using the tools for actual implementation.

By simplifying and formalizing the strategic portion of software design, JavaPlan significantly cuts the time and expense of developing and deploying custom enterprise applications. Moreover, it enables companies to reuse software designs and components - a much-promised but rarely delivered capability that drastically reduces the long-term costs of application design.

Electronic "Whiteboard" Unites Designing and Programming

In traditional custom software development, application architects and designers spend day after day brainstorming, filling whiteboards with "strawman" designs and approaches. As time passes, they modify the scribbles on the whiteboard, adding and changing their designs. If they want to discuss or share changes with other developers, they must gather everyone together in front of the whiteboard. In most cases, the majority of the whiteboard material is lost forever. JavaPlan preserves the informality and free-form expression of the physical whiteboard. Developers can try out new ideas, erase what doesn't work, add to what is already there and brainstorm together about directions or details. And, JavaPlan also maintains a record of the process.

Significantly, managers can use JavaPlan to gain perspective into the application development process, rather than simply hope their developers are working on the right pieces of the application and with a common goal in mind. Just as developers can "check the whiteboard" from anywhere and at any time, managers can use JavaPlan to see what's been done, by whom and where the process is headed.