| 1. |
|
|
| 2. |
|
|
| 3. |
|
|
| 4. |
- Berger-Reinhartz, Iris, et al.
(författare)
-
Guest editorial for EMMSAD’2019 special section
- 2021
-
Ingår i: Software and Systems Modeling. - : Springer Nature. - 1619-1366 .- 1619-1374. ; 20, s. 25-26
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)abstract
- The EMMSAD (Exploring Modeling Methods for Systems Analysis and Development) conference series organized 24 events from 1996 to 2019, associated with CAiSE (Conference on Advanced Information Systems Engineering). From 2009, EMMSAD has become a two-days working conference. From 2017, EMMSAD best papers are invited to submit extended versions for considering their publication in the Journal of Software and Systems Modeling (SoSyM). The main topics of the EMMSAD series have the focus on models and modeling methods for software and information systems development, requirements engineering, enterprise modeling and architecture, and business process management. The conference further addresses evaluation of modeling methods through a variety of empirical and nonempirical approaches.
|
|
| 5. |
- Bravos, George, et al.
(författare)
-
Deliverable 1.2 : Initial version of requirements specification for CDD
- 2013
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- The CaaS project will elaborate the Capability Driven Development (CDD) approach that will allow digital enterprises to exploit the notion of 'capability' as a means of both designing for services and with services. This deliverable defines an initial set of requirements for CDD. These requirements are provided by the industrial partners through exploration of their use cases. The goal of this deliverable is to identify potential benefits that the CaaS approach could bring to the use cases as well the features to be included the CDD methodology. The requirements are elicited from the use case partners during semi-structured interviews. They are documented in a form of goal models, actor models and concept models for each partner separately. Information documented in these models is used to define envisioned capabilities to be design and delivered during the project as well as to establish the scope of each use case. The use case scope definition focuses on use case goals, causes of capability delivery variability, capability delivery context, functions to be provided in the use case as well as potential capability delivery adjustments. The use case specific models are combined together to obtain a preliminary set of general requirements for CDD. These requirements show CDD goals, types of stakeholders, types of context and types of adjustments. The deliverable ends with concluding remarks about the partners’ expectations for CDD. The requirements for the use cases described in this deliverable will be further elaborated in the final requirements document deliverable D1.4 and will be iteratively refined during the use case elaboration performed in work packages WP2, WP3 and WP4.
|
|
| 6. |
-
Conceptual Modeling : 42nd International Conference, ER 2023, Lisbon, Portugal, November 6–9, 2023, Proceedings
- 2023
-
Samlingsverk (redaktörskap) (övrigt vetenskapligt/konstnärligt)abstract
- This book constitutes the refereed proceedings of the 42nd International Conference on Conceptual Modeling, ER 2023, held in Lisbon, Portugal, during November 6-9, 2023. The 21 full papers were carefully reviewed and selected from 121 submissions. Additionally, the book contains 4 keynote speeches and 3 tutorials, and one invited paper corresponding to one of the keynote speeches.
|
|
| 7. |
|
|
| 8. |
- Giannoulis, Constantinos, et al.
(författare)
-
Exploring Risk-Awareness in istar models
- 2010
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- The i* modeling technique focuses on an early-phase of requirements engineering aiming at understanding how a system would meet organizational goals, how it would fit within the organizational context, why would it be needed and why should it be preferred among other possible alternatives. Analysts are able to understand early the organizational context that bridges system requirements to organizational goals. However, it is not clear how uncertainty, potential threats and opportunities are taken into account both when developing a strategic dependency model and a strategic rationale model, to facilitate a continuous risk management. This paper proposes a set of guidelines for refining i* models based on risk
|
|
| 9. |
- Giannoulis, Constantinos, 1981-
(författare)
-
Model-driven Alignment : Linking Business Strategy with Information Systems
- 2014
-
Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Information technology (IT) is more pervasive than ever before, constituting a significant factor for performance and survival in the business arena. It is essential that IT within organizations understands what the Business needs in order to provide the necessary support and bring value, which is also true when IT is also the main value creator. Therefore, alignment between the Business and IT within organizations is an issue of great concern and it is still open for solvency both for business and IT executives and practitioners.This work is scoped to the alignment linkage between business strategy and information systems (IS), where business strategy typically constitutes the primary exponent of the Business and IS typically encapsulates the elements of IT sustaining an organization. Current approaches are either focused on detailed aspects of IS and treat business strategy abstractly or use distinct business strategy formulations (e.g. Value Chain) but deal with IS only partially. This is problematic because the abstract use of business strategy hinders traceability of strategic intentions and initiatives towards features/aspects of IS, which are aimed to actualize and support such intentions. Because approaches using distinct business strategy formulations are not relevant to all organizations and are limited only to the IS aspects addressed.Introducing a model-driven approach for the alignment linkage is aimed at addressing the outlined shortcomings. Following a design science research paradigm, the main artifact developed is the Unified Business Strategy Meta-Model (UBSMM), which is based on conceptualizing established business strategy formulations (e.g. Value Chain) and integrating them. UBSMM supports mappings to IS models used in organizations, such as IS requirements, enterprise models and enterprise architecture, and provides unambiguous utilization of business strategy for the alignment linkage.Contributions of this thesis are grounded both on the process of building UBSMM and mapping to IS models, as well as the artifact itself. Conceptualizing and integrating business strategy formulations provides a less ambiguous and unified view of strategic concepts. This limits variations in interpretation and reinforces mappings to IS models, which are defined based on inter-schema properties across models. Therefore, UBSMM can link business strategy to IS models enhancing their communication in a traceable manner, ergo, support alignment.
|
|
| 10. |
- Grabis, Jānis, et al.
(författare)
-
CaaS Deliverable 5.3 : The Final Version of Capability Driven Development Methodology
- 2016
-
Rapport (övrigt vetenskapligt/konstnärligt)abstract
- The overall objective of the CaaS project is to create an integrated approach consisting of methods, tools and reusable best practices that allow digital enterprises to take advantage of changes in business context and technologies. This deliverable primarily contributes to CaaS Objective 1, namely, “to elaborate a methodology and supporting methods for Capability Driven Development (CDD) which is adopted by the industrial partners involved in the project and their customers”. To this end the deliverable presents the final version of the CDD methodology, which consists of a number of method components supporting different aspects of the CDD process. More specifically, methodology components addressing capability design, enterprise and business process modelling, context modelling, supporting reuse, as well as adjusting capability delivery at run-time have been developed. Furthermore, there is a method component supporting the decision making about whether or not CDD is suitable and how to get started. The methodology also includes method extensions for specific application domains, namely business process outsourcing, collaborative software development and project management office. The deliverable reflects the modular and incremental approach to methodology engineering and documentation in CaaS, which is manifested in the methodology components and extensions. The modularity allows for the users to focus only on those parts of the methodology that are needed for their work. The CDD methodology is described from three conceptual aspects – (1) The modelling languages in terms of concepts and notations used to represent the modelling product, i.e. the models and capability designs created. (2) The way of working, the procedures and tools used, in order to arrive at a capability design that fits organization’s needs, i.e. the modelling process. (3) The technical foundation and formal definition of algorithms for run-time adjustments of capabilities. The deliverable also includes extensive examples of capability design, context modelling and run-time adjustments. These examples are meant to support understanding and selection of the method components.
|
|
