Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to main content

    Hans van Vliet

    ABSTRACT In this paper we report on four years of case study research in a large software development organization, during which we built up understanding on how to effectively support software architects in sharing knowledge. By... more
    ABSTRACT In this paper we report on four years of case study research in a large software development organization, during which we built up understanding on how to effectively support software architects in sharing knowledge. By following a typical action research cycle we first diagnosed the architecting process of this organization, after which we designed and executed a therapy for the identified problems. The insights gained over the past few years have resulted in four lessons learned and have culminated in a theoretical framework of what architects do and what they need.
    Post-mortem project reviews often yield useful lessons learned. These project reviews are mostly recorded in plain text. This makes it dicult to derive useful overall ndings from a set of such post-mortem reviews, for example to monitor... more
    Post-mortem project reviews often yield useful lessons learned. These project reviews are mostly recorded in plain text. This makes it dicult to derive useful overall ndings from a set of such post-mortem reviews, for example to monitor and guide a software process improve- ment program. We have developed a ve-step method to transform the qualitative, natural language type information present
    The SOA decision making process addresses specific concerns, which requires (its own) specific information. Currently, SOA design decisions are often documented (if at all) using generic architectural design decision models. The... more
    The SOA decision making process addresses specific concerns, which requires (its own) specific information. Currently, SOA design decisions are often documented (if at all) using generic architectural design decision models. The information that is specifically relevant to SOA design decisions remains hidden in the description of the existing entities of architectural decision models. As a result, this information could be
    Product Family Engineering is an approach to software engineering that seeks to reduce the global effort in producing multiple software products by actively governing the reuse of assets between the family members. However, Product Family... more
    Product Family Engineering is an approach to software engineering that seeks to reduce the global effort in producing multiple software products by actively governing the reuse of assets between the family members. However, Product Family Engineering is a highly knowledge intensive activity putting stringent demands careful planning and management in the organization. This paper presents a study proposal that will examine the effects of knowledge brokering among Communities of Practice as a means to assist this activity. 1.
    Research Interests:
    Research Interests:
    Design for change is a well-known adagium in software engineer- ing. We separate concerns, employ well-designed interfaces, and the like to ease evolution of the systems we build. We model and build in changeability through... more
    Design for change is a well-known adagium in software engineer- ing. We separate concerns, employ well-designed interfaces, and the like to ease evolution of the systems we build. We model and build in changeability through parameterization and variability points (as in product lines). These all concern places where we ex- plicitly consider variability in our systems. We conjecture that it is helpful to also think of and explicitly model invariability, things in our systems and their environment that we assume will not change. We give examples from the literature and our own experience to illustrate how evolution can be seriously hampered because of tacit assumptions made. In particular, we show how we can explicitly model assumptions in an existing product family. From this, we derive a metamodel to document assumptions. Finally, we show how this type of modeling adds to our understanding of the archi- tecture and the decisions that led to it.
    Research Interests:
    This document describes the Vrije Universiteit Information Technology Service Capability Maturity Model, or IT Service CMM for short. The IT Service CMM is a capability maturity model that specifies different maturity levels for... more
    This document describes the Vrije Universiteit Information Technology Service Capability Maturity Model, or IT Service CMM for short. The IT Service CMM is a capability maturity model that specifies different maturity levels for organizations that provide IT services. Examples of IT services are the maintenance of software systems, operation of information systems, the management and maintenance of workstations, networks or mainframes, or the provision of contingency services. An important...
    We discuss our experiences in using ALMA, our method for Architecture-Level Modifiability Analysis. Like many other methods for software architecture analysis, such as SAAM and ATAM, our method is scenario-based. We found that the... more
    We discuss our experiences in using ALMA, our method for Architecture-Level Modifiability Analysis. Like many other methods for software architecture analysis, such as SAAM and ATAM, our method is scenario-based. We found that the scenario elicitation process is tricky, and depends on the goal set for the analysis. Also, our experience in applying ALMA to business information systems indicates that it is important to also model the environment of the system. Data from a longitudinal study in which we collected information on the actual evolution of a system whose modifiability we analyzed earlier, provides further valuable insights into the applicability of ALMA, and points at some general limitations of this type of analysis.
    Research Interests:
    Based on interviews with a number of architects and managers from a wide range of organizations, we characterize how architecture is perceived in practice. We identify three groups of organizations that differ with respect to their level... more
    Based on interviews with a number of architects and managers from a wide range of organizations, we characterize how architecture is perceived in practice. We identify three groups of organizations that differ with respect to their level of architectural thinking and the alignment of business and IT on architectural issues. Analysis of the interviews further indicates that these three groups differ in the architecture aspects and critical success factors they emphasize. Our results provide a starting point for assessing architecture maturity and alignment within organizations, and can be used to help harmonize different architectural tunes played within organizations.
    ABSTRACT In industrial settings, multiple service teams are often involved in handling incidents, so these service teams come to depend on one another. We hypothesize that the knowledge these service teams have of the agreed upon and... more
    ABSTRACT In industrial settings, multiple service teams are often involved in handling incidents, so these service teams come to depend on one another. We hypothesize that the knowledge these service teams have of the agreed upon and realized incident handling performance of themselves and other service teams will impact their performance. We tested this hypothesis at a large financial institute, using log data from the IT service management tool and a survey to measure the knowledge of service teams. We found a significant positive correlation between incident handling performance of a service team and the knowledge a service team has of its own performance. We found no correlation between the knowledge of agreed upon performance and realized performance within a service team. Finally, we found that teams have very little knowledge of agreed upon or realized performance of other service teams. The results suggest that increasing performance visibility within and across teams is one way to help improve performance.
    ABSTRACT In large internal information technology (IT) organizations, multiple teams are often involved in handling incidents, so these teams come to depend on one another. We hypothesize that the knowledge these teams have of the agreed... more
    ABSTRACT In large internal information technology (IT) organizations, multiple teams are often involved in handling incidents, so these teams come to depend on one another. We hypothesize that the knowledge these teams have of the agreed upon and realized incident handling performance of themselves and other teams will impact their performance. We tested this hypothesis at a large financial institute, using log data from the IT service management application and a survey to measure the knowledge of teams. We found (1) a significant positive correlation between incident handling performance of a team and the knowledge a team has of its own performance; (2) no correlation between the knowledge of agreed upon performance and realized performance within a team; (3) that teams have very little knowledge of agreed upon or realized performance of other teams; and (4) that improving the knowledge a team has of the agreed upon and realized performance of that team and dependent teams results in higher incident handling performance. The results show that increasing information visibility within and across teams in large IT providers is one way to improve incident handling performance. Copyright © 2014 John Wiley & Sons, Ltd.
    Abstract. Knowledge management plays an important role in the software ar-chitecting process. Recently, this role has become more apparent by a paradigm shift that views a software architecture as the set of architectural design decisions... more
    Abstract. Knowledge management plays an important role in the software ar-chitecting process. Recently, this role has become more apparent by a paradigm shift that views a software architecture as the set of architectural design decisions it embodies. This shift has ...
    Software architecture and software architecture practices become increasingly important for information systems since they enable reasoning on the design of the system. The concept of architectural knowledge, i.e. architectural design... more
    Software architecture and software architecture practices become increasingly important for information systems since they enable reasoning on the design of the system. The concept of architectural knowledge, i.e. architectural design decisions and the resulting design, plays a pivotal role in architecture. In order to get the most out of architectural knowledge, we need insight into the ways in which architectural
    Although the benefits are well-known and undisputed, sharing architectural knowledge is not something architects automatically do. In an attempt to better understand what architects really do and what kind of support they need for sharing... more
    Although the benefits are well-known and undisputed, sharing architectural knowledge is not something architects automatically do. In an attempt to better understand what architects really do and what kind of support they need for sharing knowledge, we have conducted large-scale survey research. The results of our study indicate that architects can be characterized as rather lonesome decision makers who mainly
    ... Patricia Lago VU University Amsterdam patricia@cs.vu.nl Hans van Vliet VU University Amsterdamhans@cs.vu.nl ... 51–60. [2] J. Kotlarsky, I. Oshri, and PC van Fenema, Knowledge Processes in Globally Distributed Contexts, ser.... more
    ... Patricia Lago VU University Amsterdam patricia@cs.vu.nl Hans van Vliet VU University Amsterdamhans@cs.vu.nl ... 51–60. [2] J. Kotlarsky, I. Oshri, and PC van Fenema, Knowledge Processes in Globally Distributed Contexts, ser. Technology, Work and Globalization. ...
    Abstract In the past few years, software engineering researchers have adopted social network analysis techniques to understand collaboration patterns in global software teams. In this paper, we investigate current research in global... more
    Abstract In the past few years, software engineering researchers have adopted social network analysis techniques to understand collaboration patterns in global software teams. In this paper, we investigate current research in global software development where social network theory is used as an analysis technique. We do so through a systematic literature review where we collect and analyze previous work that adopt a social network perspective in distributed software development. We use the 3C collaboration model to classify our ...

    And 103 more