A software engineering approach to distributed systems for composite modeling

The goal of this thesis is to define and validate a software engineering approach for the development of a distributed system for the modeling of composite materials, based on the analysis of various existing software development methods. We reviewed the main features of: (1) software engineering methodologies; (2) distributed system characteristics and their effect on software development; (3) composite materials modeling activities and the requirements for the software development. Using the design science as a research methodology, the distributed system for creating models of composite materials is created and evaluated. Empirical experiments which we conducted showed good convergence of modeled and real processes. During the study, we paid attention to the matter of complexity and importance of distributed system and a deep understanding of modern software engineering methods and tools.

Using Tomato Analyzer software to determine embryo size in x-rayed seeds

A primary interest of image analysis of X-rayed seeds is to identify whether the extent of fill in the embryo cavity is associated with to seed physiological quality. The objective of this research was to verify the accuracy of the freely available Tomato Analyzer (TA) software developed at The Ohio State University to determine the ratio of embryo size over total seed area. Seeds of pumpkin, watermelon, cucumber and cotton were X-rayed and analyzed by the software which defines seed and embryo boundaries and automatically generates numerical values to quantify that ratio. Results showed that the TA has the sensitivity to evaluate the extent of embryo growth within the cucurbits and cotton seeds and is a promising alternative for this assessment in other seed species.

Assessment of physiological potential of cucumber seeds using the software Seedling Vigor Imaging System® (SVIS®)

The software Seed Vigor Imaging System (SVIS®), has been successfully used to evaluate seed physiological potential by automated analyses of scanned seedlings. In this research, the efficiency of this system was compared to other tests accepted for assessing cucumber (Cucumis sativus L.) seed vigor of distinct seed lots of Supremo and Safira cultivars. Seeds were subjected to germination, traditional and saturated salt accelerated aging, seedling emergence, seedling length and SVIS analyses (determination of vigor indices and seedling growth uniformity, lengths of primary root, hypocotyl and whole seedlings). It was also determined whether the definition of seedling growth/uniformity ratios affects the sensitivity of the SVIS®. Results showed that analyses SVIS have provided consistent identification of seed lots performance, and have produced information comparable to those from recommended seed vigor tests, thus demonstrating a suitable sensitivity for a rapid and objective evaluation of physiological potential of cucumber seeds. Analyses of four-days-old cucumber seedlings using the SVIS® are more accurate and growth/uniformity does not affect the precision of results.

Software as a Service liiketoimintamallina

Software as a Service (SaaS) on tietojärjestelmien kehityksessä käytettävä liiketoimintamalli. Sen toiminta perustuu pilvilaskentaan ja pilven kautta tarjottavaan ohjelmistoon. Perinteisen ohjelmiston vastaisesti SaaSia käyttävää ohjelmaa ei asenneta käyttäjän laitteistolle, vaan ohjelmiston loogisen osan toiminta tapahtuu pilvessä. Käyttäjä siis antaa Internetin välitykselle ohjelmalle käskyjä, joiden perusteella ohjelma suorittaa tehtäviä ja palauttaa informaatiota. Tässä tutkielmassa käsitellään SaaSin yleisen toiminnan lisäksi sen liiketoiminnallisia ominaisuuksia ja vaikutusta ohjelmistotuotannon normeihin. Työssä arvioidaan SaaSin hyötyjä ja haittoja niin yrityksien ohjelmistotuotannon kuin liiketoiminnankin kannalta ja tutkitaan milloin ja miten kyseistä toimintamallia voi hyödyntää parhaimmalla tavalla nykyaikaisessa tietojärjestelmäkehityksessä. Lopussa pohditaan syvemmin SaaSin toimintaa tällä hetkellä ja tulevaisuudessa. Tuloksista nähdään mitä SaaS ja pilvilaskenta käytännössä merkitsee nykyaikaisessa ohjelmistokehityksessä. Huomataan, että SaaSin suuri suosion kasvu on perusteltavaa sen käytännöllisyyden ja toiminnallisuuden takia. SaaSin tarjoaman modernin pilveen perustuvan tietoteknisen ja liiketoiminnallisen ratkaisun takia on oletettavissa, että SaaSin suosion kasvukäyrä tulee jatkossakin olemaan nousu-johteinen.

Measuring software security from the design of software

The vast majority of our contemporary society owns a mobile phone, which has resulted in a dramatic rise in the amount of networked computers in recent years. Security issues in the computers have followed the same trend and nearly everyone is now affected by such issues. How could the situation be improved? For software engineers, an obvious answer is to build computer software with security in mind. A problem with building software with security is how to define secure software or how to measure security. This thesis divides the problem into three research questions. First, how can we measure the security of software? Second, what types of tools are available for measuring security? And finally, what do these tools reveal about the security of software? Measuring tools of these kind are commonly called metrics. This thesis is focused on the perspective of software engineers in the software design phase. Focus on the design phase means that code level semantics or programming language specifics are not discussed in this work. Organizational policy, management issues or software development process are also out of the scope. The first two research problems were studied using a literature review while the third was studied using a case study research. The target of the case study was a Java based email server called Apache James, which had details from its changelog and security issues available and the source code was accessible. The research revealed that there is a consensus in the terminology on software security. Security verification activities are commonly divided into evaluation and assurance. The focus of this work was in assurance, which means to verify one’s own work. There are 34 metrics available for security measurements, of which five are evaluation metrics and 29 are assurance metrics. We found, however, that the general quality of these metrics was not good. Only three metrics in the design category passed the inspection criteria and could be used in the case study. The metrics claim to give quantitative information on the security of the software, but in practice they were limited to evaluating different versions of the same software. Apart from being relative, the metrics were unable to detect security issues or point out problems in the design. Furthermore, interpreting the metrics’ results was difficult. In conclusion, the general state of the software security metrics leaves a lot to be desired. The metrics studied had both theoretical and practical issues, and are not suitable for daily engineering workflows. The metrics studied provided a basis for further research, since they pointed out areas where the security metrics were necessary to improve whether verification of security from the design was desired.

Model to Build a Service Quality Centric Customer Reference Portfolio in a Software as a Service Company

The goal of the master’s thesis was to develop a model to build a service quality centric customer reference portfolio for a software as a service company. The case company is Meltwater Finland Oy that leverages customer references externally but there is no systematic model to produce good quality customer references that are in line with the company strategy. The project was carried out as a case study, where the primary source of information were seventeen internal interviews with the employees of the case company. The theory part focuses on customer references as assets and service quality in software as a service industry. In the empirical part the research problem is solved. As a result of the case study, the model to build a service quality centric customer reference portfolio was created and further research areas were suggested.

Applying software performance engineering methods to development of IT device management systems

Ohjelmiston suorituskyky on kokonaisvaltainen asia, johon kaikki ohjelmiston elinkaaren vaiheet vaikuttavat. Suorituskykyongelmat johtavat usein projektien viivästymisiin, kustannusten ylittymisiin sekä joissain tapauksissa projektin täydelliseen epäonnistumiseen. Software performance engineering (SPE) on ohjelmistolähtöinen lähestysmistapa, joka tarjoaa tekniikoita suorituskykyisen ohjelmiston kehittämiseen. Tämä diplomityö tutkii näitä tekniikoita ja valitsee niiden joukosta ne, jotka soveltuvat suorituskykyongelmien ratkaisemiseen kahden IT-laitehallintatuotteen kehityksessä. Työn lopputuloksena on päivitetty versio nykyisestä tuotekehitysprosessista, mikä huomioi sovellusten suorituskykyyn liittyvät haasteet tuotteiden elinkaaren eri vaiheissa.

Customer Discovery and Customer Validation in Lean Software Startups

The traditional business models and the traditionally successful development methods that have been distinctive to the industrial era, do not satisfy the needs of modern IT companies. Due to the rapid nature of IT markets, the uncertainty of new innovations‟ success and the overwhelming competition with established companies, startups need to make quick decisions and eliminate wasted resources more effectively than ever before. There is a need for an empirical basis on which to build business models, as well as evaluate the presumptions regarding value and profit. Less than ten years ago, the Lean software development principles and practices became widely well-known in the academic circles. Those practices help startup entrepreneurs to validate their learning, test their assumptions and be more and more dynamical and flexible. What is special about today‟s software startups is that they are increasingly individual. There are quantitative research studies available regarding the details of Lean startups. Broad research with hundreds of companies presented in a few charts is informative, but a detailed study of fewer examples gives an insight to the way software entrepreneurs see Lean startup philosophy and how they describe it in their own words. This thesis focuses on Lean software startups‟ early phases, namely Customer Discovery (discovering a valuable solution to a real problem) and Customer Validation (being in a good market with a product which satisfies that market). The thesis first offers a sufficiently compact insight into the Lean software startup concept to a reader who is not previously familiar with the term. The Lean startup philosophy is then put into a real-life test, based on interviews with four Finnish Lean software startup entrepreneurs. The interviews reveal 1) whether the Lean startup philosophy is actually valuable for them, 2) how can the theory be practically implemented in real life and 3) does theoretical Lean startup knowledge compensate a lack of entrepreneurship experience. A reader gets familiar with the key elements and tools of Lean startups, as well as their mutual connections. The thesis explains why Lean startups waste less time and money than many other startups. The thesis, especially its research sections, aims at providing data and analysis simultaneously.

Customer Discovery and Customer Validation in Lean Software Startups

The traditional business models and the traditionally successful development methods that have been distinctive to the industrial era, do not satisfy the needs of modern IT companies. Due to the rapid nature of IT markets, the uncertainty of new innovations‟ success and the overwhelming competition with established companies, startups need to make quick decisions and eliminate wasted resources more effectively than ever before. There is a need for an empirical basis on which to build business models, as well as evaluate the presumptions regarding value and profit. Less than ten years ago, the Lean software development principles and practices became widely well-known in the academic circles. Those practices help startup entrepreneurs to validate their learning, test their assumptions and be more and more dynamical and flexible. What is special about today‟s software startups is that they are increasingly individual. There are quantitative research studies available regarding the details of Lean startups. Broad research with hundreds of companies presented in a few charts is informative, but a detailed study of fewer examples gives an insight to the way software entrepreneurs see Lean startup philosophy and how they describe it in their own words. This thesis focuses on Lean software startups‟ early phases, namely Customer Discovery (discovering a valuable solution to a real problem) and Customer Validation (being in a good market with a product which satisfies that market). The thesis first offers a sufficiently compact insight into the Lean software startup concept to a reader who is not previously familiar with the term. The Lean startup philosophy is then put into a real-life test, based on interviews with four Finnish Lean software startup entrepreneurs. The interviews reveal 1) whether the Lean startup philosophy is actually valuable for them, 2) how can the theory be practically implemented in real life and 3) does theoretical Lean startup knowledge compensate a lack of entrepreneurship experience. A reader gets familiar with the key elements and tools of Lean startups, as well as their mutual connections. The thesis explains why Lean startups waste less time and money than many other startups. The thesis, especially its research sections, aims at providing data and analysis simultaneously.

The functional fit between collaborative software and work systems:Qualification of work system needs to software functionality

The study develops an approach that tries to validate software functionality to work systems needs in SMEs. The formulated approach is constructed by using a SAAS based software i.e., work collaboration service (WCS), and SMEs as the elements of study. Where the WCS’s functionality is qualified to the collaboration needs that exist in operational and project work within SMEs. For this research constructivist approach and case study method is selected because the nature of the current study requires an in depth study of the work collaboration service as well as a detailed study of the work systems within different enterprises. Four different companies are selected in which fourteen interviews are conducted to gather data pertaining. The work systems method and framework are used as a central part of the approach to collect, analyze and interpret the enterprises work systems model and the underlying collaboration needs on operational and project work. On the other hand, the functional model of the WCS and its functionality is determined from functional model analysis, software testing, documentation and meetings with the service vendor. The enterprise work system model and the WCS model are compared to reveal how work progression differs between the two and make visible unaddressed stages of work progression. The WCS functionality is compared to work systems collaboration needs to ascertain if the service will suffice the needs of the project and operational work under study. The unaddressed needs provide opportunities to improve the functionality of the service for better conformity to the needs of enterprise and work. The results revealed that the functional models actually differed in how operational and project work progressed within the stages. WCS shared similar stages of work progression apart from the stages of identification and acceptance, and progress and completion stages were only partially addressed. Conclusion is that the identified unaddressed needs such as, single point of reference, SLA and OLA inclusion etc., should be implemented or improved within the WCS at appropriate stages of work to gain better compliance of the service to the needs of the enterprise an work itself. The developed approach can hence be used to carry out similar analysis for the conformance of pre-built software functionality to work system needs with SMEs.

Cohesion Metrics for Improving Software Quality

Abstract Software product metrics aim at measuring the quality of software. Modu- larity is an essential factor in software quality. In this work, metrics related to modularity and especially cohesion of the modules, are considered. The existing metrics are evaluated, and several new alternatives are proposed. The idea of cohesion of modules is that a module or a class should consist of related parts. The closely related principle of coupling says that the relationships between modules should be minimized. First, internal cohesion metrics are considered. The relations that are internal to classes are shown to be useless for quality measurement. Second, we consider external relationships for cohesion. A detailed analysis using design patterns and refactorings confirms that external cohesion is a better quality indicator than internal. Third, motivated by the successes (and problems) of external cohesion metrics, another kind of metric is proposed that represents the quality of modularity of software. This metric can be applied to refactorings related to classes, resulting in a refactoring suggestion system. To describe the metrics formally, a notation for programs is developed. Because of the recursive nature of programming languages, the properties of programs are most compactly represented using grammars and formal lan- guages. Also the tools that were used for metrics calculation are described.

The best practices in the formation phase of Sino-Finnish joint ventures in China: For Finnish software companies

This study discusses the formation phase of Chinese-Finnish joint ventures in China. The purpose of this thesis is to create best practices for Finnish software companies in forming a joint venture with a local Chinese company in China. Therefore, the main research question, in what are the best practices for forming Sino-Finnish joint ventures in China for Finnish software firms, is examined through four different themes within the joint venture formation phase; the motives, the partner se-lection, the choice of a joint venture type and joint venture negotiations. The theoretical background of the study consists of literature relating to the establishment process of Sino-Western joint ventures in China. The empirical research conducted for this study is based on the expert interviews. The empirical data was gathered via nine semi-structured interviews with both Chinese and Finnish experts in software and technology industry, who have experience or knowledge in establishing Sino-Finnish joint ventures in China. Thematic analysis was used to cat-egorize and interpret the interview data. In addition, a thematic network was built to act as a basis of the analysis. According to the main findings, the main motives for Finnish software companies to establish a joint venture in China are lack of skills or experience, little resources to enter on their own, and China’s large market. The main motives for Chinese companies are to gain new technology or man-agerial skills, and expand internationally. The intellectual property rights (IPR) have recently im-proved a lot in China, but the Finnish companies’ knowledge on IPR is inadequate. The Finnish software companies should conduct a market and industry research in order to understand their po-sition in the market and to find a suitable location and potential joint venture partners. It is essential to define partner selection criteria and partner attributes. In addition, it is important to build the joint venture around complementary motives and a win-win situation between the joint venture partners. The Finnish companies should be prepared that the joint venture negotiations will be challenging and they will take a long time. The challenges can be overcome by gaining understanding about the Chinese culture and business environment. The findings of this study enhance understanding of the joint venture formation phase in China. This study provides guidelines for Finnish software companies to establish a joint venture in China. In addition, this study brings new insights to the Sino-Western joint venture literature with its soft-ware industry context. Future research is, however, necessary in order to gain an understanding of the advantages and disadvantages of a joint venture as an entry mode into China for Finnish soft-ware companies.

The roles and tasks of salespeople in Software-as-a-Service company's value-based sales process

Recent research in relationships marketing and sales and sales management emphasizes companies’ ability to create customer value as a core of all business-to-business relationships. The role of individual salespeople in business relation-ships is commonly acknowledged, but has been largely neglected in extant literature. This study offers especially more detailed perspective on salespeople’s roles and tasks in business-to-business value-based sales process. It focuses especially on Software-as-a-Service business environment. The objective of the study is to find out how salespeople can create value in Software-as-a-Service value-based sales process. It determines value-based sales process, salespeople’s roles and tasks in it, and combines value assessment in to process. The results indicate that salespeople have to adapt different selling roles and tasks in Software-as-a-Service value-based sales process to be able to support the customer’s value-in-use experience. The process itself is highly complex, consisting of multiple facets and selling behaviors, and involves relevant actors from both parties of relationship. The study concludes with a discussion of possibilities that provide interesting aspects for future research.

User Experience Patterns for/of Innovation by Design: A Survey on Design Practices in the Software Development and Innovation Lifecycle

The User Experience (UX) designers are undoubtedly aware of how many UX design methods currently exist and that sometimes it becomes a problem to choose an appropriate one. What are all of methods that designers have in their “arsenal”? When can they use them? This thesis presents the research on the design methods in the contemporary context of User Experience (UX) and Innovations by using a survey approach. The study is limited to cover the domain of consumer mobile services development and provider companies around the world. The study follows 2 clear objectives: (1) to understand what design methods are currently used in that context and to what extent they are used (2) to identify at what stage according to the UX design thinking process for creating innovations they are placed. The study contributes to the research in the field of UX design and Innovations and extends the knowledge in that field together with communities’ (UXPA, SIGCHI, SIGSOFT) members’ cooperation. The research is vital due to lack of information on design practices and their application in the chosen context.

Software for Transport Accessibility Analysis: The Case of Moscow

In this thesis the process of building a software for transport accessibility analysis is described. The goal was to create a software which is easy to distribute and simple to use for the user without particular background in the field of the geographical data analysis. It was shown that existing tools do not suit for this particular task due to complex interface or significant rendering time. The goal was accomplished by applying modern approaches in the process of building web applications such as maps based on vector tiles, FLUX architecture design pattern and module bundling. It was discovered that vector tiles have considerable advantages over image-based tiles such as faster rendering and real-time styling.