M.B.A / The performance of project delivery in the software development domain has a poor history of successes. This research focused on identifying some of the reasons for this poor performance for software development projects in order to propose a possible framework for measuring and evaluating a software development project's performance. The proposed framework is intended to link individual project performance into the strategic performance measurements for an organisation and hence includes the aspect of being able to evaluate an individual project's performance relative to other projects within a programme, organisation or industry. The research was conducted through in-depth interviews and literature studies. The following three Key findings resulted from this study: • Firstly that unless an organisation establishes upfront what the intended use of the measurements is, as well as how they as an organisation and project define "project success" in terms of their overall objectives, any measurements taken will be oflittle value. • Secondly that there is still strong support for the generic measurements of Time, Cost, and Quality all within good customer relations, however, these need to take into account the aspects of project complexity, project management skills, the team fit and the accuracy of the estimates. • Thirdly that the ultimate framework adopted by an organisation for measuring and evaluating project performance should be simple without being simplistic and hence should be generic and easy to implement across a broad range of projects.

Today’s software is more vulnerable to attacks due to increase in complexity, connectivity and extensibility. Securing software is usually considered as a post development activity and not much importance is given to it during the development of software. However the amount of loss that organizations have incurred over the years due to security flaws in software has invited researchers to find out better ways of securing software. In the light of research done by many researchers, this thesis presents how software can be secured by considering security in different phases of software development life cycle. A number of security activities have been identified that are needed to build secure software and it is shown that how these security activities are related with the software development activities of the software development lifecycle.

In this study, we investigate how lead time is affected during development of a large-scale telecom product. We collected raw data from the product’s Gerrit repository which were later processed with statistical analysis. When we analysed the various areas, we concluded that a method to divide the lead time into different sequences would be the preferred method. We therefore chose to analyse lead time for different parts of the development. We found that on average lead time is roughly 3,4 days for the areas we investigate. The results indicated that lead time for reviewing increases with the years. The results also indicated that the lead time decreases for developers as they become more familiar with the product however the overall lead time for implementation did not. This can be as developers switch tasks internally or decides to change employment. The results also indicated that there is no relation between the amount of submitted LOC and lead time.

Context. Agile software development mainly focuses on value creation, and the first principle of theAgile Manifesto is to deliver a valuable software to customers. In spite of the great significance of value,there are few studies investigated what value is from the perspective of industry practitioners. Objectives. In this study we perform a replication study about value definitions, usage, andmeasurements in China and make a comparative analysis with the similar study did in Sweden. Theprimary objectives of this study are to: a) identify value aspects from Chinese software organizations;b) list and describe activities to achieve or maximize the value aspects, and also with the measurements;c) find the similarities and differences between China and Sweden. Methods. The data was collected by using the semi-structured interviews from 30 participants in 20Chinese agile software development organizations. We utilized the content analysis and the Statisticsmethods to analyze the 30 data points. Results. The participants identified 18 value aspects and prioritized them, and the value aspects wereanalyzed by domains and roles. The three most important value aspects are the Delivery process w.r.t.time, Organization, and Team members; different domain focused on different value aspects; the projectmanager concerned more about the Delivery process w.r.t. time, Organization, and Team members,while the product owners focused more on Customer satisfaction. Then, we list and described theactivities to achieve or maximize the value aspects, described some methods and strategies tomeasure/assure/evaluate them. Most of the activities were related to agile practices and the mostactivities were used to achieve the Delivery process w.r.t. time. Finally, we presented the similaritiesand differences between those value results from China and Sweden, the most important difference isthat the Swedish participants put the Customer value perspective at the first place, while Chineseparticipants would like to balance the value between Customer and Internal Business. Conclusions. We concluded that: 1) the Chinese participants thought that the key success factor of asoftware product was to delivery it with high quality to customers on time; 2) the main activities toachieve value were related to agile practices, and some participants used some tools to assure projectprocess; 3) For better communications and collaborations between Chinese and Swedish softwarecompanies, we recommend: a) for Chinese companies, they need to i) concern more about Customerperspective than before; ii) understand the core concepts of agile methods and their using contexts forflexible application; iii) transfer from traditional organization architecture to project-based organizationarchitecture; b) for Swedish companies, they need to i) focus more on Internal business perspective; ii)use some tools and methods to achieve their value aspects; iii) find a suitable way to collaborate betweenagile teams and non-agile teams.

Context: Software startups are newly created companies with no operating history and are extremely fast in producing cutting-edge technologies. These companies develop software un- der highly uncertain conditions, tackling fast growing markets with severe lack of resources. Startups present an unique combination of characteristics which pose several challenges to the software development activities, creating interesting problems for software engineers. However, despite the increasing economical importance and the high failure rate, there are only a few sci- entific studies attempting to address software engineering (SE) issues, especially for early-stages startups. In a context where a wrong decision can easily lead the entire business to failure, the support of SE can contribute to foster performances of startups and making a big impact on a large number of companies. Objective: In view of a lack of primary studies, the first step to attending the software development strategies with scientific and engineering approaches is by an understanding of the startups’ behavior. For this reason this research aims to understand how software development strategies are engineered by practitioners, in the period of time that goes from idea conception to the first open beta release of the software product. Methods: This research combines a systematic review of the state-of-the-art with a cross- sectional case study conducted in 13 web startups recently founded and distributed in di↵erent geographic areas and market sectors. A grounded theory approach guided the execution of a sys- tematic mapping study, integrated with semi-structured interviews and follow-up questionnaires to explore the state-of-practice. Results: We selected, classified and evaluated 37 relevant studies. The systematic review revealed that the studies which constitute the body of knowledge are generally not rigorously designed and executed, make use of inconsistent terminology, and cover only small samples of startups. Moreover, we extrapolated concepts from the case study to form a theoretical model, explaining the underlying phenomenon of software development in early-stage startups. The model is grounded in the empirical data and its explanatory power was further validated through a systematic procedure. Finally we proposed a multi-faceted evolutionary model to describe the dynamics of the software development after the first product release. Conclusions: The research provided a wide set of evidences fostering the understanding of how software development is structured and executed, from idea conception to the first release. The results revealed the urgent priority of startups of releasing the product as quickly as possi- ble to verify the product/market fit and to adjust the business and product trajectory according to the early collected user feedbacks. Nevertheless, the initial gain obtained in speeding-up the development by low-precision and product-centric engineering activities is counterbalanced by the need of restructuring the product and the workflows before setting o↵ for further grow. In fact, when user requests and company’s size start to increase startups face an initial and temporary drop-down in productivity, creating the need of mitigation strategies to find a sweet spot between being fast enough to enter the market early while controlling the amount of accu- mulated technical debt. The conclusions can be generalized with a good degree of confidence to the majority of early-stage software startups involved in the production of innovative products, especially for web and mobile applications.

Syftet med arbetet var att ta reda på om den ökade tidsåtgången som parprogrammeringen leder till uppvägs av de fördelar som den genererar i jämförelse med enskild programmering där arbetet delas mellan två programmerare och sedan integreras. I arbetet presenteras resultatet från en enkätundersökning som sju personer från fyra olika företag i Sverige har besvarat. Samtliga personer som besvarat enkäten har arbetat både med enskild programmering och parprogrammering. Vårt arbete bidrar till forskningsområdet programvaruteknik som intresserar sig för mjukvaruutvecklingsmetoder. På senare tid har detta forskningsområde också intresserat sig för lättrörlig mjukvaruutveckling där utvecklingsmetoden Extreme Programming (XP) ingår. XP tillämpar parprogrammering och är en mjukvaruteknisk metod som har att göra med klassisk mjukvaruteknik som bl.a. utgår ifrån kodkvalite och samspel mellan utvecklare. (Rittenbruch m.fl, 2002) I den litteratur vi läst har det presenterats en undersökning som gjorts i USA om parprogrammering. I den konstaterades att detta arbetssätt ger en ökad tidsåtgång och det framkom också ett antal fördelar med att programmera i par. Vi har utgått ifrån tidsåtgången och fördelarna när vi gjorde vår enkätundersökning. Vi fann att vår undersökning styrker de fördelar som finns med parprogrammering, men däremot bekräftar inte undersökningen att tidsåtgången ökar. Samtliga i undersökningen tycker att kodkvalitén förbättrats, dvs bättre struktur och design samt mindre fel på koden. Sammanhållningen och kommunikationen har blivit bättre och fler programmerare är involverade i samma kod. Detta innebär att projektgruppen inte påverkades så mycket när en person lämnar projektet. Det har också framkommit att parprogrammering inte är lämpligt att använda vid enklare uppgifter.

In highly iterative development processes, functionality is continuously added while existing faults are repaired simultaneously. Therefore, practitioners need means to predict the fault inflow, i.e. the number of faults at the a certain project stage, in order to allocate resources adequately. This study investigates the use of software reliability growth models (SRGMs) for predicting fault inflow. Additionally, a simple linear model is developed and compared to the SRGMs. The paper provides results from applying these models on fault data from three different industrial projects. One of the key findings of this study is that SRGMs are applicable for predicting fault inflow in highly iterative processes. Moreover, the results show that a linear model provides reasonably accurate predictions as well and therefore, represents a valid alternative to the SRGMs.

På senare tid har agila systemutvecklingsmetoder trätt fram på marknaden, metoder som värderar flexibilitet, kundmedverkan och fokus på utvecklingsteamet och fungerande mjukvara snarare än fokus på utvecklingsverktygen och dokumentation. Vi vet dock inte vilken typ av systemutvecklingsmetod som verkligen är bättre än den andra. Den här uppsatsen består av en historisk översikt av systemutvecklingsmetoder och en undersökning kring graden av belåtenhet med olika typer av systemutvecklingsmetoder och attityden till de agila värderingarna. Genom en kvantitativ studie har svenska organisationer som utövar systemutveckling tillfrågats angående detta. Resultaten är inte helt säkra, men anspelar på att utövare av mer traditionella systemutvecklingsmetoder var något mer nöjda med sin metod än utövare av agila metoder var, men de agila utövarna var istället mer nöjda med hur deras metod hjälper dem med att tillgodose kundernas behov och önskemål än de traditionella utövarna var. Båda typerna av systemutvecklare var mer positiva till de agila värderingarna än deras motsatser, men de agila metodutövarna var positiva till en större utsträckning. / Recent times have seen the emergence of agile software development methods, valuing flexibility, customer collaboration, and focus on the development team and working software rather than focus on tools and documentation. What is unknown is which type of software development method is really better than the other. This thesis consists of a historical overview of software development methods and an investigation of the level of satisfaction with different types of software development methods and the attitude towards the agile values. Through a quantitative study, Swedish software development organizations have been heard regarding these issues. The results, although not fully statistically supported, indicate that practisers of more traditional software development methods were slightly more satisfied with their methods than practisers of agile methods were, but the agile method practisers were instead more satisfied with how their method helped them in satisfying their customers’ wants and needs than the traditional method practisers were. Both types of software developers were more positive towards the agile values than their counterparts, but the practisers of agile software development methods were so to a greater extent.

Context: Internet of things (IoT) technology is rapidly increasing and changes the business environment for a software organization. There is a need to understand what are important factors of business model should a software company focus on obtaining benefits from the potential that IoT offers. This thesis also focuses on finding the impact of IoT on software business model and software industry especially on software development. Objectives: In this thesis, we do research on IoT software business model and also software industry. The objectives of this research are included as follows: 1. Summarize the current business models for IoT and to identify the important factor for IoT business models. 2. Analyze the impact of IoT on software business models. 3. Analyze the impact of IoT on Software development especially on requirement engineering. 4. Provide recommendations how requirements engineering are connected to provide better support business modeling for IoT. Methods: We conducted a systematic literature review based on the guidelines suggested by Wohlin, to find the current business model for the IoT. Next, we designed and executed an industrial survey to explore the impact of IoT on a software business model and software development.The results of survey were statistically analyzed using descriptive statistics, chi-square test of significance and Friedman test. Results: 21 peer reviewed papers were identified which were analyzed in relation to their rigor and relevance. From the literature reviews, results indicate 9 business model elements are being focused on the IoT business models. In addition to this 4 most important business model factors were identified. On the other hand, the industrial survey resulted from 56 survey responses, identified that value proposition is the most important element for the IoT business model. It was also observed that even the impact is high for the value proposition. Regarding the software development, customer demands is highly impactful and moreover, the results suggest that requirement management is highly impactful. Conclusions: The current software business models were found for the IoT industries. In additional the software business model elements which were majorly focused in the IoT industries were also identified and the most important factor which brings the value for IoT business models were also discussed. Furthermore the impact of IoT on software business model element and software development, especially on the requirement phase, was analyzed and discussed. This helps the practitioners to understand the impact of IoT on software business models and software industry and helps the organization to improve IoT business to its full potential.

The research presented is motivated by the demand for process improvement for companies active within software development. High demands on software quality are a reality. At the same time, short development time and low effort consumption are required. This stresses the necessity for process improvement. Empirical research methods and close cooperation with the industry partner addressed the research challenge. The research presented in this thesis shows how the analysis of faults through fault classification can be used to determine suitable and required process improvements. Two alternatives are investigated. First, a lightweight approach, and second a fault classification approach targeting all faults. The suitability of the fault classification is stressed as well as the importance of assigning the correct fault class. The latter is determined by classifier agreement calculations. Additionally, the research proposes that the appropriate occasion for a correct fault classification is alleged to be when the fault is corrected. The research also introduces an approach to tailor the verification and validation process. The tailoring process suggested considers the functionality characteristics and the software entity complexity in terms of couplings. This is used to select the appropriate and efficient process for verification and validation.