Log in

Relevant bibliographies by topics / Formal methods for software engineering / Journal articles

To see the other types of publications on this topic, follow the link: Formal methods for software engineering.

Journal articles on the topic 'Formal methods for software engineering'

Author: Grafiati

Published: 25 May 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Formal methods for software engineering.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Hinchey, Mike, Michael Jackson, Patrick Cousot, Byron Cook, Jonathan P. Bowen, and Tiziana Margaria. "Software engineering and formal methods." Communications of the ACM 51, no. 9 (September 2008): 54–59. http://dx.doi.org/10.1145/1378727.1378742.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Aichernig, Bernhard, and Bernhard Beckert. "Software engineering and formal methods." Software & Systems Modeling 7, no. 3 (June 11, 2008): 255–56. http://dx.doi.org/10.1007/s10270-008-0091-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Barthe, Gilles, Alberto Pardo, and Gerardo Schneider. "SEFM: software engineering and formal methods." Software & Systems Modeling 14, no. 1 (February 22, 2014): 3–4. http://dx.doi.org/10.1007/s10270-014-0404-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Perseil, Isabelle, and Laurent Pautet. "Formal methods integration in software engineering." Innovations in Systems and Software Engineering 6, no. 1-2 (February 3, 2010): 5–11. http://dx.doi.org/10.1007/s11334-009-0115-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

King, Trevor. "Introduction to Formal Methods for Software Engineering." Measurement and Control 26, no. 1 (February 1993): 19–21. http://dx.doi.org/10.1177/002029409302600105.

Full text

Abstract:

This paper describes what is meant by formal methods for software engineering. It is intended for the non-mathematical reader, and a simple formal specification is presented. The process of formal specification, development and proof is described briefly. Finally the benefits and limitations of formal methods are summarized.

APA, Harvard, Vancouver, ISO, and other styles

6

Schaefer, Ina, and Reiner Hahnle. "Formal Methods in Software Product Line Engineering." Computer 44, no. 2 (February 2011): 82–85. http://dx.doi.org/10.1109/mc.2011.47.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

de Man, Josef. "Session D2: Software engineering: Formal methods I." Microprocessing and Microprogramming 24, no. 1-5 (August 1988): 361. http://dx.doi.org/10.1016/0165-6074(88)90079-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Wordsworth, John. "Education in formal methods for software engineering." Information and Software Technology 29, no. 1 (January 1987): 27–32. http://dx.doi.org/10.1016/0950-5849(87)90017-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Dodani, Mahesh. "Formal methods for object-oriented software engineering." Annals of Software Engineering 2, no. 1 (December 1996): 121–60. http://dx.doi.org/10.1007/bf02063808.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Liu, Shaoying. "Formal engineering methods for software quality assurance." Frontiers of Computer Science 6, no. 1 (January 27, 2012): 1–2. http://dx.doi.org/10.1007/s11704-012-2900-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Wang, Taehyung, Astushi Kitazawa, and Phillip Sheu. "Semantic software engineering." Encyclopedia with Semantic Computing and Robotic Intelligence 01, no. 01 (March 2017): 1630012. http://dx.doi.org/10.1142/s2425038416300123.

Full text

Abstract:

One of the most challenging task in software development is developing software requirements. There are two types of software requirements — user requirement (mostly described by natural language) and system requirements (also called as system specifications and described by formal or semi-formal methods). Therefore, there is a gap between these two types of requirements because of inherently unique features between natural language and formal or semi-formal methods. We describe a semantic software engineering methodology using the design principles of SemanticObjects for object-relational software development with an example. We also survey other semantic approaches and methods for software and Web application development.

APA, Harvard, Vancouver, ISO, and other styles

12

Maibaum, Tom. "Formal methods versus engineering." ACM SIGCSE Bulletin 41, no. 2 (June 25, 2009): 6–12. http://dx.doi.org/10.1145/1595453.1595455.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Martin, John C. "Formal methods software engineering for the CARA system." International Journal on Software Tools for Technology Transfer (STTT) 5, no. 4 (May 1, 2004): 301–7. http://dx.doi.org/10.1007/s10009-003-0113-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Beckert, Bernhard, Tony Hoare, Reiner Hahnle, Douglas Smith, Cordell Green, Silvio Ranise, Cesare Tinelli, Thomas Ball, and Sriram Rajamani. "Intelligent Systems and Formal Methods in Software Engineering." IEEE Intelligent Systems 21, no. 6 (November 2006): 71–81. http://dx.doi.org/10.1109/mis.2006.117.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Tremblay, G. "Formal methods: mathematics, computer science or software engineering?" IEEE Transactions on Education 43, no. 4 (2000): 377–82. http://dx.doi.org/10.1109/13.883345.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Nowotka, Dirk. "Formal add to traditional methods in software engineering." ATZelektronik worldwide 3, no. 4 (July 2008): 14–17. http://dx.doi.org/10.1007/bf03242180.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Ölveczky, Peter Csaba, and Gwen Salaün. "Software engineering and formal methods: SEFM 2019 special section." Software and Systems Modeling 20, no. 2 (March 12, 2021): 291–92. http://dx.doi.org/10.1007/s10270-021-00874-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Davis, James F. "The affordable application of formal methods to software engineering." ACM SIGAda Ada Letters XXV, no. 4 (November 17, 2005): 57–62. http://dx.doi.org/10.1145/1104011.1103855.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Liu, Shaoying, Kazuhiro Takahashi, Toshinori Hayashi, and Toshihiro Nakayama. "Teaching formal methods in the context of software engineering." ACM SIGCSE Bulletin 41, no. 2 (June 25, 2009): 17–23. http://dx.doi.org/10.1145/1595453.1595457.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Cuellar, Jorge, and Zhiming Liu. "SoSyM Special Section on Software Engineering and Formal Methods." Software & Systems Modeling 6, no. 1 (June 17, 2006): 37–38. http://dx.doi.org/10.1007/s10270-006-0010-3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Jasser, Muhammed Basheer. "A Survey on Refinement in Formal Methods and Software Engineering." International Journal of Advanced Trends in Computer Science and Engineering 8, no. 1.4 (September 15, 2019): 105–12. http://dx.doi.org/10.30534/ijatcse/2019/1681.42019.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Tierney, Margaret. "Software engineering standards: the ‘formal methods debate’ in the uk." Technology Analysis & Strategic Management 4, no. 3 (January 1992): 245–78. http://dx.doi.org/10.1080/09537329208524097.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Sobel, Ann E. Kelley. "Empirical results of a software engineering curriculum incorporating formal methods." ACM SIGCSE Bulletin 32, no. 1 (March 2000): 157–61. http://dx.doi.org/10.1145/331795.331846.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

WARD, M. P., and K. H. BENNETT. "FORMAL METHODS TO AID THE EVOLUTION OF SOFTWARE." International Journal of Software Engineering and Knowledge Engineering 05, no. 01 (March 1995): 25–47. http://dx.doi.org/10.1142/s0218194095000034.

Full text

Abstract:

There is a vast collection of operational software systems which are vitally important to their users, yet are becoming increasingly difficult to maintain, enhance, and keep up to date with rapidly changing requirements. For many of these so-called legacy systems, the option of throwing the system away and rewriting it from scratch is not economically viable. Methods are therefore urgently required which enable these systems to evolve in a controlled manner. The approach described in this paper uses formal proven program transformations, which preserve or refine the semantics of a program while changing its form. These transformations are applied to restructure and simplify the legacy systems and to extract higher-level representations. By using an appropriate sequence of transformations, the extracted representation is guaranteed to be equivalent to the code. The method is based on a formal wide spectrum language, called WSL, with an accompanying formal method. Over the last ten years we have developed a large catalog of proven transformations, together with mechanically verifiable applicability conditions. These have been applied to many software development, reverse engineering, and maintenance problems. In this paper, we focus on the results of using this approach in the reverse engineering of medium scale, industrial software, written mostly in languages such as assembler and JOVIAL. Results from both benchmark algorithms and heavily modified, geriatric software are summarized. We conclude that formal methods have an important practical role in software evolution.

APA, Harvard, Vancouver, ISO, and other styles

25

Molnar, B. "Software development with Z: a practical approach to formal methods in software engineering." Information and Software Technology 34, no. 11 (November 1992): 763. http://dx.doi.org/10.1016/0950-5849(92)90171-k.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Baugh, J. W. "Using formal methods to specify the functional properties of engineering software." Computers & Structures 45, no. 3 (October 1992): 557–70. http://dx.doi.org/10.1016/0045-7949(92)90440-b.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Bravetti, Mario, Robert M. Hierons, and Mercedes G. Merayo. "Introduction to the Software Engineering and Formal Methods 2013 special issue." Software & Systems Modeling 16, no. 1 (May 7, 2015): 5–6. http://dx.doi.org/10.1007/s10270-015-0467-z.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Selvaraj, Yuvaraj, Ashfaq Farooqui, Ghazaleh Panahandeh, Wolfgang Ahrendt, and Martin Fabian. "Automatically Learning Formal Models from Autonomous Driving Software." Electronics 11, no. 4 (February 18, 2022): 643. http://dx.doi.org/10.3390/electronics11040643.

Full text

Abstract:

The correctness of autonomous driving software is of utmost importance, as incorrect behavior may have catastrophic consequences. Formal model-based engineering techniques can help guarantee correctness and thereby allow the safe deployment of autonomous vehicles. However, challenges exist for widespread industrial adoption of formal methods. One of these challenges is the model construction problem. Manual construction of formal models is time-consuming, error-prone, and intractable for large systems. Automating model construction would be a big step towards widespread industrial adoption of formal methods for system development, re-engineering, and reverse engineering. This article applies active learning techniques to obtain formal models of an existing (under development) autonomous driving software module implemented in MATLAB. This demonstrates the feasibility of automated learning for automotive industrial use. Additionally, practical challenges in applying automata learning, and possible directions for integrating automata learning into the automotive software development workflow, are discussed.

APA, Harvard, Vancouver, ISO, and other styles

29

Bolton, Matthew L. "Novel Developments in Formal Methods for Human Factors Engineering." Proceedings of the Human Factors and Ergonomics Society Annual Meeting 61, no. 1 (September 2017): 715–17. http://dx.doi.org/10.1177/1541931213601664.

Full text

Abstract:

Formal methods are robust tools and techniques for modeling, specifying, and mathematically proving properties about (verifying) systems. They are particularly good at both finding unexpected problems that arise from complex system interactions and proving that specific types of problems will never manifest. Formal methods have predominantly been used in the analysis and design of computer hardware and software systems. However, a growing research area within the human factors engineering community has been examining how formal methods can be used to prove whether problems exist in systems that rely on human-automation and human-human interaction for their safe operation. This symposium contains four papers by researchers who have been pushing the boundaries of where and how formal methods can be used in human factors engineering.

APA, Harvard, Vancouver, ISO, and other styles

30

KRÄMER, BERND J., and TIZIANA MARGARIA. "A HINDSIGHT ON FORMAL METHODS AND PROSPECTS OF SEMANTIC COMPUTING IN SOFTWARE ENGINEERING." International Journal of Semantic Computing 03, no. 01 (March 2009): 5–30. http://dx.doi.org/10.1142/s1793351x09000641.

Full text

Abstract:

New research activities sailing under the brands of semantic web, semantic web service, and semantic computing have extended, and partly also confused the classical meaning of the term semantics as the software engineering community established it in the last century. In this article we try to shed some light on the different connotations of meaning with this word. We reflect on the role of semantic definitions and formally defined specifications, modeling and programming languages in software engineering activities. We sketch formally defined construction and validation methods, and discuss contributions of tools that exploit semantic information to enhance the quality of software products and development processes. We explore recent work on the use of semantic computing technology in software engineering and discuss opportunities for successful future applications. We conclude with an outlook on the potential of service-oriented computing to change the way software applications are designed, laid out, delivered, and used.

APA, Harvard, Vancouver, ISO, and other styles

31

Gruner, Stefan, and Bernhard Rumpe. "FormSERA workshop on formal methods in software engineering rigorous and agile approaches." ACM SIGSOFT Software Engineering Notes 37, no. 6 (November 27, 2012): 28–30. http://dx.doi.org/10.1145/2382756.2382777.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Dauphin, Michel. "SPECS: Formal methods and techniques for telecommunications software development." Microprocessing and Microprogramming 35, no. 1-5 (September 1992): 117–24. http://dx.doi.org/10.1016/0165-6074(92)90304-p.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Abbate, A. J., and E. J. Bass. "A formal methods approach to semiotic engineering." International Journal of Human-Computer Studies 115 (July 2018): 20–39. http://dx.doi.org/10.1016/j.ijhcs.2018.02.001.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

GANNOD, GERALD C., and BETTY H. C. CHENG. "FACILITATING THE MAINTENANCE OF SAFETY-CRITICAL SYSTEMS." International Journal of Software Engineering and Knowledge Engineering 04, no. 02 (June 1994): 183–204. http://dx.doi.org/10.1142/s0218194094000106.

Full text

Abstract:

As software is increasingly used to control safety-critical systems, correctness becomes paramount. Formal methods in software development provide many benefits in the forward engineering aspect of software development. Reverse engineering is the process of constructing a high-level representation of a system from existing lower level instanti-ations of that system. Reverse engineering of program code into formal specifications facilitates the utilization of the benefits of formal methods in projects where formal methods may not have previously been used, thus facilitating the maintenance of safety-critical systems.

APA, Harvard, Vancouver, ISO, and other styles

35

Plat, Nico, Jan van Katwijk, and Hans Toetenel. "Application and benefits of formal methods in software development." Software Engineering Journal 7, no. 5 (1992): 335. http://dx.doi.org/10.1049/sej.1992.0034.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Johnson, Timothy L. "Improving automation software dependability: A role for formal methods?" Control Engineering Practice 15, no. 11 (November 2007): 1403–15. http://dx.doi.org/10.1016/j.conengprac.2006.07.005.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Santone, Antonella. "Special issue on formal methods for security engineering." Journal of Computer Virology and Hacking Techniques 14, no. 4 (September 11, 2018): 251. http://dx.doi.org/10.1007/s11416-018-0326-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Peña, Joaquin, Christopher A. Rouff, Mike Hinchey, and Antonio Ruiz-Cortés. "Modeling NASA swarm-based systems: using agent-oriented software engineering and formal methods." Software & Systems Modeling 10, no. 1 (October 9, 2009): 55–62. http://dx.doi.org/10.1007/s10270-009-0135-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Batory, Don. "Foreword to the Special Issue on Formal Methods for Software Product Line Engineering." Journal of Logical and Algebraic Methods in Programming 85, no. 1 (January 2016): 121–22. http://dx.doi.org/10.1016/j.jlamp.2015.09.007.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Thomas, Martyn. "The role of formal methods in achieving dependable software." Reliability Engineering & System Safety 43, no. 2 (January 1994): 129–34. http://dx.doi.org/10.1016/0951-8320(94)90058-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Gleirscher, Mario, and Diego Marmsoler. "Formal methods in dependable systems engineering: a survey of professionals from Europe and North America." Empirical Software Engineering 25, no. 6 (September 9, 2020): 4473–546. http://dx.doi.org/10.1007/s10664-020-09836-5.

Full text

Abstract:

Abstract Context Formal methods (FMs) have been around for a while, still being unclear how to leverage their benefits, overcome their challenges, and set new directions for their improvement towards a more successful transfer into practice. Objective We study the use of formal methods in mission-critical software domains, examining industrial and academic views. Method We perform a cross-sectional on-line survey. Results Our results indicate an increased intent to apply FMs in industry, suggesting a positively perceived usefulness. But the results also indicate a negatively perceived ease of use. Scalability, skills, and education seem to be among the key challenges to support this intent. Conclusions We present the largest study of this kind so far (N = 216), and our observations provide valuable insights, highlighting directions for future theoretical and empirical research of formal methods. Our findings are strongly coherent with earlier observations by Austin and Graeme (1993).

APA, Harvard, Vancouver, ISO, and other styles

42

Fukuzaki, Tetsuo, Shaoying Liu, and Michael Butler. "DevFemOps: enhancing maintainability based on microservices using formal engineering methods." Connection Science 34, no. 1 (August 8, 2022): 2125–38. http://dx.doi.org/10.1080/09540091.2022.2099347.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Kordon, F., and L. Petrucci. "Toward Formal-Methods Oecumenism?" IEEE Distributed Systems Online 7, no. 7 (July 2006): 2. http://dx.doi.org/10.1109/mdso.2006.47.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Li, Shao Feng. "A Study on Network Protocol Validation Based on Timed Automata." Applied Mechanics and Materials 543-547 (March 2014): 3386–90. http://dx.doi.org/10.4028/www.scientific.net/amm.543-547.3386.

Full text

Abstract:

With the increasingly complex of computer software system, traditional software engineering methods for major software development will inevitably produce a lot of mistakes and catastrophic consequences for key industry users. Experiment with software engineering methods cannot guarantee the behavior at infinity reliability and security of the state space. All this requires formal analysis and verification to the complex system. In protocol verification based on automatic machines, the automaton is used to represent the behavior of the system, the time automaton is a formal method can be well applied to the network protocol verification.

APA, Harvard, Vancouver, ISO, and other styles

45

ter Beek, Maurice H., Dave Clarke, and Ina Schaefer. "Editorial preface for the JLAMP Special Issue on Formal Methods for Software Product Line Engineering." Journal of Logical and Algebraic Methods in Programming 85, no. 1 (January 2016): 123–24. http://dx.doi.org/10.1016/j.jlamp.2015.09.006.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Striuk, Andrii. "Formation of software design skills among software engineering students." Educational Dimension 58 (June 15, 2022): 1–21. http://dx.doi.org/10.31812/educdim.4519.

Full text

Abstract:

The study focuses on one of the mobile-oriented environment competence components for software engineering (SE) students. It has been demonstrated that the implementation of the higher education standard for SE bachelors has generated a number of issues in terms of ensuring training quality, principally due to a lack of specification for both skills and learning outcomes. Designing a precise framework of professional competencies for SE bachelors is one method to overcome these issues. The research examines methods for developing K14 (the ability to participate in software design, including modeling (formal description) of its structure, behavior, and working processes), a critical particular professional competency for future software engineers. Recommendations for software design teaching techniques, learning content, modeling and design tools, and assessment of the level of formation of relevant competence are developed based on a historical and genetic review of software design training among SE students in the UK, USA, Canada, Australia, New Zealand, and Singapore. The industrial-style software design training (studio training) is used as an example. The transition from architectural to detailed design, as well as project implementation, are discussed. The study's future prospects include substantiating the third engineering component of SE – software construction (after requirements engineering and design engineering).

APA, Harvard, Vancouver, ISO, and other styles

47

Bloomfield, R. E., P. K. D. Froome, and B. Q. Monahan. "Formal methods in the production and assessment of safety critical software." Reliability Engineering & System Safety 32, no. 1-2 (January 1991): 51–66. http://dx.doi.org/10.1016/0951-8320(91)90047-b.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Fisher, Kathleen, John Launchbury, and Raymond Richards. "The HACMS program: using formal methods to eliminate exploitable bugs." Philosophical Transactions of the Royal Society A: Mathematical, Physical and Engineering Sciences 375, no. 2104 (September 4, 2017): 20150401. http://dx.doi.org/10.1098/rsta.2015.0401.

Full text

Abstract:

For decades, formal methods have offered the promise of verified software that does not have exploitable bugs. Until recently, however, it has not been possible to verify software of sufficient complexity to be useful. Recently, that situation has changed. SeL4 is an open-source operating system microkernel efficient enough to be used in a wide range of practical applications. Its designers proved it to be fully functionally correct, ensuring the absence of buffer overflows, null pointer exceptions, use-after-free errors, etc., and guaranteeing integrity and confidentiality. The CompCert Verifying C Compiler maps source C programs to provably equivalent assembly language, ensuring the absence of exploitable bugs in the compiler. A number of factors have enabled this revolution, including faster processors, increased automation, more extensive infrastructure, specialized logics and the decision to co-develop code and correctness proofs rather than verify existing artefacts. In this paper, we explore the promise and limitations of current formal-methods techniques. We discuss these issues in the context of DARPA’s HACMS program, which had as its goal the creation of high-assurance software for vehicles, including quadcopters, helicopters and automobiles. This article is part of the themed issue ‘Verified trustworthy software systems’.

APA, Harvard, Vancouver, ISO, and other styles

49

Madhuri, K., M. Suman, M. Nalini Sri, K. Ravi Kumar, and U. Jyothi Kameswari. "A Systematic Approach to Generate and Conduct Destructive Security Test Sets." Advanced Materials Research 403-408 (November 2011): 4495–98. http://dx.doi.org/10.4028/www.scientific.net/amr.403-408.4495.

Full text

Abstract:

Security testing involves two approaches; the question of who should do it has two answers. Standard testing organizations using a traditional approach can perform functional security testing. For example, ensuring that access control mechanisms work as advertised is a classic functional testing exercise. Systematic security testing approaches should be seamlessly incorporated into software engineering curricula and software development process. Traditional software engineering textbooks failed to provide adequate methods and techniques for students and software engineers to bring security engineering approaches to software development process generating secure software as well as correct software. This paper argues that a security testing phase should be added to software development process with systematic approach to generating and conducting destructive security test sets following a complete coverage principle. Software engineers must have formal training on writing secure code. The security testing tasks include penetrating and destructive tests that are different from functional testing tasks currently covered in software engineering textbooks Moreover, component-based development and formal methods could be useful to produce secure code, as well as automatic security checking tools. Some experience of applying security testing principles in our software engineering method teaching is reported.

APA, Harvard, Vancouver, ISO, and other styles

50

HE, XUDONG. "A COMPREHENSIVE SURVEY OF PETRI NET MODELING IN SOFTWARE ENGINEERING." International Journal of Software Engineering and Knowledge Engineering 23, no. 05 (June 2013): 589–625. http://dx.doi.org/10.1142/s021819401340010x.

Full text

Abstract:

Petri nets, a formal model for concurrent and distributed systems, have been widely applied in system modeling and analysis in almost every branch of computer science and many other scientific and engineering disciplines in the past half century. In this comprehensive survey, we review some major developments of Petri nets that have enhanced their modeling capabilities and in particular the methods to incorporate well-known software engineering development paradigms in Petri nets to support general software system modeling.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!