Integration ist eine fortwährende Aufgabe in betrieblichen Informationssystemen. Durch den Einsatz verschiedener personeller und maschineller Aufgabenträger kommt es zu wiederkehrenden Integrationsproblemen, die vorrangig durch externe Dienstleister gelöst werden. Das zentrale Problem dieser Arbeit ist, dass in der Wissenschaft diskutiertes Lösungswissen in Form von Mustern existiert, aber keinen Eingang in die Praxis findet. Um dieses Problem zu untersuchen, wurde eine qualitative empirische Untersuchung durchgeführt, welche erstmals im deutschsprachigen Raum Wirkungszusammenhänge und Entscheidungsmechanismen in Integrationsprojekten analysiert. Als Ergebnis der qualitativen Erhebung kann festgehalten werden, dass dem Dienstleistungscharakter der Integration bisher zu wenig Beachtung geschenkt wurde und dass Integrationsmuster nicht eingesetzt werden, weil der Abstraktionsgrad des so konservierten Lösungswissens nicht zum Abstraktionsgrad der Problemstellungen passt. Deshalb definiert die Arbeit zunächst ein Dienstleistungsmodell der Integration, welches sich auf die empirische Untersuchung stützt. Danach wird auf der Grundla-ge einer eigenschaftsbasierten Definition von Integrationsmustern eine Grundmenge an Mustern aus der Literatur extrahiert, die weiter abstrahiert werden. Als Abstraktionsprinzipien werden die Klassifikation und die Generalisierung eingesetzt. Abstrakte Integrationsmuster können als Ressourcen in ein Dienstleistungsmodell eingehen. Für die Klassifikation wurde ein erweiterbares und flexibles Klassifikationsverfahren – die Facettenklassifikation – gewählt. Diese ermöglicht jederzeit das Hinzufügen weiterer Facetten. Die Einordnung eines Musters muss nur innerhalb einer Facette disjunkt sein, es kann aber in andere Facetten eingeordnet werden. Die verwendeten Facetten entstammen sowohl dem Problem als auch dem Lösungsbereich. Jeder Facette liegt eine umfassende Analyse zugrunde. Die Klassifikation bildet den Ausgangspunkt der erneuten Generalisierung. Muster mit ähnlichen bzw. identischen Ausprägungen werden erfasst und auf ein gemeinsames Konzept untersucht. Diese Generalisierung wurde exemplarisch für zwei Mustergruppen durchgeführt. Dabei wurden die beiden abstrakten Integrationsmuster „zusätzlicher Zugriffspunkt“ sowie „Vermittler“ identifiziert. Die entwickelten Konzepte flossen in eine umfangreiche Evaluation ein, welche am Beispiel einer konkreten Dienstleistung im Bereich der E-Procurement-Integration durchgeführt wurde. Die Unabhängigkeit der Bewertung konnte dadurch sichergestellt werden, dass weder der Dienstleister noch der Kunde an der zuvor durchgeführten empirischen Untersuchung beteiligt waren. Der erarbeitete Lösungsvorschlag wurde in einer Laborumgebung implementiert. Das vollständige Integrationsszenario ist dabei auf der Basis einer Virtualisierungsumgebung realitätsnah nachgebildet worden. Neben Instanzen der Kundensysteme mit identischem Versions- und Patch-Stand kamen auch Datenbestände aus Produktivsystemen zum Einsatz. Die Integrationshilfsmittel wurden ebenfalls in der Laborumgebung eingerichtet. Durch abstrakte Integrationsmuster verbessert sich die Dienstleistungserbringung. Auf der Kundenseite bewirkt dies eine Verbesserungen der Integrations- und Unternehmensarchitektur sowie die Erschließung weiteren Verbesserungspotenzials. Für den Dienstleister ergibt sich neben einem veränderten Dienstleistungsmodell vor allem die Möglichkeit, einmalige Angebote in ein konfigurierbares Standarddienstleistungsangebot zu überführen. Zusätzlich kann eine verbesserte Ressourcennutzung (vor allem der Humanressourcen) anhand des veränderten Dienstleistungsmodells nachgewiesen werden. Im Rahmen der Arbeit konnte so ein Ansatz entwickelt werden, der die empirisch belegten Abstraktionsprobleme behebt und die Einsetzbarkeit von bestehendem Lösungswissen verbessert. Gleichzeitig werden die Wirkungsmechanismen und Entscheidungszusammenhänge durch das Dienstleistungsmodell besser erfass-, erklär- und vor allem planbar.

The problem addressed in this study was the lack of understanding about failures of government leadership in accomplishing complex information technology (IT) projects and the ways such failures can negatively affect organizational performance. The purpose was to query subject matter experts and leaders with the intent to identify methods to reduce complex IT project failure rates in government organizations. This qualitative study drew on the technology acceptance model and the capability maturity model integration framework to evaluate organizations' abilities to manage complex IT projects. The research questions focused on exploring senior managers' experiences, the tacit knowledge of project management methodologies, and IT governance frameworks. The Delphi method was suitable for collecting and analyzing opinions of subject matter experts to help reach group consensus. Qualitative data analysis was used to identify themes, categories, and subcategories for thematic analysis. The result of the study was the identification of critical success factors and leadership attributes to increase the success rate of complex IT projects in federal agencies. This research may be beneficial to federal government program leaders who, as the result of increased insights and knowledge, can more effectively provide online government services using technology-enabled end-users' computing devices in a cost-effective and secure method.

Designing and developing complex engineering systems is a collaborative effort. In Model-Based Systems Engineering (MBSE), this collaboration is supported through the use of formal, computer-interpretable models, allowing stakeholders to address concerns using well-defined modeling languages. However, because concerns cannot be separated completely, implicit relationships and dependencies among the various models describing a system are unavoidable. Given that models are typically co-evolved and only weakly integrated, inconsistencies in the agglomeration of the information and knowledge encoded in the various models are frequently observed. The challenge is to identify such inconsistencies in an automated fashion. In this research, a probabilistic (Bayesian) approach to abductive reasoning about the existence of specific types of inconsistencies and, in the process, semantic overlaps (relationships and dependencies) in sets of heterogeneous models is presented. A prior belief about the manifestation of a particular type of inconsistency is updated with evidence, which is collected by extracting specific features from the models by means of pattern matching. Inference results are then utilized to improve future predictions by means of automated learning. The effectiveness and efficiency of the approach is evaluated through a theoretical complexity analysis of the underlying algorithms, and through application to a case study. Insights gained from the experiments conducted, as well as the results from a comparison to the state-of-the-art have demonstrated that the proposed method is a significant improvement over the status quo of inconsistency identification in MBSE.

傳統的資產負債管理(Asset-Liability Management，ALM)研究大多強調數量分析方法，並未考慮資料來源的問題。然而在銀行實務上，資產負債管理人員卻必須根據現有內外部資料來釐定資產負債組合的整体政策。在決策支援系統中，模式整合的功能包含模式之組合及連結等，可用以整合數量分析模式與相關資料。本研究運用人工智慧技術來探討資產負債管理中模式整合之問題。藉此可以明瞭ALM的分析流程，以作為銀行人員訓練之參考。另一方面由於應用黑板架構發展系統，也可以提供一個有彈性的整合環境，以反應使用者需求及資料異動狀況，亦可彈性新增、刪除及修改模式整合過程中的資料結構與知識內涵，以為未來連接理論技巧與實務環境之參考。 / The computer support for Asset Liability Management (ALM) in the literature emphasizes on the mathematical analysis and does not address the data source problems. In the practical banking environment, however, ALM decisions are made based on the dynamic internal and external data changes. Therefore, an ideal ALM decision support system has to consider the integration of data sources and mathematical analysis. Traditional Decision Support Systems (DSS) rely on the expert's assistance to understand the problem and formulate or integrate appropriate models. There is a growing recognition that incorporates Artificial Intelligence techniques (Al) into the DSS can enhance the acceptance of these decision aids by management. 　　This paper intends to develop an Intelligent Decision Support System (TDSS) and addresses the model integration concept for the ALM. In the paper, model integration is defined as a series of processes from which important decision making information is inferred through automatic data model mapping and mathematical model conversion. The investigation of model integration concept helps the ALM analysis process understanding which can be useful for baaldng personnel training. On the other hand, the IDSS provides a flexible integration environment in which the system can flexibly response to the user's analysis request with the updated data situations. Since the blackboard architecture used for the system development supports the modularization structure, its inherent maintainability aLows a flexible update of the domain knowledge and data structure, and can therefore serve as a testbed to evaluate the potential integration approaches of various ALM data and mathematical models.

In this research, it was mainly aimed to develop an acceptance model for processes, namely the process acceptance model (PAM). For this purpose, a questionnaire, comprising 3-part and 81-question, was developed to collect quantitative and qualitative data from people having relationships with certain process-focused models and/or standards (CMMI, ISO 15504, ISO 9001, ISO 27001, AQAP-160, AQAP-2110, and/or AS 9100). To revise and refine the questionnaire, expert reviews were ensured, and a pilot study was conducted with 60 usable responses. After reviews, refinements and piloting, the questionnaire was deployed to collect data and in-total 368 usable responses were collected from the people. Here, collected data were screened concerning incorrectly entered data, missing data, outliers and normality, and reliability and validity of the questionnaire were ensured. Partial least squares structural equation modeling (PLS SEM) was applied to develop the PAM. In this context, exploratory and confirmatory factor analyses were applied, and the initial model was estimated and evaluated. The initial model was modified as required by PLS SEM, and confirmatory factor analysis was repeated, and the modified final model was estimated and evaluated. Consequently, the PAM, with 18 factors and their statistically significant relationships, was developed. Furthermore, descriptive statistics and t-tests were applied to discover some interesting, meaningful, and important points to be taken into account regarding the acceptance of processes. Moreover, collected quantitative data were analyzed, and three additional factors were discovered regarding the acceptance of processes. Besides, a checklist to test and/or promote the acceptance of processes was established.

The need for information systems has increased to a point where virtually all business environments require some sort of software to aid in its daily operations. This study will address the need for quality information systems by examining techniques which can potentially aid in producing consistent high-quality information systems. Two techniques in particular, namely Process Maturity Models (PMMs) and Systems Development Methodologies (SDMs) are examined. Process Maturity Models such as the Capability Maturity Model Integration (CMMI) as well as the ISO-9000 standards aid in standardising and improving an organisation’s information systems development processes. These Process Maturity Models often require either the use of certain Systems Development Methodologies or at the very least techniques used within some Systems Development Methodologies. Systems Development Methodologies refer to a set of development processes, tools, techniques etc. which can be used during software development to standardise the entire development process by offering the use of modelling techniques, tools to analyse requirements, illustration of processes etc. These techniques differ from one Systems Development Methodology to the next. This study aims to identify the relationship between Process Maturity Models and Systems Development Methodologies. During the research process a questionnaire was sent out to people within the information technology business environment. The questionnaire contained questions used to determine and measure the usage of Systems Development Methodologies and how projects were affected. The questionnaire was also used to do an informal assessment of each respondent’s Capability Maturity Model level. Furthermore the data retrieved was statistically analysed and the results were interpreted. The results indicate that a relationship exists between the use of SDMs and the success of the respondent’s development processes and developed products. A total of 73% of respondents indicated that they do use SDMs to some extent, the most common being the Systems Development Lifecycle (SDLC). The majority of organizations implementing SDMs have been doing so for three years or more. Results also show that most of the respondents are not certified in some formal Process Maturity Model; however, they do implement some of the processes required by models such as the CMMI. An informal assessment performed indicated that 65% of respondents can be grouped into a perceived CMMI level 2 category. Project outcome was measured and the relationship between PMM implementation as well as SDM use was measured. Results show no statistical evidence which indicates that an organisation’s perceived CMMI level is influenced by SDM use, both vertically and horizontally. Results do, however, indicate that organizations which have been implementing SDMs for a longer period of time are more likely to apply CMMI level 4 activities. Results also indicate that the horizontal use (number of projects/people which implement SDM knowledge) of SDMs have a significant effect on the development process- and the developed product success. Lastly the results indicated that organizations which satisfy more of the CMMI’s level 4 activities experience a higher quality development process which leads to a more successful development process. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2013.

The need for information systems has increased to a point where virtually all business environments require some sort of software to aid in its daily operations. This study will address the need for quality information systems by examining techniques which can potentially aid in producing consistent high-quality information systems. Two techniques in particular, namely Process Maturity Models (PMMs) and Systems Development Methodologies (SDMs) are examined. Process Maturity Models such as the Capability Maturity Model Integration (CMMI) as well as the ISO-9000 standards aid in standardising and improving an organisation’s information systems development processes. These Process Maturity Models often require either the use of certain Systems Development Methodologies or at the very least techniques used within some Systems Development Methodologies. Systems Development Methodologies refer to a set of development processes, tools, techniques etc. which can be used during software development to standardise the entire development process by offering the use of modelling techniques, tools to analyse requirements, illustration of processes etc. These techniques differ from one Systems Development Methodology to the next. This study aims to identify the relationship between Process Maturity Models and Systems Development Methodologies. During the research process a questionnaire was sent out to people within the information technology business environment. The questionnaire contained questions used to determine and measure the usage of Systems Development Methodologies and how projects were affected. The questionnaire was also used to do an informal assessment of each respondent’s Capability Maturity Model level. Furthermore the data retrieved was statistically analysed and the results were interpreted. The results indicate that a relationship exists between the use of SDMs and the success of the respondent’s development processes and developed products. A total of 73% of respondents indicated that they do use SDMs to some extent, the most common being the Systems Development Lifecycle (SDLC). The majority of organizations implementing SDMs have been doing so for three years or more. Results also show that most of the respondents are not certified in some formal Process Maturity Model; however, they do implement some of the processes required by models such as the CMMI. An informal assessment performed indicated that 65% of respondents can be grouped into a perceived CMMI level 2 category. Project outcome was measured and the relationship between PMM implementation as well as SDM use was measured. Results show no statistical evidence which indicates that an organisation’s perceived CMMI level is influenced by SDM use, both vertically and horizontally. Results do, however, indicate that organizations which have been implementing SDMs for a longer period of time are more likely to apply CMMI level 4 activities. Results also indicate that the horizontal use (number of projects/people which implement SDM knowledge) of SDMs have a significant effect on the development process- and the developed product success. Lastly the results indicated that organizations which satisfy more of the CMMI’s level 4 activities experience a higher quality development process which leads to a more successful development process. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2013.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho. / This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.