Requirements traceability in model-driven development: Applying model and transformation conformance

The variety of design artifacts (models) produced in a model-driven design process results in an intricate relationship between requirements and the various models. This paper proposes a methodological framework that simplifies management of this relationship, which helps in assessing the quality of models, realizations and transformation specifications. Our framework is a basis for understanding requirements traceability in model-driven development, as well as for the design of tools that support requirements traceability in model-driven development processes. We propose a notion of conformance between application models which reduces the effort needed for assessment activities. We discuss how this notion of conformance can be integrated with model transformations

From trading to eCommunity management : responding to social and contractual challenges

"The increasing pressure for enterprises to join into agile business networks is changing the requirements on the enterprise computing systems. The supporting infrastructure is increasingly required to provide common facilities and societal infrastructure services to support the lifecycle of loosely-coupled, eContract-governed business networks. The required facilities include selection of those autonomously administered business services that the enterprises are prepared to provide and use, contract negotiations, and furthermore, monitoring of the contracted behaviour with potential for breach management. The essential change is in the requirement of a clear mapping between business-level concepts and the automation support for them. Our work has focused on developing B2B middleware to address the above challenges; however, the architecture is not feasible without management facilities for trust-aware decisions for entering business networks and interacting within them. This paper discusses how trust-based decisions are supported and positioned in the B2B middleware.""The increasing pressure for enterprises to join into agile business networks is changing the requirements on the enterprise computing systems. The supporting infrastructure is increasingly required to provide common facilities and societal infrastructure services to support the lifecycle of loosely-coupled, eContract-governed business networks. The required facilities include selection of those autonomously administered business services that the enterprises are prepared to provide and use, contract negotiations, and furthermore, monitoring of the contracted behaviour with potential for breach management. The essential change is in the requirement of a clear mapping between business-level concepts and the automation support for them. Our work has focused on developing B2B middleware to address the above challenges; however, the architecture is not feasible without management facilities for trust-aware decisions for entering business networks and interacting within them. This paper discusses how trust-based decisions are supported and positioned in the B2B middleware.""The increasing pressure for enterprises to join into agile business networks is changing the requirements on the enterprise computing systems. The supporting infrastructure is increasingly required to provide common facilities and societal infrastructure services to support the lifecycle of loosely-coupled, eContract-governed business networks. The required facilities include selection of those autonomously administered business services that the enterprises are prepared to provide and use, contract negotiations, and furthermore, monitoring of the contracted behaviour with potential for breach management. The essential change is in the requirement of a clear mapping between business-level concepts and the automation support for them. Our work has focused on developing B2B middleware to address the above challenges; however, the architecture is not feasible without management facilities for trust-aware decisions for entering business networks and interacting within them. This paper discusses how trust-based decisions are supported and positioned in the B2B middleware."Peer reviewe

拡張性を備えた企業アプリケーションのモデルベース設計開発手法に関する研究

指導教員：高橋　

An empirical study on the use of i* by non-technical stakeholders: the case of strategic dependency diagrams

Early phases of information systems engineering include the understanding of the enterprise’s context and the construction of models at different levels of decomposition, required to design the system architecture. These time-consuming activities are usually conducted by relatively large teams, composed of groups of non-technical stakeholders playing mostly an informative role (i.e. not involved in documentation and even less in modelling), led by few experienced technical consultants performing most of the documenting and modelling effort. This paper evaluates the ability of non-technical stakeholders to create strategic dependency diagrams written with the i* language in the design of the context model of a system architecture, and find out which difficulties they may encounter and what the quality of the models they build is. A case study involving non-technical stakeholders from 11 organizational areas in an Ecuadorian university held under the supervision and coordination of the two authors acting as consultants. The non-technical stakeholders identified the majority of the dependencies that should appear in the case study’s context model, although they experienced some difficulties in declaring the type of dependency, representing such dependencies graphically and applying the description guidelines provided in the training. Managers were observed to make more mistakes than other more operational roles. From the observations of these results, a set of methodological advices were compiled for their use in future, similar endeavours. It is concluded that non-technical stakeholders can take an active role in the construction of the context model. This conclusion is relevant for both researchers and practitioners involved in technology transfer actions with use of i*.Peer ReviewedPostprint (author's final draft

Consistency in multi-viewpoint architectural design

This thesis presents a framework that aids in preserving consistency in multi-viewpoint designs. In a multi-viewpoint design each stakeholder constructs his own design part. We call each stakeholder’s design part the view of that stakeholder. To construct his view, a stakeholder has a viewpoint. This viewpoint defines the design concepts, the notation and the tool support that the stakeholder uses. The framework presented in this thesis focuses on architectural multiviewpoint design of distributed systems. A distributed system is a system of which the parts execute on different physical system nodes. Interaction between the system parts plays an important role in such systems. An example of a distributed system is a mobile communication network. In such a network, the parts of the system execute on e.g. the mobile telephones of the clients, the desktops of the employees of the network operator and the mobile access points. Architectural design is the area of design that focuses on higher levels of abstraction in the design process. The lowest level of abstraction that we consider is the level at which the system parts correspond to parts that can be deployed on communication middleware. Using our framework, consistency is preserved through inter-viewpoint relations and consistency rules that must be specified by the stakeholders. The stakeholders use inter-viewpoint relations to specify how one view relates to another and they use consistency rules to specify what rules must at least be satisfied in a consistent design. To aid in preserving consistency, our framework defines: – a common set of basic design concepts; – pre-defined inter-viewpoint relations; – pre-defined consistency rules; – a language to represent inter-viewpoint relations and consistency rules. The basic design concepts that the framework defines have been adopted from earlier work. These concepts were developed by carefully examining the area of distributed systems design. Using our framework, viewpoint-specific design concepts must be defined as compositions or specializations of these basic concepts. Hence, the basic concepts form a common vocabulary that the different stakeholders can use to understand each other’s designs. The framework pre-defines inter-viewpoint relations that can be reused to specify how one view relates to another. The two main types of inter-viewpoint relations that it pre-defines are: refinement relations and overlap relations. Refinement relations exist between views that (partly) consider the same design concerns at different levels of abstraction. Overlap relations exist between views that (partly) consider the same design concerns at the same level of abstraction. We derived the pre-defined relations by examining existing frameworks for multi-viewpoint design and extracting frequently occurring relations between viewpoints in these frameworks. If a pre-defined inter-viewpoint relation exists between two views, this implies that certain consistency rules must be satisfied. Specifically, if two views have a refinement relation, this implies that one must preserve the system properties specified by the other. If two views have an overlap relation, this implies that the two views must be equivalent with respect to the overlap that they have. Our framework pre-defines consistency rules that can be re-used to verify these properties. We define an architecture for tool-support to aid in specifying view relations and consistency rules and to check whether the specified consistency rules hold. The architecture contains the pre-defined relations and consistency rules, such that they can be re-used. As a case study for the framework we define adapted versions of the RM-ODP enterprise, computational and information viewpoints, using our framework. We define the concepts from these viewpoints as compositions of the basic concepts. Also, we define the relations between views from these viewpoints, as well as the corresponding consistency rules, using the relations and consistency rules that are pre-defined by the framework. The results of the case study support the claim that our framework aids in preserving consistency in multi-viewpoint designs