Rick Kazman
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Research Interests
Rick Kazman has a total of 39 co-authors. Here are the top co-authors by number of shared publications:
Mark Klein
7 shared publications- Len Bass
Software Engineering Institute/Carnegie Mellon University
3 shared publications - Hong-Mei Chen
University of Hawaii TU Eindhoven
2 shared publications - Len Bass
Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213, USA
2 shared publications - Mark Klein
Software Engineering Institute, Carnegie Mellon University, Pittsburgh, USA
2 shared publications - Paul Clements
Software Engineering Institute/Carnegie Mellon University
2 shared publications
Latest Publications
- 16 June 2015
- Published by Springer Nature
- p. 207-219
Empowering End-Users to Collaboratively Structure Processes for Knowledge Work
- 16 June 2015
- Published by Springer Nature
- p. 207-219
Empowering End-Users to Collaboratively Structure Processes for Knowledge Work
- 2 April 2011
- Published by Elsevier in Journal of Systems and Software
- Vol. 85 (7) , 1511-1519
Scaling up software architecture analysis
- 2 April 2011
- Published by Elsevier in Journal of Systems and Software
- Vol. 85 (7) , 1511-1519
Scaling up software architecture analysis
- 18 January 2011
- Published by IGI Global Scientific Publishing
The Affective and Cognitive Impacts of Perceived Touch on Online Customers' Intention to Return in the Web-based eCRM Environment
The Affective and Cognitive Impacts of Perceived Touch on Online Customers' Intention to Return in the Web-based eCRM Environment: 10.4018/978-1-60566-652-5.ch112: Electronic Customer Relationship Management (ECRM) systems focus on a website as the interaction channel for creating a one-to-one relationship with customers
- 18 January 2011
- Published by IGI Global Scientific Publishing
The Affective and Cognitive Impacts of Perceived Touch on Online Customers' Intention to Return in the Web-based eCRM Environment
The Affective and Cognitive Impacts of Perceived Touch on Online Customers' Intention to Return in the Web-based eCRM Environment: 10.4018/978-1-60566-652-5.ch112: Electronic Customer Relationship Management (ECRM) systems focus on a website as the interaction channel for creating a one-to-one relationship with customers
- Open Access
- 10 February 2009
- Published by Springer Nature in Innovations in Systems and Software Engineering
- Vol. 5 (1) , 1-3
Introduction to special issue: model-based development methodologies
- 10 February 2009
- Published by Springer Nature in Innovations in Systems and Software Engineering
- Vol. 5 (1) , 1-3
Open AccessIntroduction to special issue: model-based development methodologies
- Open Access
- 1 December 2008
- Published by Defense Technical Information Center (DTIC)
Results of SEI Independent Research and Development Projects
The Software Engineering Institute (SEI) annually undertakes several independent research and development (IRAD) projects. These projects serve to (1) support feasibility studies investigating whether further work by the SEI would be of potential benefit and (2) support further exploratory work to determine whether there is sufficient value in eventually funding the feasibility study work as an SEI initiative Projects are chosen based on their potential to mature and/or transition software engineering practices develop information that will help in deciding whether further work is worth funding and set new directions for SEI work This report describes the IRAD projects that were conducted during fiscal year 2008 (October 2007 through September 2008).
- 1 December 2008
- Published by Defense Technical Information Center (DTIC)
Open AccessResults of SEI Independent Research and Development Projects
The Software Engineering Institute (SEI) annually undertakes several independent research and development (IRAD) projects. These projects serve to (1) support feasibility studies investigating whether further work by the SEI would be of potential benefit and (2) support further exploratory work to determine whether there is sufficient value in eventually funding the feasibility study work as an SEI initiative Projects are chosen based on their potential to mature and/or transition software engineering practices develop information that will help in deciding whether further work is worth funding and set new directions for SEI work This report describes the IRAD projects that were conducted during fiscal year 2008 (October 2007 through September 2008).
- Open Access
- 23 October 2007
- Published by Defense Technical Information Center (DTIC)
Ionospheric Monitoring and Specification Utilizing Data From the Defense Meteorological Satellite Program
Software architecture competence is the ability of an individual or organization to acquire, use, and sustain the skills and knowledge necessary to carry out software architecture-centric practices. Previous work in architecture has concentrated on its technical aspects: methods and tools for creating, analyzing, and using architecture. However, a different perspective recognizes that these activities are carried out by people working in organizations, and those people and organizations can use assistance towards consistently producing high-quality architectures. This report lays out the basic concepts of software architecture competence and describes four models for explaining, measuring, and improving the architecture competence of an individual or a software-producing organization. The models are based on the following: (1) the duties, skills, and knowledge required of a software architect or architecture organization; (2) human performance technology, an engineering approach applied to improving the competence of individuals; (3) organizational coordination, the study of how people and units in an organization share information; and (4) organizational learning, an approach to how organizations acquire, internalize, and utilize knowledge to improve their performance. The report also shows how the four models can be synergistically applied to produce an evaluation instrument to measure an organization's architecture competence.
- 23 October 2007
- Published by Defense Technical Information Center (DTIC)
Open AccessIonospheric Monitoring and Specification Utilizing Data From the Defense Meteorological Satellite Program
Software architecture competence is the ability of an individual or organization to acquire, use, and sustain the skills and knowledge necessary to carry out software architecture-centric practices. Previous work in architecture has concentrated on its technical aspects: methods and tools for creating, analyzing, and using architecture. However, a different perspective recognizes that these activities are carried out by people working in organizations, and those people and organizations can use assistance towards consistently producing high-quality architectures. This report lays out the basic concepts of software architecture competence and describes four models for explaining, measuring, and improving the architecture competence of an individual or a software-producing organization. The models are based on the following: (1) the duties, skills, and knowledge required of a software architect or architecture organization; (2) human performance technology, an engineering approach applied to improving the competence of individuals; (3) organizational coordination, the study of how people and units in an organization share information; and (4) organizational learning, an approach to how organizations acquire, internalize, and utilize knowledge to improve their performance. The report also shows how the four models can be synergistically applied to produce an evaluation instrument to measure an organization's architecture competence.
- Open Access
- 1 May 2007
- Published by Defense Technical Information Center (DTIC)
Quality-Attribute-Based Economic Valuation of Architectural Patterns
Quality attribute requirements are a driving force for software and system architecture design. Architectural patterns can be used to achieve quality attribute requirements. Consequently, architectural patterns generate value based on the present and future utility of the quality attributes they achieve. This report makes the case that architectural patterns carry economic value, in part in the form of real options, providing software architects the right, but not the obligation, to take subsequent design actions. The report shows, via a simple example, how an analysis of the options embodied within architectural patterns allows an architect or manager to make reasoned choices about the future value of design decisions, considering this value along multiple quality attribute dimensions.
- 1 May 2007
- Published by Defense Technical Information Center (DTIC)
Open AccessQuality-Attribute-Based Economic Valuation of Architectural Patterns
Quality attribute requirements are a driving force for software and system architecture design. Architectural patterns can be used to achieve quality attribute requirements. Consequently, architectural patterns generate value based on the present and future utility of the quality attributes they achieve. This report makes the case that architectural patterns carry economic value, in part in the form of real options, providing software architects the right, but not the obligation, to take subsequent design actions. The report shows, via a simple example, how an analysis of the options embodied within architectural patterns allows an architect or manager to make reasoned choices about the future value of design decisions, considering this value along multiple quality attribute dimensions.
- Open Access
- 1 April 2007
- Published by Defense Technical Information Center (DTIC)
SAAM: A Method for Analyzing the Properties of Software Architectures
While software architecture has become an increasingly important research topic in recent years, insufficient attention has been paid to methods for evaluation of these architectures. Evaluating architectures is difficult for two main reasons. First, there is no common language used to describe different architectures. Second, there is no clear way of understanding an architecture with respect to an organization's life cycle concerns--software quality concerns such as maintainability, portability, modularity, reusability and so forth. This paper addresses these shortcomings by describing three perspectives by which we can understand the description of a software architecture and then proposing a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). We illustrate the method by analyzing three separate user interface architectures with respect to the quality of modifiability.
- 1 April 2007
- Published by Defense Technical Information Center (DTIC)
Open AccessSAAM: A Method for Analyzing the Properties of Software Architectures
While software architecture has become an increasingly important research topic in recent years, insufficient attention has been paid to methods for evaluation of these architectures. Evaluating architectures is difficult for two main reasons. First, there is no common language used to describe different architectures. Second, there is no clear way of understanding an architecture with respect to an organization's life cycle concerns--software quality concerns such as maintainability, portability, modularity, reusability and so forth. This paper addresses these shortcomings by describing three perspectives by which we can understand the description of a software architecture and then proposing a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). We illustrate the method by analyzing three separate user interface architectures with respect to the quality of modifiability.
- 1 August 2006
- Published by Elsevier in Journal of Systems and Software
- Vol. 79 (8) , 1207-1216
The essential components of software architecture design and analysis
- 1 August 2006
- Published by Elsevier in Journal of Systems and Software
- Vol. 79 (8) , 1207-1216
The essential components of software architecture design and analysis
- 30 June 2006
- Published by Elsevier in Science of Computer Programming
- Vol. 61 (1) , 4-15
Interface descriptions for enterprise architecture
- 30 June 2006
- Published by Elsevier in Science of Computer Programming
- Vol. 61 (1) , 4-15
Interface descriptions for enterprise architecture