No description available.

Denna rapport beskriver arbetsgången för att utreda och ta fram ett lösningsförslag för hur en meddelandemotor skulle kunna implementeras i TeamTags delvis redan befintliga system. Små delar av implementeringen som infördes under projektet presenteras också. / This report describes the workflow to investigate and develop a solution proposal for how a messaging engine could be implemented in TeamTags partly already implemented system. Small parts of the implementation that was introduced during the project is also presented.

Social Software-Technologien finden immer stärker Einzug in den Intranets der Unternehmen. Insbesondere der Einsatz von Enterprise Wikis hat sich durchgesetzt. In diesem Paper wird untersucht, auf welche Art und Weise Enterprise Wikis eingesetzt werden können. Hierfür wird mittels der Grounded Theory-Methodik eine Untersuchung des Enterprise Wikis „TeamWeb“ der T-Systems Multimedia Solutions GmbH durchgeführt. Auf Basis einer Analyse der TeamWeb-Spaces wird eine Einsatzszenarien-Typologie konstruiert, welche die Typen „Bereichspräsentation und -kommunikation“, „Nachschlagen und Lernen“, „Projekt- und Bereichsorganisation“ und „Kollaborative Konzeption“ unterscheidet. Im Anschluss wurde die der Nutzung zugrundeliegende Motivation mit Hilfe von semi-strukturierten Gesprächen mit den Wiki-Nutzern weiterführend untersucht. Hierbei wurde festgestellt, dass die Nutzungsmotive ausschließlich egoistischer Natur sind. Diese Erkenntnis wird im Paper zu einer allgemeinen Theorie zur Nutzungsmotivation in Enterprise Wikis ausgebaut.:1. Einleitung 1.1 Problemstellung und Forschungsfragen 1.2 Das Untersuchungsobjekt 1.3 Methodik und Forschungsprozess 1.4 Stand der Forschung 2 Vorschlag einer Typologie für Wiki-Einsatzszenarien 2.1 Bereichspräsentation und Kommunikation 2.2 Nachschlagen und Lernen 2.3 Bereichs- und Projektorganisation 2.4 Kollaborative Konzeption 3 Nutzungsmotivation in Enterprise Wikis 3.1 Primat der egoistischen Nutzungsmotive 3.2 Wikipedia und die Knowledge Base 2.0 – Ausnahmeerscheinungen? 3.3 Theoretisches Modell der Nutzungsmotivation in Enterprise Wikis 4 Zusammenfassung und Ausblick 4.1 Kritische Würdigung 4.2 Potentiale für Anschlussforschung

This thesis is focused on IBM Rational Unified Process methodology, which represents complex and robust aproach to software development and software lifecycle. This methodology is well described and every step of software lifecycle is predictible. Thats the reason why is becoming used in many software development organizations. The main goal of this thesis is deep description of this methodology and creation common outputs of inception and elaboration phase of e-learning information system. IBM Rational Unified Process is called use-case driven aproach, thats the reason why is emphasized descripton of all use-cases.

IBM Rational Unified Process is a robust iterative software development methodology. The main goal of master´s thesis is to describe the aspects of this methodology and to analyze and design a fictional information system within the scope of "inception" and "elaboration" phase.

A smart contract is a recently emerging technology which enables agreement to be automatable by computers and enforceable by legal enforcement or tamper-proof execution of code. A majority of smart contracts are run on the blockchain which enables smart contract transactions without a central authority. Smart contract implementation contains several challenges which makes implementation more difficult. The problem is that organisations struggle to implement smart contracts due to the absence of documentation, standardisation, and guidelines making it difficult to know how a smart contract should be implemented. Additionally, it is unclear what capabilities and tools are required for smart contract implementation. Therefore, it is challenging for organisations to assess their own competence of smart contract implementation. This thesis aims to develop a Smart Contract Maturity Model (SCMM). The purpose of the model is to clarify the functionalities and capabilities required to implement a smart contract while also offering organisations the ability to assess the smart contract implementation competency. This improves the adoption of smart contracts. Through the help of the design science framework, the SCMM emerged from the thesis. Applying design science included explicating the problem, defining requirements, designing and developing the artefact, demonstrating and evaluating the artefact. A literature survey was used to explicate the problem and to define requirements for the maturity model. Furthermore, a case study including interviews were used to refine the requirements and to demonstrate and evaluate the SCMM. The SCMM includes maturity levels, generic goals and practices, specific goals, key processing areas and practices, tools, glossaries and smart contract examples. Inspired by the Capability Maturity model Model Integration for Development (CMMI-DEV), the maturity levels of the SCMM consisted of initial, foundation, managed, defined, quantitatively managed and optimising. The identified key processing areas were stakeholder capabilities, resources and tools, platform, contract implementation, standards, laws and terminology and security. Although there were several limitations, the SCMM contributed to the field of smart contracts by closing the gap of previous research and improving the adoption of smart contracts.