Journal articles on the topic 'Software verification'

To see the other types of publications on this topic, follow the link: Software verification.

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 'Software verification.'

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

Kwiatkowska, Marta. "From software verification to ‘everyware’ verification." Computer Science - Research and Development 28, no. 4 (September 7, 2013): 295–310. http://dx.doi.org/10.1007/s00450-013-0249-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Goerigk, Wolfgang. "Mechanical Software Verification." Electronic Notes in Theoretical Computer Science 58, no. 2 (November 2001): 117–37. http://dx.doi.org/10.1016/s1571-0661(04)00282-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Filliâtre, Jean-Christophe. "Deductive software verification." International Journal on Software Tools for Technology Transfer 13, no. 5 (August 20, 2011): 397–403. http://dx.doi.org/10.1007/s10009-011-0211-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Dobrescu, Mihai, and Katerina Argyraki. "Software dataplane verification." Communications of the ACM 58, no. 11 (October 23, 2015): 113–21. http://dx.doi.org/10.1145/2823400.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

V. Gayetri Devi, S., C. Nalini, and N. Kumar. "An efficient software verification using multi-layered software verification tool." International Journal of Engineering & Technology 7, no. 2.21 (April 20, 2018): 454. http://dx.doi.org/10.14419/ijet.v7i2.21.12465.

Full text
Abstract:
Rapid advancements in Software Verification and Validation have been critical in the wide development of tools and techniques to identify potential Concurrent bugs and hence verify the software correctness. A concurrent program has multiple processes and shared objects. Each process is a sequential program and they use the shared objects for communication for completion of a task. The primary objective of this survey is retrospective review of different tools and methods used for the verification of real-time concurrent software. This paper describes the proposed tool ‘F-JAVA’ for multithreaded Java codebases in contrast with existing ‘FRAMA-C’ platform, which is dedicated to real-time concurrent C software analysis. The proposed system is comprised of three layers, namely Programming rules generation stage, Verification stage with Particle Swarm Optimization (PSO) algorithm, and Performance measurement stage. It aims to address some of the challenges in the verification process such as larger programs, long execution times, and false alarms or bugs, and platform independent code verification
APA, Harvard, Vancouver, ISO, and other styles
6

Büchner, Frank. "Software Unit Verification of Medical Software." New Electronics 54, no. 3 (February 23, 2021): 22–23. http://dx.doi.org/10.12968/s0047-9624(22)60332-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Esbel, Ousama, and Ng Ah Ngan Mike Christian. "Hardware/Software Verification Process through Cloud Computing." Lecture Notes on Software Engineering 4, no. 2 (May 2016): 123–28. http://dx.doi.org/10.7763/lnse.2016.v4.236.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Korablin, Y. P., and A. A. Shipov. "Questions of verification in distributed software systems." Contemporary problems of social work 1, no. 2 (June 30, 2015): 102–6. http://dx.doi.org/10.17922/2412-5466-2015-1-2-102-106.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Huisman, Marieke. "Verification of Concurrent Software." Electronic Proceedings in Theoretical Computer Science 261 (November 29, 2017): 2. http://dx.doi.org/10.4204/eptcs.261.2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Abdulla, Parosh Aziz, and K. Rustan M. Leino. "Tools for software verification." International Journal on Software Tools for Technology Transfer 15, no. 2 (March 3, 2013): 85–88. http://dx.doi.org/10.1007/s10009-013-0270-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
11

Beyer, Dirk, and Andreas Stahlbauer. "BDD-based software verification." International Journal on Software Tools for Technology Transfer 16, no. 5 (August 19, 2014): 507–18. http://dx.doi.org/10.1007/s10009-014-0334-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
12

Malkis, Alexander, and Anindya Banerjee. "Verification of software barriers." ACM SIGPLAN Notices 47, no. 8 (September 11, 2012): 313–14. http://dx.doi.org/10.1145/2370036.2145871.

Full text
APA, Harvard, Vancouver, ISO, and other styles
13

Niculaescu, Oana. "What's formal software verification?" XRDS: Crossroads, The ACM Magazine for Students 25, no. 4 (July 9, 2019): 64–65. http://dx.doi.org/10.1145/3341815.

Full text
APA, Harvard, Vancouver, ISO, and other styles
14

Holzmann, Gerard J., and Margaret H. Smith. "Automating software feature verification." Bell Labs Technical Journal 5, no. 2 (August 28, 2002): 72–87. http://dx.doi.org/10.1002/bltj.2223.

Full text
APA, Harvard, Vancouver, ISO, and other styles
15

Tutnov, An A., Al A. Tutnov, and E. E. Alekseev. "Verification of PULSAR+software." Atomic Energy 83, no. 2 (August 1997): 591–95. http://dx.doi.org/10.1007/bf02413887.

Full text
APA, Harvard, Vancouver, ISO, and other styles
16

Wang, Shihao. "Software Simulation for Hardware/Software Co-Verification." Journal of Computer Research and Development 42, no. 3 (2005): 514. http://dx.doi.org/10.1360/crad20050322.

Full text
APA, Harvard, Vancouver, ISO, and other styles
17

Hsiung, Pao-Ann. "Embedded software verification in hardware–software codesign." Journal of Systems Architecture 46, no. 15 (December 2000): 1435–50. http://dx.doi.org/10.1016/s1383-7621(00)00034-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
18

Alkazemi, Basem Y. "On Verification of Software Components." International Journal of Software Engineering & Applications 3, no. 5 (September 30, 2012): 17–29. http://dx.doi.org/10.5121/ijsea.2012.3502.

Full text
APA, Harvard, Vancouver, ISO, and other styles
19

Greengard, Samuel. "Formal software verification measures up." Communications of the ACM 64, no. 7 (July 2021): 13–15. http://dx.doi.org/10.1145/3464933.

Full text
APA, Harvard, Vancouver, ISO, and other styles
20

Distefano, Dino. "Moving fast with software verification." Electronic Proceedings in Theoretical Computer Science 188 (August 14, 2015): 5. http://dx.doi.org/10.4204/eptcs.188.2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
21

Mantovani, Jacopo. "Automatic software verification for robotics." AI Communications 21, no. 4 (2008): 263–64. http://dx.doi.org/10.3233/aic-2008-0426.

Full text
APA, Harvard, Vancouver, ISO, and other styles
22

M. Leino, K. Rustan. "Accessible Software Verification with Dafny." IEEE Software 34, no. 6 (November 2017): 94–97. http://dx.doi.org/10.1109/ms.2017.4121212.

Full text
APA, Harvard, Vancouver, ISO, and other styles
23

Lowry, M., and D. Dvorak. "Analytic verification of flight software." IEEE Intelligent Systems 13, no. 5 (September 1998): 45–49. http://dx.doi.org/10.1109/5254.722359.

Full text
APA, Harvard, Vancouver, ISO, and other styles
24

Andersen, B. Scott, and George Romanski. "Verification of safety-critical software." Communications of the ACM 54, no. 10 (October 2011): 52–57. http://dx.doi.org/10.1145/2001269.2001286.

Full text
APA, Harvard, Vancouver, ISO, and other styles
25

Flanagan, Cormac, and Shaz Qadeer. "Predicate abstraction for software verification." ACM SIGPLAN Notices 37, no. 1 (January 2002): 191–202. http://dx.doi.org/10.1145/565816.503291.

Full text
APA, Harvard, Vancouver, ISO, and other styles
26

Hailpern, B., and P. Santhanam. "Software debugging, testing, and verification." IBM Systems Journal 41, no. 1 (2002): 4–12. http://dx.doi.org/10.1147/sj.411.0004.

Full text
APA, Harvard, Vancouver, ISO, and other styles
27

Andersen, B. Scott, and George Romanski. "Verification of Safety-critical Software." Queue 9, no. 8 (August 2011): 50–59. http://dx.doi.org/10.1145/2016036.2024356.

Full text
APA, Harvard, Vancouver, ISO, and other styles
28

Déharbe, David, and Silvio Ranise. "Satisfiability solving for software verification." International Journal on Software Tools for Technology Transfer 11, no. 3 (March 24, 2009): 255–60. http://dx.doi.org/10.1007/s10009-009-0105-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
29

Voas, J. M., and K. W. Miller. "Software testability: the new verification." IEEE Software 12, no. 3 (May 1995): 17–28. http://dx.doi.org/10.1109/52.382180.

Full text
APA, Harvard, Vancouver, ISO, and other styles
30

Straunstrup, J., H. R. Andersen, H. Hulgaard, J. Lind-Nielsen, G. Behrmann, K. Kristoffersen, A. Skou, HH Leerberg, and N. B. Theilgaard. "Practical verification of embedded software." Computer 33, no. 5 (May 2000): 68–75. http://dx.doi.org/10.1109/2.841786.

Full text
APA, Harvard, Vancouver, ISO, and other styles
31

Almeida, José Bacelar, Manuel Barbosa, Jorge Sousa Pinto, and Bárbara Vieira. "Deductive verification of cryptographic software." Innovations in Systems and Software Engineering 6, no. 3 (April 1, 2010): 203–18. http://dx.doi.org/10.1007/s11334-010-0127-y.

Full text
APA, Harvard, Vancouver, ISO, and other styles
32

Gravier, Erwan, Markus Gros, and Anne Geburzi. "Verification of Autosar software architectures." ATZelektronik worldwide 5, no. 4 (August 2010): 24–27. http://dx.doi.org/10.1007/bf03242277.

Full text
APA, Harvard, Vancouver, ISO, and other styles
33

Coe, David J., Jeffrey H. Kulick, Aleksandar Milenkovic, and Letha Etzkorn. "Virtualized In Situ Software Update Verification: Verification of Over-the-Air Automotive Software Updates." IEEE Vehicular Technology Magazine 15, no. 1 (March 2020): 84–90. http://dx.doi.org/10.1109/mvt.2019.2954302.

Full text
APA, Harvard, Vancouver, ISO, and other styles
34

Chun, Seung Su. "Effective Extraction of State Invariant for Software Verification." Applied Mechanics and Materials 752-753 (April 2015): 1097–104. http://dx.doi.org/10.4028/www.scientific.net/amm.752-753.1097.

Full text
Abstract:
In software design of complex systems, more time and effort are spent on verification than on constructions. Model checking for software verification techniques offer a large potential to obtain and early integration of verification in the design process. This paper describes how to easily specify and the software properties and to understand the software generating automatically invariant. In this paper deal with issue that state invariant is a property that holds in every reachable state. Not only can be used in understanding and analysis of complex software systems. In addition, it can be used for system verifications such as checking safety, consistency, and completeness. For these reasons, there are many vital researches for deriving state invariant from finite state machine models. In this research was to be considered to extract state invariant. Thus it is likely to be too complex for the user to understand. This paper let the user focus on some interested parts (called scopes) rather than a whole state space in a model. Computation Tree Logic (CTL) is used to specify scopes in which he/she is interested. Given a scope in CTL, forward reachability analysis is used to find out a set of states inside it. Obviously, a set of states calculated in this way is a subset of every reachable state. Keywords: Software verification, Invariant, Scopes, Model Checking
APA, Harvard, Vancouver, ISO, and other styles
35

Mahmoud, Mohammad. "The Role Software Project Scope Verification in Software Development." International Journal of Computer Applications 182, no. 7 (August 14, 2018): 26–29. http://dx.doi.org/10.5120/ijca2018917647.

Full text
APA, Harvard, Vancouver, ISO, and other styles
36

McGregor, John D. "Variation Verification." Journal of Object Technology 8, no. 2 (2009): 7. http://dx.doi.org/10.5381/jot.2009.8.2.c1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
37

Liu, Hua Xiao, Peng Zhang, Li Wen Mu, Ying Jin, and Xue Hang Chi. "A Verification Method of Software Acceptability." Applied Mechanics and Materials 411-414 (September 2013): 436–39. http://dx.doi.org/10.4028/www.scientific.net/amm.411-414.436.

Full text
Abstract:
Software requirements validation is one of the hot problems of software engineering field, for the formal verification of software acceptability, this paper presents a formal verification software acceptability method. This method uses the 4-variable model to character the software system requirements and the software behavior, and gives a formal description of the 4-variable model based on the generic model of Tabular expression, and converts the Tabular expression into predicate logic knowledge base to verify the software acceptability. The analysis shows that the proposed method is effective, and the software acceptability can be verified.
APA, Harvard, Vancouver, ISO, and other styles
38

SHINOZAKI, Koichi. "Software Verification using Model-Checking Techniques." Journal of The Institute of Electrical Engineers of Japan 127, no. 10 (2007): 664–67. http://dx.doi.org/10.1541/ieejjournal.127.664.

Full text
APA, Harvard, Vancouver, ISO, and other styles
39

Kishi, Tomoji, and Natsuko Noda. "Formal verification and software product lines." Communications of the ACM 49, no. 12 (December 2006): 73–77. http://dx.doi.org/10.1145/1183236.1183270.

Full text
APA, Harvard, Vancouver, ISO, and other styles
40

Kajiwara, M., H. Ichikawa, M. Itoh, and Y. Yoshida. "Specification and Verification of Switching Software." IEEE Transactions on Communications 33, no. 3 (1985): 193–98. http://dx.doi.org/10.1109/tcom.1985.1096279.

Full text
APA, Harvard, Vancouver, ISO, and other styles
41

Wallace, D. R., and R. U. Fujii. "Planning for software verification and validation." ACM SIGSOFT Software Engineering Notes 12, no. 2 (April 1987): 37. http://dx.doi.org/10.1145/24562.24567.

Full text
APA, Harvard, Vancouver, ISO, and other styles
42

Shokry, Hesham, and Mike Hinchey. "Model-Based Verification of Embedded Software." Computer 42, no. 4 (April 2009): 53–59. http://dx.doi.org/10.1109/mc.2009.125.

Full text
APA, Harvard, Vancouver, ISO, and other styles
43

Dykstra, Josiah. "Software verification and validation with destiny." XRDS: Crossroads, The ACM Magazine for Students 8, no. 3 (April 2002): 23–27. http://dx.doi.org/10.1145/567162.567168.

Full text
APA, Harvard, Vancouver, ISO, and other styles
44

Wang, Chao, Zijiang Yang, Franjo Ivančić, and Aarti Gupta. "Disjunctive image computation for software verification." ACM Transactions on Design Automation of Electronic Systems 12, no. 2 (April 2007): 10. http://dx.doi.org/10.1145/1230800.1230802.

Full text
APA, Harvard, Vancouver, ISO, and other styles
45

Gotlieb, Arnaud. "TCAS software verification using constraint programming." Knowledge Engineering Review 27, no. 3 (July 26, 2012): 343–60. http://dx.doi.org/10.1017/s0269888912000252.

Full text
Abstract:
AbstractSafety-critical software must be thoroughly verified before being exploited in commercial applications. In particular, any TCAS (Traffic Alert and Collision Avoidance System) implementation must be verified against safety properties extracted from the anti-collision theory that regulates the controlled airspace. This verification step is currently realized with manual code reviews and testing. In our work, we explore the capabilities of Constraint Programming for automated software verification and testing. We built a dedicated constraint solving procedure that combines constraint propagation with Linear Programming to solve conditional disjunctive constraint systems over bounded integers extracted from computer programs and safety properties. An experience we made on verifying a publicly available TCAS component implementation against a set of safety-critical properties showed that this approach is viable and efficient.
APA, Harvard, Vancouver, ISO, and other styles
46

Birla, Shilpi, Shikha Sharma, and Neeraj Kr Shukla. "UVM-powered hardware/software co-verification." Journal of Information and Optimization Sciences 38, no. 6 (August 18, 2017): 945–52. http://dx.doi.org/10.1080/02522667.2017.1372141.

Full text
APA, Harvard, Vancouver, ISO, and other styles
47

Bucur, Doina, and Marta Kwiatkowska. "On software verification for sensor nodes." Journal of Systems and Software 84, no. 10 (October 2011): 1693–707. http://dx.doi.org/10.1016/j.jss.2011.04.054.

Full text
APA, Harvard, Vancouver, ISO, and other styles
48

Ding, Zuohua, and Jing Liu. "An Improvement of Software Architecture Verification." Electronic Notes in Theoretical Computer Science 243 (July 2009): 49–67. http://dx.doi.org/10.1016/j.entcs.2009.07.005.

Full text
APA, Harvard, Vancouver, ISO, and other styles
49

Karamanlidis, D. "Software validation: inspection - testing - verification - alternatives." Advances in Engineering Software (1978) 7, no. 4 (October 1985): 216. http://dx.doi.org/10.1016/0141-1195(85)90080-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
50

Wallace, D. R., and R. U. Fujii. "Software verification and validation: an overview." IEEE Software 6, no. 3 (May 1989): 10–17. http://dx.doi.org/10.1109/52.28119.

Full text
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!

To the bibliography