Since the emergence of software engineering in the late 1960s, require-ments analysis has always been an important theme of software development. In the process of software development, many people are needed to coop-erate to ensure the stability and reliability of the software. According to the degree of formalization in the software development process, software en-gineering methods can be divided into three types: non-formal, semi-formal and formal. In object- oriented software development, UML has become a de facto modeling standard. However, although UML is intuitive and easy to understand and apply, it has inaccurate semantics, and UML is a semi-formal modeling language that cannot be formally verified. Event-B is a formal method based on a large number of mathematical predicate logic, which is accurate but difficult to understand and apply. Therefore, how to combine the advantages of UML diagrams and Event- B methods is the focus of re-search.
This will help us customize your experience to showcase the most relevant content to your age group
Please select from below
Login
Not registered?
Sign up
Already registered?
Success – Your message will goes here
We'd love to hear from you!
Thank you for visiting our website. Would you like to provide feedback on how we could improve your experience?
This site does not use any third party cookies with one exception — it uses cookies from Google to deliver its services and to analyze traffic.Learn More.