Content uploaded by Ulrike Lechner
Author content
All content in this area was uploaded by Ulrike Lechner
Content may be subject to copyright.
A preview of the PDF is not available
How Do System and Enterprise Architectures Influence Knowledge Management in Software Projects? - An Explorative Study of Six Software Projects.
Abstract
This paper covers the influence of system- and enterprise architectures on knowledge management in software development projects. The common impact of architectures is researched in the context of six case studies of medium and large sized software- and system development as well as technical and organizational consultancy companies in the military and non-military domain. Observations are collected in a wide variety of aspects and evaluated on the basis of the Probst et al. knowledge management model [PRR06].
... As EAM is a knowledge-intensive management discipline, quite some research has been done on how the chosen EA framework and tool support can support the key challenges of knowledge management. Buckl et al. [14] and Lucke et al. [15] discussed this topic on the basis of the knowledge management cycle of Probst (cf. Probst et al. [16]). ...
Adequate tool support for Enterprise Architecture (EA) and its respective management function is crucial for the success of the discipline in practice. However, currently available tools used in organizations focus on structured information neglecting the collaborative effort required for developing and planning the EA. As a result, utilization of these tools by stakeholders is often not sufficient and availability of EA products in the organization is limited. We investigate the integration of existing EA tools and Enterprise Wikis to tackle these challenges. We will describe how EA initiatives can benefit from the use and integration of an Enterprise Wiki with an existing EA tool. Main goal of our research is to increase the utilization of EA tools and enhance the availability of EA products by incorporating unstructured information content in the tools. For this purpose we analyze task characteristics that we revealed from the processes and task descriptions of the EA department of a German insurance organization and align them with technology characteristics of EA tools and Enterprise Wikis. We empirically evaluated these technology characteristics using an online survey with results from 105 organizations in previous work. We apply the technology-to-performance chain model to derive the fit between task and technology characteristics for EA management (EAM) tool support in order to evaluate our hypotheses.
Management of the enterprise architecture has become increasingly recognized as a crucial part of both business and IT management. Still, a common understanding and methodological consistency seems far from being developed. Acknowledging the significant role of research in moving the development process along, this article employs different bibliometric methods, complemented by an extensive qualitative interpretation of the research field, to provide a unique overview of the enterprise architecture literature. After answering our research questions about the collaboration via co-authorships, the intellectual structure of the research field and its most influential works, and the principal themes of research, we propose an agenda for future research based on the findings from the above analyses and their comparison to empirical insights from the literature. In particular, our study finds a considerable degree of co-authorship clustering and a positive impact of the extent of co-authorship on the diffusion of works on enterprise architecture. In addition, this article identifies three major research streams and shows that research to date has revolved around specific themes, while some of high practical relevance receive minor attention. Hence, the contribution of our study is manifold and offers support for researchers and practitioners alike.
A transparent, simple, and straightforward approach that is free from any arbitrary rank valuation is required to estimate the credit associated with the sequence of authors' names on multiauthored papers.
For most organizations, getting started may be the hardest part of
building an enterprise information technology architecture. One reason
is that people have only a hazy idea of how to use a systematic
architecting process to achieve specific goals. The entire idea of
enterprise architecting seems grand and out of reach, so they feel more
comfortable chipping away at it with patches. Unfortunately, these
patches evolve to something only slightly more sophisticated. Some
efforts never get that far. The architects get caught in a never-ending
series of analyses and end up with nothing but a long to-do list just as
the money runs out and the CEO expects to start seeing a return on
investment. The article shows how to scope the project, set up the
development team, and form a target architecture vision
It makes sense to plan the growth of your information systems. But
many attempts to create a road map start at the wrong level. Ensuring a
consistent, coherent vision to direct the evolution of the enterprise's
information systems is difficult enough with a development framework.
Without one, it's impossible. The concepts we outline are just a task
list in the work to establish an enterprise architecture, but they give
you some idea of the breadth of the job ahead of you. However, we hope
we've given you a start toward a more realistic vision of your
enterprise architecture
IEEE Standard 1471 identifies sound practices to establish a
framework and vocabulary for software architecture concepts.In 2000, the
Computer Society approved IEEE Standard 1471, which documents a
consensus on good architectural description practices. Five core
concepts and relationships provide the foundation for the approved IEEE
1471 version: every system has an architecture, but an architecture is
not a system; an architecture and an architecture description are not
the same thing; architecture standards, descriptions, and development
processes can differ and be developed separately; architecture
descriptions are inherently multiviewed; and separating the concept of
an object's view from its specification is an effective way to write
architecture description standards. IEEE 1471 focuses on both software
intensive systems and more general systems, such as information systems,
embedded systems, systems-of-systems, product lines, and product
families in which software plays a substantial role in development,
operation, or evolution
This paper describes the process of inducting theory using case studies-from specifying the research questions to reaching closure. Some features of the process, such as problem definition and construct validation, are similar to hypothesis-testing research. Others, such as within-case analysis and replication logic, are unique to the inductive, case-oriented process. Overall, the process described here is highly iterative and tightly linked to data. This research approach is especially appropriate in new topic areas. The resultant theory is often novel, testable, and empirically valid. Finally, framebreaking insights, the tests of good theory (e.g., parsimony, logical coherence), and convincing grounding in the evidence are the key criteria for evaluating this type of research.
Architekturbeschreibung vonA nwendungslandschaften: Softwarekartographie und IEEE Std 1471-2000
- Aw Ittenburg
[LMW05] JL ankes, FM atthes, and AW ittenburg. Architekturbeschreibung vonA nwendungslandschaften: Softwarekartographie und IEEE Std 1471-2000. SoftwareE ngineering,
pages 43–54, 2005.
Die Ve rwendung vonArchitectural Frameworks als Vo rgehensmodell für die System-of-Systems-Entwicklung
- Rschönbein Sleuchter
[LS06]
SLeuchter and RSchönbein. Die Ve rwendung vonArchitectural Frameworks als Vo rgehensmodell für die System-of-Systems-Entwicklung. INFORMATIK 2006. Informatik
für Menschen. Beiträgeder 36. Jahrestagung der Gesellschaft für Informatik e.V. (GI),
2006.