Das e-Business hat aufgrund der technologischen Möglichkeiten durch den kommerziellen Einsatz des Internet zahlreiche neue Geschäftsmodelle hervorgebracht. Dabei wurden zum einen bestehende Geschäftsmodelle der traditionellen Geschäftswelt auf die neuen Rahmenbedingungen des e-Business angepasst und zum anderen gänzlich neue Formen von Geschäftsmodellen erfunden. Ein Grund für das Entstehen neuer Geschäftsideen und deren Konkretisierung durch Geschäftsmodelle ist die Möglichkeit, im e-Business neue, zuvor nicht realisierbare Erlösmodelle umzusetzen. Die Erlösmodelle sind somit nicht nur ein wesentlicher Teil der Geschäftsmodelle, sondern bilden in einigen Fällen darüber hinaus das entscheidende Element einer neuartigen Geschäftsidee im e-Business. Um von einem Geschäftsmodell zu einer lauffähigen Anwendung zu gelangen, werden Softwarearchitekturen benötigt. Sie stellen den Bauplan der Softwareanwendung dar, die im e-Business als Realisierung des Geschäftsmodells interpretiert werden kann. Um die Gestaltung dieser Architekturen zu erleichtern und zu beschleunigen, können entsprechende Referenzarchitekturen als abstrakte Entwurfsvorlagen verwendet werden, sofern sie existieren. Mit der Aufstellung eines Kataloges von Software-Referenzarchitekturen für Erlösmodelle des e-Business als wesentlicher Bestandteil eines Geschäftsmodells befasst sich diese Arbeit. Dazu wird zunächst eine Klassifikation der Erlösmodelle des e-Business geliefert, die den Übergang vom fachlich orientierten Geschäftsmodell auf die zugrundeliegende technisch orientierte Softwarearchitektur unterstützt. Aufbauend auf dieser Klassifikation wird ein Katalog der Software-Referenzarchitekturen hergeleitet. Der Katalog enthält eine Sammlung von Komponenten, die gemeinsam als Bausatz der Software-Referenzarchitekturen angesehen werden können. Da die Klassifikation ein breites Spektrum potenzieller Erlösmodelle berücksichtigt, stehen mit den Referenzarchitekturen Entwurfsvorlagen für zahlreiche unterschiedliche Geschäftsmodelle zur Verfügung. Die detaillierte Granularität der Software-Referenzarchitekturen mit den aufgeführten Komponenten und Klassen kann dabei sehr gut verwendet werden, um einfacher und schneller eine konkrete Architektur abzuleiten, als wenn diese von Grund auf neu entwickelt werden müsste. Die Ergebnisse dieser Arbeit leisten einen wesentlichen Beitrag, um die Realisierung von Geschäftsmodellen des e-Business in vereinfachter und beschleunigter Form durchzuführen und unterschiedliche, daran beteiligte Personengruppen zu unterstützen.

<p>I ett samhälle där upphovsrätten och immaterialrätten blir allt mer uppmärksammad är det viktigt för företag att vara medvetna om sitt innehav av licenser för mjukvaror. I detta arbete kommer företags medvetenhet om deras licenshanteringssituation att undersökas. I den här rapporten kommer problemställningen att undersökas med hjälp av intervjuer med företag. Dessa intervjuer kommer att ske via telefon och per e-post. Ett liknande arbete har tidigare inte gjorts och därför känns det relevant samt intressant att göra denna undersökning.</p><p>Arbetet resulterade i intervjusvar från 11 företag. Det visade sig att företagens medvetenhet om deras licenshantering varierade stort, vilket även att storleken på företagen och innehav av en policy för licenshantering bland företagen gjorde. Metoden för licenshantering och licensinventering skiljde sig åt bland företagen.</p><p>Ett flertal program, tillammans med pärmar och Excel-listor var de dominerande licenshanteringsmetoderna bland företagen. Mjukvarutillverkarna och deras intresseorganisationer däribland BSA ställer krav på att företag som använder deras licensierade programvaror skall ha en strukturerad licenshantering. De ser gärna att företagen följer någon vedertagen metod för detta, en sådan metod är Software Asset Management, SAM.</p><p>Det är svårt att rekommendera någon licenshanteringsmetod och program som fungerar för samtliga företag, då användandet av dessa är väldigt företags- och organisationsspecifikt. De flesta större mjukvaror som finns i dagsläget följer en vedertagen metod för licenshantering och fungerar därmed bra att tillförlitligt inventera licenser med.</p> / <p>In a community where copyright and intellectual property law is getting more attention in the media, it is important for companies to be aware of their possession of software licenses. In this thesis we are going to investigate the awareness of the software licensing situation in some companies. To collect data that can be analyzed, we are interviewing companies. The interviews are performed by phone or e-mail. A similar report hasn’t been done before therefore it’s an interesting subject to look at.</p><p>The interviews resulted in answers from 11 companies. The answers showed that the awareness about software licensing among the companies had big variations. Some other things that varied among the companies were the size of the companies and the usage of software licensing policy within the companies. The way and method of handling software licensing also varied among the companies.</p><p>A lot of software programs, along with folders and Excel-lists dominated the method of handling software licenses among the companies. Software developing companies together with their interest organization for example BSA has demands on companies using their software to have a foreseeable documentation for the software licenses. They gladly see that the companies uses a best practice method to manage their license possessions, one best practice method is Software Asset Management, SAM.</p><p>It is hard to recommend a method for software license management to a non-specific company, because every company has a unique organization and computer network structure. Most of the big license management software is following a best practice method for software license management.</p>

I ett samhälle där upphovsrätten och immaterialrätten blir allt mer uppmärksammad är det viktigt för företag att vara medvetna om sitt innehav av licenser för mjukvaror. I detta arbete kommer företags medvetenhet om deras licenshanteringssituation att undersökas. I den här rapporten kommer problemställningen att undersökas med hjälp av intervjuer med företag. Dessa intervjuer kommer att ske via telefon och per e-post. Ett liknande arbete har tidigare inte gjorts och därför känns det relevant samt intressant att göra denna undersökning. Arbetet resulterade i intervjusvar från 11 företag. Det visade sig att företagens medvetenhet om deras licenshantering varierade stort, vilket även att storleken på företagen och innehav av en policy för licenshantering bland företagen gjorde. Metoden för licenshantering och licensinventering skiljde sig åt bland företagen. Ett flertal program, tillammans med pärmar och Excel-listor var de dominerande licenshanteringsmetoderna bland företagen. Mjukvarutillverkarna och deras intresseorganisationer däribland BSA ställer krav på att företag som använder deras licensierade programvaror skall ha en strukturerad licenshantering. De ser gärna att företagen följer någon vedertagen metod för detta, en sådan metod är Software Asset Management, SAM. Det är svårt att rekommendera någon licenshanteringsmetod och program som fungerar för samtliga företag, då användandet av dessa är väldigt företags- och organisationsspecifikt. De flesta större mjukvaror som finns i dagsläget följer en vedertagen metod för licenshantering och fungerar därmed bra att tillförlitligt inventera licenser med. / In a community where copyright and intellectual property law is getting more attention in the media, it is important for companies to be aware of their possession of software licenses. In this thesis we are going to investigate the awareness of the software licensing situation in some companies. To collect data that can be analyzed, we are interviewing companies. The interviews are performed by phone or e-mail. A similar report hasn’t been done before therefore it’s an interesting subject to look at. The interviews resulted in answers from 11 companies. The answers showed that the awareness about software licensing among the companies had big variations. Some other things that varied among the companies were the size of the companies and the usage of software licensing policy within the companies. The way and method of handling software licensing also varied among the companies. A lot of software programs, along with folders and Excel-lists dominated the method of handling software licenses among the companies. Software developing companies together with their interest organization for example BSA has demands on companies using their software to have a foreseeable documentation for the software licenses. They gladly see that the companies uses a best practice method to manage their license possessions, one best practice method is Software Asset Management, SAM. It is hard to recommend a method for software license management to a non-specific company, because every company has a unique organization and computer network structure. Most of the big license management software is following a best practice method for software license management.

Im Projekt TransBS wurden existierende, über viele Jahre gewachsene Softwaresysteme zur Realisierung von Geschäftsprozessen betrachtet, in denen Aspekte wie Verteiltheit, Anpassbarkeit an heterogene Plattformen oder Skalierbarkeit zunehmend Bedeutung erlangen. Die notwendigen Anpassungen der Systeme sind nur schwierig und mit erheblichem Aufwand zu realisieren, da sie eine vollständige Reorganisation erfordern. Deshalb wurde im Projekt eine Methodik entwickelt und prototypisch realisiert, die monolithische Legacy-Business-Softwaresysteme in eine komponentenbasierte, verteilte Client-Server-Architektur mit konfigurierbaren Workflows für heterogene Plattformen schrittweise überführt. Die entwickelten Werkzeuge zur Transformation wurden exemplarisch mit einem gegebenen Softwaresystem evaluiert und können für weitere Problemstellungen der Analyse und Transformation von Business-Software eingesetzt werden.

The data generated from the user's activities and surfing online can have a significant impact when used to improve the content of web pages. The user has little time to scan the content of a web page and the motivation to save time is high. Recommendations and personalized content are becoming more and more common and both businesses and consumers seem to benefit from more targeted content. In order to know what recommendations to present to each individual, information about the user is needed and there are many tools to analyze the behaviours of the users online. In this study, we examined if relevant content on the front-page of Visma, a business software provider, can increase the interaction on the front-page and what metrics can be used to measure the interaction. Together with experts in the field we investigated the eAccounting software users’ preferences for targeted recommendations. By having a pop up survey for users of Visma, conducting an A/B test and using a heatmap for the eAccounting users we found out that a more customized front-page makes the user interact more with the page.

面對商場日益競爭激烈及服務型態的翻新迅速，通路革命已使流通業者的結構產生劇幅的改變。業者對營業資訊的需求增加，上下游、連鎖經營店間的資料傳輸日漸綿密，再加上企業為了市場競爭，其經營模式或組織需要非常靈活的彈性調整，使得資訊系統的開發與運用重要性日增，其維護上的負擔也日益沉重。在軟體技術方面，由於物件導向技術的成熟，資訊系統開發人員也戮力於導入此技術。然而現今之電腦軟體技術愈來愈複雜，對品質的要求也不斷地提昇，資訊系統開發生命週期在市場的變化下愈來愈短，這些現象都使軟體元件的角色加重。為要達到品質與生產力的雙重要求，軟體元件的再使用與配套的軟體發展程序是一個關鍵成功因素。本研究運用方法論 (Methodology)、概念形成 (Concept Formulation) 與雛型發展(Prototype) 三種研究方式，結合物件導向技術及軟體元件觀念相輔相成的軟體發展塑模方式，建構一套以使用個案及企業元件為主軸、軟體架構為中心的軟體元件發展程序，以期強化軟體再使用度及維護度，減低開發的時程及成本，並建立一個流通業訂單資訊系統的雛型，產生相關的企業軟體元件及開發程序，用以說明本研究所提概念的運用方式。 / Due to the rigorous competition and the rapid change of service type, the channel revolution has huge impact on the business structure of channel service providers. Because of the increased information requirement in business operating, frequent communication between channels and dynamic business model with changing organization structure intensify the importance of flexibility and maintainability of information systems development and usage. On the other hand, object-oriented technology has been adopted wildly by information systems developers. However, due to the incurred complexity in software technology, the requests on higher software quality and shorter life cycle make the focus shift to software component technology gradually. To meet the expectation in both software quality and productivity, the reusability in software components and the related development process will be the critical factor in success. In this thesis, we introduce a modeling process in terms of object-oriented technology d software component concepts, such as use case, business component and software architecture. The proposed process should potentially increase the software reusability and maintenance, as well as reduce the developing schedule and cost. A prototype for order processing is also built to illustrate the process and the involved concepts.

An innovation is the process of making improvements by introducing new idea in the form of product or service. In recent years, successful societies are shifting their focus towards the realization and acceptance of these new ideas. Plug and Play business software platform is the first step to transform these ideas into reality. The study presented in this thesis introduced that a new business idea contains specific business role and consists of a set of capabilities or needs and any one of them. Plug and play business software platform mainly consists of three major business processes that are required to run this platform those are; business match making process, negotiating process and collaboration process. This study analyzes the process of business match making in detail and introduce an ontology based business match making process which will find new businesses in a hierarchical fashion based on their specific business roles. Match making ontology consists of three processes i.e. information collection process which is used to collect and register information, extraction process which is an optional process to extract set of capabilities and needs if actor/innovator is unable to define its business capabilities and needs in information collection process and finally finding and ranking process which will find a set of potential collaborators and then will rank that set based on ranking parameters collected in information collection process from actor/innovator. This study also presents a technological model which will provide foundation to develop plug and play business software platform. This model identifies business processes of the platform and presents each business process as a separate loosely coupled software module. This model divides the platform into two layers; the upper layer is called PnP layer and consists of PnP Client Service, PnP Community Service, Finding and Ranking Service, Negotiating Service and Collaboration Service; lower layer is called kernel layer and consists of Security management Service, Operational management Services and Communication Service. Finally partially implemented prototype, test data and results will be used to visualize the presented concept.

This master thesis deals with the analysis of information system and selected processes linked to the information system. It contains teoretical foundations of the selected problem, analysis and information system assessment and proposes several changes in order to make the information system and processes more efficient.

Im Projekt TransBS wurden existierende, über viele Jahre gewachsene Softwaresysteme zur Realisierung von Geschäftsprozessen betrachtet, in denen Aspekte wie Verteiltheit, Anpassbarkeit an heterogene Plattformen oder Skalierbarkeit zunehmend Bedeutung erlangen. Die notwendigen Anpassungen der Systeme sind nur schwierig und mit erheblichem Aufwand zu realisieren, da sie eine vollständige Reorganisation erfordern. Deshalb wurde im Projekt eine Methodik entwickelt und prototypisch realisiert, die monolithische Legacy-Business-Softwaresysteme in eine komponentenbasierte, verteilte Client-Server-Architektur mit konfigurierbaren Workflows für heterogene Plattformen schrittweise überführt. Die entwickelten Werkzeuge zur Transformation wurden exemplarisch mit einem gegebenen Softwaresystem evaluiert und können für weitere Problemstellungen der Analyse und Transformation von Business-Software eingesetzt werden.

A certificação CERTICS foi desenvolvida para ser um instrumento de política pública que busca contribuir para o desenvolvimento nacional sustentável e pode apoiar as empresas nacionais de software na evolução necessária para se tornarem mais competitivas frente aos softwares estrangeiros. No entanto, esta certificação, assim como outras, requer investimento de profissionais e recursos financeiros, o que é um problema notadamente nas pequenas empresas de software. Este trabalho tem o objetivo de apresentar o GARREC, Guia para Atendimento dos Requisitos dos Resultados Esperados da CERTICS, que é uma ferramenta desenvolvida para apoiar no processo da certificação CERTICS, atuando em complemento à documentação existente. O GARREC foi construído visando facilitar o entendimento dos conceitos da CERTICS e no atendimento dos resultados esperados por meio de proposição de evidências, considerando cenários de pequenas empresas. Assim, o GARREC contribuirá para reduzir o investimento necessário para a certificação. O método de pesquisa adotado envolveu a análise do Modelo de Referência para Avaliação da CERTICS e o detalhamento dos Requisitos Específicos dos seus Resultados Esperados e, para estes foram propostas evidências para atendimento classificadas por relevância. Desta forma, todos os aspectos avaliados são considerados, garantindo qualidade de cobertura do atendimento aos requisitos da certificação. Para a avaliação do GARREC foi realizado um experimento no qual os participantes o utilizaram para atender a resultados esperados predeterminados e responderam a uma pesquisa. Participaram do experimento três empresas com diferentes níveis de conhecimento da CERTICS, uma empresa certificada, uma em processo de certificação e uma sem conhecimento anterior. A partir dos resultados coletados da pesquisa de avaliação, o GARREC atinge os seus objetivos de auxiliar no entendimento e no atendimento dos requisitos da certificação CERTICS, com 91,3% de aceitação aos itens de efetividade e 97,5% referente aos itens de aplicabilidade. Uma validação mais ampla em campo ainda se faz necessária para uma avaliação mais consistente da ferramenta. / The CERTICS certification was developed to be a public policy tool that seeks to contribute to sustainable national development and it can support national software companies in the evolution required to become more competitive compared to the foreign software. However, this certification, as well as others, requires professional investment and financial resources, which is usually a problem for small software companies. This work aims to present GARREC, Guide for Meeting the Requirements of Results Expected from CERTICS, which is a tool developed to support the understanding and obtaining of the CERTICS certification, working in addition to the existing documentation. GARREC was built to facilitate the understanding of the CERTICS’ concepts and in meeting the expected results through evidence proposition considering small business scenarios.Therefore, GARREC will contribute to reducing the investment required for certification. The research method involved the analysis of the Reference Model for Evaluation of CERTICS and detailing of the Specific Requirements of its Expected Results, and for these, evidence was presented to meet them, classified by relevance. In this way all evaluated aspects are considered, guaranteeing quality of coverage of the attendance to the certification requirements. For the GARREC evaluation, an experiment was carried out in which the participants used it to meet predetermined expected results and answered to a survey. Three companies with different levels of knowledge of CERTICS, a certified company, one in the process of certification and one without previous knowledge participated in the experiment. Based on the results of the evaluation survey, GARREC achieves its objectives of assisting in the understanding and fulfillment of CERTICS certification requirements, with 91.3% acceptance of the items referring to Effectiveness and, 97.5% acceptance of the related items Applicability. Further validation in the field is still necessary for a more consistent evaluation of the tool.