Tiedon hallinta varastonhallintajärjestelmän hankinnassa

Diplomityössä toteutettiin varastonhallintajärjestelmän hankinta prosessoimalla tietoa hallitusti varastonhallinnan kehittämiseksi. Kvalitatiivinen tapaustutkimus tehtiin tietojohtamisen näkökulmasta käyttäjälähtöisen C-CEI –menetelmän avulla haastattelemalla ja havainnoimalla tapausyritystä. Haastatteluja tehtiin 10 kertaa. Tutkimuksessa kartoitettiin ja kilpailutettiin kotimaiset järjestelmätoimittajat, joita löydettiin 15. Näistä toimittajista 6 vastasi vaatimuksia ja teki tarjouksen. Tutkimuksen lopuksi tehtiin järjestelmän hankintaehdotus. Tutkimuksen teoreettinen viitekehys koostui tietojohtamisesta, varastonhallinnasta ja ohjelmistotuotannosta. Tutkimuksessa pääkysymyksenä esitettiin miten tietojohtamisen avulla voidaan tukea varastonhallintajärjestelmän hankintaa. Tutkimuksessa havaittiin, että tietojärjestelmän hankinta varastonhallinnan osalta on moniulotteinen liiketoiminnan kehittämistehtävä. Tietojärjestelmähankinta tulisi siten nähdä liiketoimintaa eteenpäin vievänä mahdollisuutena. Lisäksi loppukäyttäjän vaatimusten kartoittamiseen tulisi sitoutua huolella ja suhtautua kriittisesti eri järjestelmävaihtoehtoihin. Vaatimusmäärittelyn asettaminen ja vaatimusten priorisoiminen ovat haasteellisia tehtäviä. Tiedon hallinnan aikana saatiin selville, että loppukäyttäjän vaatimusten mukainen tarjouspyyntö edesauttaa ensinnäkin tarjousten tekemistä mutta myös niiden prosessointia ja analysointia. Vain oikealla tiedolla ja sen yhteyksillä on merkitystä. Tutkimuksen perusteella tietojärjestelmän hankinta suositellaan tehtäväksi hallitsemalla tietoa systemaattisesti erityisesti sen alkuvaiheen aikana. Tietojohtaminen virtaviivaistaa hankkeen etenemistä ja aikataulutusta, vähentää loppukäyttäjän kustannuksia tehokkaalla kilpailutusmenettelyllä, edistää kilpailukykyä ja luo hyvän lähtökohdan koko tietojärjestelmän hankinnan läpiviemiselle ja yhteistyö-suhteen rakentumiselle kauppakumppaneiden välille.

Analysis of companies' software as a service adoption intention factors

The goal of this study is to develop managerial recommendations for international vendors and system integrators, which offer Software as a Service for enterprise information systems on the Russian market. Those recommendations can be used to develop marketing, sales, new product and service level agreement strategies. For those reasons factors affecting SaaS adoption were determined and their influence on intention to adoption was examined.

Intellectual capital management in international and Russian software companies

The importance of the company’s intellectual capital (IC) increased during the last decades due to knowledge-based economy development. Despite the clear understanding of the IC importance, researchers agree on the fact that many difficulties in management of intangibles still exist from the both theoretical and practical points of view. The goal of the study is to conduct a comparison of IC management approaches used in international and Russian software companies. To carry out a proper comparison and identify similarities and differences, software firms are explored from the point of view of IC, and then be compared in the context of international and Russian sectors. At the end of the study, current IC management findings in international and Russian software companies are presented, and comparison of IC management is done. It was investigated from the comparison that international and Russian software companies have similarities and few principal differences in several IC management areas. The comparison of IC management approaches between international and Russian software companies provide helpful information to both, researchers and practitioners.

When to Utilize Software as a Service

Cloud computing enables on-demand network access to shared resources (e.g., computation, networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort. Cloud computing refers to both the applications delivered as services over the Internet and the hardware and system software in the data centers. Software as a service (SaaS) is part of cloud computing. It is one of the cloud service models. SaaS is software deployed as a hosted service and accessed over the Internet. In SaaS, the consumer uses the provider‘s applications running in the cloud. SaaS separates the possession and ownership of software from its use. The applications can be accessed from any device through a thin client interface. A typical SaaS application is used with a web browser based on monthly pricing. In this thesis, the characteristics of cloud computing and SaaS are presented. Also, a few implementation platforms for SaaS are discussed. Then, four different SaaS implementation cases and one transformation case are deliberated. The pros and cons of SaaS are studied. This is done based on literature references and analysis of the SaaS implementations and the transformation case. The analysis is done both from the customer‘s and service provider‘s point of view. In addition, the pros and cons of on-premises software are listed. The purpose of this thesis is to find when SaaS should be utilized and when it is better to choose a traditional on-premises software. The qualities of SaaS bring many benefits both for the customer as well as the provider. A customer should utilize SaaS when it provides cost savings, ease, and scalability over on-premises software. SaaS is reasonable when the customer does not need tailoring, but he only needs a simple, general-purpose service, and the application supports customer‘s core business. A provider should utilize SaaS when it offers cost savings, scalability, faster development, and wider customer base over on-premises software. It is wise to choose SaaS when the application is cheap, aimed at mass market, needs frequent updating, needs high performance computing, needs storing large amounts of data, or there is some other direct value from the cloud infrastructure.

Software Test Process Development

In this thesis, the components important for testing work and organisational test process are identified and analysed. This work focuses on the testing activities in reallife software organisations, identifying the important test process components, observing testing work in practice, and analysing how the organisational test process could be developed. Software professionals from 14 different software organisations were interviewed to collect data on organisational test process and testing‐related factors. Moreover, additional data on organisational aspects was collected with a survey conducted on 31 organisations. This data was further analysed with the Grounded Theory method to identify the important test process components, and to observe how real‐life test organisations develop their testing activities. The results indicate that the test management at the project level is an important factor; the organisations do have sufficient test resources available, but they are not necessarily applied efficiently. In addition, organisations in general are reactive; they develop their process mainly to correct problems, not to enhance their efficiency or output quality. The results of this study allows organisations to have a better understanding of the test processes, and develop towards better practices and a culture of preventing problems, not reacting to them.

Tuotehallinnan tietoprosessin haasteet ja kehittäminen ohjelmistoyrityksessä

Diplomityössä tutustuttiin ohjelmistoyrityksen tuotteiden asiakastarpeiden ja vaatimusten käsittelyyn tuotehallinnan tietoprosessin näkökulmasta. Työssä kuvattiin yrityksen nykyinen prosessi sekä analysoitiin erityisesti sen haasteita. Teoriatiedon sekä yrityksen asiantuntijalausuntojen pohjalta laadittiin tuotehallinnan tietoprosessin kehitysehdotuksia. Kvalitatiivinen tapaustutkimus toteutettiin käytännönläheisesti esittämällä kohdeyrityksen asiantuntijoille avoimia kysymyksiä sekä heidän kanssaan keskustellen. Tutkimus tehtiin neljässä vaiheessa ja sen päätavoitteena oli selvittää, millä keinoilla voidaan tukea kohdeyrityksen tuotekehitystarpeisiin ja tuotekehitysehdotuksiin liittyvän tiedon hallintaa sekä tuotantopäätöksiä. Tutkimuksen teoreettinen viitekehys koostui organisaation tietoprosessista, organisaation päätöksentekoprosessista, ohjelmistotuotteen erityispiirteistä sekä ohjelmiston tuotehallinnasta. Kohdeyrityksen tuotehallinnan tietoprosessin kehittämisen keskeisiksi tekijöiksi nousivat tuotehallinnan tukena käytettävän tietojärjestelmän ominaisuudet, tiedon hakeminen, tiedon löytäminen ja tulkinta. Kehityskohteiksi nousivat lisäksi prosessin kulku, perustuotekehityksen ja asiakastoimituksien rinnakkainen hallinta sekä asiakasarvon tuottaminen tuotehallinnan keinoin. Tutkimuksen lopputuloksena toteutettiin kohdeyrityksen tuotehallinnan tietoprosessin tavoitetilan kuvaus. Tavoitetilan elementtejä olivat tuotteiden pidemmän tähtäimen suunnitelmat (roadmap), tuotehallinnan organisointi tiimeille sekä sensemaking-prosessin hyödyntäminen osapuolien yhteisen ymmärryksen luomiseksi kehitystarpeille. Käytössä olevan tietojärjestelmän kehitysehdotukset perustuivat näiden tuotehallinnan elementtien tukemiseen.

Automated Software Testing in Machine Automation

The problem of software (SW) defaults is becoming more and more topical because of increasing amount of the SW and its complication. The majority of these defaults are founded during the test part that consumes about 40-50% of the development efforts. Test automation allows reducing the cost of this process and increasing testing effectiveness. In the middle of 1980 the first tools for automated testing appeared and the automated process was implemented in different kinds of SW testing. In short time, it became obviously, automated testing can cause many problems such as increasing product cost, decreasing reliability and even project fail. This thesis describes automated testing process, its concept, lists main problems, and gives an algorithm for automated test tools selection. Also this work presents an overview of the main automated test tools for embedded systems.

Integrating user experience into early phases of software development

The value and benefits of user experience (UX) are widely recognized in the modern world and UX is seen as an integral part of many fields. This dissertation integrates UX and understanding end users with the early phases of software development. The concept of UX is still unclear, as witnessed by more than twenty-five definitions and ongoing argument about its different aspects and attributes. This missing consensus forms a problem in creating a link between UX and software development: How to take the UX of end users into account when it is unclear for software developers what UX stands for the end users. Furthermore, currently known methods to estimate, evaluate and analyse UX during software development are biased in favor of the phases where something concrete and tangible already exists. It would be beneficial to further elaborate on UX in the beginning phases of software development. Theoretical knowledge from the fields of UX and software development is presented and linked with surveyed and analysed UX attribute information from end users and UX professionals. Composing the surveys around the identified 21 UX attributes is described and the results are analysed in conjunction with end user demographics. Finally the utilization of the gained results is explained with a proof of concept utility, the Wizard of UX, which demonstrates how UX can be integrated into early phases of software development. The process of designing, prototyping and testing this utility is an integral part of this dissertation. The analyses show statistically significant dependencies between appreciation towards UX attributes and surveyed end user demographics. In addition, tests conducted by software developers and industrial UX designer both indicate the benefits and necessity of the prototyped Wizard of UX utility. According to the conducted tests, this utility meets the requirements set for it: It provides a way for software developers to raise their know-how of UX and a possibility to consider the UX of end users with statistical user profiles during the early phases of software development. This dissertation produces new and relevant information for the UX and software development communities by demonstrating that it is possible to integrate UX as a part of the early phases of software development.

Software Security Vulnerabilities in Mobile Peer-to-peer Environment

Increase of computational power and emergence of new computer technologies led to popularity of local communications between personal trusted devices. By-turn, it led to emergence of security problems related to user data utilized in such communications. One of the main aspects of the data security assurance is security of software operating on mobile devices. The aim of this work was to analyze security threats to PeerHood, software intended for performing personal communications between mobile devices regardless of underlying network technologies. To reach this goal, risk-based software security testing was performed. The results of the testing showed that the project has several security vulnerabilities. So PeerHood cannot be considered as a secure software. The analysis made in the work is the first step towards the further implementation of PeerHood security mechanisms, as well as taking into account security in the development process of this project.

Software for design of experiments and response modelling of cake ltration applications

Filtration is a widely used unit operation in chemical engineering. The huge variation in the properties of materials to be ltered makes the study of ltration a challenging task. One of the objectives of this thesis was to show that conventional ltration theories are di cult to use when the system to be modelled contains all of the stages and features that are present in a complete solid/liquid separation process. Furthermore, most of the ltration theories require experimental work to be performed in order to obtain critical parameters required by the theoretical models. Creating a good overall understanding of how the variables a ect the nal product in ltration is somewhat impossible on a purely theoretical basis. The complexity of solid/liquid separation processes require experimental work and when tests are needed, it is advisable to use experimental design techniques so that the goals can be achieved. The statistical design of experiments provides the necessary tools for recognising the e ects of variables. It also helps to perform experimental work more economically. Design of experiments is a prerequisite for creating empirical models that can describe how the measured response is related to the changes in the values of the variable. A software package was developed that provides a ltration practitioner with experimental designs and calculates the parameters for linear regression models, along with the graphical representation of the responses. The developed software consists of two software modules. These modules are LTDoE and LTRead. The LTDoE module is used to create experimental designs for di erent lter types. The lter types considered in the software are automatic vertical pressure lter, double-sided vertical pressure lter, horizontal membrane lter press, vacuum belt lter and ceramic capillary action disc lter. It is also possible to create experimental designs for those cases where the variables are totally user de ned, say for a customized ltration cycle or di erent piece of equipment. The LTRead-module is used to read the experimental data gathered from the experiments, to analyse the data and to create models for each of the measured responses. Introducing the structure of the software more in detail and showing some of the practical applications is the main part of this thesis. This approach to the study of cake ltration processes, as presented in this thesis, has been shown to have good practical value when making ltration tests.

Making Sense of Software Product Requirements

One of the most crucial tasks for a company offering a software product is to decide what new features should be implemented in the product’s forthcoming versions. Yet, existing studies show that this is also a task with which many companies are struggling. This problem has been claimed to be ambiguous and changing. There are better or worse solutions to the problem, but no optimal one. Furthermore, the criteria determining the success of the solution keeps changing due to continuously changing competition, technologies and market needs. This thesis seeks to gain a deeper understanding of the challenges that companies have reportedly faced in determining the requirements for their forthcoming product versions. To this end, product management related activities are explored in seven companies. Following grounded theory approach, the thesis conducts four iterations of data analysis, where each of the iterations goes beyond the previous one. The thesis results in a theory proposal intended to 1) describe the essential characteristics of organizations’ product management challenges, 2) explain the origins of the perceived challenges and 3) suggest strategies to alleviate the perceived challenges. The thesis concludes that current product management approaches are becoming inadequate to deal with challenges that have multiple and conflicting interpretations, different value orientations, unclear goals, contradictions and paradoxes. This inadequacy continues to increase until current beliefs and assumptions about the product management challenges are questioned and a new paradigm for dealing with the challenges is adopted.

A Case Study of Agile Software Engineering Methods and Practices in the MeeGo Harmattan Open Source and Product Context

The aim of this master’s thesis is to study how Agile method (Scrum) and open source software are utilized to produce software for a flagship product in a complex production environment. The empirical case and the used artefacts are taken from the Nokia MeeGo N9 product program, and from the related software program, called as the Harmattan. The single research case is analysed by using a qualitative method. The Grounded Theory principles are utilized, first, to find out all the related concepts from artefacts. Second, these concepts are analysed, and finally categorized to a core category and six supported categories. The result is formulated as the operation of software practices conceivable in circumstances, where the accountable software development teams and related context accepts a open source software nature as a part of business vision and the whole organization supports the Agile methods.

Organizational mechanisms and conditions of individuals for knowledge sharing in post-acquisition integration

The challenges of knowledge sharing after cross-border acquisitions are widely recognised. The study took a new view to the subject by applying a two-level framework provided by the knowledge governance approach. The purpose of the study was to investigate the effects of organizational mechanisms on the conditions of individuals for knowledge sharing in post-acquisition integration context. Qualitative research methods were used in this case study. Individual interviews were performed within an international firm after a recent cross-border acquisition. The results showed that integrators, the rotation of the personnel from the acquiring firm and visits and meetings enhance the conditions at the individual level for knowledge sharing after the acquisition. Respectively, strategic change, matrix structure and foreign HRM practices challenge the conditions at the individual level for knowledge sharing in the early post-acquisition integration phase. The findings are supported by the prior research on knowledge management in acquisitions. In particular, the study enlightens how organizational level actions influence the conditions of individuals for knowledge sharing. The study suggests that organizations should adjust organizational mechanisms to support the conditions of individuals, in order to promote knowledge sharing in the early phase of the integration.

Toimintaohjeiston laatiminen HSY:n jätehuollon elinkaarimallinnuspalveluiden hankkimiseksi

Elinkaariarviointi on menetelmä, missä tuotejärjestelmän aikaiset syötteet ja tuotteet koostetaan yhteen ja tuloksena saadaan sen ympäristökuormitus. Elinkaariarviointi on päätöksentekoa tukeva työkalu. Jätelain kokonaisuudistuksen myötä elinkaariarvioinnin käyttö tullee lisääntymään kuntavastuullisessa jätehuollossa. Helsingin seudun ympäristöpalvelut -kuntayhtymä HSY:n jätehuollon tavoitteena on rakentaa elinkaarimalli, jonka avulla voidaan selvittää koko toiminnan aiheuttama ympäristökuormitus ja taloudelliset vaikutukset. HSY:n jätehuolto on päättänyt toteuttaa elinkaarimallin rakentamisen konsulttityönä. Työn tavoitteena on ollut laatia toimintaohjeisto HSY:n jätehuollon elinkaarimallinnuspalveluiden hankkimiseksi. Elinkaarimalli voidaan tehdä kaupallista ohjelmistoa käyttämällä. Tähän selvitykseen on valittu arvioitavaksi kolme elinkaariarvioinnin työkalua: EASEWASTE, WRATE ja GaBi 4.4. Ohjelmistojen ominaisuuksia on arvioitu kirjallisuuden ja haastattelun perusteella. Työssä on laadittu kriteeristö näiden ohjelmistojen arviointiin. Kirjallisuuden perusteella on selvitetty elinkaariarvioinnin soveltamiskohteet kuntavastuullisessa jätehuollossa. HSY:n jätehuollon elinkaariarvioinnin soveltamiskohteet ja mallinnustarpeet on tunnistettu haastattelemalla HSY:n jätehuollon asiantuntijoita. HSY:n jätehuollolle rakennettavan mallin päivittämistä, käyttöä ja kehittämistä tulisi hallita HSY:n jätehuollon toimesta. Kaikki työssä arvioidut ohjelmistot soveltuvat HSY:n jätehuollon tunnistamien mallinnustarpeiden laskentaan. Elinkaarimallinnuspalveluiden toimintaohjeistolla pyritään varmistamaan HSY:n jätehuollon tarpeisiin soveltuvan mallin hankinta ja jatkotoimenpiteiden suunnittelu.