Agile Development And Application In Development Of An Enterprise Portal

Today, we are more and more surrounded by computer which in some way we cannot get away with, and the software become very important to be a clear symbol in modern society. However, project team feel frustrated by the fact that the project increasingly become huge and difficult to maintain because of the rigid and fragile design. Until the early 2000, some expert of software come together to get a conclusion to make the development easy responsive to changes and easy to develop and reached a document know as Manifesto for Agile Software Development.Agile Development can face rapidly changes through whole life cycle of software. To achieve agile development, we need to use some necessary disciplines and the practices of feedback. We need to maintain our flexibility in the software, maintaining the design principle, and also need to know the balance of these principles and the design pattern. Agile developers must make design easy to maintain and refactoring. As "Agile Manifesto" advocated: emphasize interaction between the people and respond to changes, Rails stressed these agile practices. Agile design is the basis lies of Rails. Rails are not heavy tools, no complicated configuration, and no lengthy process. Rails has always adhered to the two core principles: DRY (Don't Repeat Yourself) and the selector practice focused on the allocation of CoC (convention over configuration). Moreover, the Rails-built a powerful tool set of supporting testing make the test simple. Thus, we can do more frequent testing.In this paper, the Portal is a sub-project of MLR (Multi-bank Link Report) of which the main purpose is to support the statements generated, statements of the data needed to provide CRUD (create, retrieve, update, delete) function. There have already implemented a J2EE version which uses a lot of excellent J2EE technologies such as Hibernate, Struts, and by developing it again using Ruby on Rails to achieve the same function and interface, achieve some conclusions of the principle and design pattern of agile development; also compare differences of the process between typical J2EE and agile development using Rails; moreover, finally discuss the feasibility of the method of agile development with Rails.