2011
DOI: 10.1007/978-3-642-22056-2_29
|View full text |Cite
|
Sign up to set email alerts
|

Tool Integration beyond Wasserman

Abstract: Abstr act. The typical development environment today consists of many specialized development tools, which are partially integrated, forming a complex tool landscape with partial integration. Traditional approaches for reasoning about tool integration are insufficient to measure the degree of integration and integration optimality in today's complex tool landscape. This paper presents a reference model that introduces dependencies between, and metrics for, integration aspects to overcome this problem. This mod… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
4
1
1

Relationship

3
3

Authors

Journals

citations
Cited by 8 publications
(5 citation statements)
references
References 14 publications
0
5
0
Order By: Relevance
“…Some sources add to the denition by including user interface sophistication Stavridou, 1999) or interaction paradigms . Others entirely reject the view that the goal of presentation integration is always to produce a uniform user interface (Wong, 1999;Tilley, 2000;Asplund et al, 2011). These instead argue that the focus should be changed to the integration of the dierent users to the tools via their user interfaces.…”
Section: Presentation Integrationmentioning
confidence: 99%
“…Some sources add to the denition by including user interface sophistication Stavridou, 1999) or interaction paradigms . Others entirely reject the view that the goal of presentation integration is always to produce a uniform user interface (Wong, 1999;Tilley, 2000;Asplund et al, 2011). These instead argue that the focus should be changed to the integration of the dierent users to the tools via their user interfaces.…”
Section: Presentation Integrationmentioning
confidence: 99%
“…Dealing with MVM is complex, with (i) multiple types of contextual settings in terms of processes and legacy, (ii) multiple heterogeneous viewpoints and views , (iii) multiple types of relations among views, and (iv) multiple ways of dealing with such relations. Supporting them in a multi-tool environment will require addressing all classical tool integration aspects [61,8,17]. Derived challenges for MVM include that of designing such systems, dealing with legacy systems, and in supporting automation for such systems, while ensuring that the above mentioned challenges are properly handled.…”
Section: Challenges Of MV Modelingmentioning
confidence: 99%
“…STPA defines generic risks for inadequate control or enforcement of safety constraints that can lead to hazards. We first translated these generic risks into risks associated with tool integration by use of a reference model for tool integration that takes tool integration related to platform, control, data, presentation and process into account (the details of this reference model are given in [16]). The risks associated with these aspects of tool integration were then further translated into programmatic risks (i.e.…”
Section: From Characteristics To Safety Goalsmentioning
confidence: 99%
“…They both allow (1) a stronger focus on the relevant parts of tool chains in regard to safety and (2) ) and extra efforts to ensure safety goals relevant to tool integration. They also have the additional benefits of allowing comparisons between different setups for mitigating safety issues already after step 2 (giving an early indication of the effort required) and favoring early planning in regard to the development environment (helping to avoid fragmentation of the development environment into several islands of automation [16]). …”
Section: Fully Composable Safety Goals For Operator Supportmentioning
confidence: 99%