Competences of IT Architects

The field of architecture in the digital world uses a plethora of terms to refer to different kinds of architects, and recognises a confusing variety of competences that these architects are required to have. Different service providers use different terms for similar architects and even if they use the same term, they may mean something different. This makes it hard for customers to know what competences an architect can be expected to have.\ud \ud This book combines competence profiles of the NGI Platform for IT Professionals, The Open Group Architecture Framework (TOGAF), as well as a number of Dutch IT service providers in a comprehensive framework. Using this framework, the book shows that notwithstanding a large variety in terminology, there is convergence towards a common set of competence profiles. In other words, when looking beyond terminological differences by using the framework, one sees that organizations recognize similar types of architects, and that similar architects in different organisations have similar competence profiles. The framework presented in this book thus provides an instrument to position architecture services as offered by IT service providers and as used by their customers.\ud \ud The framework and the competence profiles presented in this book are the main results of the special interest group “Professionalisation” of the Netherlands Architecture Forum for the Digital World (NAF). Members of this group, as well as students of the universities of Twente and Nijmegen have contributed to the research on which this book is based

Semantic verification of Behavior Conformance

This paper introduces a formal yet practical method to verify whether the behavior design of a distributed application conforms to the behavior design of the enterprise in which the application is embedded. The method allows both enterprise architects and application architects to talk about designs in their own terms, and introduces a common set of terms as the linking pin between enterprise and application designs. The formal semantics of these common terms allows us to verify the conformance between an enterprise and its applications formally and automatically

Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

Preliminary Results in a Multi-site Empirical Study on Cross-organizational ERP Size and Effort Estimation

This paper reports on initial findings in an empirical study carried out with representatives of two ERP vendors, six ERP adopting organizations, four ERP implementation consulting companies, and two ERP research and advisory services firms. Our study’s goal was to gain understanding of the state-of-the practice in size and effort estimation of cross-organizational ERP projects. Based on key size and effort estimation challenges identified in a previously published literature survey, we explored some difficulties, fallacies and pitfalls these organizations face. We focused on collecting empirical evidence from the participating ERP market players to assess specific facts about the state-of-the-art ERP size and effort estimation practices. Our study adopted a qualitative research method based on an asynchronous online focus group

Engineering Bureaucracy: The Genesis of Formal Policies, Positions, and Structures in High-Technology Firms

[Excerpt] This article examines the impact of organizational founding conditions on several facets of bureaucratization—managerial intensity, the proliferation of specialized managerial and administrative roles, and formalization of employment relations. Analyzing information on a sample of technology start-ups in California\u27s Silicon Valley, we characterize the organizational models or blueprints espoused by founders in creating new enterprises. We find that those models and the social composition of the labor force at the time of founding had enduring effects on growth in managerial intensity (i.e., reliance on managerial and administrative specialists) over time. Our analyses thus provide compelling evidence of path dependence in the evolution of bureaucracy—even in a context in which firms face intense selection pressures—and underscore the importance of the logics of organizing that founders bring to new enterprises. We find less evidence that founding models exert persistent effects on the formalization of employment relations or on the proliferation of specialized senior management titles. Rather, consistent with neo-institutional perspectives on organizations, those superficial facets of bureaucracy appear to be shaped by the need to satisfy external gatekeepers (venture capitalists and the constituents of public corporations), as well as by exigencies of organizational scale, growth, and aging. We discuss some implications of these results for efforts to understand the varieties, determinants, and consequences of bureaucracy

The lack of design quality focus in construction: a case for examining suitable design processes

A large number of projects in UK construction now involve contractor-led design and are thus very different from the traditional approach which formed the basis of the original Royal Institute of British Architects (RIBA) Outline Plan of Work. Such integrated and contractor-led approaches support the reform agenda of the late 1990s that was introduced to tackle process inefficiency. However, within the design professions there has been concern that this resulted in buildings that were designed-down to a cost rather than designed-up to a value. An attempt to address this resulted in the formation of the Commission for Architecture and Built Environment (CABE) in 1999 and the launch, in 2003, of the Design Quality Indicator (DQI) which measures how well a building satisfies stakeholders. This paper presents the early phases of doctoral research which will examine the impact of integrated design management approaches upon Design Quality

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version