The Experts below are selected from a list of 24 Experts worldwide ranked by ideXlab platform
Hong Mei - One of the best experts on this subject based on the ideXlab platform.
-
Quality Attribute Scenario based architectural modeling for self adaptation supported by architecture based reflective middleware
Asia-Pacific Software Engineering Conference, 2004Co-Authors: Yali Zhu, Gang Huang, Hong MeiAbstract:Reflective middleware is proposed for guaranteeing desired qualities of middleware based systems which reside in the extremely open and dynamic Internet. Current researches and practices focus on how to monitor and change the whole system through reflective mechanisms provided by middleware. However, they put little attention on why, when and what to monitor and change because it is very hard for middleware to collect enough knowledge which is usually specific to the whole system. Being an important artifact in software development, software architecture records plentiful design information, especially the considerations for Quality Attributes of the target system. It is a natural idea to provide reflective middleware with enough knowledge via software architecture. This paper presents a demonstration of the idea. In this demonstration, the self-adaptations can be analyzed in a Quality Attribute Scenario based way and specified by an extended architecture description language. Such knowledge prescribed at the design phase can be used directly by an architecture based reflective middleware which then automatically adapts itself at runtime.
-
APSEC - Quality Attribute Scenario based architectural modeling for self-adaptation supported by architecture-based reflective middleware
11th Asia-Pacific Software Engineering Conference, 1Co-Authors: Yali Zhu, Gang Huang, Hong MeiAbstract:Reflective middleware is proposed for guaranteeing desired qualities of middleware based systems which reside in the extremely open and dynamic Internet. Current researches and practices focus on how to monitor and change the whole system through reflective mechanisms provided by middleware. However, they put little attention on why, when and what to monitor and change because it is very hard for middleware to collect enough knowledge which is usually specific to the whole system. Being an important artifact in software development, software architecture records plentiful design information, especially the considerations for Quality Attributes of the target system. It is a natural idea to provide reflective middleware with enough knowledge via software architecture. This paper presents a demonstration of the idea. In this demonstration, the self-adaptations can be analyzed in a Quality Attribute Scenario based way and specified by an extended architecture description language. Such knowledge prescribed at the design phase can be used directly by an architecture based reflective middleware which then automatically adapts itself at runtime.
Yali Zhu - One of the best experts on this subject based on the ideXlab platform.
-
Quality Attribute Scenario based architectural modeling for self adaptation supported by architecture based reflective middleware
Asia-Pacific Software Engineering Conference, 2004Co-Authors: Yali Zhu, Gang Huang, Hong MeiAbstract:Reflective middleware is proposed for guaranteeing desired qualities of middleware based systems which reside in the extremely open and dynamic Internet. Current researches and practices focus on how to monitor and change the whole system through reflective mechanisms provided by middleware. However, they put little attention on why, when and what to monitor and change because it is very hard for middleware to collect enough knowledge which is usually specific to the whole system. Being an important artifact in software development, software architecture records plentiful design information, especially the considerations for Quality Attributes of the target system. It is a natural idea to provide reflective middleware with enough knowledge via software architecture. This paper presents a demonstration of the idea. In this demonstration, the self-adaptations can be analyzed in a Quality Attribute Scenario based way and specified by an extended architecture description language. Such knowledge prescribed at the design phase can be used directly by an architecture based reflective middleware which then automatically adapts itself at runtime.
-
APSEC - Quality Attribute Scenario based architectural modeling for self-adaptation supported by architecture-based reflective middleware
11th Asia-Pacific Software Engineering Conference, 1Co-Authors: Yali Zhu, Gang Huang, Hong MeiAbstract:Reflective middleware is proposed for guaranteeing desired qualities of middleware based systems which reside in the extremely open and dynamic Internet. Current researches and practices focus on how to monitor and change the whole system through reflective mechanisms provided by middleware. However, they put little attention on why, when and what to monitor and change because it is very hard for middleware to collect enough knowledge which is usually specific to the whole system. Being an important artifact in software development, software architecture records plentiful design information, especially the considerations for Quality Attributes of the target system. It is a natural idea to provide reflective middleware with enough knowledge via software architecture. This paper presents a demonstration of the idea. In this demonstration, the self-adaptations can be analyzed in a Quality Attribute Scenario based way and specified by an extended architecture description language. Such knowledge prescribed at the design phase can be used directly by an architecture based reflective middleware which then automatically adapts itself at runtime.
Gang Huang - One of the best experts on this subject based on the ideXlab platform.
-
Quality Attribute Scenario based architectural modeling for self adaptation supported by architecture based reflective middleware
Asia-Pacific Software Engineering Conference, 2004Co-Authors: Yali Zhu, Gang Huang, Hong MeiAbstract:Reflective middleware is proposed for guaranteeing desired qualities of middleware based systems which reside in the extremely open and dynamic Internet. Current researches and practices focus on how to monitor and change the whole system through reflective mechanisms provided by middleware. However, they put little attention on why, when and what to monitor and change because it is very hard for middleware to collect enough knowledge which is usually specific to the whole system. Being an important artifact in software development, software architecture records plentiful design information, especially the considerations for Quality Attributes of the target system. It is a natural idea to provide reflective middleware with enough knowledge via software architecture. This paper presents a demonstration of the idea. In this demonstration, the self-adaptations can be analyzed in a Quality Attribute Scenario based way and specified by an extended architecture description language. Such knowledge prescribed at the design phase can be used directly by an architecture based reflective middleware which then automatically adapts itself at runtime.
-
APSEC - Quality Attribute Scenario based architectural modeling for self-adaptation supported by architecture-based reflective middleware
11th Asia-Pacific Software Engineering Conference, 1Co-Authors: Yali Zhu, Gang Huang, Hong MeiAbstract:Reflective middleware is proposed for guaranteeing desired qualities of middleware based systems which reside in the extremely open and dynamic Internet. Current researches and practices focus on how to monitor and change the whole system through reflective mechanisms provided by middleware. However, they put little attention on why, when and what to monitor and change because it is very hard for middleware to collect enough knowledge which is usually specific to the whole system. Being an important artifact in software development, software architecture records plentiful design information, especially the considerations for Quality Attributes of the target system. It is a natural idea to provide reflective middleware with enough knowledge via software architecture. This paper presents a demonstration of the idea. In this demonstration, the self-adaptations can be analyzed in a Quality Attribute Scenario based way and specified by an extended architecture description language. Such knowledge prescribed at the design phase can be used directly by an architecture based reflective middleware which then automatically adapts itself at runtime.
Wouter Joosen - One of the best experts on this subject based on the ideXlab platform.
-
TwinPeaks@ICSE - On the role of early architectural assumptions in Quality Attribute Scenarios: a qualitative and quantitative study
2015 IEEE ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture, 2015Co-Authors: Dimitri Van Landuyt, Wouter JoosenAbstract:Architectural assumptions are fundamentally different from architectural decisions because they can not be traced directly to requirements, nor to domain, technical or environmental constraints; they represent conditions under which the designed solution is expected to be valid. Early architectural assumptions are similar in nature, with the key difference that they are not made during architectural design but during requirement elicitation, not by the software architect (a solution-oriented stakeholder), but by the requirements engineer (a problem-oriented stakeholder). They represent initial assumptions about the system's architecture, and allow the requirements engineer to be more precise in documenting the requirements of the system. The role of early architectural assumptions in the current practice of Quality Attribute Scenario elicitation and related development activities in the transition to architecture is unknown and under-investigated. In this paper, we present the results of an exploratory study that focuses on the role and nature of these assumptions in the early development stages. We studied a reasonably large set of Quality Attribute Scenarios for a realistic industrial case, a smart metering system. Our study (i) confirms that Quality Attribute Scenario elicitation in practice does rely heavily on early architectural assumptions, and (ii) shows that they do influence the perceived Quality of the requirements body as a whole, in some cases positively, in other cases negatively. These findings provide empirical arguments in favor of making such assumptions explicit already during the requirements elicitation activities. Especially in the context of iterative software development methodologies such as the Twin Peaks model, a well-defined and -documented set of assumptions could smoothen the transition between successive development iterations.
-
WICSA/ECSA - Documenting Early Architectural Assumptions in Scenario-Based Requirements
2012 Joint Working IEEE IFIP Conference on Software Architecture and European Conference on Software Architecture, 2012Co-Authors: Dimitri Van Landuyt, Eddy Truyen, Wouter JoosenAbstract:In Scenario-based requirement elicitation techniques such as Quality Attribute Scenario elicitation and use case engineering, the requirements engineer is typically forced to make some implicit early architectural assumptions. These architectural assumptions represent initial architectural elements such as supposed building blocks of the envisaged system. Such implicitly specified assumptions are prone to ambiguity, vagueness, duplication, and contradiction. Furthermore, they are typically scattered across and tangled within the different Scenario-based requirements. This lack of modularity hinders navigability of the requirement body as a whole. This paper discusses the need to explicitly document otherwise implicit architectural assumptions. Such an explicit intermediary between Quality Attribute Scenarios and use cases enables the derivation and exploration of interrelations between these different requirements. This is essential to lower the mental effort required to navigate these models and facilitates a number of essential activities in the early development phases such as the selection of candidate drivers in Attribute-driven design, architectural trade-off analysis and architectural change impact analysis.
Dimitri Van Landuyt - One of the best experts on this subject based on the ideXlab platform.
-
TwinPeaks@ICSE - On the role of early architectural assumptions in Quality Attribute Scenarios: a qualitative and quantitative study
2015 IEEE ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture, 2015Co-Authors: Dimitri Van Landuyt, Wouter JoosenAbstract:Architectural assumptions are fundamentally different from architectural decisions because they can not be traced directly to requirements, nor to domain, technical or environmental constraints; they represent conditions under which the designed solution is expected to be valid. Early architectural assumptions are similar in nature, with the key difference that they are not made during architectural design but during requirement elicitation, not by the software architect (a solution-oriented stakeholder), but by the requirements engineer (a problem-oriented stakeholder). They represent initial assumptions about the system's architecture, and allow the requirements engineer to be more precise in documenting the requirements of the system. The role of early architectural assumptions in the current practice of Quality Attribute Scenario elicitation and related development activities in the transition to architecture is unknown and under-investigated. In this paper, we present the results of an exploratory study that focuses on the role and nature of these assumptions in the early development stages. We studied a reasonably large set of Quality Attribute Scenarios for a realistic industrial case, a smart metering system. Our study (i) confirms that Quality Attribute Scenario elicitation in practice does rely heavily on early architectural assumptions, and (ii) shows that they do influence the perceived Quality of the requirements body as a whole, in some cases positively, in other cases negatively. These findings provide empirical arguments in favor of making such assumptions explicit already during the requirements elicitation activities. Especially in the context of iterative software development methodologies such as the Twin Peaks model, a well-defined and -documented set of assumptions could smoothen the transition between successive development iterations.
-
WICSA/ECSA - Documenting Early Architectural Assumptions in Scenario-Based Requirements
2012 Joint Working IEEE IFIP Conference on Software Architecture and European Conference on Software Architecture, 2012Co-Authors: Dimitri Van Landuyt, Eddy Truyen, Wouter JoosenAbstract:In Scenario-based requirement elicitation techniques such as Quality Attribute Scenario elicitation and use case engineering, the requirements engineer is typically forced to make some implicit early architectural assumptions. These architectural assumptions represent initial architectural elements such as supposed building blocks of the envisaged system. Such implicitly specified assumptions are prone to ambiguity, vagueness, duplication, and contradiction. Furthermore, they are typically scattered across and tangled within the different Scenario-based requirements. This lack of modularity hinders navigability of the requirement body as a whole. This paper discusses the need to explicitly document otherwise implicit architectural assumptions. Such an explicit intermediary between Quality Attribute Scenarios and use cases enables the derivation and exploration of interrelations between these different requirements. This is essential to lower the mental effort required to navigate these models and facilitates a number of essential activities in the early development phases such as the selection of candidate drivers in Attribute-driven design, architectural trade-off analysis and architectural change impact analysis.
