Evaluation of Software Development Practices through Error Analysis

This thesis studies evaluation of software development practices through an error analysis. The work presents software development process, software testing, software errors, error classification and software process improvement methods. The practical part of the work presents results from the error analysis of one software process. It also gives improvement ideas for the project. It was noticed that the classification of the error data was inadequate in the project. Because of this it was impossible to use the error data effectively. With the error analysis we were able to show that there were deficiencies in design and analyzing phases, implementation phase and in testing phase. The work gives ideas for improving error classification and for software development practices.

Vaatimusmäärittelykäytäntöjen sovellettavuus talousohjauksen vaatimuksia kartoitettaessa

Vaatimusten määrittelyn tarkoitus on kartoittaa tietojärjestelmän käyttäjien työtehtäviä ja niihin liittyviä järjestelmän toiminnallisia ja ei-toiminnallisia vaatimuksia. Todellinen asiakasnäkökulma tulee esille yrityksen itse käynnistämässä vaatimusten määrittelyssä. Nykytilan selvittäminen ja kriittisten toimintojen havaitseminen käynnistävät kohdeyksikössä käytävän keskinäisen keskustelun, mikä on edellytyksenä järjestelmävaatimusten havaitsemiseen. Tämän työn teoriaosuudessa lähestytään eri näkökulmia vaatimustenmäärittelyyn. Tämän jälkeen esitellään muutamia asiakasyritykselle sopivia määrittelymenetelmiä, joita voidaan hyödyntää valmisohjelmistohankeen määrittelyssä. Työssä esitetään myös toiminnanohjaukseen ja tietovarastointiin tarkoitettujen järjestelmien tapaa kerätä taloudellista informaatiota ja luoda raportteja johdolle päätöksenteon tueksi. Työn empiirisessä osassa selvitetään mitkä ovat Lappeenrannan Energia Oy:n asettamat liiketoiminnalliset tarpeet ja vaatimukset uudelle talousohjauksen tietojärjestelmälle.

Improving the effectiveness of supply chain development work – an expert role perspective

This study focuses to the intersection of three sets of activities in a company: expert work, development work and supply chain management, SCM. Experts and expert work represent a set of individuals whose efficiency and impact this study is intended to improve, while development work defines the set of organizational activities to focus on. SCM as an expertise area acts as the platform on which this study is built. The study has two aims. Firstly, it aims to derive a model helping an SCM expert to increase the effectiveness of expert work in development tasks by understanding the encountered organizational situations and processes better, reflecting his/her past and future actions to organizational processes and selecting and adjusting the processes and contents of his/her work accordingly. Secondly, it aims to develop applicable approaches and methods to understand, evaluate and manage the organizational processes and situations in development work. The integrative model on approaches and methods to improve the effectiveness of development processes is split to two aggregate dimensions: technical performance of the developed solution and consumption of resources of the development process. Six potential approaches and methods aiming at helping in the management of organizational dimensions are presented in enclosed publications. The approaches focus on three subtasks of development work: decision making, implementation and change, and knowledge accumulation. The approaches and methods have been tested in case studies representing typical development processes in the area of supply chain management. As a result, four suggestions are presented. Firstly, SCM experts are advised to consider the SCM development work to be consisting of development processes. Secondly, inside these processes they should identify and evaluate the risk of difficult decision-making related to organizational factors. Thirdly, they are prompted for an active role in implementation and change, supporting the implementation through whole process. Finally, the development should be seen in a holistic view, taking into account the stage of knowledge and organizational issues related to it, and adopt a knowledge development strategy.

Improving Evaluation and Development Capability in Verification and Validation

Validation and verification operations encounter various challenges in product development process. Requirements for increasing the development cycle pace set new requests for component development process. Verification and validation usually represent the largest activities, up to 40 50 % of R&D resources utilized. This research studies validation and verification as part of case company's component development process. The target is to define framework that can be used in improvement of the validation and verification capability evaluation and development in display module development projects. Validation and verification definition and background is studied in this research. Additionally, theories such as project management, system, organisational learning and causality is studied. Framework and key findings of this research are presented. Feedback system according of the framework is defined and implemented to the case company. This research is divided to the theory and empirical parts. Theory part is conducted in literature review. Empirical part is done in case study. Constructive methode and design research methode are used in this research A framework for capability evaluation and development was defined and developed as result of this research. Key findings of this study were that double loop learning approach with validation and verification V+ model enables defining a feedback reporting solution. Additional results, some minor changes in validation and verification process were proposed. There are a few concerns expressed on the results on validity and reliability of this study. The most important one was the selected research method and the selected model itself. The final state can be normative, the researcher may set study results before the actual study and in the initial state, the researcher may describe expectations for the study. Finally reliability of this study, and validity of this work are studied.

Measuring Customer Experience in Mobile Internet

Problems in the mobile services are complex where the lack of the user analysis is not the modest issue. User centered design has increasingly become as a basis for the design of mobile services. The concept of user centered design gives end-user extensive attention at each stage of the design process. Mobile service providers want to offer experiences for users and clearly the users look for services that can provide pleasant experiences. In this thesis, the elements of user experience in mobile internet were studied as well as user experience measuring methods were researched. This study was looking for user experience measuring metrics and methods to specify new factors to measure user experience. During this thesis research project an application called CEM4Mobile was designed and implemented. CEM4Mobile is an application for observing and analysing user experience based on the user activity and behaviour. As a result of this thesis, a collection of user experience elements and measuring metrics were found. The elements and metrics were designed and implemented to CEM4Mobile product, which measures user experience. It was found out that the user experience measuring methods were based on interaction between two people but CEM4Mobile makes user observation programmatic.

Introducing Continuous Integration for C and C++ Software Development Projects on Linux Platform

Software integration is a stage in a software development process to assemble separate components to produce a single product. It is important to manage the risks involved and being able to integrate smoothly, because software cannot be released without integrating it first. Furthermore, it has been shown that the integration and testing phase can make up 40 % of the overall project costs. These issues can be mitigated by using a software engineering practice called continuous integration. This thesis work presents how continuous integration is introduced to the author's employer organisation. This includes studying how the continuous integration process works and creating the technical basis to start using the process on future projects. The implemented system supports software written in C and C++ programming languages on Linux platform, but the general concepts can be applied to any programming language and platform by selecting the appropriate tools. The results demonstrate in detail what issues need to be solved when the process is acquired in a corporate environment. Additionally, they provide an implementation and process description suitable to the organisation. The results show that continuous integration can reduce the risks involved in a software process and increase the quality of the product as well.

Challenges and Means for the Front End Activities of Software Development

The front end of innovation is regarded as one of the most important steps in building new software products or services, and the most significant benefits in software development can be achieved through improvements in the front end activities. Problems in the front end phase have an impact on customer dissatisfaction with delivered software, and on the effectiveness of the entire software development process. When these processes are improved, the likelihood of delivering high quality software and business success increases. This thesis highlights the challenges and problems related to the early phases of software development, and provides new methods and tools for improving performance in the front end activities of software development. The theoretical framework of this study comprises two fields of research. The first section belongs to the field of innovation management, and especially to the management of the early phases of the innovation process, i.e. the front end of innovation. The second section of the framework is closely linked to the processes of software engineering, especially to the early phases of the software development process, i.e. the practice of requirements engineering. Thus, this study extends the theoretical knowledge and discloses the differences and similarities in these two fields of research. In addition, this study opens up a new strand for academic discussion by connecting these research directions. Several qualitative business research methodologies have been utilized in the individual publications to solve the research questions. The theoretical and managerial contribution of the study can be divided into three areas: 1) processes and concepts, 2) challenges and development needs, and 3) means and methods for the front end activities of software development. First, the study discloses the difference and similarities between the concepts of the front end of innovation and requirements engineering, and proposes a new framework for managing the front end of the software innovation process, bringing business and innovation perspectives into software development. Furthermore, the study discloses managerial perceptions of the similarities and differences in the concept of the front end of innovation between the software industry and the traditional industrial sector. Second, the study highlights the challenges and development needs in the front end phase of software development, especially challenges in communication, such as linguistic problems, ineffective communication channels, a communication gap between users/customers and software developers, and participation of multiple persons in software development. Third, the study proposes new group methods for improving the front end activities of software development, especially customer need assessment, and the elicitation of software requirements.

Usability Centered Implementation of a Web Based Value Added Module

Customer specific functionalities are a challenging part of procurement and invoice automation environments. In Basware Enterprise Purchase to Payment product family the customer specific reports are supported only in a basic level without any seamless interface between all EPP products. Also other customer specific functionalities are not supported as there is no customizable interface between the applications and only the most common features are implemented to the products themselves. In this thesis foundations are created for a new web based value added module where it is possible to create seamless customer specific functionalities throughout the whole EPP product family. The work is implemented in a Proof of Concept type of piloting. The system is created in user centered way where the users are able to explain their requests and determine their needs. The result is an excellent foundation for a module that can be developed further.

Modeling and developing a customer-oriented configuration process in a mass customization environment

In this thesis the main objective is to examine and model configuration system and related processes. When and where configuration information is created in product development process and how it is utilized in order-delivery process? These two processes are the essential part of the whole configuration system from the information point of view. Empirical part of the work was done as a constructive research inside a company that follows a mass customization approach. Data models and documentation are created for different development stages of the configuration system. A base data model already existed for new structures and relations between these structures. This model was used as the basis for the later data modeling work. Data models include different data structures, their key objects and attributes, and relations between. Representation of configuration rules for the to-be configuration system was defined as one of the key focus point. Further, it is examined how the customer needs and requirements information can be integrated into the product development process. Requirements hierarchy and classification system is presented. It is shown how individual requirement specifications can be connected for physical design structure via features by developing the existing base data model further.

Structured software development with the IPIDDDT method - A lean method for small agile organizations

A software development process is a predetermined sequence of steps to create a piece of software. A software development process is used, so that an implementing organization could gain significant benefits. The benefits for software development companies, that can be attributed to software process improvement efforts, are improved predictability in the development effort and improved quality software products. The implementation, maintenance, and management of a software process as well as the software process improvement efforts are expensive. Especially the implementation phase is expensive with a best case scenario of a slow return on investment. Software processes are rare in very small software development companies because of the cost of implementation and an improbable return on investment. This study presents a new method to enable benefits that are usually related to software process improvement to small companies with a low cost. The study presents reasons for the development of the method, a description of the method, and an implementation process for the method, as well as a theoretical case study of a method implementation. The study's focus is on describing the method. The theoretical use case is used to illustrate the theory of the method and the implementation process of the method. The study ends with a few conclusions on the method and on the method's implementation process. The main conclusion is that the method requires further study as well as implementation experiments to asses the value of the method.

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.

AGRICULTURAL MACHINERY AND IMPLEMENTS DESIGN PROCESS: GUIDELINES FOR SMALL AND MID-SIZED BUSINESSES

ABSTRACT This study aims at presenting the process of machine design and agricultural implements by means of a reference model, formulated with the purpose of explaining the development activities of new products, serving as a guideline to coach human resources and to assist in formalizing the process in small and medium-sized businesses (SMB), i.e. up to 500 employees. The methodology used included the process modeling, carried out from case studies in the SMB, and the study of reference models in literature. The modeling formalism used was based on the IDEF0 standard, which identifies the dimensions required for the model detailing: input information; activities; tasks; knowledge domains; mechanisms; controls and information produced. These dimensions were organized in spreadsheets and graphs. As a result, a reference model with 27 activities and 71 tasks was obtained, distributed over four phases of the design process. The evaluation of the model was carried out by the companies participating in the case studies and by experts, who concluded that the model explains the actions needed to develop new products in SMB.

Järjestelmätoimittajan suorituskyvyn mittaaminen johtamisen välineenä

Tutkimuksen tavoitteena on analysoida kokonaisratkaisuja tarjoavan järjestelmätoimittajan suorituskyvyn mittaamisen suunnittelua johdon päätöksenteon tukivälineeksi. Alitavoitteena oli suunnitella mittaristo case-yrityksen valitulle yksikölle sekä konsernitasolle. Tutkimuksen myötä havaittiin tarpeelliseksi tunnistaa järjestelmätoimittajan toimialatason vahvimmat ydinkyvykkyydet ja esittää ratkaisuja niiden mittaamiselle. Tutkimuksesta rajattiin mittariston hyödyntäminen yksilötason ohjauksessa. Tutkimusta lähestyttiin toiminta-analyyttisenä tapaustutkimuksena. Tutkimuksen yhteydessä määriteltiin järjestelmätoimittaja teollisen palveluliiketoiminnan toimijaksi, jonka mittaus painottuu asiakaslähtöisen toiminnan edistämiseen. Suurimmat haasteet muodostuivat aineettoman pääoman, pääosin uudistuvan ja uuden liiketoiminnan verkostojen mittaamisesta. Tutkimustuloksena voitiin havaita, että toimialatason keskeisimpiin ydinkyvykkyyksiin ja case-yrityksen linjaamiin menestystekijöihin pohjautunut tarkastelu onnistui tunnistamaan keskeisiä ongelmakohtia järjestelmätoimittajan mittariston suunnittelussa. Merkittävimmät toimenpidesuositukset ja laaditut mittariehdotukset painottavat asiakkaan prosessien tuntemista, oman osaamisen johtamista asiakkaan prosesseihin soveltuviksi, uusien innovaatioiden ja kyvykkyyksien luomista, erilaisten verkostojen tunnistamista ja kehittämistä, kyvykkyyksien johtamista ja tuotekeskeisen myynnin kehittämistä palvelukeskeiseen suuntaan. Tutkimus esittää näihin tuloksiin pohjautuvan mittariston ja prosessin aikana syntyneet mittariehdotukset.

The value of digitalization of services in the new service development

The purpose of this thesis is to study factors that have an impact on the company’s capabilities to identify and analyze the value of digitalization of services during the early stages of service development process and evaluate them from the perspective of a case company. The research problem was defined: “How digitalization of services affects delivering the services of the future?” The research method of this thesis was based on the qualitative case study which aimed to study both company’s and customer’s set of values. The study included a literature review and a development study. The empirical research part consisted of analyzing three existing services, specifying a new digital service concept and its feasibility analysis as part of a business requirement phase. To understand the set of values, 10 stakeholder interviews were conducted and earlier customer surveys were utilized, and additionally, a number of meetings were conducted with the case company representatives to develop service concept, and evaluate the findings. The impact of the early stages of service development process discovered to reflect directly in the capabilities of the case company to identify and create customer value were related to the themes presented in the literature review. In order to specify the value achieved from the digitalization the following areas of strategic background elements were deepened during the study: Innovations, customer understanding and business service. Based on the findings, the study aims to enhance the case company’s capability to identify and evaluate the impact of the digitalization in delivering services of the future. Recognizing the value of digital service before the beginning of the development project is important to the businesses of both customer and provider. By exploring the various levels of digitalization one can get the overall picture of the value gained from utilizing digital opportunities. From the development perspective, the process of reviewing and discovering the most promising opportunities and solutions is the key step in order to deliver superior services. Ultimately, a company should understand the value outcome determination of the individual services as well as their digital counterparts.

Formal development and quantitative verification of dependable systems

-