Results 1 - 10
of
15
A comparative evaluation of robotic software integration systems: A case study
, 2007
"... Abstract — One might expect that after nearly 50 years of research in robot manipulation and mobile robotics the architectural design of robot systems has converged to a small set of best practice solutions, very much like in the area of operating systems, where the world is dominated by less then a ..."
Abstract
-
Cited by 13 (0 self)
- Add to MetaCart
(Show Context)
Abstract — One might expect that after nearly 50 years of research in robot manipulation and mobile robotics the architectural design of robot systems has converged to a small set of best practice solutions, very much like in the area of operating systems, where the world is dominated by less then a handful systems. Quite the opposite is the case. It is only a small overstatement to say that almost every lab has brewed its own solution for robot control architecture, middleware and software integration concepts. One reason for this situation is the fact that the complexity and variety of systems and applications has grown considerably since then leading to a diversity of approaches. Another reason is clearly the lack of any sound methodology to measures and compare architectural designs. This article tries to address the problem by proposing a comparison and evaluation methodology for robotics software systems. The methodology facilitates an assessment of software systems through experimentation and takes into account the possible operational profile and quality attribute requirements of the robotic application. The approach is validated through the evaluation of three software systems, i.e. GenoM, ORCA2 and GO. The results suggest possible applicability domains of each system and show the efficiency of the approach. I.
Sharing the architectural knowledge of quantitative analysis
- In Proceedings of the 4th International Conference on the Quality of SoftwareArchitectures (QoSA
, 2008
"... Abstract. Sharing the architectural knowledge of architectural analysis among stakeholders proves to be troublesome. This causes problems in and with architectural analysis, which can have serious consequences for the quality of a system being developed, as this quality might be incompletely or wron ..."
Abstract
-
Cited by 6 (4 self)
- Add to MetaCart
(Show Context)
Abstract. Sharing the architectural knowledge of architectural analysis among stakeholders proves to be troublesome. This causes problems in and with architectural analysis, which can have serious consequences for the quality of a system being developed, as this quality might be incompletely or wrongly assessed. This paper presents a domain model, which can be used as a common ground among analysts and architects to capture and explicitly share such knowledge. This enables a way to overcome some of the obstacles imposed by the multi-disciplinary context in which architectural analysis takes place. To apply the domain model in practice, we have created a tool implementing (part of) this domain model for capturing and using explicit architectural knowledge during analysis. We validate the tool and domain model in the context of an industrial case study. 1
Methods for Evaluating Software Architecture: A Survey
, 2008
"... Software architectural evaluation becomes a familiar practice in software engineering community for developing quality software. Architectural evaluation reduces software development effort and costs, and enhances the quality of the software by verifying the addressability of quality requirements an ..."
Abstract
-
Cited by 5 (0 self)
- Add to MetaCart
(Show Context)
Software architectural evaluation becomes a familiar practice in software engineering community for developing quality software. Architectural evaluation reduces software development effort and costs, and enhances the quality of the software by verifying the addressability of quality requirements and identifying potential risks. There have been several methods and techniques to evaluate software architectures with respect to the desired quality attributes such as maintainability, usability and performance. This paper presents a discussion on different software architectural evaluation methods and techniques using a taxonomy. The taxonomy is used to distinguish architectural evaluation methods based on the artifacts on which the methods are applied and two phases (early and late) of software life cycle. The artifacts include specification of a whole software architecture and its building blocks: software architectural styles or design patterns. The role of this paper discussion is to review different existing well known architectural evaluation
Sustainability evaluation of software architectures
- in: ACM Sigsoft Int’l Conf. on the Quality of Softw. Architectures
, 2011
"... Long-living software systems are sustainable if they can be cost-efficiently maintained and evolved over their entire life-cycle. The quality of software architectures determines sus-tainability to a large extent. Scenario-based software archi-tecture evaluation methods can support sustainability an ..."
Abstract
-
Cited by 5 (0 self)
- Add to MetaCart
(Show Context)
Long-living software systems are sustainable if they can be cost-efficiently maintained and evolved over their entire life-cycle. The quality of software architectures determines sus-tainability to a large extent. Scenario-based software archi-tecture evaluation methods can support sustainability anal-ysis, but they are still reluctantly used in practice. They are also not integrated with architecture-level metrics when evaluating implemented systems, which limits their capabil-ities. Existing literature reviews for architecture evaluation focus on scenario-based methods, but do not provide a criti-cal reflection of the applicability of such methods for sustain-ability evaluation. Our goal is to measure the sustainabil-ity of a software architecture both during early design us-ing scenarios and during evolution using scenarios and met-rics, which is highly relevant in practice. We thus provide a systematic literature review assessing scenario-based meth-ods for sustainability support and categorize more than 40 architecture-level metrics according to several design prin-ciples. Our review identifies a need for further empirical research, for the integration of existing methods, and for the more efficient use of formal architectural models. 1.
Extending the Capabilities of Component Models for Embedded Systems
"... Abstract. Component-based development helps to improve the modularity and reusability of embedded systems. Component models devised for embedded systems are typically restricted due to the limited computing, storage and power resources of the target systems. Most existing component models for embedd ..."
Abstract
-
Cited by 3 (1 self)
- Add to MetaCart
(Show Context)
Abstract. Component-based development helps to improve the modularity and reusability of embedded systems. Component models devised for embedded systems are typically restricted due to the limited computing, storage and power resources of the target systems. Most existing component models for embedded systems therefore only support a static component architecture and provide a simple and lightweight core. With the increasing demand for more feature-rich embedded systems these component architectures must be extended. In order to remain useful for the development of resource-restricted embedded systems, however, the extensions must be optional. Creating such extensions requires a cost-effective development process that can produce reusable, rather than application-specific, extensions. This necessitates a systematic approach to seamlessly integrate application specific requirements of the extension, the existing component model and the constraints of the computing environment. In this paper we propose a scenario-based architectural approach to extending the capabilities of the CAmkES component model. This approach is used to distil application specific requirements and computing constraints, summarise generic scenarios, drive the extension to the core CAmkES architecture. We illustrate our approach with a case study involving the addition of dynamic capabilities to CAmkES.
An empirical study of groupware support for distributed software architecture
, 2006
"... www.elsevier.com/locate/jss ..."
(Show Context)
A comparison framework for open source software evaluation methods
- Open Source Software: New Horizons, volume 319 of IFIP Advances in Information and Communication Technology
"... Abstract. The use of Open Source Software (OSS) components has become a viable alternative to Commercial Off-The-Shelf (COTS) components in product development. Since the quality of OSS products varies widely, both industry and the research community have reported several OSS evaluation methods that ..."
Abstract
-
Cited by 3 (3 self)
- Add to MetaCart
(Show Context)
Abstract. The use of Open Source Software (OSS) components has become a viable alternative to Commercial Off-The-Shelf (COTS) components in product development. Since the quality of OSS products varies widely, both industry and the research community have reported several OSS evaluation methods that are tailored to the specific characteristics of OSS. We have performed a system-atic identification of these methods, and present a comparison framework to compare these methods.
Keung, "Quality Assessment of Mission Critical Middleware System Using MEMS
- in International Conference on Quality Software (QSIC), Jeju, Korea
, 2009
"... Architecture evaluation methods provide general guidelines to assess quality attributes of systems, which are not necessarily straightforward to practice with. With COTS middleware based systems, this assessment process is further complicated by the complexity of middleware technology and a number o ..."
Abstract
-
Cited by 2 (2 self)
- Add to MetaCart
(Show Context)
Architecture evaluation methods provide general guidelines to assess quality attributes of systems, which are not necessarily straightforward to practice with. With COTS middleware based systems, this assessment process is further complicated by the complexity of middleware technology and a number of design and deployment options. Efficient assessment is key to produce accurate evaluation results for stakeholders to ensure good decisions are made on system acquisition. In this paper, a systematic evaluation method called MEMS is developed to provide some structure to this assessment process. MEMS produces the evaluation plan with thorough design of experiments, definition of metrics and development of techniques for measurement. This paper presents MEMS and its application to a mission critical middleware system. 1
A Statistical Method for Middleware System Architecture Evaluation
"... The architecture of complex software systems is a collection of decisions that are very expensive to change. This makes effective software architecture evaluation methods essential in today’s system development for mission critical systems. We have previously developed MEMS for evaluating middleware ..."
Abstract
-
Cited by 1 (1 self)
- Add to MetaCart
(Show Context)
The architecture of complex software systems is a collection of decisions that are very expensive to change. This makes effective software architecture evaluation methods essential in today’s system development for mission critical systems. We have previously developed MEMS for evaluating middleware architectures, which provides an effective assessment of important quality attributes and their characterizations. To provide additional quantitative assessments on the overall system performance using actual runtime data, we employed a set of statistical procedures in this work. Our proposed assessment procedures comprises a standard sensitivity analysis procedure that utilizes leverage statistics to identify and remove influential data points, and an estimator for evaluating system stability and a metric for evaluating system load capacity. Experiments were conducted using real runtime datasets. Results show that our procedures effectively identified and isolated abnormal data points, and provided valuable statistics to show system stability. Our approach thus provides a sound statistical basis to support software architecture evaluation. 1.
A framework for supporting the software architecture evaluation process in global software development
, 2009
"... Software Architecture (SA) evaluation process requires a large number of stakeholders to be collocated for evaluation sessions. Given the increasing trend of using globally distributed software development teams, organizations are likely to be discouraged from introducing disciplined architectural e ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Software Architecture (SA) evaluation process requires a large number of stakeholders to be collocated for evaluation sessions. Given the increasing trend of using globally distributed software development teams, organizations are likely to be discouraged from introducing disciplined architectural evaluation practices that require stakeholders to be collocated. To address this issue, we propose that SA evaluation can be carried out using suitable groupware systems. In this paper, we present a framework for supporting the SA evaluation process using groupware systems. The framework highlights the changes required in the existing SA evaluation processes. We provide an illustrated example of modeling and mapping the activities of the proposed process on electronic workspaces provided by a groupware system. We have also identified some of the features a groupware system should have to successfully support the process.
