Embedding Requirements within the Model Driven Architecture

The Model Driven Architecture (MDA) brings benefits to software development, among them the potential for connecting software models with the business domain. This paper focuses on the upstream or Computation Independent Model (CIM) phase of the MDA. Our contention is that, whilst there are many models and notations available within the CIM Phase, those that are currently popular and supported by the Object Management Group (OMG), may not be the most useful notations for business analysts nor sufficient to fully support software requirements and specification. Therefore, with specific emphasis on the value of the Business Process Modelling Notation (BPMN) for business analysts, this paper provides an example of a typical CIM approach before describing an approach which incorporates specific requirements techniques. A framework extension to the MDA is then introduced; which embeds requirements and specification within the CIM, thus further enhancing the utility of MDA by providing a more complete method for business analysis

Designing Digital Work

Combining theory, methodology and tools, this open access book illustrates how to guide innovation in today’s digitized business environment. Highlighting the importance of human knowledge and experience in implementing business processes, the authors take a conceptual perspective to explore the challenges and issues currently facing organizations. Subsequent chapters put these concepts into practice, discussing instruments that can be used to support the articulation and alignment of knowledge within work processes. A timely and comprehensive set of tools and case studies, this book is essential reading for those researching innovation and digitization, organization and business strategy

Discovering Business Models for Software Process Management - An Approach for Integrating Time and Resource Perspectives from Legacy Information Systems

Business Process Management (BPM) is becoming the modern core to support business in all type of organizations and software business is not an exception. Software companies are often involved in important and complex collaborative projects carried out by many stakeholders. Each actor (customers, suppliers or government instances, among others) works with individual and shared processes. Everyone needs dynamic and evolving approaches for managing their software projects lifecycle. Nevertheless, many companies still use systems that are out of the scope of BPM for planning and control projects and managing enterprise content (Enterprise Content Management, ECM) as well as all kinds of resources (ERP). Somehow systems include scattered artifacts that are related to BPM perspectives: control and data flow, time, resource and case, for example. It is aimed to get interoperable BPM models from these classical Legacy Information Systems (LIS). Model-Driven Engineering (MDE) allows going from application code to higher-level of abstraction models. Particularly, there are standards and proposals for reverse engineering LIS. This paper illustrates LIS cases for software project planning and ECM, looking at time and resource perspectives. To conclude, we will propose a MDE-based approach for taking out business models in the context of software process management.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-

Formal Specification, Implementation, and Evaluation of the AdoBPRIM Approach

Modeling is one of the fundamental aspects of Risk-aware Business Process Management. The conceptualization of new modeling approaches needs to integrate all abstraction layers of risk and business process concepts and requires a highly specialized knowledge in conceptual modeling foundations and formal specification of meta-models. This paper introduces a risk-aware business process modeling approach based on the BPRIM method. In order to comprehensively and unambiguously specify the proposed approach, we revert to the FDMM formalism. Furthermore, a corresponding software prototype called AdoBPRIM has been implemented using the ADOxx meta-modeling platform to assess the technical feasibility of the approach. The usability of the tool has been empirically evaluated and a healthcare process-based example is presented as a proof-of-concept. We show that the AdoBPRIM approach enables Risk-aware Business Process Management with an excellent usability. In summary, this paper constitutes a best-practice for formally specifying, technically implementing, and empirically evaluating modeling method conceptualizations

Embedding requirements within the model driven architecture.

The Model Driven Architecture (MDA) is offered as one way forward in software systems modelling to connect software design with the business domain. The general focus of the MDA is the development of software systems by performing transformations between software design models, and the automatic generation of application code from those models. Software systems are provided by developers, whose experience and models are not always in line with those of other stakeholders, which presents a challenge for the community. From reviewing the available literature, it is found that whilst many models and notations are available, those that are significantly supported by the MDA may not be best for use by non technical stakeholders. In addition, the MDA does not explicitly consider requirements and specification. This research begins by investigating the adequacy of the MDA requirements phase and examining the feasibility of incorporating a requirements definition, specifically focusing upon model transformations. MDA artefacts were found to serve better the software community and requirements were not appropriately integrated within the MDA, with significant extension upstream being required in order to sufficiently accommodate the business user in terms of a requirements definition. Therefore, an extension to the MDA framework is offered that directly addresses Requirements Engineering (RE), including the distinction of analysis from design, highlighting the importance of specification. This extension is suggested to further the utility of the MDA by making it accessible to a wider audience upstream, enabling specification to be a direct output from business user involvement in the requirements phase of the MDA. To demonstrate applicability, this research illustrates the framework extension with the provision of a method and discusses the use of the approach in both academic and commercial settings. The results suggest that such an extension is academically viable in facilitating the move from analysis into the design of software systems, accessible for business use and beneficial in industry by allowing for the involvement of the client in producing models sufficient enough for use in the development of software systems using MDA tools and techniques

Recommendations and best practices for cloud enterprise security

© 2014 IEEE. Enterprise security is essential to achieve global information security in business and organizations. Enterprise Cloud computing is a new paradigm for that enterprise where businesses need to be secured. Enterprise Cloud computing has established its businesses and software as a service paradigm is increasing its demand for more services. However, this new trend needs to be more systematic with respect to Enterprise Cloud security. Enterprise Cloud security is the key factor in sustaining Enterprise Cloud technology by building-in trust. For example, current challenges that are witnessed today with cyber security and application security flaws are important lessons to be learned. It also has provided best practices that can be adapted. Similarly, as the demand for Enterprise Cloud services increases and so increased importance sought for security and privacy. This paper presents recommendations for enterprise security to analyze and model Enterprise Cloud organizational security of the Enterprise Cloud and its data. In particular, Enterprise Cloud data and Enterprise Cloud storage technologies have become more commonly used in organization that adopt Cloud Computing. Therefore, building trust for Enterprise Cloud users should be the one of the main focuses of Enterprise Cloud computing research

Integrated Modeling of Process- and Data-Centric Software Systems with PHILharmonicFlows

Process- and data-centric software systems require a tight integration of processes, functions, data, and users. Thereby, the behavioral perspective is described by process models, while the information perspective is captured in a data model. Eliciting and capturing requirements of such software systems in a consistent way is a challenging task, demanding that both process and data model are well aligned and consistent with each other. While traditional software modeling languages do not allow for an explicit integration of data and process models, activity-centric process modeling languages tend to neglect the role of data as a driver of process execution; i.e., business objects are usually outside the control of the process, normally stored in external databases. To overcome this drawback, PHILharmonicFlows provides a comprehensive framework for enabling object-aware process support. In addition, a sound specification of process- and object-centric software systems becomes possible. In this paper, we present a requirements modeling approach that provides methodological guidance for modeling large process- and data-centric software systems based on PHILharmonicFlows. Such guidance will foster the introduction of respective software systems in the large scale