Different J2EE project development processes

xiaoxiao2021-03-06  21

Which development process should a typical J2EE project usually use? There are many popular development processes, and the application is relatively widely available: waterfalls, iterative, and RUP (Rational Unified Process). Each has its advantages and deficiencies, so we should usually combine them instead of identifying one of them and then 100% is going on.

Let's take a look at everything roughly:

[Waterfall]

The process of this mode emphasizes all demand analysis and design before starting coding and testing. This mode history is quite a long time, and it is also very mature, and even today, this model is still widely used to most companies and projects. in. The projects developed using this model are usually very large and take longer to deliver. Because of this, these projects usually have more risks: today, today, if the system to be developed can not respond to changes in these demands in time, the ultimately developed products may no longer need customers.

[Iterative]

In response to the shortcomings of traditional waterfall development in handling demand changes, a new ultimate programming concept has occurred in recent years. The core idea of ​​Extreme Programming (XP) is: From the long run, early discovery errors and reduced complexity can save costs. Extreme Programming emphasizes that we will subdivibize task / system into a subtrane / module that can be resolved in a shorter period, and emphasizes testing, code quality, and early detection of problems. Typically, through a short iterative cycle, we can obtain a phased progress and can form a version for user reference in time to respond to the user's possible demand change in time.

[Rup]

RUP's full name is Rational Unified Process, which is a set of software engineering models defined. It emphasizes the demand analysis and design before the encoding, as well as the development and release of the short antennament cycle. It encourages team first to develop the highest risk modules in the project, discover and respond to problems with more time, which can reduce some repetitions to some extent when designing changes. However, because RUP is very rigorous, it is more specific, usually, it is not 100% necessary to follow this process.

Let's take a look at what kind of process or strategy we should take:

In the actual J2EE project, RUP's application has increased year by year, but it is not all of these projects that use RUPs to complete RUP. We can consider a way in which the above three processes are integrated, according to specific project quantities. It is necessary to summarize these advantages: waterfall is more mature, usually very good emphasizes the importance of designing re-coding after the first demand, and is more suitable for the way the big company is budget; extreme programming emphasizes test first And simple is beautiful, which is conducive to early discovery and better response; RUP emphasizes the analysis and design of concentrated concentration also has its irreplaceable superiority.

It is not easy to make a conclusive answer. If your company is relatively large and willing to pay a certain management cost, push a ripe and complete development process and all projects inside the company or most projects, I I want RUP to be preferred; if your company wants to have more flexibility, consider some compromised programs, according to specific items, from above three processes to determine specific processes.

转载请注明原文地址:https://www.9cbs.com/read-68187.html

New Post(0)