基本介紹
- 中文名：JavaPlan
- 性質：軟體開發工具
- 編寫語言：用Java語言編寫
- 作用：為建築大型編程任務解構圖形平台
Java術語介紹,JavaPlan發展,JavaPlan套用,JavaPlan英文原文,
Java術語介紹
術語名稱：JavaPlan
術語解釋：面向的設計和編程工具，用Java語言編寫。
JavaPlan發展
JavaPlan推出
Java語言和Java小程式已在網際網路掀起風暴，收益率在以前從未見過的方式網頁互動性。迄今為止，然而，Java並沒有被套用到更大規模的發展問題，一個基於Java的前端努力專注的結果，但很少通過後端的方式。從Sun公司新的收購是列出來改變這種狀況。
憑藉其旗艦JavaPlan，燈塔設計已展開令人信服的先進開發者Java的準備黃金開發大型應用程式的時間。
在更大意義上說，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.
