[Impressum]
[E-Mail]
Modeling ePassport (2)
The
next step is to describe the data types and messages with UML class
diagrams and the communication structure and attacker capabilities with
an UML deployment diagram.
- Classes with the stereotype <<Terminal>>, <<Smartcard>> or <<User>>
describe components. This components have some attributes and use
messages to interact with each other. Messages are classes that are
derived from a class with the stereotype <<Message>>. The security property for this application is modelled as an OCL constraint in the class EPass.
- The
attacker capabilities are described in the deployment diagram by the
stereotype <<Threat>>. Since the attacker can read all
messages, send arbitrary messages, and suppress messages, we have a Dolev-Yao attacker model.
Back, Next Step: Detailed model with activity diagrams