The Experts below are selected from a list of 372915 Experts worldwide ranked by ideXlab platform
Rick Kazman - One of the best experts on this subject based on the ideXlab platform.
-
Scaling up software Architecture Analysis
Journal of Systems and Software, 2012Co-Authors: Rick Kazman, Michael Gagliardi, William G. WoodAbstract:This paper will show how Architecture design and Analysis techniques rest on a small number of foundational principles. We will show how those principles have been instantiated as a core set of techniques. These techniques, combined together, have resulted in several highly successful Architecture Analysis and design methods. Finally, we will show how these foundations, and the techniques that instantiate them, can be re-combined for new purposes addressing problems of ever-increasing scale, specifically: addressing the highly complex problems of analyzing software-intensive ecosystems.
-
from software Architecture Analysis to service engineering an empirical study of methodology development for enterprise soa implementation
IEEE Transactions on Services Computing, 2010Co-Authors: Hongmei Chen, Rick Kazman, Opal PerryAbstract:This paper presents an integrated service-oriented enterprise system development framework (called the BITAM-SOA Framework) as well as an instantiated design process model (called the Service Engineering Schematic) that was a result from a three-year action research case study with a Fortune 50 company in the financial services industry. The BITAM-SOA Framework and Schematic advance are both business-IT alignment and software Architecture Analysis techniques supporting the engineering of enterprise-wide service-oriented systems-that is, service engineering.
-
A Basis for Analyzing Software Architecture Analysis Methods
Software Quality Journal, 2005Co-Authors: Rick Kazman, Tony Lattanze, Mark Klein, Len Bass, Linda NorthropAbstract:A software Architecture is a key asset for any organization that builds complex software-intensive systems. Because of an Architecture's central role as a project blueprint, organizations should analyze the Architecture before committing resources to it. An Analysis helps to ensure that sound architectural decisions are made. Over the past decade a large number of Architecture Analysis methods have been created, and at least two surveys of these methods have been published. This paper examines the criteria for analyzing Architecture Analysis methods, and suggests a new set of criteria that focus on the essence of what it means to be an Architecture Analysis method. These criteria could be used to compare methods, to help understand the suitability of a method, or to improve a method. We then examine two methods—the Architecture Tradeoff Analysis Method and Architecture-level Modifiability Analysis—in light of these criteria, and provide some insight into how these methods can be improved.
-
a life cycle view of Architecture Analysis and design methods
2003Co-Authors: Rick Kazman, Robert L Nord, Mark KleinAbstract:Abstract : Many Architecture-centric Analysis and design methods have been created in the past 10 years at the Software Engineering Institute, beginning with the Software Architecture Analysis Method (SAAM). The SAAM inspired the creation of other methods, namely the Architecture Tradeoff Analysis MethodSM, the Quality Attribute Workshop, the Cost-Benefit Analysis Method, Active Reviews for Intermediate Designs, and the Attribute-Driven Design method. As these methods become more widespread, more widely adopted, and integrated into the software development life cycle, organizations inevitably will want to tailor them. Consequently, organizations that wish to include quality-attribute-based requirements, explicit Architecture design, and Architecture Analysis in their software development life cycles will be best served if they can do so "organically." The steps and artifacts of the five methods listed above, therefore, may require tailoring, blending, and, in some cases, removal when integrated into an existing life cycle. This report examines these methods and activities to understand their commonalities and relationships to life-cycle changes, and proposes a means of tailoring the activities so that they can fit more easily into existing life-cycle models.
Pontus Johnson - One of the best experts on this subject based on the ideXlab platform.
-
The Enterprise Architecture Analysis Tool for Decision-Making : a case study
2013Co-Authors: Konstantinos Pantazis, Markus Buschle, Magnus Österlind, Pontus JohnsonAbstract:In this paper a tool for Enterprise Architecture Decision-making is proposed and its usage is described. Firstly, the Enterprise Architecture Analysis Tool (EAAT), which has been developed by the Industrial Information and Control Systems (ICS) department of KTH, is described. This tool has been used during a case study at a large Nordic company in order to create present and future state models for measuring service availability. These models, which are based on a metamodel, enable us to analyze service availability and identify bottlenecks of the company’s Enterprise Architecture. Subsequently the results of the case study are presented, showcasing that the changes proposed are beneficiary for company’s Enterprise Architecture. Finally it can be concluded that the case study validated that the tool is very helpful in decision making for Enterprise Architecture, but, nevertheless, some improvement suggestions are proposed.
-
Architecture Analysis of enterprise systems modifiability: a metamodel for software change cost estimation
Software Quality Journal, 2010Co-Authors: Robert Lagerström, Pontus Johnson, Mathias EkstedtAbstract:Enterprise Architecture models can be used in order to increase the general understanding of enterprise systems and specifically to perform various kinds of Analysis. The present paper proposes a metamodel for enterprise systems modifiability Analysis, i.e. assessing the cost of making changes to enterprise-wide systems. The enterprise Architecture metamodel is formalized using probabilistic relational models, which enables the combination of regular entity-relationship modeling aspects with means to perform enterprise Architecture Analysis. The content of the presented metamodel is validated based on survey and workshop data and its estimation capability is tested with data from 21 software change projects. To illustrate the applicability of the metamodel an instantiated architectural model based on a software change project conducted at a large Nordic transportation company is detailed.
-
Architecture Analysis of enterprise systems modifiability models Analysis and validation
Ubiquitous Computing, 2010Co-Authors: Robert Lagerström, Pontus Johnson, David HookAbstract:Enterprise Architecture (EA) models can be used in order to increase the general understanding of enterprise systems and to perform various kinds of Analysis. This paper presents instantiated architectural models based on a metamodel for enterprise systems modifiability Analysis, i.e. for assessing the cost of making changes to enterprise-wide systems. The instantiated architectural models detailed are based on 21 software change projects conducted at four large Nordic companies. Probabilistic relational models (PRMs) are used for formalizing the EA Analysis approach. PRMs enable the combination of regular entity-relationship modeling aspects with means to perform enterprise Architecture Analysis under uncertainty. The modifiability metamodel employed in the Analysis is validated with survey and workshop data (in total 110 experts were surveyed) and with the data collected in the 21 software change projects. Validation indicates that the modifiability metamodel contains the appropriate set of elements. It also indicates that the metamodel produces estimates within a 75% accuracy in 87% of the time and has a mean accuracy of 88% (when considering projects of 2000 man-hours or more).
-
Education in Enterprise Architecture Analysis : Assessing interoperability of service oriented Architectures
2009Co-Authors: Johan Ullberg, Pontus Johnson, Robert LagerströmAbstract:Education in Enterprise Architecture Analysis : Assessing interoperability of service oriented Architectures
-
CSMR - A Tool for Enterprise Architecture Analysis of Maintainability
2009 13th European Conference on Software Maintenance and Reengineering, 2009Co-Authors: Mathias Ekstedt, Robert Lagerström, Johan Ullberg, Teodor Sommestad, Pontus Johnson, Ulrik Franke, Markus BuschleAbstract:A tool for Enterprise Architecture Analysis using a probabilistic mathematical framework is demonstrated. The Model-View-Controller tool Architecture is outlined, before the use of the tool is considered. A sample abstract maintainability model is created, showing the dependence of system maintainability on documentation quality, developer expertise, etc. Finally, a concrete model of an ERP system is discussed.
Peter H Feiler - One of the best experts on this subject based on the ideXlab platform.
-
What’s New in V2 of the Architecture Analysis & Design Language Standard?
2018Co-Authors: Peter H Feiler, Joe Seibel, Lutz WrageAbstract:This report provides an overview of changes and improvements to the Architecture Analysis & Design Language (AADL) standard for describing both the software Architecture and the execution platform Architectures of performance-critical, embedded, real-time systems. The standard was initially defined in the document SAE AS-5506 and published in November 2004 by SAE International (formerly the Society of Automotive Engineers). SAE International published the revised language, known as AADL V2, in January 2009. Feedback from users of the standard guided the plan for improvements. Their experience and suggestions resulted in the addition of component categories to better represent protocols as logical entities (virtual bus), scheduler hierarchies and logical time partitions (virtual processor), and a generic component (abstract). The revisions also led to the abilities to (1) explicitly parameterize component declarations to better express Architecture patterns, (2) specify multiple instances of the same component in one declaration (component array) and corresponding connection patterns, (3) set visibility rules for packages and property sets that access other packages and property sets, (4) specify system-level mode transitions more precisely, and (5) use additional property capabilities including property value records.
-
model based engineering with aadl an introduction to the sae Architecture Analysis design language
2012Co-Authors: Peter H Feiler, David P GluchAbstract:Conventional build-then-test practices are making todays embedded, software-reliant systems unaffordable to build. In response, more than thirty leading industrial organizations have joined SAE (formerly, the Society of Automotive Engineers) to define the SAE Architecture Analysis & Design Language (AADL) AS-5506 Standard, a rigorous and extensible foundation for model-based engineering Analysis practices that encompass software system design, integration, and assurance. Using AADL, you can conduct lightweight and rigorous analyses of critical real-time factors such as performance, dependability, security, and data integrity. You can integrate additional established and custom Analysis/specification techniques into your engineering environment, developing a fully unified Architecture model that makes it easier to build reliable systems that meet customer expectations. Model-Based Engineering with AADL is the first guide to using this new international standard to optimize your development processes. Coauthored by Peter H. Feiler, the standards author and technical lead, this introductory reference and tutorial is ideal for self-directed learning or classroom instruction, and is an excellent reference for practitioners, including architects, developers, integrators, validators, certifiers, first-level technical leaders, and project managers. Packed with real-world examples, it introduces all aspects of the AADL notation as part of an Architecture-centric, model-based engineering approach to discovering embedded software systems problems earlier, when they cost less to solve. Throughout, the authors compare AADL to other modeling notations and approaches, while presenting the language via a complete case study: the development and Analysis of a realistic example system through repeated refinement and Analysis. Part One introduces both the AADL language and core Model-Based Engineering (MBE) practices, explaining basic software systems modeling and Analysis in the context of an example system, and offering practical guidelines for effectively applying AADL. Part Two describes the characteristics of each AADL element, including their representations, applicability, and constraints. The Appendix includes comprehensive listings of AADL language elements, properties incorporated in the AADL standard, and a description of the books example system.
-
What's New in V2 of the Architecture Analysis & Design Language Standard?
2012Co-Authors: Peter H Feiler, Joseph Seibel, Lutz WrageAbstract:Abstract : This report provides an overview of changes and improvements to the Architecture Analysis & Design Language (AADL) standard for describing both the software Architecture and the execution platform Architectures of performance-critical, embedded, real-time systems. The standard was initially defined in the document SAE AS-5506 and published in November 2004 by SAE International (formerly the Society of Automotive Engineers). SAE International published the revised language, known as AADL V2, in January 2009. Feedback from users of the standard guided the plan for improvements. Their experience and suggestions resulted in the addition of component categories to better represent protocols as logical entities (virtual bus), scheduler hierarchies and logical time partitions (virtual processor), and a generic component (abstract). The revisions also led to the abilities to (1) explicitly parameterize component declarations to better express Architecture patterns, (2) specify multiple instances of the same component in one declaration (component array) and corresponding connection patterns, (3) set visibility rules for packages and property sets that access other packages and property sets, (4) specify system-level mode transitions more precisely, and (5) use additional property capabilities including property value records.
-
model based software quality assurance with the Architecture Analysis and design language
AIAA Infotech@Aerospace Conference, 2009Co-Authors: Peter H Feiler, David P Gluch, Kathryn Anne Weiss, Kurt WoodhamAbstract:Model-based software quality assurance (MB-SQA) provides a rigorous framework for the verification and validation of software systems through the systematic modeling and Analysis of formal Architecture representations. This paper describes the results of applying an MB-SQA practice framework that utilizes the Architecture Analysis and Design Language (AADL) to JPL’s Mission Data System (MDS) reference Architecture. The MDS is a unified reference Architecture for space mission flight, ground, and test systems. In the case study, the AADL assurance practice framework and several AADL-based analyses were applied to the evaluation of critical quality attributes of the MDS reference Architecture as well as an MDS adaptation for the control of a heated camera. The results of the case study demonstrate the utility of the practice framework and the AADL-based analyses in addressing (1) the modeling of key MDS architectural themes and (2) quality assurance with respect to performance, particularly flow latency.
-
dependability modeling with the Architecture Analysis design language aadl
2007Co-Authors: Peter H Feiler, Ana RuginaAbstract:Abstract : The Society for Automotive Engineers (SAE) recently published an Error Model Annex document (SAE AS-5506/1) to complement the SAE Architecture Analysis & Design Language (AADL) standard document (SAE AS5506) with capabilities for dependability modeling. The purpose of this report is to: (1) explain the capabilities of the Error Model Annex and (2) provide guidance on the use of the AADL and the error model in modeling dependability aspects of embedded system Architectures. The focus of the guidance is the creation of error model libraries and the instantiation of these error models on AADL Architecture models. In that context, the report discusses modeling of error propagation, error filtering and masking, the interactions between error models and systems with operational modes, and modeling of repair activities.
Mathias Ekstedt - One of the best experts on this subject based on the ideXlab platform.
-
Architecture Analysis of enterprise systems modifiability: a metamodel for software change cost estimation
Software Quality Journal, 2010Co-Authors: Robert Lagerström, Pontus Johnson, Mathias EkstedtAbstract:Enterprise Architecture models can be used in order to increase the general understanding of enterprise systems and specifically to perform various kinds of Analysis. The present paper proposes a metamodel for enterprise systems modifiability Analysis, i.e. assessing the cost of making changes to enterprise-wide systems. The enterprise Architecture metamodel is formalized using probabilistic relational models, which enables the combination of regular entity-relationship modeling aspects with means to perform enterprise Architecture Analysis. The content of the presented metamodel is validated based on survey and workshop data and its estimation capability is tested with data from 21 software change projects. To illustrate the applicability of the metamodel an instantiated architectural model based on a software change project conducted at a large Nordic transportation company is detailed.
-
CSMR - A Tool for Enterprise Architecture Analysis of Maintainability
2009 13th European Conference on Software Maintenance and Reengineering, 2009Co-Authors: Mathias Ekstedt, Robert Lagerström, Johan Ullberg, Teodor Sommestad, Pontus Johnson, Ulrik Franke, Markus BuschleAbstract:A tool for Enterprise Architecture Analysis using a probabilistic mathematical framework is demonstrated. The Model-View-Controller tool Architecture is outlined, before the use of the tool is considered. A sample abstract maintainability model is created, showing the dependence of system maintainability on documentation quality, developer expertise, etc. Finally, a concrete model of an ERP system is discussed.
-
EDOC - Enterprise Architecture Analysis for Data Accuracy Assessments
2009 IEEE International Enterprise Distributed Object Computing Conference, 2009Co-Authors: Per Närman, Mathias Ekstedt, Pontus Johnson, Moustafa Chenine, Johan KonigAbstract:Poor data in information systems impede the quality of decision-making in many modern organizations. Manual business process activities and application services are never executed flawlessly which results in steadily deteriorating data accuracy, the further away from the source the data gets, the poorer its accuracy becomes. This paper proposes an Architecture Analysis method based on Bayesian Networks to assess data accuracy deterioration in a quantitative manner. The method is model-based and uses the ArchiMate language to model business processes and the way in which data objects are transformed by various operations. A case study at a Swedish utility demonstrates the approach.
-
ICSOC Workshops - Assessing System Availability Using an Enterprise Architecture Analysis Approach
Service-Oriented Computing – ICSOC 2007, 2009Co-Authors: Jakob Raderius, Per Närman, Mathias EkstedtAbstract:During the last decade, a model based technique known as enterprise Architecture has grown into an established approach for management of information systems in organizations. The use of enterprise Architecture primarily promotes good decision-making and communication between business and IT stakeholders. This paper visualizes a scenario where enterprise Architecture models are utilized to evaluate the availability of an information system. The problem is approached by creating models based on metamodels tailored to the domain of enterprise Architecture Analysis. As the instantiated models are fed with data particular to the information system, one can deduce how the organization needs to act in order to improve the system's availability.
Robert Lagerström - One of the best experts on this subject based on the ideXlab platform.
-
Architecture Analysis of enterprise systems modifiability: a metamodel for software change cost estimation
Software Quality Journal, 2010Co-Authors: Robert Lagerström, Pontus Johnson, Mathias EkstedtAbstract:Enterprise Architecture models can be used in order to increase the general understanding of enterprise systems and specifically to perform various kinds of Analysis. The present paper proposes a metamodel for enterprise systems modifiability Analysis, i.e. assessing the cost of making changes to enterprise-wide systems. The enterprise Architecture metamodel is formalized using probabilistic relational models, which enables the combination of regular entity-relationship modeling aspects with means to perform enterprise Architecture Analysis. The content of the presented metamodel is validated based on survey and workshop data and its estimation capability is tested with data from 21 software change projects. To illustrate the applicability of the metamodel an instantiated architectural model based on a software change project conducted at a large Nordic transportation company is detailed.
-
Architecture Analysis of enterprise systems modifiability models Analysis and validation
Ubiquitous Computing, 2010Co-Authors: Robert Lagerström, Pontus Johnson, David HookAbstract:Enterprise Architecture (EA) models can be used in order to increase the general understanding of enterprise systems and to perform various kinds of Analysis. This paper presents instantiated architectural models based on a metamodel for enterprise systems modifiability Analysis, i.e. for assessing the cost of making changes to enterprise-wide systems. The instantiated architectural models detailed are based on 21 software change projects conducted at four large Nordic companies. Probabilistic relational models (PRMs) are used for formalizing the EA Analysis approach. PRMs enable the combination of regular entity-relationship modeling aspects with means to perform enterprise Architecture Analysis under uncertainty. The modifiability metamodel employed in the Analysis is validated with survey and workshop data (in total 110 experts were surveyed) and with the data collected in the 21 software change projects. Validation indicates that the modifiability metamodel contains the appropriate set of elements. It also indicates that the metamodel produces estimates within a 75% accuracy in 87% of the time and has a mean accuracy of 88% (when considering projects of 2000 man-hours or more).
-
CAiSE Forum - A Tool for Enterprise Architecture Analysis Using the PRM Formalism
Progress in Pattern Recognition Image Analysis Computer Vision and Applications, 2010Co-Authors: Markus Buschle, Robert Lagerström, Johan Ullberg, Ulrik Franke, Teodor SommestadAbstract:Enterprise Architecture advocates for model-based decision-making on enterprise-wide information system issues. In order to provide decision-making support, enterprise Architecture models should not only be descriptive but also enable Analysis. This paper presents a software tool, currently under development, for the evaluation of enterprise Architecture models. In particular, the paper focuses on how to encode scientific theories so that they can be used for model-based Analysis and reasoning under uncertainty. The tool Architecture is described, and a case study shows how the tool supports the process of enterprise Architecture Analysis.
-
Education in Enterprise Architecture Analysis : Assessing interoperability of service oriented Architectures
2009Co-Authors: Johan Ullberg, Pontus Johnson, Robert LagerströmAbstract:Education in Enterprise Architecture Analysis : Assessing interoperability of service oriented Architectures
-
CSMR - A Tool for Enterprise Architecture Analysis of Maintainability
2009 13th European Conference on Software Maintenance and Reengineering, 2009Co-Authors: Mathias Ekstedt, Robert Lagerström, Johan Ullberg, Teodor Sommestad, Pontus Johnson, Ulrik Franke, Markus BuschleAbstract:A tool for Enterprise Architecture Analysis using a probabilistic mathematical framework is demonstrated. The Model-View-Controller tool Architecture is outlined, before the use of the tool is considered. A sample abstract maintainability model is created, showing the dependence of system maintainability on documentation quality, developer expertise, etc. Finally, a concrete model of an ERP system is discussed.