Obtaining Use Cases and Security Use Cases from Secure Business Process through the MDA Approach

2011 ◽  
Vol 51 (3) ◽  
pp. 446-465 ◽  
Author(s):  
Alfonso Rodríguez ◽  
Eduardo Fernández-Medina ◽  
Juan Trujillo ◽  
Mario Piattini

2008 ◽  
pp. 257-297 ◽  
Author(s):  
Asif Akram ◽  
Rob Allen ◽  
Sanjay Chaudhary ◽  
Prateek Jain ◽  
Zakir Laliwala

This chapter presents a ‘Case Study’ based on the distributed market. The requirements of this Grid Business Process are more demanding than any typical business process deployed within a single organization or enterprise. Recently different specifications built on top of Web service standards have originated from the Grid paradigm to address limitations of stateless Web services. These emerging specifications are evaluated in the first part of the chapter to capture requirements of a dynamic business process i.e. Business Process Grid. In second part of the chapter, a case study with different use cases is presented to simulate various scenarios. The abstract discussion and requirements of the case study is followed by the actual implementation. The implementation is meant for the proof-of-concept rather than fully functional application.


2012 ◽  
Vol 21 (01) ◽  
pp. 34-43 ◽  
Author(s):  
S. de Lusignan ◽  
P. Krause ◽  
G. Michalakidis ◽  
M. Vicente ◽  
S. Thompson ◽  
...  

SummaryTo perform a requirements analysis of the barriers to conducting research linking of primary care, genetic and cancer data.We extended our initial data-centric approach to include socio-culturalandbusinessrequirements.Wecreatedreferencemodels of core data requirements common to most studies using unified modelling language (UML), dataflow diagrams (DFD) and business process modelling notation (BPMN). We conducted a stakeholder analysis and constructed DFD and UML diagrams for use cases based on simulated research studies. We used research output as a sensitivity analysis.Differences between the reference model and use cases identified study specific data requirements. The stakeholder analysis identified: tensions, changes in specification, some indifference from data providers and enthusiastic informaticians urging inclusion of socio-cultural context. We identified requirements to collect information at three levels: microdata items, which need to be semantically interoperable, meso-the medical record and data extraction, and macro-the health system and socio-cultural issues. BPMN clarified complex business requirements among data providers and vendors; and additional geographical requirements for patients to be represented in both linked datasets. High quality research output was the norm for most repositories.Reference models provide high-level schemata of the core data requirements. However, business requirements’ modelling identifies stakeholder issues and identifies what needs to be addressed to enable participation.


2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Luis San Martín ◽  
Alfonso Rodríguez ◽  
Angélica Caro ◽  
Ignacio Velásquez

PurposeSecurity requirements play an important role in software development. These can be specified both in enterprise architecture models and in business processes. Enterprises increasingly carry out larger amounts of business processes where security plays a major role. Business processes including security can be automatically obtained from enterprise architecture models by applying a model-driven architecture approach, through a CIM to CIM transformation. The aim of this article is to present the specification of transformation rules for the correspondence between enterprise architecture and business process model elements focusing on security.Design/methodology/approachThis work utilizes motivational aspects of the ArchiMate language to model security in the business layer of enterprise architectures. Next, a set of transformation rules defined with the Atlas Transformation Language are utilized to obtain the correspondence of the enterprise architecture elements in a business process, modelled with a security extension of BPMN.FindingsA total of 19 transformation rules have been defined. These rules are more complex than element to element relations, as they take into consideration the context of the elements for establishing the correspondence. Additionally, the prototype of a tool that allows the automatic transformation between both models has been developed.Originality/valueThe results of this work demonstrate the possibility to tackle complex transformations between both models, as previous literature focuses on semantic correspondences. Moreover, the obtained models can be of use for software developers applying the model-driven approach.


Sign in / Sign up

Export Citation Format

Share Document