A programming and a modelling perspective on the evaluation of Java Card implementations

Pieter H. Hartel, Eduard de Jong

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    3 Citations (Scopus)
    54 Downloads (Pure)


    Java Card Technology has provided a huge step forward in programming smart cards: from assembler to using a high level Object Oriented language. However, the authors have found some differences between the current Java Card version (2.1) and main stream Java that may restrict the benefits of using Java achievable in smartcard programming. In particular, efforts towards evaluating Java Card implementations at a high level of assurance may be hampered by the presence of these differences as well as by the complexity of the Java Card VM and API. The goal of the present paper is to detail the differences from a programming and a modelling point of view.
    Original languageEnglish
    Title of host publicationJava on Smart Cards: Programming and Security
    Subtitle of host publicationFirst International Workshop, JavaCard 2000 Cannes, France, September 14, 2000, Revised Papers
    EditorsIsabelle Attali, Thomas Jensen
    Place of PublicationBerlin, Heidelberg
    Number of pages21
    ISBN (Electronic)978-3-540-45165-5
    ISBN (Print)978-3-540-42167-2
    Publication statusPublished - Sep 2000
    Event1st International Java Card Workshop, JavaCard 2000 - Cannes, France
    Duration: 14 Sep 200014 Sep 2000
    Conference number: 1

    Publication series

    NameLecture Notes in Computer Science
    ISSN (Print)0302-9743


    Workshop1st International Java Card Workshop, JavaCard 2000
    Abbreviated titleJavaCard


    • SCS-Cybersecurity
    • Smart cards
    • Garbage collection
    • Context switch
    • Modelling perspective
    • Power failure

    Fingerprint Dive into the research topics of 'A programming and a modelling perspective on the evaluation of Java Card implementations'. Together they form a unique fingerprint.

    Cite this