Blog Replacement-Agile Development Learning

Reference: Http://baike.baidu.com/link?url=Sr0U52SUMhFl0jdpQQM0BoER5P1gHx8jEul4Rfg518v9SLp0qg4C2c1Twb5KyYTh6B4Ght9m_ Avlestiuhploa

The agile development takes the user's demand evolution as the core, uses the iterative, the gradual step method carries on the software development. In agile development, software projects are cut into multiple sub-projects in the early stages of construction, and the results of each sub-project are tested for visual, integrated, and operational use features. In other words, a large project is divided into several interconnected, but also can be run independently of small projects, and completed, in the process of software has been in a state of use.

Values

Agile Modeling,am's values include the four values of XP (Extreme Programming: Extreme Programming): Communication, simplicity, feedback, courage, and, in addition, a fifth value: humility.

Follow the principles

Single responsibility principle (SRP) in the case of a class, there should be only one cause for it to change. The open-close principle (OCP) software entity should be extensible, but not modifiable. The Liskov substitution principle (LSP) subtypes must be able to replace their base types. Dependency inversion principle (DIP) abstraction should not be dependent on detail. The details should depend on abstraction. The interface Isolation principle (ISP) should not force customers to rely on methods that they do not use. The interface belongs to the customer and does not belong to the class hierarchy in which it resides. The granularity of reuse of the reuse publishing equivalence principle (REP) is the granularity of the release. All classes in the common closure principle (CCP) package should be closed together for changes of the same class nature. If a change affects a package, it will affect all classes in the package, but not the other packages. Common reuse principle (CRP) All classes in a package should be reused together. If one of the classes in the package is reused, then all classes in the package must be reused. The Ring Dependency principle (ADP) does not permit the presence of loops in the package's dependency graph. The stable dependency principle (SDP) relies on a stable direction. The abstraction of the Stability Abstraction principle (SAP) package should be consistent with its degree of stability.

1. Fast IterationThe requirements, development, and testing of a small version are much simpler and faster than that of a half-yearly large release. Some companies publish only two or three versions a year, the release process is slow, they still use the waterfall development model, more serious is the Agile development model has misunderstood. 2. Involve testers and developers in the requirements discussionThe demand discussion is most efficient in the form of discussion groups. Discussion groups, which need to include testers and developers, make it easier to define testable requirements, group requirements, and prioritize them. At the same time, this method can also make full use of the complementary characteristics between team members. The need for such certainty is often more efficient, more active and more participatory than the need to discuss the conference. 3. Write a testable requirements documentStart by using the user story method to write the requirements document. This approach allows us to focus on requirements rather than solutions and implementation techniques. Premature mention of a technology implementation reduces the need for attention. 4. Communicate more, minimize documentationCommunication is a common problem in any project. Good communication is a prerequisite for agile development. The longer you mix in a circle, the more you emphasize the importance of good and efficient communication. The team wants to make sure that everyday communication is much better than email. 5. Do the product prototypeIt is recommended that you use sketches and models to clarify the user interface. Not everyone can understand a complex document, but everyone will look at the picture. 6. Early consideration of testingIt is important to consider testing early in agile development. Traditional software development, test cases start writing late, which leads to late detection of problems in demand, making the cost of improvement too high. Start writing test cases earlier, and when the requirements are complete, the acceptable test cases are basically complete.

Blog Replacement-Agile Development Learning