Under två decennier har utvecklare inom mjukvarutestning utvecklat testtekniken Modell-baseradtestning. Tekniken bygger på att man genererar testfall från en modell (tex i UML), istället föratt manuallet skriva testfall. Detta kan göra testprocessen mer effektiv, vilket leder till att merarbeten kan göras på kortare tid. Det kan också ses som en ekonomiskt fördel för företag därtestning är huvudområdet. Modell-baserad testning har goda omdömen och teorin för teknikenär väl dokumenterad i artiklar, arbeten samt böcker. Mycket tyder på att tekniken rent teoretisktär användbar i praktiken dessutom finns det väldigt lite kritik mot tekniken. Men trots alltdetta har Modell-baserad testning inte blomstrat inom IT-industrin.Syftet med detta arbete är att ta reda på vad anledningarna skulle kunna vara till att MBT intelyckats bättre inom industrin. I arbetet används tre olika MBT-verktyg för att testa och sedanjämföra om resultatet i praktiken blir som teorin beskriver tekniken. Studiens resultat pekar påatt tekniken fortfarande är omogen och många brister kring Modell-baserad testning stöts på. / For two decades, software testing developers have developed the Model-based testing technique.The technology is based on generating test cases from a model (e.g. in UML) instead of manuallywriting test cases. This can make the test process more efficient, which leads to more workcan be done in less time. It can also be seen as an economic benefit for companies where testingis the main area. Model-based testing has good reviews and the theory of the technique is welldocumented in articles, works and books. There are many indications that the technology istheoretically useful in practice, with a very few criticisms of the technology. Despite all this,Model-based testing has not expanded in the IT industry.The purpose of this study is to find out what the reasons could be to the fact that MBTdid not succeed better in the industry. In this thesis, three different MBT tools are used totest and then compare whether the result in practice becomes as the theory describes the technique.The result of the study indicates the opposite direction and many shortcomings regardingModel-based testing come across.

Organized cybercrime has no borders in cyberspace. This paper suggests a state-of-the-art architected solution for a global Automated cross-border mutual legal assistance system within Digital Forensic (AUTOMLA). The Enterprise framework with technical viewpoint enables international collaboration between sovereign countries Fusion Centers. The evaluation concludes a user interface built in React, middleware Apollo with schema support linked to graph database Neo4j. GraphQL is the preferred application protocol over REST. Fusion Centers API is deployed as federated gateways, and business functions are implemented as PaaS serverless services.  Its intuitive modeling Forensics in graphs, semantic networks enables causality and inference. All suggested elements in AUTOMLA are forming an internationally agreed collaborative platform; the solution for fast cross-border crime investigations. AUTOMLA deployed on the Internet is a subject for threats. Risks are mitigated in design guided by security frameworks. The recommended development method is agile, distributed in between autonomous teams.

The methods for creating new (To-be) models within Enterprise Architecture is very similar to those used in Human-Computer Interaction for creating new products. Since Enterprise Architecture is used on existing systems, and because of the similarities between the methods used between the fields, the research question has been formulated as follows: "What is the relationship between tacit knowledge and the utility value of an architectural model for an organisational department studied through observations with experienced users?". The study aims to show that methods for reusing/changing already existing products produces a higher utility value when developing on an existing system. Since observations could show flaws and opportunities which can otherwise be overlooked, the architecture could benefit from gaining tacit knowledge which does not show from interviews. The results show that observations overall give higher utility and the hypothesis, that the observation and interview methods give equal utility values, can be discarded. / De metoder som används för att skapa nya (To-be) modeller inom Enterprise Architecture är mycket lika de som används inom Människa-Dator Interaktion för att skapa nya produkter. Då Enterprise Architecture används på redan existerande system, och eftersom det finns likheter mellan metoderna från båda fälten, har studiens fråga formulerats som: "Vad är reltationen mellan fingertoppskänsla och ’utility value’, av en arkitekturmodell för en organisationsavdelning studerat genom observationer med erfarna användare? Studien ämnar visa att metoder för att återanvända/ändra redan existerande produkter kan ge högre ’utility values’ när man utvecklar ett redan existerande system. Då observationer kan visa på brister och möjligheter, som annars kunde ha förbisetts, kan arkitekturen dra nytta av att erhålla denna underförstådda kunskap som inte yttras via intervjuer. Resultatet visar på att observationer övergripande ger högre ’utility value’ samt att hypotesen, att observationer och intervjuer ger samma ’utility values’, kan förkastas.

The field of Enterprise Architecture (EA) emerged as an answer to the increasing complexity in managing and aligning the business-IT relationship within enterprises. Both practitioners and academics have expressed interest in the field, with a growing number of publicized works related to EA. In an attempt to provide an outlook of the current research landscape of EA, a systematic literature review was conducted. Citation data from the Scopus (Elsevier) API were automatically extracted and analyzed. By applying the Louvain method on the collected data, 8 research communities and their topic were identified: (1) Enterprise Engineering (I & II), (2) Enterprise Architecture Management, (3) Enterprise Modelling, (4) IT Architecture, (5) Enterprise Integration, (6) Digital Transformation, and (7) Smart Cities. For each community, a summarized description with sub-community graphs as well as tables (describing the top authors, articles, and affiliation countries) are presented. Lastly, a comparison of the results and the EA trends identified by Gampfer et al. are presented. / Fältet Enterprise Architecture (EA) framkom som ett svar på den ökande komplexiteten i att hantera och anpassa affärs-IT-relationen inom företag. Både utövare och akademiker har uttryckt intresse för området, då antal publicerade verk relaterade till EA fortsätter att växa. I ett försök att ge en syn på det aktuella forskningslandskapet inom EA genomfördes ett systematisk litteraturöversikt. Citeringsdata från Scopus (Elsevier) API extraherades och analyserades automatiskt. Genom att tillämpa Louvain-metoden på insamlade datan identifierades 8 forskarsamhällen och deras ämnen: (1) Enterprise Engineering (I & II), (2) Enterprise Architecture Management, (3) Enterprise Modelling, (4) IT Architecture, (5) Enterprise Integration, (6) Digital Transformation och (7) Smart Cities. För varje gemenskap gavs en sammanfattad beskrivning med undergruppsdiagram samt tabeller (över t.ex. de främsta författarna, artiklarna, och anslutningsländerna). Slutligen så gjordes en jämförelse av resultaten och de EA trender som identifierats av Gampfer et al.

Тема магистерской диссертации: Организация системы сбора входящих потоков информации на производственном предприятии. Магистерская диссертация выполнена на 74 страницах, содержит 1 таблицу, 36 рисунка, 61 использованных источников. Актуальность темы обусловлена растущим количеством информации в организации, в том числе информации о клиентах, которую необходимо обрабатывать, систематизировать, и хранить, а обработка информации является очень трудоемким процессом для сотрудников, которые работают с клиентами. Целью работы является разработка архитектуры информации и методологии систематизации обработки клиентской информации на предприятии. Задачами работы являются:  изучение теоретических вопросов предмета работы;  сбор данных об объекте и разработка модели архитектуры информации;  написание методологии;  обоснование эффективности. Объектом написания выпускной квалификационной работы был выбран «Бобровский Экспериментальный Завод». Предметом выпускной квалификационной работы является система обработки входящей информации от клиента в организации. В первой главе освещается проблематика обработки информации на крупных предприятиях, имеющих автоматизации по отделам. Так же рассматривается теория архитектуры информации. Во второй главе проведана работа над выявлением узких мест в процессе обработки информации. Разработана концептуальная модель архитектуры информации, показаны возможности развития информационной системы на основе архитектуры информации. Третья глава посвящена изучению предприятия. В главе описана полная модель предприятия, показан основной процесс сбора информации. Создана модель информации, как она есть. Результаты работы: практическим результатом работы стала разработанная концепция модели архитектуры информации, интеграция двух систем, 1С и Битрикс24, а также частично внедрение полностью автоматической обработки клиентской информации из таких источников как сайт, и портал SuplBiz. / Theme of the master's thesis: The organization of the collection of incoming information flows at a manufacturing enterprise. The master's thesis is executed on 74 pages, contains 1 table, 36 figures, 61 sources used. The relevance of the topic is due to the growing amount of information in the organization, including information about customers, which needs to be processed, systematized, and stored, and information processing is a very laborious process for employees who work with clients. The aim of the work is to develop an information architecture and methodology for systematizing the processing of client information in the enterprise. The tasks of the work are:  study of the theoretical issues of the subject of work;  collection of data on the object and development of an information architecture model;  Writing a methodology;  Justification of effectiveness. The object of writing the final qualifying work was chosen "Bobrovsky Experimental Plant". The subject of final qualifying work is the system for processing incoming information from the client in the organization. The first chapter highlights the problem of processing information at large enterprises that have automation by department. The theory of information architecture is also considered. In the second chapter, work was done to identify bottlenecks in the processing of information. The conceptual model of the information architecture is developed, the possibilities of the information system development on the basis of the information architecture are shown. The third chapter is devoted to the study of the enterprise. The chapter describes the full model of the enterprise, shows the main process of collecting information. A model of information is created, as it is. The results of the work: the practical result of the work was the developed concept of the information architecture model, the integration of two systems, 1C and Bitrix24, as well as partly the implementation of completely automatic processing of client information from sources such as the site, and the SuplBiz portal.

No description available.

Bakgrund:  Digitaliseringens framfart påverkar i princip allting i dagens samhälle. Detta har lett till att företagens IT-landskap blir alltmer komplexa. För att hantera detta introduceras många olika IT-projekt inom organisationer. Dessa IT-projekt har dock en historia av att misslyckas och det finns därför mängder av rekommenderade implementationsprocesser samt litteratur som beskriver hur man bör hantera projektkomplexitet. Däremot saknas forskning som utreder om verksamhetsarkitektur bidrar till projektkomplexiteten samt empiriska undersökningar angående hur detta hanteras.  Syfte: Syftet med studien är att undersöka hur verksamhetsarkitektur kan påverka projektkomplexitet och i sin tur implementation av nya affärssystem. Vidare ämnar studien skapa förståelse för hur projektkomplexitet hanteras i implementeringsprocesser.   Metod: Denna studie är en kvalitativ fallstudie, där vi undersökt ett företag inom miljö- och återvinningsbranschen. Empirin har samlats in genom fem semistrukturerade intervjuer där urvalet varit målstyrt. Slutsats: Denna studie visar att verksamhetsarkitekturen påverkar de faktorer som ingår i projektkomplexitet. I detta fall har det även påverkat implementeringen av nya affärssystem negativt. Vidare visar studien en bristfällig hantering av projektkomplexitet då fallföretaget inte haft något tillvägagångssätt för att vare sig förebygga komplexitet eller hantera det utmaningar som uppstått. / Background: The advance of digitalisation affects almost everything in today's society. This has led to an increasingly complex IT landscape for businesses. To cope with this, many different IT projects are being introduced within organisations. However, these IT projects have a history of failing and there is therefore a wealth of recommended implementation processes and literature describing how to deal with project complexity. However, there is a lack of research investigating whether enterprise architecture contributes to project complexity and empirical studies on how this is managed. Purpose: The purpose of this study is to investigate how architecture has affected project complexity and in turn the implementation of new business systems. Furthermore, the study intends to provide an understanding of how project complexity is handled within implementation processes.   Completion: This study is a qualitative case study, in which we investigated a company in the environmental and recycling industry. The empirical data have been collected through five semi-structured interviews where the sample was purposive.  Conclusion: This study shows that the enterprise architecture influences the factors of project complexity. In this case, it has also negatively affected the implementation of new enterprise systems. Furthermore, the study shows a poor management of project complexity as the case company had no approach to either prevent complexity or manage the challenges that arose.

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts. / Computing / M. Sc. (Information Systems)

This dissertation focuses on the re-use of business process reference models, available in a business process model warehouse, to enable the definition of more comprehensive business requirements. It proposes a business process model warehouse framework to promote the re-use of multiple business process reference models and the flexible visualisation of business process models. The critical success factor for such a framework is that it should contribute to minimise to some extent the causes of inadequate business requirements. The proposed framework is based on an analogy with a data warehouse framework, consisting of the following components: usage of multiple business process reference models as source models, the conceptual design of a process to extract, load and transform multiple business process reference models into a repository, a description of repository functionality for managing enterprise architecture artefacts, and motivation of flexible visualisation of business process models to ensure more comprehensive business requirements. / Computer Science (School of Computing) / M.Sc. (Information Systems)