A Safety-Critical Java Technology Compatibility Kit

Søndergaard, Hans; Korsholm, Stephan Erbs; Ravn, Anders P.

doi:10.1145/2661020.2661021

Cited by 2 publications

(11 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Mostly, JML specifications or models are written as annotations in Java source files, but, as explained in Section 3.1, it is possible to write the specifications in separate files [53]. For that reason, OpenJML is now applied in this work instead of using the jml4c compiler that was used in our previous works [13,14], see Section 4.1. For that reason, OpenJML is now applied in this work instead of using the jml4c compiler that was used in our previous works [13,14], see Section 4.1.…”

Section: Related Workmentioning

confidence: 99%

“…This paper presents a model-based development of a Technology Compatibility Kit test suite and a test execution tool for the draft safety-critical Java profile specification. Yet, in order to complete the JSR process for SCJ, we began working on the TCK component in early 2013 [13] and reported on our progress in [14]. Java Modeling Language annotations define contracts for classes and interfaces.…”

mentioning

confidence: 99%

“…Java Modeling Language annotations define contracts for classes and interfaces. As argued in previous works [13,14], a first step in this approach formalizes the informal specification in the JML [17,18]. Hereby, the design and elaboration of the concrete test cases are simplified, because the expected results are derived from contracts and thus do not need to be provided explicitly.…”

mentioning

confidence: 99%

“…Yet, in order to complete the JSR process for SCJ, we began working on the TCK component in early 2013 [13] and reported on our progress in [14]. Because SCJ builds on RTSJ, this has led to many last minute changes to the SCJ specification.…”

mentioning

confidence: 99%

See 3 more Smart Citations

Conformance test development with the Java modeling language

Søndergaard

Korsholm

Ravn

2017

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

In order to claim conformance with a Java Specification Request, a Java implementation has to pass all tests in an associated Technology Compatibility Kit. This paper presents a model-based development of a Technology Compatibility Kit test suite and a test execution tool for the draft safety-critical Java profile specification. The Java Modeling Language is used to model conformance constraints for the profile. Java Modeling Language annotations define contracts for classes and interfaces. The annotations are translated by a tool into runtime assertion checks. Hereby, the design and elaboration of the concrete test cases are simplified, because the expected results are derived from contracts and thus do not need to be provided explicitly. Bottom-up testing is applied for testing methods of the safety-critical Java classes, whereas topdown testing is applied for testing global properties, such as protocols, memory management, and real-time properties, including scheduling. The tests are executed using a simplified version of JUnit, which makes the test suite executable on resource-constrained platforms. Furthermore, Section 2 gives an overview of SCJ and its three conformance levels and concludes with a short overview of Java Modeling Language (JML).It is probably impossible to develop a test suite without familiarity with the language being tested. In our case, we have followed the development of the SCJ specification closely, commented on intermediate draft specifications and, over the years, acquired considerable insight in the details of the specification, as we have developed several prototype implementations [4][5][6]; the most recent one includes all three SCJ levels [7,8].This implementation is developed for resource-constrained embedded platforms, specifically the hardware-near virtual machine (HVM) [9]. Other prototype implementations are [6, 10,11].The draft specification work has nearly finished now (September 2016), although it has been delayed by a combined effort to revise the Real-Time Specification for Java (RTSJ) [12] to version 2.0. Because SCJ builds on RTSJ, this has led to many last minute changes to the SCJ specification. Yet, in order to complete the JSR process for SCJ, we began working on the TCK component in early 2013 [13] and reported on our progress in [14]. This paper consolidates the work of these papers and reports on the most recent progress with building the TCK. Furthermore, the approach is related to model-based testing in general, so it should be of interest for other developers of suites for conformance testing.A TCK is first of all a suite of tests checking whether an implementation of the SCJ technology conforms to the SCJ specification. Of course, the test suite must be based on the SCJ specification only and not be tailored for a particular implementation of the SCJ technology. The specification is written in natural language (English), where the detailed behavior of Java constructs such as classes and methods is documented in the Javadoc standard format.Writing test cod...

show abstract

Section: Related Workmentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 2 more Smart Citations

Conformance test development with the Java modeling language

Søndergaard

Korsholm

Ravn

2017

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

show abstract

“…Moreover, a simplified subset of a language is easier to express in a formal way and therefore it is expected that implementing formal analysis tools for SCJ to be a feasible task. There is indeed research in this direction that uses the Java modeling language (JML) [49,100,122] to formally specify and verify properties of SCJ (the next section elaborates on this topic). From these arguments it follows that two of the generic challenges for safety-critical systems presented at the end of Section 2.2, namely those related to formal verification and development time and effort can be addressed with the new technology proposal of SCJ.…”

Section: Lessons Learnedmentioning

confidence: 99%

Safety‐critical Java for embedded systems

Schoeberl

Dalsgaard

Hansen

et al. 2016

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

Phone +45 4525 3351 compute@compute.dtu.dk www.compute.dtu.dk IMM-PhD-2014-340 Summary (English) Safety-critical systems are real-time systems whose failure can have severe or catastrophic consequences, possibly endangering human life. Many safety-critical systems incorporate embedded computers used to control different tasks. Software running on safety-critical systems needs to be certified before its deployment and the most time-consuming step of this process is the testing and verification phase. Due to the increasing complexity in safety-critical systems there is a need for new technologies that can facilitate testing and verification activities.The safety-critical specification for Java aims at providing a reduced set of the Java programming language that can be used for systems that need to be certified at the highest levels of criticality. Safety-critical Java (SCJ) restricts how a developer can structure an application by providing a specific programming model and by restricting the set of methods and libraries that can be used. Furthermore, its memory model do not use a garbage-collected heap but scoped memories.In this thesis we examine the use of the SCJ specification through an implementation in a time-predictable, FPGA-based Java processor. The specification is now in a mature state and with our implementation we have proved its feasibility in an embedded platform. Moreover, we have explored how simple hardware extensions can reduce the execution time of time-critical operations required by the SCJ specification.The scoped memory model used in SCJ is perhaps one of its most difficult features to use correctly. Therefore, in this work we have also studied practical aspects of its usage by developing scoped memory use patterns and reusable libraries aiming at facilitating the development of complex software systems.ii Summary (Danish)Sikkerhedskritiske systemer er realtidssystemer. Hvis sådanne systemer fejler, kan det have alvorlige eller katastrofale konsekvenser, muligvis livsfarlige konsekvenser. Mange sikkerhedskritiske systemer inkorporerer embeddede computere, som bruges til at kontrollere forskellige opgaver. Software, som kører på sikkerhedskritiske systemer, skal certificeres, før softwaren udrulles, og det mest tidskraevende skridt i denne proces er test-og verifikationsfasen. På grund af den stigende kompleksitet i sikkerhedskritiske systemer er der behov for nye teknologier til at facilitere test-og verifikationsaktiviteter.Den sikkerhedskritiske specifikation for Java har til formål at levere en reduceret udgave af Java-programmeringssproget, som kan bruges til systemer, der skal kunne certificeres på de højeste kritikalitetsniveauer. Safety Critical Java (SCJ) begraenser, hvordan en udvikler kan strukturere en applikation, ved at levere en specifik programmeringsmodel og ved at begraense de metoder og biblioteker, som kan anvendes. Derudover benytter hukommelsesmodellen i SCJ ikke en heap, der er garbage-collected, men afgraensede hukommelser.I denne afhandling undersøger vi brugen a...

show abstract

A Safety-Critical Java Technology Compatibility Kit

Cited by 2 publications

References 9 publications

Conformance test development with the Java modeling language

Conformance test development with the Java modeling language

Safety‐critical Java for embedded systems

Contact Info

Product

Resources

About