Automated Encapsulation of UML Activities for Incremental Development and Verification

Kraemer, Frank Alexander; Herrmann, Peter

doi:10.1007/978-3-642-04425-0_44

Cited by 32 publications

(13 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Applications are composed of building blocks that can specify local behaviour as well as the interaction between several distributed entities. This specification style enables a rapid application development because, on average, more than 70% of a system specification comes from reusable building blocks provided in domain‐specific libraries . In turn, this strategy helps to reduce the expertise required in developing cross domain applications.…”

Section: Case Study and Backgroundmentioning

confidence: 99%

“…Thus, if Arctis models of the considered concrete SBBs exist (e.g. they are available in the Arctis library of building blocks ), the corresponding activity can be omitted. The Creation of a DSSM activity includes definition of assets, abstract SBBs with their goals and strategies, and concrete SBBs omitting definition of a functional model (i.e.…”

Section: Domain‐specific Security Knowledgementioning

confidence: 99%

“…Another possibility to make model‐based engineering more attractive for the development of security‐enhanced embedded systems is to support a better reuse of functionality created for prior systems, which reduces the engineering effort significantly . We consider domain‐specific modelling (DSM) as one way to achieve such reuse.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Integrating security mechanisms into embedded systems by domain‐specific modelling

Vasilevskaya

Gunawan

Nadjm‐Tehrani

et al. 2013

Security Comm Networks

Self Cite

View full text Add to dashboard Cite

Embedded devices are crucial enablers of the Internet of Things and become increasingly common in our daily life. They store, manipulate and transmit sensitive information and, therefore, must be protected against security threats. Due to the security and also resource constraint concerns, designing secure networked embedded systems is a difficult task. Modelbased development (MBD) is promoted to address complexity and ease the design of software intensive systems. We leverage MBD and domain-specific modelling to characterise common issues related to security and embedded systems that are specific to a given application domain. Security-specific knowledge relevant for a certain application domain is represented in the form of an adapted information security ontology. Further, the elements of the ontology are associated with security building blocks modelled with the MBD method SPACE. The selection of relevant security building blocks is based on (i) assets automatically elicited from the functional models, (ii) domain security knowledge captured by the security expert and (iii) the platform adopted by the embedded system engineer. A tool is developed to support the steps supporting this methodology and help to bridge between the security and embedded systems domains. We illustrate our approach with a case study from the smart metering domain.

show abstract

Section: Case Study and Backgroundmentioning

confidence: 99%

Section: Domain‐specific Security Knowledgementioning

confidence: 99%

See 1 more Smart Citation

Integrating security mechanisms into embedded systems by domain‐specific modelling

Vasilevskaya

Gunawan

Nadjm‐Tehrani

et al. 2013

Security Comm Networks

Self Cite

View full text Add to dashboard Cite

show abstract

“…This specification style is suitable for specifying security protocols because such mechanisms are inherently collaborative. Moreover, since a large part of an application specification (on average about 70% [11]) is taken from reusable building blocks, the specification style also facilitates rapid system development. The models have a formal semantics [12] which enables verification of relevant properties, e.g., the correct integration of building blocks into activities, by the model checker included in the tool-support Arctis [13].…”

Section: Collaborative Modelsmentioning

confidence: 99%

Security asset elicitation for collaborative models

Vasilevskaya

Nadjm‐Tehrani

Gunawan

et al. 2012

Proceedings of the Workshop on Model-Driven Security

Self Cite

View full text Add to dashboard Cite

Building secure systems is a difficult job for most engineers since it requires in-depth understanding of security aspects. This task, however, can be assisted by capturing security knowledge in a particular domain and reusing the knowledge when designing applications. We use this strategy and employ an information security ontology to represent the security knowledge. The ontology is associated with system designs which are modelled in collaborative building blocks specifying the behaviour of several entities. In this paper, we identify rules to be applied to the elements of collaborations in order to identify security assets present in the design. Further, required protection mechanisms are determined by applying a reasoner to the ontology and the obtained assets. We exemplify our approach with a case study from the smart metering domain.

show abstract

“…In [15], a reactive semantics is defined for a subset of UML activities, which makes it a precise design language for reactive systems. The same authors also define in [14] an automated compositional mechanism for UML activities together with an interface (a so-called External State Machine), seen as building blocks. Outline.…”

Section: Introductionmentioning

confidence: 99%

Activity Diagrams Patterns for Modeling Business Processes

André

Choppy

Reggio³

2014

Software Engineering Research, Management and Applications

View full text Add to dashboard Cite

Designing and analyzing business processes is the starting point of the development of enterprise applications, especially when following the SOA (Service Oriented Architecture) paradigm. UML activity diagrams are often used to model business processes. Unfortunately, their rich syntax favors mistakes by designers; furthermore, their informal semantics prevents the use of automated verification techniques. In this paper, (i) we propose activity diagram patterns for modeling business processes, (ii) we devise a modular mechanism to compose diagram fragments into a UML activity diagram, and (iii) we propose a semantics for the produced activity diagrams, formalized by colored Petri nets. Our approach guides the modeler task (helping to avoid common mistakes), and allows for automated verification.

show abstract

Automated Encapsulation of UML Activities for Incremental Development and Verification

Cited by 32 publications

References 19 publications

Integrating security mechanisms into embedded systems by domain‐specific modelling

Integrating security mechanisms into embedded systems by domain‐specific modelling

Security asset elicitation for collaborative models

Activity Diagrams Patterns for Modeling Business Processes

Contact Info

Product

Resources

About