1 / 18

An ASN.1 Profile Anders Ek

An ASN.1 Profile Anders Ek. Motivation / Scenarios Profile Basics A Draft ASN.1 Profile Example Summary. Motivation: Usage Scenarios. Access to ASN.1 module from UML models Visualization of ASN.1 Modules Design of ASN.1 Modules. Accessing ASN.1 Modules. Precond: ASN.1 module exist

melody
Download Presentation

An ASN.1 Profile Anders Ek

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An ASN.1 ProfileAnders Ek Motivation / Scenarios Profile Basics A Draft ASN.1 Profile Example Summary

  2. Motivation: Usage Scenarios • Access to ASN.1 module from UML models • Visualization of ASN.1 Modules • Design of ASN.1 Modules

  3. Accessing ASN.1 Modules • Precond: • ASN.1 module exist • Application design using UML • Need to use type definitions • Actions: • Import the ASN.1 module into UML as a package • Access the ASN.1 types from the UML code

  4. Visualization of ASN.1 Module • Precond • Complex ASN.1 modules exists • Need to understand the modules • Actions • Import ASN.1 modules into UML • Use UML graphics (mainly composition hierarchies in class diagrams) to explain & understand the module.

  5. Design of ASN.1 Modules • Precond: • No existing ASN.1 module • Need to produce one • Like UML graphics!! • Actions • Design using UML class diagrams • Tag with ASN.1 concepts • Generate the ASN.1 module

  6. Motivation: Summary • Accessing ASN.1 type defs from UML models • Visualization of ASN.1 Modules • Design of ASN.1 Modules

  7. Profile Definition Basics • Purpose: • To define how to associate extra information with model elements in a UML model. • Basics • A ’profile’ is a UML package stereotyped by <<profile>>. • A profile contains stereotypes that define • tagged values (the attributes of the stereotype) • what model element to extend (the ’extends’ relation to a metaclass) • Often includes a ModelLibary (package with data types) • A profile contains constraints that give static semantics • A profile typically comes with dynamic semantics usually • informally definined • implemented as tool feature, often a code generator

  8. <<metaclass>> UML::UseCase Simple Profile Example • <<profile>> package • metaclass from appropriate metamodel • extention definition • stereotype definition • tag definitions (stereotype attributes) <<profile>> package UseCaseDetails 1 <<stereotype>> UseCaseDef Precondition : Charstring ActionSequence : Charstring Alternatives : Charstring Postcondition : Charstring

  9. Using the Profile • Apply the profile • activate addin • load & use model profile • Select ’Tagged values...’ for a use case

  10. Profiles Summary • Extends UML • Stereotypes / tagged values • Model library • Semantics • Constraints • Dynamic semantics

  11. A (Very) Incomplete ASN.1 Profile

  12. Profile

  13. Model Library

  14. Example Module ExampleASN1Module ::= BEGIN EMPLOYEES ::= SEQUENCE OF PERSON PERSON ::= SEQUENCE { name VisibleString, age INTEGER, car CAR, house HOUSE } CAR ::= SEQUENCE { licenseNo INTEGER, manufacturer VisibleString } HOUSE ::= SEQUENCE { address VisibleString } END

  15. ExampleModule

  16. Example Application

  17. Example Application, cnt

  18. Summary • Purpose • Usage of ASN.1 modules in UML applications • Visualization / Design • Profile • Stereotypes / tagged values etc • Constraints • Semantics • Issues • Information classes and objects • Inline type definitions • Parametrized classes • Values and value syntax

More Related