Extreme Modeling Method

Extreme Programming (XP) is a set of interrelated principles and practices, some of which focus on basic activities, such as configuration management, however, most of them focus on communication and cultural issues between team members and enterprise groups of teams and application systems. We recommend that you use the cyclic iterative development method for XP.

Modeling is an important component of software development. A model describes a complete aspect of software. Software and software processes can be simplified through modeling. A graph can contain dozens or even hundreds of lines of text. Through the graphic media, you can get feedback quickly and modify your model in time to meet your needs. Extreme modeling (XM) is a lightweight Modeling Method built on existing and proven to be an effective modeling method.XMYesXP.

In the process of developing an object-oriented software, software developers may apply the basic modeling tools and modeling processes as shown in. For the sake of simplicity, the project management content, such as test cases and other evaluation and test tools, is omitted in the figure. The square in the figure indicates the development tools such as basic case model and activity diagram that may be used. The lines in the diagram describe the main relationship between tools. For example, the information contained in the class model in the analysis phase will affect the development of Information in the class model in the design phase. These relationships reveal the relationships between different tools in iterative development. For example, when you modify the use case model, it may affect the development of the sequence chart, and then it will affect your class model. The blue colored squares in the figure indicate that these modeling tools are the modeling tools described in the unified Industrial Modeling Language (UML), which is developed and maintained by the Object Management Group (http://www.omg.org.

Although many modeling tools are listed in, you do not have to use them in every project development. You should only use modeling technologies that can better demonstrate the software you have developed. For example, a basic user interface prototype can help you better understand a user interface requirement. However, if your user interface requirements are obvious, this technology is not necessarily of great value to your team. Similarly, the activity diagram is useful for understanding complex transaction logic flows. However, if the business flow is simple and clear, it is not very valuable. However, although you do not need to be proficient in all modeling tools, you are not familiar with some of the modeling technologies required by your project team in project development, however, if you are unable to grasp the necessary technologies immediately during your work, you should voluntarily withdraw from the project.

The yellow boxes in indicate that in actual application development, it is not enough to develop projects by using UML alone. Some modeling tools shown in yellow blocks will be adopted in subsequent UML revisions. It also indicates that the software development process is continuous and iterative. It is continuous because it runs the entire development process from left to right, including requirements, analysis, design and implementation. Development is an iterative process, because you can move back and forth in each modeling phase and modeling tool. It is an iterative process to analyze user requirements and determine how to meet and meet user needs. From a global perspective, the modeling process is a continuous process, while from a local perspective, it is an iterative process.

The basic principle of extreme modeling is concise, that is, the whole process of project development can be clearly and effectively described with as few and refined images as possible. The secret of extreme modeling lies not in the modeling technology itself, but in how they can be well applied to the development of software projects. As an excellent software professional developer, he must master various development tools and technologies covering the entire development process, and have the ability to know when to use which tool is the most efficient.