Visual software modeling method for constructing software view on basis of software meta view

Abstract

The invention relates to a visual software modeling method for constructing a software view on the basis of a software meta view. The software view is constructed by taking a software hierarchy view, a software interface view, a software interaction view, a software algorithm view, a software process view and a software transmission view as step elements after basic components of the software meta view is determined, and visual software modeling standards which have the advantages of computability, universality and usability are provided for software modeling activities in various fields. According to the visual software modeling method for constructing the software view on the basis of the software meta view, the constructed software view is clear in structure, adjustable in hierarchy and controllable in modeling granularity, and full consistency of being computed is achieved; the method is uniform, analysis design from top to bottom is convenient, integration from bottom to top is achieved conveniently, and the method is suitable for various software modeling; the modeling method is simple, fully visual modeling is conducted, common area personnel who are not familiar with the modeling language and the computer programming language can independently and easily construct the software view, dependency and communication to special modeling personnel or programming personnel are avoided, and the modeling time is greatly shortened.

Description

technical field [0001] The invention relates to the technical field of software engineering, in particular to a visual software modeling method and a computer program product for constructing a software view based on a software meta-view. Background technique [0002] In today's highly developed information technology, software plays an increasingly important role in human life and development. After the software method has gone through the development stages of function-oriented and process-oriented, the object-oriented software method has become quite mature and has become the current mainstream software method. As software systems become more and more complex, object-oriented methods expose more and more deficiencies, and model-driven methods become the ideal software design methods that people pursue. The core idea of ​​the model-driven software method is: developers focus on constructing software models, express knowledge as software models, and hand over the work of c...

AI Technical Summary

Problems solved by technology

Unfortunately, UML has the following defects: First, non-computability: Due to the lack of rigorous theoretical support in UML, the software view constructed by UML lacks operability, that is, the view described by UML lacks automatic code generation technology. Sufficient and consistent information that can run the software, to obtain the software that can be run by the computer, it must be edited manually in the form of code; this defect also makes UML only an auxiliary representation tool for software analysis, but not a The real construction of software meta-views with operable software views; second, code-oriented: Although UML claims to be a view description language independent of specific languages ​​and platforms, in essence UML is basically oriented to programmers using object-oriented programming expressive tools for program analysis and design

This code-oriented feature for programmers makes "emphasis on implementation and neglect of business" a chronic problem in the software development industry

Third, it is difficult to use: UML creates concepts, a large number of relationships and a large number of diagrams

This visual software modeling method based on prefabricated parts assembly has two basic defects: first, it must be assembled based on prefabricated components, and the construction of the software view is severely restricted by prefabricated components; Component integration of any interface, this kind of visual software modeling method is usually applied to specific domain modeling based on domain component library, so it is not suitable for general software modeling; second, the assembly and operation principles of components are also It is very simple, based on the fact that the data transmission relationship determines the working collaboration relationship of the components. At the same time, with the increase of the components, the complexity of the data transmission makes the readability of the view sharply worse. Therefore, although this method claims to be a software Modeling, but in fact it is only suitable for describing relatively simple algorithms, and cannot describe large and complex software;

[0007] In general, although the model-driven method is generally recognized as an ideal software development method, there is still a lack of a software meta-view that can be easily understood and mastered by ordinary people in the field, providing general visual software modeling Specifications, support software modeling activities in various fields, especially visual modeling of complex software systems, to construct operable software views, so that software views can be automatically converted into software that can be run by computers through automatic code generation technology, Bringing the model-driven software approach to life

Images