Java open source projects in enterprise application development

To the current enterprise application development competition is increasingly fierce, the demand changes frequently, each system integrator faces the huge survival pressure. There are two aspects that are particularly prominent: the absence of a unified software development process or the copying of heavyweight software development processes, such as RUP, which is often not implemented because of the pressure of time, and most companies still do not get rid of the practices of the manual workshops, Each project or product, because of the different management or team, redesign the system framework, waste a lot of time on the structure verification and adjustment.

In the development of enterprise application system, the change of requirement is the only invariable thing in the project, and in order to keep the development consistency and benefit maximization, the system integrator needs to maintain long-term cooperation with customers. Therefore, the adoption of evolutionary agile software development can better guarantee the quality of the project. Of all the agile software development methods, XP is the most widely used one. It is a highly dynamic process that is responsive to changes in demand through very short iterations; communication, simplicity, feedback and courage are its four core values. At the same time, it has focused on many of the best practices in the industry, and there are now 18 of them, and XP insists on getting the "limit" effect by rigorously enforcing all the best practices.

At the same time, for reuse and efficiency considerations, especially for system integrators, enterprise application systems should have their own framework and structure. With a good performance, project validation of the system framework, combined with an effective software development process, system integrators can quickly and successfully develop enterprise application systems.

To better develop successful systems, system integrators can try to solve the problem from the following two aspects: combining the support of open source tools, implementing the "Agile Software development Method" within the organization, and establishing a flexible and effective framework for the core business areas.

Since many enterprise applications are based on Java technology for the development of Web applications, the following is mainly based on java-based open source projects, tools and applications.

1. Open Source Tools and XP

XP's 12 best practices, for all enterprise application developers, due to organizational and cultural differences, it is not possible to apply all, but the following practices are conditional step-by-step implementation:

Code specification: STANDARD

Test-driven Development: Test-driven DEVELOPMENT

Day Build: Daily building

Continuous Integration: Continuous integration

Small step: SMALL Release

Daily morning Meeting:

Work 40 hours per week: 40-hours A WEEK

The CODE Standard and TDD are the basis for continuous integration, daily building, and small release, while the daily meeting and 40-hours a work are separate practice processes, It can be combined with other practices to enhance the communication and morale of the project team.

It should be explained that the above best practices are not unique to XP, but are being applied by the most software development methodologies, in which the "Day build" is officially seen in Microsoft's software development approach.

1) Code specification

While most companies are implementing code standards and specifications to some extent, and Sun's recommended coding specifications for application development using Java, the actual situation is not ideal.

The main reason is: On the one hand, developers have a strong habit, on the other hand, the strength of the code review is not enough. If tools are available to help you perform a code-standard performance check, code reviews can focus on examining the logic and performance of your program.

Open Source Product Checkstyle (Http://sourceforge.net/projects/checkstyle) can help develop organizations to solve the problem of code standards review.

The latest version, currently 3.0, provides two ways to run: One is the command line, and one is the ant combination (ant has support for Checkstyle from the optional tasks provided after 1.5). At the same time, SourceForge has plug-in support for popular Ides such as JBuilder, which can define properties files at the global, project level, but currently only supports version 2.42.

Prior to the 3.x release, the configuration information for Checkstyle was written in the property file, and after 3.x, the configuration information was an XML file and the configuration was more flexible. A specific check File for the Sun Code conventions is available in the release version of 3.0 and can be referenced for use.

Implementation of recommendations:

Manual execution: The developer manually triggers the Checkstyle check in the IDE or the code review is performed manually by the censor;

Automatic execution: Checkstyle and Source control system (CVS), in the source code checkin when the rules of judgment, if not compliant, then do not allow to enter the system.