Embedded software development system

Abstract

The invention relates to an embedded software development system. The method comprises the following steps: establishing a demand model of an embedded system program to be developed according to demand analysis of the embedded software system program; analyzing and detecting the demand model, generating source codes required by the target software system program at the same time, and further generating the target software system program; performing program analysis on the target software system program to obtain a program model, performing comparative analysis on the program model and the demand model to find difference, and if difference is found, repairing the generated target software system program or demand model. Aiming at the characteristics of the embedded software system program, a demand modeling technical scheme suitable for the embedded software system program is provided, the demand expressed by a user by using a natural language is converted into a scene and behavior expression, and a good foundation is laid for automatically detecting whether the demand of a software system is correct and complete or not.

Description

technical field [0001] The invention belongs to the field of software development technology and tools, in particular to an embedded software development system. Background technique [0002] There are many deficiencies in the traditional embedded software system program development work, mainly in the following aspects: [0003] (1) The high-level system requirements analysis stage is easily disconnected from the software implementation stage. Usually, the requirements specifications and requirements models established according to user requirements are the basis and norms for software implementation, but in the actual software implementation process, due to the variability of user requirements and frequent program changes, the final source program is different from the original requirements. Specifications and requirements models will produce inconsistencies or contradictions. If the original requirements specifications and requirements models are not revised in time, thi...

AI Technical Summary

Problems solved by technology

Usually, the requirements specifications and requirements models established according to user requirements are the basis and norms for software implementation, but in the actual software implementation process, due to the variability of user requirements and frequent program changes, the final source program is different from the original requirements. Specifications and requirements models will produce inconsistencies or contradictions. If the original requirements specifications and requirements models are not revised in time, this will lead to inconsistencies among system documents, making the requirements specifications and requirements models established with a lot of effort and cost impossible. play its due role

[0004] (2) Due to the above-mentioned disconnection, the detection of the requirement model in the system requirements analysis stage is also disconnected from the testing of the source program in the software implementation stage, resulting in the need to spend a lot of effort and cost to repeatedly design test cases

[0005] (3) There is a lack of a comprehensive framework for guiding the development of embedded software systems and effective methods and technologies for supporting embedded software development from requirements to source programs

Images