Environmental organizations EJB
Class: Junior
Scott W. Ambler (scott.ambler @ ronin-intl.com), president of Ronin International
July 5, 2001
If there is no firm basis, then the Enterprise JavaBeans (EJB) project will certainly be messy. Scott W. Ambler explains why in the early stages of the development of the definition environment, and provides a definition of the environment skills.
Early in the project, if followed Rational Unified Process (RUP) or Enterprise Unified Process (EUP), it is usually considered in the environmental work flow problem, you need to define the technical project team environment. This includes the selection, and then install the project team will use the corresponding standards, guidelines and development tools.
To be successful at this stage, you must consider the following factors:
- Recognition tools, standards and guidelines have been improving. Today your choice of tools in the future may be replaced by their competitive opponent. Does that mean that you tools to change? It is not likely, because the purchase, installation tools and training to the entire group may be more than the cost of the tool the benefits of new features. In addition, tools suppliers will soon release a new version of tools to make tools were not eliminated, then you will last between indecision in the development environment: If it did, you would never begin to consider the real work - EJB software development. Tool changes, in particular in the medium-term projects, could be a dangerous and costly process. If you find tools not your expectations, then they should consider abandoning it, if there was a new version, you should consider upgrading it. But if applicable tools, we should persist in using it. The standards and guidelines should also be so.
- Early in the project as far as possible the establishment of environmental projects. Environmental projects for the development team to work together to lay the foundation for, we need as soon as possible to lay this foundation. Tools will choose to stay to the last minute of the group will find that they did not have enough time to train everyone in order to enable them to effectively adapt to the environment. The standards and guidelines will choose to stay late to the project will lead to inconsistent work, the conflict within the group, the failure of comments, and sometimes even serious need to redo.
- Very useful product reviews, but not Gaiguan conclusion. When you quickly search the Internet, you can find many independent product reviews - especially in the magazine, such as JavaPro, Java Report and Software Development (see references) - These comments can be presented to you in detail what each tool can be done . Comments will help you narrow the choices, but you still need your own environmental assessment of these tools in order to make the final choice. You also should consider hire a consultant to help you to define a project environment and to ensure that you make the most suited to their own conditions choice. Moreover, specific tools for the news or portals, such as The Server Side (see References) good illustration of what tools can really play a role.
- Environmental projects must reflect methods / process. When the project environment and the software process inconsistent, your team will soon find the need to spend a lot of energy in order to maintain progress (because of the need to solve the shortage of project environmental problems). For example, if using iterative and incremental approach to development, then it requires a high degree of support regression testing, testing tools. Otherwise, it is necessary to make their own manual regression testing suite. In addition, if you have chosen to use use-case driven approach, then you obviously need to support the use of development tools.
- According to choose project environment. If we do not know what to buy, then why buy? For example, in the choice of test tools, first identifying the need to implement the test type.
- Do not assess each category for each one. Java developers will be able to use hundreds of development tools, but you use in the project which only a few development tools. Will be reduced to the choice of several candidates tool to find some of the comments on these tools, testing the performance of these tools, choose the environment, and then went forward. Remember KISS principle: to simplify things, fool! (Keep It Simple, Stupid!)
- When the only tool in a benefit when using it. If every developer can maximize the use of tools, each for the purchase of thousands of dollars worth of tools is cost-effective. However, if developers use tools only a small part of capacity, and some of the more simple and cheaper tools can also provide the ability, it is that the sale of T very terrible. In addition, please remember that as long as a little search on the Internet can find many free tools.
- Look forward to training. You can not be a tool for standard document or software process into a personal table, and expect them to master it. In this regard, please refer to last week's tip on EJB training. (Please also note that next week's article will explore further skills training.)
- Use of existing standards, guidelines and tools. While trying to prepare their own development guidelines, tools or build their own personal integrate several tools are usually attractive, but not for what should be on the circumstances to do so. Otherwise, the best Although not perfect but a very good project environment, continue to carry out the actual work of software development.
Note: This article extracted from the skills will be in August 2001 published Mastering Enterprise JavaBeans, Second Edition.
original English text.
- EJB application server choice
- EJB training: Start your project off right
- JavaPro
- Java Report
- Software Development
- For the RUP, please read Philippe Kruchten of The Rational Unified Process: An Introduction, Second Edition (Addison Wesley Longman, 2000).
- Larry Constantine and I co-produced The Unified Process Inception Phase (R & D Books 2001).
- Ed Roman, Tyler Jewell, Floyd Marinescu and I co-authored the forthcoming publication of Mastering Enterprise Java Beans, Second Edition (John Wiley & Sons, August 2001).
- The object-oriented programming, please refer to The Object Primer, Second Edition (Cambridge University Press, 2001).
- To learn the basic knowledge of the Java programming, please refer to The Elements of Java Style (Cambridge University Press, 2000).
- This IBM white paper on WebSphere technology description of the organizational complexity of a method of EJB environment.
- Security should never EJB environment is created after consideration. This group of many useful links in the safety of the EJB reference.
- For the RUP, please read Philippe Kruchten of The Rational Unified Process: An Introduction, Second Edition (Addison Wesley Longman, 2000).
- Larry Constantine and I co-produced The Unified Process Inception Phase (R & D Books 2001).
- Ed Roman, Tyler Jewell, Floyd Marinescu and I co-authored the forthcoming publication of Mastering Enterprise Java Beans, Second Edition (John Wiley & Sons, August 2001).
- The object-oriented programming, please refer to The Object Primer, Second Edition (Cambridge University Press, 2001).
- To learn the basic knowledge of the Java programming, please refer to The Elements of Java Style (Cambridge University Press, 2000).
- This IBM white paper on WebSphere technology description of the organizational complexity of a method of EJB environment.
- Security should never EJB environment is created after consideration. This group of many useful links in the safety of the EJB reference.
Ronin International, the company is a specialized object-oriented process to provide guidance, architecture modeling and Enterprise JavaBean (EJB) development consulting business. Through scott.ambler @ ronin-intl.com contact with him, his website at www.ambysoft.com.
Tags: EJB






