Atitit. Improved development efficiency-a revolution in the method of MDA Software Development

Atitit. Improved development efficiency-a revolution in the method of MDA Software Development

 

 

1. The abstraction level of the revolutionary development tools for software development will be upgraded to 1 again

2. Application Framework and its implementation are separated 2

3. The current problem model and Code are not synchronized 2

4. History and origin of MDA 2

5. The three main objectives of MDA are convenience, interoperability and reusability. 3

6. Differences between MDA and code generation 3

7. Problem: Maybe the MDA is just a flash in the existing case tools 3

8. Improved efficiency by 3

9. MDA success in the embedded system 4

10. My summary: it is better to generate a pseudo code. 4

11. Reference 4

 

1. the Abstraction Level of revolutionary development tools for software development will be upgraded again

 

MDA is another revolutionary "mutation" after software development from assembly language to advanced language"

 

MDA is a new software development methodology proposed by OGM. From this point of view, software development is modeling. It is built on the basis of the great success of the UML modeling language.

 

 

MDA changes the development process. In the software requirement analysis stage, it is no longer about writing documents.

 

MDA changes development tools. As technology advances, the abstract layers of mainstream development tools will be upgraded again. In IDE, the most important thing is not the code editor, but the graphic-based modeling window. The code will be automatically generated by the changing tool, and it is no longer a concern.

 

 

MDA allows us to get to know the document again. In the past, we thought that documents or models do not need to be too precise because people have a strong understanding ability. Writing too accurately is a waste of time because they cannot be something that can run. However, MDA will overturn these facts. The model is not written to people, but to machines. The accuracy of the model is not a waste of time.

 

In the future, tools will replace people to complete coding (most of the work), followed by a compiler, and we only need to focus on the creation process.

 

Author: old wow's paw attilax iron, email: [email protected]

Reprinted please indicate Source: http://blog.csdn.net/attilax

 

 

2. Application Framework and its implementation are separated

MDA can separate the application framework from its implementation. The supporters of MDA hope that changes in supporting software and hardware will not render existing enterprise applications unusable. More importantly, by reducing the coupling between the application architecture and its runtime environment, MDA can bring about better design, this makes the application longer and can be easily transplanted to other underlying platforms.

 

 

3. The current problem model and Code are not synchronized

The main problem with modeling today is that it is only a practical exercise for many enterprises. This causes the model and code to be not synchronized. The Code will be constantly modified, and the model will not be updated. This will make the model meaningless.

4. History and origin of MDA

Since MDA was proposed by OMG (Object Management Group International Object Management Group) in 2001, "sneak into the night with the wind, clean things and silent things" has not seen vigorous publicity, major manufacturers are following up with each other, and the topic about MDA is booming on the Internet in a twinkling of an eye.
Model Driven Architecture (MDA) is a new software development framework launched by OMG. The launch of this framework has brought an "earthquake" to the entire software industry"

It isolates us from the "violent vibration" of the underlying platform and protects the security of our "business logic building, this gives us peace of mind in the face of a round of shock waves caused by dramatic changes in platform technology. It will certainly have a profound impact on the future of software technology in many aspects. However, where is its "Source?

 

Since 1995, OMG has adopted some industrial-related technical specifications in an informal manner and formulated the work in 96 and 97 years. At the same time, under the leadership of Mary Loomis, the scope of work was further expanded to include Object Modeling, which led to the generation of the UML modeling language, in 2001, the OMG further adopted another framework-MDA. Of course, MDA is not used to implement a distributed object system like the CORBA framework, but a method to use models in software development. Looking back at the history of MDA, we can see that the great success of UML has laid a solid foundation for the generation of MDA,

 

MDA is derived from the well-known idea of separating system operation specifications from the details of how the system uses the underlying platform capabilities. MDA provides a way (through related tools) to standardize a platform independent system, standardize the platform, select a specific implementation platform for the system, and convert the system specifications to a specific implementation platform.

 

5. The three main objectives of MDA are convenience, interoperability and reusability.

The lightweight, interoperability, and reusability are achieved through disruptive separation.

 

6. Differences between MDA and code generation

 

The essence of MDA is not code generation, although code generation is considered a major achievement. MDA can also be achieved by constructing virtual machines that can directly execute models.

MDA is not just "UML + code generation", but it brings us a new way of thinking about problems and changing concepts.

 

7. Problem: Maybe the MDA is just a flash of cake in the existing case tools"

 

8. Improved efficiency

The MDA team has an absolute advantage in efficiency, and the efficiency has improved by nearly 30%.

There is no time to calculate the familiarity and learning tools required for using the MDA method for the first time. Obviously, using the MDA method can greatly improve the efficiency of software development, which is beyond doubt.

 

 

Status Quo of three major MDA tools

Compared with the cool-down and tolerance of major manufacturers in the industry, some small and medium manufacturers are particularly active,

Like the famous arcstyler,

The famous optimalj of compuware,

In addition, open-source version of andromda and other OMG-compliant MDA tools have been widely used in some projects and achieved remarkable results.
Conclusion

 

9. The success of MDA in the embedded system

Because the embedded system has different platforms ..

. Schlaer-Mellor-based systems are used to generate embedded code for all types of electronic devices and generate millions of lines of C/C ++ code from the abstract model to complete complex telecom exchanges. In some respects, I can say that, compared with enterprise application systems, MDA has a more successful performance in such systems ."
As embedded and real-time systems have been successful, enterprise-level development will surely be successful, we will wait and see.

 

 

10. My summary: it is better to generate a pseudo code.

Using UML to generate code is not completed yet... the pseudo code may be used as the language...

11. Reference

MDA: a revolution in software development, or a new vinegar installed in the old case tools bottle? -Dynasty network-wangchao.net.cn.htm