SQL version of UML activity diagram--merge1.0

The idea of the merge development platform: If the activity diagram can run, then the development process of the business logic is approximate to the drawing process.

Developed for Merge1.0 scripting:

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M01/89/46/wKioL1gOoRSxPhHjAAG0iwYg2Dg758.png-wh_500x0-wm_3 -wmp_4-s_1413011658.png "title=" P1.png "alt=" Wkiol1goorsxphhjaag0iwyg2dg758.png-wh_50 "/>

Models include:

Base part: Start, variable assignment, judgment, end,

Extended sections: External classes, service instances (that is, script calls)

Data manipulation section: Data query, Data update

The run process generates logs by model:

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M02/89/46/wKioL1gOqh3RZxHOAAFeLfbPUfY278.png-wh_500x0-wm_3 -wmp_4-s_18791905.png "title=" P2.png "alt=" Wkiol1goqh3rzxhoaafelfbpufy278.png-wh_50 "/>

Scripts are published to support HTTP requests, WebService calls, and no requirements for client technology.

According to the business logic organization model, implement the processing process, support single-step debugging.

Service scripts can be saved directly as JSON text files, while supporting the generation of Java source code and jar packages.

This article is from the "small Partners" blog, please be sure to keep this source http://zglei.blog.51cto.com/9304205/1865262

SQL version of UML activity diagram--merge1.0