Endre søk
Begrens søket
3456789 251 - 300 of 637
RefereraExporteraLink til resultatlisten
Permanent link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Treff pr side
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sortering
  • Standard (Relevans)
  • Forfatter A-Ø
  • Forfatter Ø-A
  • Tittel A-Ø
  • Tittel Ø-A
  • Type publikasjon A-Ø
  • Type publikasjon Ø-A
  • Eldste først
  • Nyeste først
  • Skapad (Eldste først)
  • Skapad (Nyeste først)
  • Senast uppdaterad (Eldste først)
  • Senast uppdaterad (Nyeste først)
  • Disputationsdatum (tidligste først)
  • Disputationsdatum (siste først)
  • Standard (Relevans)
  • Forfatter A-Ø
  • Forfatter Ø-A
  • Tittel A-Ø
  • Tittel Ø-A
  • Type publikasjon A-Ø
  • Type publikasjon Ø-A
  • Eldste først
  • Nyeste først
  • Skapad (Eldste først)
  • Skapad (Nyeste først)
  • Senast uppdaterad (Eldste først)
  • Senast uppdaterad (Nyeste først)
  • Disputationsdatum (tidligste først)
  • Disputationsdatum (siste først)
Merk
Maxantalet träffar du kan exportera från sökgränssnittet är 250. Vid större uttag använd dig av utsökningar.
  • 251.
    Johansson, Eric
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Adapting the web: Analysis of guidelines for responsive design2019Independent thesis Basic level (university diploma), 10 poäng / 15 hpOppgave
    Abstract [en]

    Smartphone usage is higher than ever and the number is steadily increasing, but not all websites on the Internet are adapted for use on smartphones. This study set out to find common and proven guidelines from the current scientific literature and create a guide on how to best adapt a desktop website to be optimized for use on smartphones. Areas of research were usability, readability and energy saving. A literature review of the body of data on the subject was reviewed and the result was put in a list of guidelines. The guidelines were used to compare the desktop version versus the smartphone version on 5 frequently visited websites.

       The result was summarized with a score for each website and their respective solution for displaying components on small screens was noted. A prototype website was constructed in two versions: one responsive and one unresponsive. The prototype website’s different versions were then tested by a group of testers. The result of the tests concluded that the guidelines raised user satisfaction and readability. Sufficient energy saving metrics could not be extracted in the way design and usability was tested and had to be excluded from the testing.

       The list of guidelines showed that there are solutions for solving readability, usability issues  and energy-saving issues on smartphones. The testing concluded that there was an increase in text readability and usability of the website when the guidelines were implemented. Further testing of energy saving must be conducted to test the validity of the remaining untested  guidelines.

  • 252.
    Johnell, Carl
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Parallel programming in Go and Scala: A performance comparison2015Independent thesis Basic level (degree of Bachelor), 10 poäng / 15 hpOppgave
    Abstract [en]

        This thesis provides a performance comparison of parallel programming in Go and Scala. Go supports concurrency through goroutines and channels. Scala have parallel collections, futures and actors that can be used for concurrent and parallel programming. The experiment used two different types of algorithms to compare the performance between Go and Scala. Parallel versions of matrix multiplication and matrix chain multiplication were implemented with goroutines and channels in Go. Matrix multiplication was implemented with parallel collections and futures in Scala, and chain multiplication was implemented with actors.

        The results from the study shows that Scala has better performance than Go, parallel matrix multiplication was about 3x faster in Scala. However, goroutines and channels are more efficient than actors. Go performed better than Scala when the number of goroutines and actors increased in the benchmark for parallel chain multiplication.

        Both Go and Scala have features that makes parallel programming easier, but I found Go as a language was easier to learn and understand than Scala. I recommend anyone interested in Go to try it out because of its ease of use.

  • 253.
    Jonarv Hultgren, Susanne
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Tennevall, Philip
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Saving resources through smart farming: An IoT experiment study2019Independent thesis Basic level (degree of Bachelor), 10 poäng / 15 hpOppgave
    Abstract [en]

    Context: Smart farming, agritech, is growing in popularity and is starting to develop rapidly with some already existing technology that is implemented in agriculture for both industrial and private use.

    Objectives: The goal of this thesis is to investigate the benefits and issues with implementing technology in agriculture, agritech. In this thesis the investigation and research is performed by conduction a literature study and an experiment.

    Realization: A prototype was created to monitor the soil moisture level and calculating the average soil moisture value, then water the plants when needed. This was then compared to a manually watered pot to investigate if agritech could reduce the water usage when maintaining plants.

    Results: The result of the experiment indicates that it is possible to improve the use of resources such as human labor, time spent on maintaining the plants and water usage.

    Conclusions: The conclusion of this thesis is with the help of agritech, human workers can spend more time on other tasks and maintain the technology implemented. Instead of observing the plants to see if they need watering and watering them manually. Water usage may also be minimized with the help of sensors that make sure the plants only get watered when needed by constantly checking the soil moisture level.

  • 254.
    Josyula, Jitendra
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Panamgipalli, Sarat
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Usman, Muhammad
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Britto, Ricardo
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Ali, Nauman bin
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software Practitioners' Information Needs and Sources: A Survey Study2018Inngår i: Proceedings - 2018 9th International Workshop on Empirical Software Engineering in Practice, IWESEP 2018, IEEE , 2018, s. 1-6Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Software engineering practitioners have information needs to support strategic, tactical and operational decision-making. However, there is scarce research on understanding which information needs exist and how they are currently fulfilled in practice. This study aims to identify the information needs, the frequency of their occurrence, the sources of information used to satisfy the needs, and the perception of practitioners regarding the usefulness of the sources currently used. For this purpose, a literature review was conducted to aggregate the current state of understanding in this area. We built on the results of the literature review and developed further insights through in-depth interviews with 17 practitioners. We further triangulated the findings from these two investigations by conducting a web-based survey (with 83 completed responses). Based on the results, we infer that information regarding product design, product architecture and requirements gathering are the most frequently faced needs. Software practitioners mostly use blogs, community forums, product documentation, and discussion with colleagues to address their information needs.

  • 255.
    Josyula, Jitendra Rama Aswadh
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Panamgipalli, Soma Sekhara Sarat Chandra
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Identifying the information needs and sources of software practitioners.: A mixed method approach.2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context. Every day software practitioners need information for resolving a number of questions. This information need should be identified and addressed in order to successfully develop and deliver a software system. One of the ways to address these information needs is to make use of some information sources like blogs, websites, documentation etc. Identifying the needs and sources of software practitioners can improve and benefit the practitioners as well as the software development process. But the information needs and sources of software practitioners are partially studied and rather it is mostly focused on the knowledge management in software engineering. So, the current context of this study is to identify the information needs and information sources of software practitioners and also to investigate the practitioner’s perception on different information sources.           

    Objectives. In this study we primarily investigated some of the information needs of software practitioners and the information sources that they use to fulfill their needs. Secondly we investigated the practitioner’s perception on available information sources by identifying the aspects that they consider while using different information sources. 

    Methods. To achieve the research objectives this study conducted an empirical investigation by performing a survey, with two data collection techniques. A simple literature review was also performed initially to identify some of the information needs and sources of software practitioners. Then we started survey by conducting the semi-structured interviews, based on the data obtained from the literature. Moreover, an online questionnaire was designed, after conducting the preliminary analysis of the data obtained from both the interviews and literature review. Coding process of grounded theory was used for analyzing the data obtained from the interviews and descriptive statistics were used for analyzing the data obtained from the online questionnaire. The data obtained from both the qualitative and quantitative methods is triangulated by comparing the identified information needs and sources with those that are presented in the literature. 

    Results. From the preliminary literature review, we identified seven information needs and six information sources. Based on the results of the literature review, we then conducted interviews with software practitioners and identified nine information needs and thirteen information sources. From the interviews we also investigated the aspects that software practitioners look into, while using different information sources and thus we identified four major aspects. We then validated the results from the literature review and interviews with the help of an online questionnaire. From the online questionnaire, we finally identified the frequency of occurrence of the identified information needs and the frequency of use of different information sources.     

    Conclusions. We identified that the software practitioners are currently facing nine type of information needs, out of which, information on clarifying the requirements and information on produce design and architecture are the most frequently faced needs. To address these needs most of the practitioners are using the information sources like blogs and community forums, product documentation and discussion with colleagues. While the research articles are moderately used and the IT magazines and social networking sites are least used to address their needs. We also identified that most of the practitioners consider the reliability/accuracy of the information source as an extremely important factor. The identified information needs and sources along with the practitioner’s perception are clearly elucidated in the document.

    A future direction of this work could be, testing the applicability of the identified information needs by extending the sample population. Also, there is a scope for research on how the identified information needs can be minimized to make the information acquisition more easy for the practitioners. 

  • 256.
    Kabir, Md Alamdir
    et al.
    City University of Hong Kong, CHN.
    Keung, Jacky Wai
    City University of Hong Kong, CHN.
    Bennin, Kwabena Ebo
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Zhang, Miao
    City University of Hong Kong, CHN.
    Assessing the significant impact of concept drift in software defect prediction2019Inngår i: Proceedings - International Computer Software and Applications Conference, IEEE Computer Society , 2019, s. 53-58Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Concept drift is a known phenomenon in software data analytics. It refers to the changes in the data distribution over time. The performance of analytic and prediction models degrades due to the changes in the data over time. To improve prediction performance, most studies propose that the prediction model be updated when concept drift occurs. In this work, we investigate the existence of concept drift and its associated effects on software defect prediction performance. We adopt the strategy of an empirically proven method DDM (Drift Detection Method) and evaluate its statistical significance using the chi-square test with Yates continuity correction. The objective is to empirically determine the concept drift and to calibrate the base model accordingly. The empirical study indicates that the concept drift occurs in software defect datasets, and its existence subsequently degrades the performance of prediction models. Two types of concept drifts (gradual and sudden drifts) were identified using the chi-square test with Yates continuity correction in the software defect datasets studied. We suggest concept drift should be considered by software quality assurance teams when building prediction models. © 2019 IEEE.

  • 257.
    Kaliniak, Paweł
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik. Wrocław University of Technology.
    Conversion of SBVR Behavioral Business Rules to UML Diagrams: Initial Study of Automation2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context. Automation of conversion of business rules into source code in software development project can reduce time and effort in phase of development. In this thesis we discuss automatic conversion of behavioral business rules defined in Semantics of Business Vocabulary and Rules (SBVR) standard, to fragments of Unified Modeling Language diagrams: activity, sequence and state machine. It is conversion from Computation Independent Model (CIM) into Platform Independent Model (PIM) levels defined by Model Driven Architecture (MDA). PIM in MDA can be further transformed into Platform Specific Model which is prepared for source code generation.

    Objectives. Aim of this thesis is to initially explore field of automatic conversion of behavioral business rules - conversion from SBVR representation to fragments of UML diagrams. It is done by fulfilment of objectives defined as following:

    -To find out properties of SBVR behavioral rule which ensure that the rule can be automatically converted to parts of UML behavioral diagrams (activity, sequence, state machine).

    -To propose mapping of SBVR contructs to constructs of UML behavioral diagrams.

    -To prepare guidelines which help to specify SBVR behavioral business rules in such way that they can be automatically transformed into fragments of selected UML behavioral diagrams.

    Methods. Expert opinion and case study were applied. Business analysts from industry and academia were asked to convert set of SBVR behavioral business rules to UML behavioral diagrams: activity, sequence and state machine. Analysis of the set of business rules and their conversions to UML diagrams was basis for fulfilment of objectives.

    Results. 2 syntax and 3 semantic properties were defined. Conversion rules which define mapping for SBVR behavioral business rules constructs to UML constructs were defined: 5 rules for conversion to activity diagram, 6 for conversion to sequence diagram, 5 for conversion to state machine diagram. 6 guidelines which are intended to help in specification of behavioral business rules that can be automatically transformed into UML diagrams according to the presented conversion rules, were defined.

    Conclusions. Research performed in this thesis is initial study of automatic conversion of behavioral business rules from SBVR notation to UML behavioral diagrams notation. Validation of defined properties, conversion rules and guidelines can be done in industry as future work. Re-execution of research for larger and more diverse set/sets of behavioral business rules taken from industry projects, sufficiently broad access to business analysts from industry and academia could help to improve results.

  • 258. Kalinowski, Marcos
    et al.
    Mendes, Emilia
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Travassos, G.H.
    An industry ready defect causal analysis approach exploring Bayesian networks2014Inngår i: Lecture Notes in Business Information Processing, Vienna: Springer , 2014, Vol. 166, s. 12-33Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Defect causal analysis (DCA) has shown itself an efficient means to improve the quality of software processes and products. A DCA approach exploring Bayesian networks, called DPPI (Defect Prevention-Based Process Improvement), resulted from research following an experimental strategy. Its conceptual phase considered evidence-based guidelines acquired through systematic reviews and feedback from experts in the field. Afterwards, in order to move towards industry readiness the approach evolved based on results of an initial proof of concept and a set of primary studies. This paper describes the experimental strategy followed and provides an overview of the resulting DPPI approach. Moreover, it presents results from applying DPPI in industry in the context of a real software development lifecycle, which allowed further comprehension and insights into using the approach from an industrial perspective.

  • 259.
    Kancharla, Akshitha
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Pannala, Akhil
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Factors for Accelerating the Development Speed in Systems of Artificial Intelligence2019Independent thesis Advanced level (degree of Master (One Year)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Background: With the increase in the application of Artificial Intelligence, there is an urge to find ways to increase the development speed of these systems (time-to-market). Because time is one of the most expensive and valuable resources in software development. Faster development speed is essential for companies to survive. There are articles in the literature that states the factors/antecedents for improving the development speed in Traditional Software Engineering. However, we cannot draw direct conclusions from these factors because development in Traditional Software Engineering and Artificial Intelligence differ.

    Objectives: The primary objectives of this research are: a) Conduct a literature review to identify the list of factors that affect the speed of Traditional Software Engineering. b) Perform an In-depth interview study to evaluate whether the listed factors of Traditional Software Engineering can be applied in accelerating the development of AI systems engineering.

    Methods: The method chosen to address the research question 1 is the Systematic Literature Review. The reason for selecting Systematic Literature Review (SLR) is that we follow specific well-defined structure to identify, analyze and interpret the data about the research question with the evidence. The search strategy Snowballing is the best alternative for conducting SLR as per the guidelines are given by Wohlin. The method chosen to address the research question 2 is an In-depth interview study. We conduct interviews to gather information related to our research. Here, the participant is the interviewee, who may be a data scientist or project manager in the field of AI and the interviewer is a student. Each interviewee lists the factors that affect the development speed of AI systems and rank them based on their importance using Trello.

    Results: The results from the systematic literature is the list of papers that are obtained from the snowball sampling. From the collected data, factors are extracted which are then used for the interviews. The interviews are conducted based on the questionnaire that was prepared. All the interviews are recorded and then transcribed. The transcribed data is analyzed using Conventional Content Analysis.

    Conclusions: The study identifies the factors that will help accelerate the development speed of Artificial Intelligence systems. The identified factors are mostly non-technical such as team leadership, trust, etc. By selecting suitable research methods for each research question, the objectives are addressed.

  • 260.
    Karlson, Max
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Olsson, Fredrik
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Investigating the Newly Graduated StudentsExperience after University2019Independent thesis Basic level (degree of Bachelor), 10 poäng / 15 hpOppgave
    Abstract [en]

    Today’s labor market is teeming with software development jobs, and employeesare needed more than ever. With this statement, one would believe it is easy fora newly graduated student to start their career. However, according to severalstudies, there are specific areas where newly graduated Software Engineeringstudents struggle when beginning their first job. Currently, there is a displace-ment about what the school should focus on when teaching their students. Thiscauses various challenges to arise for newly graduated students when they areinitially starting their career. To address this issue, this study aims to iden-tify whether or not there exists a gap between the education provided by theuniversities, and what is expected from the industry. In accordance with this,the purpose is also the point out which areas might be challenging for newlygraduated students, and highlight how the school and industry can benefit fromthe results of this study.By conducting interviews with both newly graduated student with one to threeyears working experience or personnel responsible for hiring new employees atcompanies, this study will give an insight on which common areas newly grad-uates may struggle with. Although the result specifies several areas which arechallenging to newly graduated students. The greatest challenges which thenewly graduated graduated students faced were areas revolving around softskills. This was in accordance with the opinions of the recruiters. Insinuatingthat these areas are what the school should focus more on. Other differencesbetween the newly graduated interviewee’s opinions and the recruiters are alsohighlighted in the report Several subjects in school could improve its way ofteaching. Furthermore, there are possibilities for companies to better adjusttheir on-boarding of newly graduated. By addressing the challenges which newlygraduated face they can provide their new employees with a better understand-ing of how to properly work and function in the industry today.

  • 261.
    Karlsson, Jan
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Eriksson, Patrik
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    How the choice of Operating System can affect databases on a Virtual Machine2014Independent thesis Basic level (degree of Bachelor)Oppgave
    Abstract [en]

    As databases grow in size, the need for optimizing databases is becoming a necessity. Choosing the right operating system to support your database becomes paramount to ensure that the database is fully utilized. Furthermore with the virtualization of operating systems becoming more commonplace, we find ourselves with more choices than we ever faced before. This paper demonstrates why the choice of operating system plays an integral part in deciding the right database for your system in a virtual environment. This paper contains an experiment which measured benchmark performance of a Database management system on various virtual operating systems. This experiment shows the effect a virtual operating system has on the database management system that runs upon it. These findings will help to promote future research into this area as well as provide a foundation on which future research can be based upon.

  • 262.
    Karras, Oliver
    et al.
    Gottfried Wilhelm Leibniz Universität, DEU.
    Schneider, Kurt
    Gottfried Wilhelm Leibniz Universität, DEU.
    Fricker, Samuel
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Representing software project vision by means of video: A quality model for vision videos2020Inngår i: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, artikkel-id 110479Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Establishing a shared software project vision is a key challenge in Requirements Engineering (RE). Several approaches use videos to represent visions. However, these approaches omit how to produce a good video. This missing guidance is one crucial reason why videos are not established in RE. We propose a quality model for videos representing a vision, so-called vision videos. Based on two literature reviews, we elaborate ten quality characteristics of videos and five quality characteristics of visions which together form a quality model for vision videos that includes all 15 quality characteristics. We provide two representations of the quality model: (a) a hierarchical decomposition of vision video quality into the quality characteristics and (b) a mapping of these characteristics to the video production and use process. While the hierarchical decomposition supports the evaluation of vision videos, the mapping provides guidance for video production. In an evaluation with 139 students, we investigated whether the 15 characteristics are related to the overall quality of vision videos perceived by the subjects from a developer's the point of view. Six characteristics (video length, focus, prior knowledge, clarity, pleasure, and stability) correlated significantly with the likelihood that the subjects perceived a vision video as good. These relationships substantiate a fundamental relevance of the proposed quality model. Therefore, we conclude that the quality model is a sound basis for future refinements and extensions. © 2019 Elsevier Inc.

  • 263.
    Kartheek arun sai ram, chilla
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Kavya, Chelluboina
    Investigating Metrics that are Good Predictors of Human Oracle Costs An Experiment2017Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context. Human oracle cost, the cost associated in estimating the correctness of the output for the given test inputs is manually evaluated by humans and this cost is significant and is a concern in the software test data generation field. This study has been designed in the context to assess metrics that might predict human oracle cost.

    Objectives. The major objective of this study is to address the human oracle cost, for this the study identifies the metrics that are good predictors of human oracle cost and can further help to solve the oracle problem. In this process, the identified suitable metrics from the literature are applied on the test input, to see if they can help in predicting the correctness of the output for the given test input. Methods. Initially a literature review was conducted to find some of the metrics that are relevant to the test data. Besides finding the aforementioned metrics, our literature review also tries to find out some possible code metrics that can be ap- plied on test data. Before conducting the actual experiment two pilot experiments were conducted. To accomplish our research objectives an experiment is conducted in the BTH university with master students as sample population. Further group interviews were conducted to check if the participants perceive any new metrics that might impact the correctness of the output. The data obtained from the experiment and the interviews is analyzed using linear regression model in SPSS suite. Further to analyze the accuracy vs metric data, linear discriminant model using SPSS pro- gram suite was used.

    Results.Our literature review resulted in 4 metrics that are suitable to our study. As our test input is HTML we took HTML depth, size, compression size, number of tags as our metrics. Also, from the group interviews another 4 metrics are drawn namely number of lines of code and number of <div>, anchor <a> and paragraph <p> tags as each individual metric. The linear regression model which analyses time vs metric data, shows significant results, but with multicollinearity effecting the result, there was no variance among the considered metrics. So, the results of our study are proposed by adjusting the multicollinearity. Besides, the above analysis, linear discriminant model which analyses accuracy vs metric data was conducted to predict the metrics that influences accuracy. The results of our study show that metrics positively correlate with time and accuracy.

    Conclusions. From the time vs metric data, when multicollinearity is adjusted by applying step-wise regression reduction technique, the program size, compression size and <div> tag are influencing the time taken by sample population. From accuracy vs metrics data number of <div> tags and number of lines of code are influencing the accuracy of the sample population. 

  • 264. Kashfi, P.
    et al.
    Feldt, Robert
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Nilsson, A.
    Berntsson Svensson, Richard
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    A conceptual ux-aware model of requirements2016Inngår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), Springer, 2016, Vol. 9856 LNCS, s. 234-245Konferansepaper (Fagfellevurdert)
    Abstract [en]

    User eXperience (UX) is becoming increasingly important for success of software products. Yet, many companies still face various challenges in their work with UX. Part of these challenges relate to inadequate knowledge and awareness of UX and that current UX models are commonly not practical nor well integrated into existing Software Engineering (SE) models and concepts. Therefore, we present a conceptual UX-aware model of requirements for software development practitioners. This layered model shows the interrelation between UX and functional and quality requirements. The model is developed based on current models of UX and software quality characteristics. Through the model we highlight the main differences between various requirement types in particular essentially subjective and accidentally subjective quality requirements. We also present the result of an initial validation of the model through interviews with 12 practitioners and researchers. Our results show that the model can raise practitioners’ knowledge and awareness of UX in particular in relation to requirement and testing activities. It can also facilitate UX-related communication among stakeholders with different backgrounds. © IFIP International Federation for Information Processing 2016.

  • 265.
    Kashfi, Pariya
    et al.
    Chalmers; Gothenburg Univ, SWE.
    Feldt, Robert
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Nilsson, Agneta
    Chalmers; Gothenburg Univ, SWE.
    Berntsson Svensson, Richard
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Evidence-based Timelines for User eXperience Software Process Improvement Retrospectives2016Inngår i: 2016 42ND EUROMICRO CONFERENCE ON SOFTWARE ENGINEERING AND ADVANCED APPLICATIONS (SEAA), IEEE Computer Society, 2016, s. 59-62Konferansepaper (Fagfellevurdert)
    Abstract [en]

    We performed a retrospective meeting at a case company to reflect on its decade of Software Process Improvement (SPI) activities for enhancing UX integration. We supported the meeting by a pre-generated timeline of the main activities. This approach is a refinement of a similar approach that is used in Agile projects to improve effectiveness and decrease memory bias of retrospective meetings. The method is evaluated through gathering practitioners' view using a questionnaire. We conclude that UX research and practice can benefit from the SPI body of knowledge. We also argue that a cross-section evidence-based timeline retrospective meeting is useful for enhancing UX work in companies, especially for identifying and reflecting on `organizational issues'. This approach also provides a cross-section longitudinal overview of the SPI activities that cannot easily be gained in other common SPI learning approaches.

  • 266.
    Kasraee, Pezhman
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Lin, Chong
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Readability of Method Chains: A Controlled Experiment with Eye Tracking Approach2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context. Source codes with lower level of readability impose a higher cost to software maintainability. Research also exposed the importance of readability as a vital factor on software maintainability. Therefore, readability has recently investigated by software engineers. Readability involves human’s interactions making the study on readability difficult. In this study, we explore the readability of method chain and non-method chain in Java source codes with the means of an eye tracking device as a newly-introduced approach.

    Objectives. Objectives of this study are: 1. we investigated if the number of methods in a method chain affects the readability of Java source codes, and 2. we investigated the readability of two programming styles: method chain and non-method chain.

    Methods. To achieve both objectives of this study, two controlled experiments were conducted inside a laboratory with the means of an eye tracker device. In the first experiment, treatment groups were exposed separately to method chains with different number of methods. In the second experiment, the treatment groups were exposed separately to two different programming styles: method chain and non-method chain.

    Results. Participants of this study were students with the average age of 24.56 years old. Fixation durations of participants’ reading was measured in millisecond (ms). In the first experiment, the average of fixation durations per method with lower number of methods was 600.93 ms, and with higher number of methods was 411.53 ms. In the second experiment, the average of fixation durations per method for non-method chain style was 357.94 ms, and for method chain style was 411.53 ms.

    Conclusions. In the first experiment, the analysis of fixation durations indicates that method chains with higher number of methods are slightly more readable. Analysis of t-test (t − value = −0.5121, significance level = 0.05, and two-tailed prob-ability) confirms that the results of the first experiment does not show a significant difference at p < 0.05. The results of the second experiment show that non-method chain style is slightly more readable in comparison with method chain style. Analysis of t-test (t − value = 3.1675, significance level = 0.05, and two-tailed probability) confirms that the results of the second experiment show a significant difference at p < 0.05.

  • 267.
    Kelkkanen, Viktor
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Implementation and Evaluation of Positional Voice Chat in a Massively Multiplayer Online Role Playing Game2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Computer games, especially Massively Multiplayer Online Role Playing Games, have elements where communication between players is of great need. This communication is generally conducted through in-game text chats, in-game voice chats or external voice programs. In-game voice chats can be constructed to work in a similar way as talking does in real life. When someone talks, anyone close enough to that person can hear what is said, with a volume depending on distance. This is called positional or spatial voice chat in games. This differs from the commonly implemented voice chat where participants in conversations are statically defined by a team or group belonging. Positional voice chat has been around for quite some time in games and it seems to be of interest for a lot of users, despite this, it is still not very common.

    This thesis investigates impacts of implementing a positional voice chat in the existing MMORPG Mortal Online by Star Vault. How is it built, what are the costs, how many users can it support and what do the users think of it? These are some of the questions answered within this project.

    The design science research method has been selected as scientific method. A product in form of a positional voice chat library has been constructed. This library has been integrated into the existing game engine and its usage has been evaluated by the game’s end users.

    Results show a positional voice system that in theory supports up to 12500 simultaneous users can be built from scratch and be patched into an existing game in less than 600 man-hours. The system needs third-party libraries for threading, audio input/output, audio compression, network communication and mathematics. All libraries used in the project are free for use in commercial products and do not demand code using them become open source.

    Based on a survey taken by more than 200 users, the product received good ratings on Quality of Experience and most users think having a positional voice chat in a game like Mortal Online is important. Results show a trend of young and less experienced users giving the highest average ratings on quality, usefulness and importance of the positional voice chat, suggesting it may be a good tool to attract new players to a game.

  • 268.
    Kettunen, Petri
    et al.
    University of Helsinki, FIN.
    Laanti, Maarit
    Nitor Delta, FIN.
    Fagerholm, Fabian
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Mikkonen, Tommi
    University of Helsinki, FIN.
    Agile in the Era of Digitalization: A Finnish Survey Study2019Inngår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) / [ed] Franch X.,Mannisto T.,Martinez-Fernandez S., Springer , 2019, Vol. 11915, s. 383-398Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Agile software development has been applied since the early 2000s. It is now mainstream industrial practice in information and communication technology (ICT) companies and IT organizations. However, recently increasing and even disruptive digitalization has brought new drivers and needs for agility both in software organizations as well as in traditional companies, which are becoming more and more software-intensive. Following that line of developments, based on our recent survey conducted in Finland in 2018, in this paper we explore the current state of the affairs with respect to how different organizations currently address agility and agile development in both IT and non-software industrial sectors. The results show that operative goals (productivity, quality) are considered the most important ones to achieve by agile means. Scrum, Kanban and DevOps are the most frequently reported methods, and SAFe is the dominant scaling model. Lead time metrics are the most typically followed measurements. The operative goals as well as responsiveness are also the most highly ranked future aims. The impacts of digitalization are considered substantial but agile developments are seen to address them well. As a conclusion of this survey study, there is no “one agile way” for all. Different organizations seem to emphasize multiple aspects of agility when they develop, adapt and even transform themselves. Yet, also many commonalities were indicated. © Springer Nature Switzerland AG 2019.

  • 269.
    Khan, Rizwan Bahrawar
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Comparative Study of Performance Testing Tools: Apache JMeter and HP LoadRunner2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Software Testing plays a key role in Software Development. There are two approaches to software testing i.e. Manual Testing and Automated Testing which are used to detect the faults. There are numbers of automated software testing tools with different purposes but it is always a problem to select a software testing tool according to the needs. In this research, the author compares two software testing tools i.e. Apache JMeter and HP LoadRunner to determine their usability and efficiency. To compare the tools, different parameters were selected which guide the tool evaluation process. To complete the objective of the research, a scenario-based survey is conducted and two different web applications were tested. From this research, it is found that Apache JMeter got an edge over HP Loadrunner in different aspects which include installation, interface and learning.

  • 270. Khurum, Mahvish
    et al.
    Fricker, Samuel
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    The Contextual Nature of Innovation: An Empirical Investigation of Three Software Intensive Products2015Inngår i: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 57, nr 1Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Context: New products create significant opportunities for differentiation and competitive advantage. To increase the chances of new product success, a universal set of critical activities and determinants have been recommended. Some researchers believe, however, that these factors are not universal, but are contextual. Objective: This paper reports innovation processes followed to develop three software intensive products for understanding how and why innovation practice is dependent on innovation context. Method: This paper reports innovation processes and practices with an in-depth multi-case study of three software product innovations from Ericsson, IBM, and Rorotika. It describes the actual innovation processes followed in the three cases and discusses the observed innovation practice and relates it to state-of-the-art. Results: The cases point to a set of contextual factors that influence the choice of innovation activities and determinants for developing successful product innovations. The cases provide evidence that innovation practice cannot be standardized, but is contextual in nature. Conclusion: The rich description of the interaction between context and innovation practice enables future investigations into contextual elements that influence innovation practice, and calls for the creation of frameworks enabling activity and determinant selection for a given context – since one size does not fit all.

  • 271. Khurum, Mahvish
    et al.
    Petersen, Kai
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Extending value stream mapping through waste definition beyond customer perspective2014Inngår i: Journal of Software: Evolution and Process, ISSN 2047-7481, Vol. 26, nr 12, s. 1074-1105Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Value Stream Mapping is one of the several Lean practices, which has recently attracted interest in the software engineering community. In other contexts (such as military, health, production), Value Stream Mapping has achieved considerable improvements in processes and products. The goal is to also leverage on these benefits in the software intensive product development context. The primary contribution is that we are extending the definition of waste to fit in the software intensive product development context. As traditionally in Value Stream Mapping everything that is not considered valuable is waste, we do this practically by looking at value beyond the customer perspective, and using the Software Value Map. A detailed illustration, via application in an industrial case at Ericsson AB, demonstrates usability and usefulness of the proposed extension. The case study results consist of two parts. First, the instantiation and motivations for selecting certain strategies have been provided. Second, the outcome of the value stream map is described in detail. Overall, the conclusion is that this case study indicates that Value Stream Mapping and the integration with the Software Value Map is useful in a software intensive product development context. In a retrospective the value stream approach was perceived positively by the practitioners with respect to process and outcome.

  • 272.
    Kihlström, Kalle
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Responsive Images: A comparison of responsive image techniques with a focus on performance2016Independent thesis Basic level (degree of Bachelor), 10 poäng / 15 hpOppgave
    Abstract [en]

    This bachelor thesis dives into the topic of responsive images on the web. With more and more devices different devices accessing the web all with different conditions, serving the right image for each and every device is an important matter. This thesis looks into the topic and compares a few available techniques that potentially could solve this problem of providing the right image.

    This thesis will include a literature study as well as an experiment. When both these parts are done they will be presented, analyzed and summarized for the reader. The experiment is a performance benchmark of two different responsive image techniques, a non responsive image alternative is also tested in order to have something to evaluate the responsive image techniques with and see how big of a difference the techniques can make.

    Ultimately both responsive image techniques put through the experiment performed relatively even and both showed huge improvements in terms of performance over the non responsive alternative.

  • 273.
    Kitamura, Takashi
    et al.
    National Institute of Advanced Industrial Science and Technology, JPN.
    Alégroth, Emil
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Ramler, Rudolf
    Software Competence Center Hagenber, AUT.
    Industry-Academia Collaboration in Software Testing: An Overview of TAIC PART 20172017Inngår i: Proceedings - 10th IEEE International Conference on Software Testing, Verification and Validation Workshops, ICSTW 2017, Institute of Electrical and Electronics Engineers Inc. , 2017, s. 42-43Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Collaboration between industry and academia in software testing leads to improvement and innovation in industry, and it is the basis for achieving transferable and empirically evaluated results. Thus, the aim of TAIC PART is to forge collaboration between industry and academia on the challenging and exciting problem of real-world software testing. The workshop is promoted by representatives of both industry and academia, bringing together industrial software engineers and testers with researchers working on theory and practice of software testing. We present an overview of the 12th Workshop on Testing: Academia-Industry Collaboration, Practice and Research Techniques (TAIC PART 2017) and its contributions. © 2017 IEEE.

  • 274. Kittlaus, Hans-Bernd
    et al.
    Fricker, Samuel
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software Product Management: The ISPMA-Compliant Study Guide and Handbook2017Bok (Annet vitenskapelig)
    Abstract [en]

    This book gives a comprehensive overview on Software Product Management (SPM) for beginners as well as best practices, methodology and in-depth discussions for experienced product managers. This includes product strategy, product planning, participation in strategic management activities and orchestration of the functional units of the company. The book is based on the results of the International Software Product Management Association (ISPMA) which is led by a group of SPM experts from industry and research with the goal to foster software product management excellence across industries. This book can be used as textbook for ISPMA-based education and as guide for anybody interested in SPM as one of the most exciting and challenging disciplines in the business of software.

  • 275.
    Klotins, Erik
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software engineering knowledge areas in startup companies: A mapping study2015Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Background – Startup companies are becoming important suppliers of innovative and software intensive products. The failure rate among startups is high due to lack of resources, immaturity, multiple influences and dynamic technologies. However, software product engineering is the core activity in startups, therefore inadequacies in applied engineering practices might be a significant contributing factor for high failure rates. Aim – This study identifies and categorizes software engineering knowledge areas utilized in startups to map out the state-of-art, identifying gaps for further research. Method – We perform a systematic literature mapping study, applying snowball sampling to identify relevant primary studies. Results – We have identified 54 practices from 14 studies. Although 11 of 15 main knowledge areas from SWEBOK are covered, a large part of categories is not. Conclusions – Existing research does not provide reliable support for software engineering in any phase of a startup life cycle. Transfer of results to other startups is difficult due to low rigor in current studies. © Springer International Publishing Switzerland 2015.

  • 276.
    Klotins, Eriks
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software Engineering in Start-up Companies2019Doktoravhandling, med artikler (Annet vitenskapelig)
    Abstract [en]

    Start-up companies have emerged as suppliers of innovation and software-intensive products. Small teams, lack of legacy products, experimental nature, and absence of any organizational processes enable start-ups to develop and market new products and services quickly. However, most start-ups fail before delivering any value. Start-up failures can be attributed to market factors, shortcomings in business models, lack of motivation, or self-destruction, among other reasons. However, inadequacies in product engineering precede any market or business-related challenges and could be a significant contributing factor to start-up failures. At the same time, state-of-the-art software engineering (SE) practices are often neglected by start-ups as inadequate. At the beginning of this work, SE in start-ups had attracted very little attention from researchers. Thus, there was no coherent view of SE state-of-practice in start-ups and no starting point for a focused investigation.

     

    In this thesis, we explore how start-ups practice SE, what specific SE challenges should be addressed, and what new SE practices are needed to support the engineering of innovative software-intensive products and services.

     

    A substantial part of this work is exploratory and aimed to explore SE state-of-practice in start-ups. Our initial findings suggest that start-ups overlook the best SE practices. Teams of a few people working on relatively experimental and straightforward software see no upside of following the best practices. However, late start-ups face substantial challenges as their teams grow, and products become more complex. The key difficulties concern installing adequate SE practices supporting collaboration, coordination of work, and management of accumulated technical debt. To support the evolution of engineering practices in start-ups, we propose the start-up progression model outlining engineering goals, common challenges, and useful practices with regards to the start-up life-cycle phases. Further findings suggest inadequate support for market-driven requirements engineering (MDRE). Specifically, on how to aggregate needs and wishes of a large and loosely defined set of stakeholders who may not be able to articulate their needs and expectations. To address this challenge, we propose a method for the identification and prioritization of data sources and stakeholders in MDRE. Analyzing SE context in start-ups and other organizations developing innovative and market-driven products, we have found many similarities. While start-ups have challenges, they do not appear to be unique. Thus, most start-up challenges can be addressed by transferring the best practices from other engineering contexts.

     

    We conclude that there is a little need for start-up specific engineering practices. Best software engineering practices are relevant to address challenges in start-ups. The key engineering challenge in start-ups is the management of the evolution of SE practices to match the growing complexity of the product and the organization. Our work also highlights the need for better MDRE practices to support new market-driven product development in both start-ups and other types of organizations. 

  • 277.
    Klotins, Eriks
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software start-ups through an empirical lens: Are start-ups snowflakes?2018Inngår i: CEUR Workshop Proceedings / [ed] Wang X.,Munch J.,Suominen A.,Bosch J.,Jud C.,Hyrynsalmi S., CEUR-WS , 2018Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Most of the existing research assume that software start-ups are “unique” and require a special approach to software engineering. The uniqueness of start-ups is often justified by the scarcity of resources, time pressure, little operating history, and focus on innovation. As a consequence, most research on software start-ups concentrate on exploring the start-up context and are overlooking the potential of transferring the best engineering practices from other contexts to start-ups. In this paper, we examine results from an earlier mapping study reporting frequently used terms in literature used to characterize start-ups. We analyze how much empirical evidence support each characteristic, and how unique each characteristic is in the context of innovative, market-driven, software-intensive product development. Our findings suggest that many of the terms used to describe startups originate from anecdotal evidence and have little empirical backing. Therefore, there is a potential to revise the original start-up characterization. In conclusion, we identify three potential research avenues for further work: a) considering shareholder perspective in product decisions, b) providing support for software engineering in rapidly growing organizations, and c) focusing on transferring the best engineering practices from other contexts to start-ups. © 2018 CEUR-WS. All rights reserved.

  • 278.
    Klotins, Eriks
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Using the Case Survey Method to Explore Engineering Practices in Software Start-Ups2017Inngår i: Proceedings - 2017 IEEE/ACM 1st International Workshop on Software Engineering for Startups, SoftStart 2017, Institute of Electrical and Electronics Engineers (IEEE), 2017, s. 24-26Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Software start-ups are a new and relatively unexplored field for software engineering researchers. However, conducting empirical studies with start-ups is difficult. Start-ups produce very little 'hard' evidence, thus data collection methods are limited to interviews and surveys. These methods come with their limitations, namely interview studies are not scalable to a large number of companies, and surveys are not generally applicable for exploratory studies. In this paper we present of a hybrid research method aimed to provide a compromise between breadth of a survey and depth of an interview study. The case survey method enables both qualitative and quantitative analysis of studied cases. We adapt the case survey method for use in primary studies and report experience with its application. The case survey method was successfully applied to design and launch a large scale study into engineering aspects of start-ups. We conclude that the case survey method is a promising research method to launch exploratory studies into large samples of start-up companies. © 2017 IEEE.

  • 279.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Boeva, Veselka
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Wnuk, Krzysztof
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    A collaborative method for identification and prioritization of data sources in MDREManuskript (preprint) (Annet vitenskapelig)
    Abstract [en]

    Requirements engineering (RE) literature acknowledges the importance of stakeholder identification early in the software engineering activities. However, literature overlooks the challenge of identifying and selecting the right stakeholders and the potential of using other inanimate requirements sources for RE activities for market-driven products.

    Market-driven products are influenced by a large number of stakeholders. Consulting all stakeholders directly is impractical, and companies utilize indirect data sources, e.g. documents and representatives of larger groups of stakeholders. However, without a systematic approach, companies often use easy to access or hard to ignore data sources for RE activities. As a consequence, companies waste resources on collecting irrelevant data or develop the product based on the input from a few sources, thus missing market opportunities.

    We propose a collaborative and structured method to support analysts in the identification and selection of the most relevant data sources for market-driven product engineering. The method consists of four steps and aims to build consensus between different perspectives in an organization and facilitates the identification of most relevant data sources. We demonstrate the use of the method with two industrial case studies.

    Our results show that the method can support market-driven requirements engineering in two ways: (1) by providing systematic steps to identify and prioritize data sources for RE, and (2) by highlighting and resolving discrepancies between different perspectives in an organization.

  • 280.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Chatzipetrou, Panagiota
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Prikladnicki, Rafael
    Tripathi, Nirnaya
    Bento Pompermaier, Leandro
    Use of Agile Practices in Start-upsManuskript (preprint) (Annet vitenskapelig)
    Abstract [en]

    Context. Software start-ups have shown their ability to develop and launch in- novative software products and services. Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices.

    Objective. We explore how start-ups use Agile practices and what effects can be associated with the use of those practices.

    Method. We use a case survey to analyze 84 start-up cases and 56 Agile prac- tices. We apply statistical methods to test for statistically significant associa- tions between the use of Agile practices, team, and product factors.

    Results. Our results suggest that backlog, version control, refactoring, and user stories are the most frequently reported practices. We identify 22 associations between the use of Agile practices, team, and product factors. The use of Agile practices is associated with effects on source code and overall product quality. A teams’ positive or negative attitude towards best engineering practices is a significant indicator for either adoption or rejection of certain Agile practices. To explore the relationships in our findings, we set forth a number of propositions that can be investigated by future research.

    Conclusions. We conclude that start-ups use Agile practices, however without following any specific methodology. We identify the opportunity for more fine- grained studies into the adoption and effects of individual Agile practices. Start- up practitioners could benefit from Agile practices in terms of better overall quality, tighter control over team performance and resource utilization.

  • 281.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Chatzipetrou, Panagiota
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Prikladnicki, Rafael
    Pontificia Universidade Catolica do Rio Grande do Sul, BRA.
    Tripathi, Nirnaya
    Oulun Yliopisto, Oulu, FIN.
    Pompermaier, Leandro Bento
    Pontificia Universidade Catolica do Rio Grande do Sul, BRA.
    Exploration of technical debt in start-ups2018Inngår i: Proceedings - International Conference on Software Engineering, IEEE Computer Society , 2018, s. 75-84Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Context: Software start-ups are young companies aiming to build and market software-intensive products fast with little resources. Aiming to accelerate time-to-market, start-ups often opt for ad-hoc engineering practices, make shortcuts in product engineering, and accumulate technical debt. Objective: In this paper we explore to what extent precedents, dimensions and outcomes associated with technical debt are prevalent in start-ups. Method: We apply a case survey method to identify aspects of technical debt and contextual information characterizing the engineering context in start-ups. Results: By analyzing responses from 86 start-up cases we found that start-ups accumulate most technical debt in the testing dimension, despite attempts to automate testing. Furthermore, we found that start-up team size and experience is a leading precedent for accumulating technical debt: larger teams face more challenges in keeping the debt under control. Conclusions: This study highlights the necessity to monitor levels of technical debt and to preemptively introduce practices to keep the debt under control. Adding more people to an already difficult to maintain product could amplify other precedents, such as resource shortages, communication issues and negatively affect decisions pertaining to the use of good engineering practices. © 2018 ACM.

  • 282.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Chatzipetrou, Panagiota
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Prikladniki, Rafael
    Pontificia Universidade Catolica do Rio Grande do Sul, BRA.
    Tripathi, Nirnaya
    Oulun Yliopisto, FIN.
    Pompermaier, Leandro Bento
    Pontificia Universidade Catolica do Rio Grande do Sul, BRA.
    A progression model of software engineering goals, challenges, and practices in start-ups2019Inngår i: IEEE Transactions on Software Engineering, ISSN 0098-5589, E-ISSN 1939-3520Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Context: Software start-ups are emerging as suppliers of innovation and software-intensive products. However, traditional software engineering practices are not evaluated in the context, nor adopted to goals and challenges of start-ups. As a result, there is insufficient support for software engineering in the start-up context. IEEE

  • 283.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software Engineering Anti-Patterns in Start-Ups2019Inngår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 36, nr 2, s. 118-126Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Software start-up failures are often explained with a poor business model, market issues, insufficient funding, or simply a bad product idea. However, inadequacies in software engineering are relatively unexplored and could be a significant contributing factor to the high start-up failure rate. In this paper we present the analysis of 88 start-up experience reports, revealing three anti-patterns associated with start-up progression phases. The anti-patterns address challenges of releasing the first version of the product, attracting customers, and expanding the product into new markets. The anti-patterns show that challenges and failure scenarios that appear to be business or market related are, at least partially, rooted in engineering inadequacies.

  • 284.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software engineering in start-up companies: An analysis of 88 experience reports2019Inngår i: Journal of Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 24, nr 1, s. 68-102Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Context: Start-up companies have become an important supplier of innovation and software-intensive products. The flexibility and reactiveness of start-ups enables fast development and launch of innovative products. However, a majority of software start-up companies fail before achieving any success. Among other factors, poor software engineering could be a significant contributor to the challenges experienced by start-ups. However, the state-of-practice of software engineering in start-ups, as well as the utilization of state-of-the-art is largely an unexplored area. Objective: In this study we investigate how software engineering is applied in start-up context with a focus to identify key knowledge areas and opportunities for further research. Method: We perform a multi-vocal exploratory study of 88 start-up experience reports. We develop a custom taxonomy to categorize the reported software engineering practices and their interrelation with business aspects, and apply qualitative data analysis to explore influences and dependencies between the knowledge areas. Results: We identify the most frequently reported software engineering (requirements engineering, software design and quality) and business aspect (vision and strategy development) knowledge areas, and illustrate their relationships. We also present a summary of how relevant software engineering knowledge areas are implemented in start-ups and identify potentially useful practices for adoption in start-ups. Conclusions: The results enable a more focused research on engineering practices in start-ups. We conclude that most engineering challenges in start-ups stem from inadequacies in requirements engineering. Many promising practices to address specific engineering challenges exists, however more research on adaptation of established practices, and validation of new start-up specific practices is needed. © 2018 The Author(s)

  • 285.
    Klotins, Eriks
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software-intensive product engineering in start-ups: a taxonomy2018Inngår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 35, nr 4, s. 44-52Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    Software start-ups are new companies aiming to launch an innovative product to mass markets fast with minimal resources. However a majority of start-ups fail before realizing their potential. Poor software engineering, among other factors, could be a significant contributor to the challenges experienced by start-ups.

    Very little is known about the engineering context in start-up companies. On the surface, start-ups are characterized by uncertainty, high risk and minimal resources. However, such characterization is not granular enough to support identification of specific engineering challenges and to devise start-up specific engineering practices.

    The first step towards understanding on software engineering in start-ups is definition of the Start-up Context Map - a taxonomy of engineering practices, environment factors and goals influencing the engineering process. Goal of the Start-up Context Map is to support further research on the field and to serve as an engineering decision support tool for start-ups. 

  • 286. Kocaguneli, Ekrem
    et al.
    Menzies, Tim
    Mendes, Emilia
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Transfer learning in effort estimation2015Inngår i: Journal of Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 20, nr 3, s. 813-843Artikkel i tidsskrift (Fagfellevurdert)
    Abstract [en]

    When projects lack sufficient local data to make predictions, they try to transfer information from other projects. How can we best support this process? In the field of software engineering, transfer learning has been shown to be effective for defect prediction. This paper checks whether it is possible to build transfer learners for software effort estimation. We use data on 154 projects from 2 sources to investigate transfer learning between different time intervals and 195 projects from 51 sources to provide evidence on the value of transfer learning for traditional cross-company learning problems. We find that the same transfer learning method can be useful for transfer effort estimation results for the cross-company learning problem and the cross-time learning problem. It is misguided to think that: (1) Old data of an organization is irrelevant to current context or (2) data of another organization cannot be used for local solutions. Transfer learning is a promising research direction that transfers relevant cross data between time intervals and domains.

  • 287.
    Kollu, Ravichandra Kumar
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Requirements scoping outside product lines: Systematic Literature Review and Survey2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context: Scoping is admitted as a key activity in Market Driven Software Development for handling the constant inflow of requirements. It helps in identifying the features, domains and products which help for gaining economic benefits in Software Product Line (SPL) development. Beyond SPL, managing the scope of the project is a major risk for project management. Continuously changing scope creates a congestion state to handle the requirements inflow which causes negative consequences like scope scrap and scope creep. However, for managing negative consequences caused due to requirements volatility depicts a need for work on requirements scoping outside the product line. 

    Objectives: In this study, an exploratory work is carried to identify the literature and industrial perspectives on requirements scoping outside the product line. The main objectives are:

    • Identifying the state of literature of requirements scoping outside product line and variability analysis.
    • To explore the industrial practice on requirements scoping.
    • Suggesting recommendations in improving the scoping process based on the literature and survey. 

    Methods: Systematic Literature Review (SLR) using snowballing procedure was conducted to identify the literature available on requirements scoping outside the product line. Quality assessment using rigor and relevance was performed to find the trustworthiness of the papers obtained through SLR. The data obtained through SLR was analyzed using narrative analysis. Furthermore, an industrial survey was performed using web questionnaire to identify the industrial perspective on requirements scoping. Statistical analysis was performed for analyzing the data obtained from survey. 

    Results: 23 relevant papers were identified through SLR. The results were categorized as definitions obtained, phenomena, challenges and methods/tools identified. From the finding of SLR, an industrial survey was conducted, which has obtained 93 responses. The challenges that were identified through literature were validated through survey and are prioritized. Moreover, the study identified additional challenges that are not discussed in the literature. Additionally, the approaches followed in organizations while scoping the requirements were identified through the survey.

    Conclusions: This study identified that scope creep is the most frequently occurring phenomenon that organizations are facing throughout the lifecycle of the project. In addition project delays, quality issues and project cost were identified as the most occurring scoping associated challenges. Moreover, scoping activity was identified as the continuous activity which changes significantly throughout the lifecycle. Finally, suggestions were given for improving the scoping process.

  • 288.
    Kolonko, Kamil
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Performance comparison of the most popular relational and non-relational database management systems2018Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context. Database is an essential part of any software product. With an emphasis on application performance, database efficiency becomes one of the key factors to analyze in the process of technology selection. With a development of new data models and storage technologies, the necessity for a comparison between relational and non-relational database engines is especially evident in the software engineering domain.

    Objectives. This thesis investigates current knowledge on database performance measurement methods, popularity of relational and non-relational database engines, defines characteristics of databases, approximates their average values and compares the performance of two selected database engines.Methods. In this study a number of research methods are used, including literature review, a review of Internet sources, and an experiment. Literature datasets used in the research incorporate over 100 sources including IEEE Xplore and ACM Digital Library. YCSB Benchmark was used as a direct performance comparison method in an experiment to compare OracleDB’s and MongoDB’s performance.

    Results. A list of database performance measurement methods has been defined as a result of the literature review. Two most popular database management engines, one relational and one non-relational has been identified. A set of database characteristics and a database performance comparison methodology has been identified. Performance of two selected database engines has been measured and compared.

    Conclusions. Performance comparison between two selected database engines indicated superior results for MongoDB under the experimental conditions. This database proved to be more efficient in terms of average operation latency and throughput for each of the measured workloads. OracleDB however, presented stable results in each of the category leaving the final choice of database to the specifics of a software engineering project. Activities required for the definition of database performance comparison methodology proved to be challenging and require study extension.

  • 289.
    Kommineni, Mohanarajesh
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Parvathi, Revanth
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    RISK ANALYSIS FOR EXPLORING THE OPPORTUNITIES IN CLOUD OUTSOURCING2013Independent thesis Advanced level (degree of Master (Two Years))Oppgave
    Abstract [en]

    Context: Cloud Outsourcing is a new form of outsourcing which is not more under implementation and yet to be implemented. It is a form of outsourcing in which software organizations outsource the work to e-freelancers available throughout the world using cloud services via the Internet. Software organizations handovers the respective task to the cloud and from the cloud e-freelancers undertake the development of task and then return back the finished task to the cloud. Organizations recollect the finished task from the cloud and verify it and then pay to the e-freelancer. Objectives: The aim of this study is to identify the sequence of activities involved during the entire process of cloud outsourcing and to find out the risks which are likely to be occurred during the implementation of this process. To prioritize the elicitated risks according to their probability of occurrence, impact and cost required to mitigate the corresponding risk. Methods: Data is collected by literature review and then the data is synthesized. On the other side interviews with practitioners are conducted to know the activities involved and to find out the risks that are likely to be occurred during the implementation of cloud outsourcing. After this, a survey is conducted in order to prioritize the risks and a standard risk analysis is conducted to know the risks which are likely to be occurred. Literature review is done using four databases including the literature from the year 1990 to till date. Results: Totally we have identified 21 risks that are likely to be occurred and 8 activities so far. By performing risk analysis we have presented the risks, which should be considered first and relevant counter measures are suggested to overcome them.

  • 290.
    Koppula, Thejendar Reddy
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Regression Testing Goals and Measures: An industrial approach2018Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Context: When a software is modified, regression testing is performed to ensure the behaviour of software is not affected because of those modifications. Due to frequent modifications, the regression testing became challenging. Although there are many regression testing techniques are developed in the research, they are not incorporating in the industry. This is because of the differences in regression testing goals and measures in research and industry. The current context of this study is to identify the regression testing goals and measures in the research and industry perspectives and to find the differences and similarities in both perspectives.

    Objectives: The primary objective of this study is to identify the similarities and differences in regression testing goals and measure from research and industry perspectives. Additionally, in this study, a general adapted goals list is presented.

    Methods: A mixed method approach is used for this study. A literature review has been used to identify the regression testing goals and measures in research. A survey is used to identify the regression testing goals and measures in the industry. Semi-structured interviews and online questionnaire are used as data collection methods in the survey. Thematic analysis and descriptive statistics are used as data analysis methods for the qualitative and quantitative data.

    Results: A literature review is conducted using 33 research articles. In the survey, the data is collected from 11 semi-structured interviews which are validated with 45 responses from an online questionnaire. A total of 6 regression testing goals are identified from the literature review and 8 goals are identified in the survey respectively. The measures used to evaluate these goals are identified and tabulated.

    Conclusions: From the results, we observed the similarities and differences in the regression testing goals and measures in industry and research. There are few similarities in goals but the major difference is the priority order of these goals. There are various measures used in research but very fewer measures are incorporating in the industry. The respondents from the survey implied that there is a need for generic adaptive goals. Further, a general list of goals is presented.

    Keywords: Regression, Regression testing, Goals, Objectives, Measures, Metrics.

  • 291.
    Korraprolu, Srinivasa Abhilash
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Evaluation of the Relevance of Agile Maturity Models in the Industry: A Case Study2018Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
    Abstract [en]

    Background.

    Over the years, agile software development has become increasingly popular in the software industry. One of the reasons is that agile development addressed the needs of the organisations better than the traditional models, such as the waterfall model. However, the textbook version of agile development still leaves something to be desired. This could be learnt by observing the implementation of agile methods/frameworks in the industry. The teams often customize agile methods to suit their context-specific needs. When teams in the industry decide to adopt the agile way of working, they are confronted by a choice¾either they have to implement all the agile practices at a time or adopt them over the time. The former choice has shown to come with risks and, therefore, was found that practitioners generally preferred the latter. However, agile practices are not independent, they have dependencies amongst them. A new approach to agile development emerged in the recent years known as Agile Maturity Models (AMMs). AMMs claim to offer a better path to agile adoption. In AMMs, the practices are typically introduced gradually in a particular order. However, these AMMs are multifarious and haven’t been sufficiently evaluated¾especially in the industry practice. Thus, they need to be evaluated in order to understand their relevance in the industry.

     

    Objectives.

    The goal is to evaluate the relevance of AMMs in the industry. By finding relevant AMMs, they could be used to alleviate the formation of agile teams and contribute toward their smoother functioning. By finding those that aren’t, this research could act as a cautionary to those practitioners who could potentially implement these AMMs and risk failure. The objectives are: identifying the agile practice dependencies in the AMMs; finding the agile practice dependencies in an agile team by conducting a case study in the industry; comparing the dependencies from the case study with those in the AMMs.


     

    Methods.

    The agile maturity models were identified and analysed. A case study was conducted on an agile team to identify the dependencies between the agile practices in the industry practice. Semi-structured interviews were conducted with members of the agile team. Qualitative coding was used to analyse the collected data. The dependencies from the case study were compared with the AMMs to achieve the aim of this research.

     

    Results.

    It was found that dependencies between individual agile practices in the AMMs were almost never possible to be found. However, practices suggested in each maturity levels were derived. Hence, the dependencies were found in the maturity-level level. From the case study, 20 agile practice dependencies were found. 7/8 AMMs were found to be not relevant. 1 AMM couldn’t be evaluated as it heavily relied on the practitioner’s choices.

     

    Conclusions.

    The researchers could use the evaluation method presented in this thesis to conduct more such evaluations. By doing so, the dynamics present in the industry teams could be better understood. On their basis, relevant AMMs could be developed in the future. Such AMMs could help practitioners leverage agile development.

  • 292. Kosti, Makrina Viola
    et al.
    Feldt, Robert
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Angelis, Lefteris
    Archetypal personalities of software engineers and their work preferences: a new perspective for empirical studies2016Inngår i: Journal of Empirical Software Engineering, ISSN 1382-3256, E-ISSN 1573-7616, Vol. 21, nr 4, s. 1509-1532Artikkel i tidsskrift (Fagfellevurdert)
  • 293.
    Koutsoumpos, Vasileios
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Marinelarena, Iker
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Agile Methodologies and Software Process Improvement Maturity Models, Current State of Practice in Small and Medium Enterprises2013Independent thesis Advanced level (degree of Master (One Year))Oppgave
    Abstract [en]

    Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM.

  • 294.
    Krishna Chaitanya, Konduru
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Scalability Drivers in Requirements Engineering2016Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
  • 295.
    Krusche, Stephan
    et al.
    Technische Universität München, DEU.
    Seitz, Andreas
    Technische Universität München, DEU.
    Börstler, Jürgen
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Bruegge, Bernd
    Technische Universität München, DEU.
    Interactive Learning: Increasing Student Participation through Shorter Exercise Cycles2017Inngår i: ACM International Conference Proceeding Series Volume Part F126225, ACM Digital Library, 2017, s. 17-26Konferansepaper (Fagfellevurdert)
    Abstract [en]

    In large classes, there is typically a clear separation between content delivery in lectures on the one hand and content deepening in practical exercises on the other hand. This temporal and spatial separation has several disadvantages. In particular, it separates students’ hearing about a new concept from being able to actually practicing and applying it, which may decrease knowledge retention.

    To closely integrate lectures and practical exercises, we propose an approach which we call interactive learning: it is based on active, computer based and experiential learning, includes immediate feedback and learning from the reflection on experience. It decreases the time between content delivery and content deepening to a few minutes and allows for flexible and more efficient learning. Shorter exercise cycles allow students to apply and practice multiple concepts per teaching unit directly after they first heard about them.

    We applied interactive learning in two large software engineering classes with 300 students each and evaluated its use qualitatively and quantitatively. The students’ participation increases compared to traditional classes: until the end ofthe course, around 50% of the students attend class and participate in exercises. Our evaluations show that students’ learning experience and exam grades correlate with the increased participation. While educators need more time to prepare the class and the exercises, they need less time to review exercise submissions. The overall teaching effort for instructors and teaching assistants does not increase.

  • 296.
    Krüger, Anders
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Recognizing and classifying a golf swing using accelerometer in a Smartwatch2017Independent thesis Advanced level (degree of Master (Two Years)), 20 poäng / 30 hpOppgave
  • 297.
    Kulanthaivetpillai, Nishandan
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Gorges, Gorges
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Implementing an Augmented Reality application to use on Microsoft Hololens to interact with automotive vehicle objects2017Independent thesis Basic level (degree of Bachelor), 10 poäng / 15 hpOppgave
  • 298.
    Kuzniarz, Ludwik
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Martins, Luiz Eduardo Galvão
    Federal University of São Paulo, BRA.
    Teaching model-driven software development: A pilot study2016Inngår i: Proceedings of the 2016 ITiCSE Working Group Reports, ITiCSE 2016, Association for Computing Machinery (ACM), 2016, s. 45-56Konferansepaper (Fagfellevurdert)
    Abstract [en]

    Software development is a process starting with specification of requirements, then providing design of the required software and implementing the design. Introducing understanding of the process and teaching the skills required for conducting the process is an important learning objective in any CS/SE curriculum. Recently a new paradigm - model-driven software development - has been introduced and extensively used in order to manage increasing complexity in the development of software. We want to investigate and discuss the state-of-The-practice of teaching MDSD and further to provide suggestions on what to include in the teaching curricula and how to teach MDSD in a proper way. The paper presents the results of the work performed by the ITiCSE 2016 "Teaching Model-Driven Software Development" working group. The objective for the work performed at ITiCSE was to elaborate on a foreseen survey based framework for the research by performing a pilot study using the framework. The pilot study was supposed to validate the framework by performing the initial survey, presenting the results, drawing conclusions from the results but also to find out necessary changes and modifications for the research framework so that it could be used for further more extensive research. CCS Concepts • Computing methodologies→Modeling and Siumlation →Model development and analysis→Modeling methodologies • Social and professional topics → Professional topics→Computing education→Computing education programs?Software engineering education.

  • 299.
    Lenberg, Per
    et al.
    Chalmers, SWE.
    Alégroth, Emil
    Chalmers, SWE.
    Feldt, Robert
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Wallgren, Lars-Göran
    Göteborgs Universitet, SWE.
    An initial analysis of differences in software engineers’ attitudes towards organizational change2016Inngår i: Proceedings - 9th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2016, ACM Press, 2016, s. 1-7Konferansepaper (Fagfellevurdert)
    Abstract [en]

    The ability to manage change is important in software engineering organizations, where rapid progress in technologies and constantly evolving methodologies create a turbulent environment. Research has identified employees’ attitudes towards organizational change as a key factor in the change process. Nonetheless, few studies exist that explore such attitudes in a software engineering context. The nature of change efforts is such that they often do not equally affect the various roles in the organization, which indicates that the roles may hold different attitudes. This study aimed to verify the existence of these presumed differences in attitudes towards organizational change between roles in a software engineering organization and to identify factors that contribute to these differences. The result of a survey (N=51) confirmed that there were significant differences, and that the software developers had a more positive attitude towards change and had deeper knowledge about the intended outcome compared to the line managers. The result of in-depth interviews (N=11) revealed that the software engineers evaluate the planned change in relation to the norms, values and standards of their peer group, meaning that an employee will have a positive attitude towards a change if its result is likely to make, or has made, it easier for him/her to uphold the peer group’s norms and values.

  • 300. Lenberg, Per
    et al.
    Feldt, Robert
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Wallgren, Lars Goran
    Behavioral software engineering: A definition and systematic literature review2015Inngår i: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 107, s. 15-37Artikkel, forskningsoversikt (Fagfellevurdert)
    Abstract [en]

    Throughout the history of software engineering, the human aspects have repeatedly been recognized as important. Even though research that investigates them has been growing in the past decade, these aspects should be more generally considered. The main objective of this study is to clarify the research area concerned with human aspects of software engineering and to create a common platform for future research. In order to meet the objective, we propose a definition of the research area behavioral software engineering (BSE) and present results from a systematic literature review based ori the definition. The result indicates that there are knowledge gaps in the research area of behavioral software engineering and that earlier research has been focused on a few concepts, which have been applied to a limited number of software engineering areas. The individual studies have typically had a narrow perspective focusing on few concepts from a single unit of analysis. Further, the research has rarely been conducted in collaboration by researchers from both software engineering and social science. Altogether, this review can help put a broader set of human aspects higher on the agenda for future software engineering research and practice. (C) 2015 Elsevier Inc. All rights reserved.

3456789 251 - 300 of 637
RefereraExporteraLink til resultatlisten
Permanent link
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annet format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annet språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf