The Experts below are selected from a list of 250389 Experts worldwide ranked by ideXlab platform
Mehmet Aksit - One of the best experts on this subject based on the ideXlab platform.
-
Software Architecture reliability analysis using failure scenarios
Journal of Systems and Software, 2008Co-Authors: Bedir Tekinerdogan, Hasan Sozer, Mehmet AksitAbstract:With the increasing size and complexity of Software in embedded systems, Software has now become a primary threat for the reliability. Several mature conventional reliability engineering techniques exist in literature but traditionally these have primarily addressed failures in hardware components and usually assume the availability of a running system. Software Architecture analysis methods aim to analyze the quality of Software-intensive system early at the Software Architecture design level and before a system is implemented. We propose a Software Architecture Reliability Analysis Approach (SARAH) that benefits from mature reliability engineering techniques and scenario-based Software Architecture analysis to provide an early Software reliability analysis at the Architecture design level. SARAH defines the notion of failure scenario model that is based on the Failure Modes and Effects Analysis method (FMEA) in the reliability engineering domain. The failure scenario model is applied to represent so-called failure scenarios that are utilized to derive fault tree sets (FTS). Fault tree sets are utilized to provide a severity analysis for the overall Software Architecture and the individual architectural elements. Despite conventional reliability analysis techniques which prioritize failures based on criteria such as safety concerns, in SARAH failure scenarios are prioritized based on severity from the end-user perspective. SARAH results in a failure analysis report that can be utilized to identify architectural tactics for improving the reliability of the Software Architecture. The approach is illustrated using an industrial case for analyzing reliability of the Software Architecture of the next release of a Digital TV.
-
Software Architecture reliability analysis using failure scenarios
IEEE IFIP International Conference on Software Architecture, 2005Co-Authors: Bedir Tekinerdogan, Hasan Sozer, Mehmet AksitAbstract:We propose a Software Architecture Reliability Analysis (SARA) approach that benefits from both reliability engineering and scenario-based Software Architecture analysis to provide an early reliability analysis of the Software Architecture. SARA makes use of failure scenarios that are prioritized with respect to the user-perception in order to provide a severity analysis for the Software Architecture and the individual components.
Hans Van Vliet - One of the best experts on this subject based on the ideXlab platform.
-
decision making in Software Architecture
Journal of Systems and Software, 2016Co-Authors: Hans Van Vliet, Antony TangAbstract:Software Architecture is nowadays seen as a set of design decisions.This leads to studying decision making in Software Architecture.We outline research directions following from this paradigm shift. Traditionally, Software Architecture is seen as the result of the Software Architecture design process, the solution, usually represented by a set of components and connectors. Recently, the why of the solution, the set of design decisions made by the Software architect, is complementing or even replacing the solution-oriented definition of Software Architecture. This in turn leads to the study of the process of making these decisions. We outline some research directions that may help us understand and improve the Software Architecture design process.
-
Software Architecture knowledge management theory and practice
2009Co-Authors: Muhammad Ali Babar, Torgeir Dingsøyr, Patricia Lago, Hans Van VlietAbstract:A Software Architecture manifests the major early design decisions, which determine the systems development, deployment and evolution. Thus, making better architectural decisions is one of the large challenges in Software engineering. Software Architecture knowledge management is about capturing practical experience and translating it into generalized architectural knowledge, and using this knowledge in the communication with stakeholders during all phases of the Software lifecycle. This book presents a concise description of knowledge management in the Software Architecture discipline. It explains the importance of sound knowledge management practices for improving Software Architecture processes and products, and makes clear the role of knowledge management in Software Architecture and Software development processes. It presents many approaches that are in use in Software companies today, approaches that have been used in other domains, and approaches under development in academia. After an initial introduction by the editors, the contributions are grouped in three parts on "Architecture Knowledge Management", "Strategies and Approaches for Managing Architectural Knowledge", and "Tools and Techniques for Managing Architectural Knowledge". The presentation aims at information technology and Software engineering professionals, in particular Software architects and Software Architecture researchers. For the industrial audience, the book gives a broad and concise understanding of the importance of knowledge management for improving Software Architecture process and building capabilities in designing and evaluating better Architectures for their mission- and business-critical systems. For researchers, the book will help to understand the applications of various knowledge management approaches in an industrial setting and to identify research challenges and opportunities.
-
Software Architecture Knowledge Management - Introduction to Software Architecture and Knowledge Management
Software Architecture Knowledge Management, 2009Co-Authors: Torgeir Dingsøyr, Hans Van VlietAbstract:Designing the global structure of a Software intensive system – the Software Architecture – is a knowledge-intensive process. The knowledge produced and consumed during this process is broad and complex, and needs to be shared and reused among different stakeholders, and across different life-cycle phases. Managing architectural knowledge is the topic of this book. This introductory chapter discusses the two fields that form the underlying basis for the topic of this book: Software Architecture, and knowledge management.
-
WICSA - Software Architecture Education Session Report
5th Working IEEE IFIP Conference on Software Architecture (WICSA'05), 1Co-Authors: M. Shaw, Hans Van VlietAbstract:In the Software Architecture education session, we discussed four main issues: how to make a Software Architecture course sufficiently realistic, how to teach non-technical competencies of Software architects, the place of such a course in a university curriculum, and how to grow Software architects beyond the university. The session resulted in a first sketch of Software Architecture knowledge areas, and the extent to which these are deemed required for certain classes of Software professionals.
Bedir Tekinerdogan - One of the best experts on this subject based on the ideXlab platform.
-
Software Architecture reliability analysis using failure scenarios
Journal of Systems and Software, 2008Co-Authors: Bedir Tekinerdogan, Hasan Sozer, Mehmet AksitAbstract:With the increasing size and complexity of Software in embedded systems, Software has now become a primary threat for the reliability. Several mature conventional reliability engineering techniques exist in literature but traditionally these have primarily addressed failures in hardware components and usually assume the availability of a running system. Software Architecture analysis methods aim to analyze the quality of Software-intensive system early at the Software Architecture design level and before a system is implemented. We propose a Software Architecture Reliability Analysis Approach (SARAH) that benefits from mature reliability engineering techniques and scenario-based Software Architecture analysis to provide an early Software reliability analysis at the Architecture design level. SARAH defines the notion of failure scenario model that is based on the Failure Modes and Effects Analysis method (FMEA) in the reliability engineering domain. The failure scenario model is applied to represent so-called failure scenarios that are utilized to derive fault tree sets (FTS). Fault tree sets are utilized to provide a severity analysis for the overall Software Architecture and the individual architectural elements. Despite conventional reliability analysis techniques which prioritize failures based on criteria such as safety concerns, in SARAH failure scenarios are prioritized based on severity from the end-user perspective. SARAH results in a failure analysis report that can be utilized to identify architectural tactics for improving the reliability of the Software Architecture. The approach is illustrated using an industrial case for analyzing reliability of the Software Architecture of the next release of a Digital TV.
-
Software Architecture reliability analysis using failure scenarios
IEEE IFIP International Conference on Software Architecture, 2005Co-Authors: Bedir Tekinerdogan, Hasan Sozer, Mehmet AksitAbstract:We propose a Software Architecture Reliability Analysis (SARA) approach that benefits from both reliability engineering and scenario-based Software Architecture analysis to provide an early reliability analysis of the Software Architecture. SARA makes use of failure scenarios that are prioritized with respect to the user-perception in order to provide a severity analysis for the Software Architecture and the individual components.
Sun Chang - One of the best experts on this subject based on the ideXlab platform.
-
Overview on Software Architecture Description
Computer Science, 2003Co-Authors: Sun ChangAbstract:Recently, Software Architecture has become one focus in Software Engineering community, and a key issue to successful large-scale Software development. Software Architecture Description forms the base for architectural construction,evolution,verification,analysis,maintenance and Architecture-driven Software development. The concept related with Software Architecture Description is introduced,and Architecture Description Language and Typical Architecture Description Method are discussed in the paper. At the same time,the industrial standards for Software Architecture Description,such as IEEE P1471 and Rational RAS-ADS,is also introduced. Finally,the conclusion and envision for Software Architecture Description are present in the paper.
Marco Sandrini - One of the best experts on this subject based on the ideXlab platform.
-
Software Architecture helpdesk
Lecture Notes in Computer Science, 2004Co-Authors: Anssi Karhinen, Juha Kuusela, Marco SandriniAbstract:Software Architecture has been identified as a main tool for high quality system development. Software Architecture provides the basis for the reuse in a Software product line. Unfortunately the potential benefits of a well designed Software Architecture can be lost if the Software Architecture is not followed in the design of the products. We suggest that a Software Architecture help desk could play an important role in enabling the dissemination of Software Architecture and in improving the communication between designers and architects.
-
PFE - Software Architecture Helpdesk
Software Product-Family Engineering, 2004Co-Authors: Anssi Karhinen, Juha Kuusela, Marco SandriniAbstract:Software Architecture has been identified as a main tool for high quality system development. Software Architecture provides the basis for the reuse in a Software product line. Unfortunately the potential benefits of a well designed Software Architecture can be lost if the Software Architecture is not followed in the design of the products. We suggest that a Software Architecture help desk could play an important role in enabling the dissemination of Software Architecture and in improving the communication between designers and architects.
