Varying market demands and changes in production standards require systems to be effortlessly modifiable quickly operational. On the other hand, designing, developing, testing control system of a new prove costly time-consuming. Therefore most engineers write codes intuitively apply basic insufficient tests. This study aims develop reusable implementable method that will accurately translate RT...

We present combined-case k-induction, a novel technique for verifying software programs. This technique draws on the strengths of the classical inductive-invariant method and a recent application of k-induction to program verification. In previous work, correctness of programs was established by separately proving a base case and inductive step. We present a new k-induction rule that takes an u...

Embedded systems have the characteristics of reactive, real-time, distributed systems. For these kind of systems formal veri£cation is by nature complex, even more since the system interaction with its environment is often modeled, e.g., as hybrid systems. However, every embedded control system will certainly fail, if its software fails. In this work we present an approach to the formal veri£ca...

Component-Based Software Engineering depends on reliable, robust components, since it may omit a unit test phase wholly or partially from the development cycle. This paper describes a tool that allows a component developer to design and run verification tests. In developing components for our library, we found it necessary to provide multiple mechanisms for identifying and capturing tests to ov...

Utilizing third party software components in the development of new systems became somewhat unfavourable approach among many organizations nowadays. This reluctance is primarily built due to the lack of support to verify the quality attributes of software components in order to avoid potential mismatches with system’s requirements. This paper presents an approach to overcome this problem by pro...

When developing safety-critical software such as reactor protection systems (RPS) in nuclear power plants, a demonstration of software trust (e.g., safety) is not only absolutely essential but also usually mandated by government authorities. While automated generation of fault trees has become possible with increased use of formal specifications, industrial use of fault trees has been limited p...

The software testing process example, as illustrated in Figure 19, is an 11-step testing process that follows the “V” concept of testing. The “V” represents both the software development process and the 11-step software testing process. The first five steps use verification as the primary means to evaluate the correctness of the interim development deliverables. Validation is used to test the s...

For organisations like Facebook, high quality software is important. However, the pace of change and increasing complexity of modern code makes it difficult to produce error-free software. Available tools are often lacking in helping programmers develop more reliable and secure applications. Formal verification is a technique able to detect software errors statically, before a product is actual...

Software veriication encompasses a wide range of techniques and activities that are geared towards demonstrating that software is reliable. Veriication techniques such as testing provide a way to assess the likelihood that software will fail during use. This paper introduces a diierent type of ver-iication that shows how likely it is that an incorrect program will not fail. Our veriication appl...

Computer programs are used in almost every area of our daily life. Especially in fields like medical computing and the whole sector of security systems they became almost vital or at least mission critical. One of the main problems of software engineering is to develop programs that are reliable enough to meet the needs of a mission critical appliance. Several approaches are taken to prove that...