Ändra sökning
Avgränsa sökresultatet
32333435363738 1701 - 1750 av 1886
RefereraExporteraLänk till träfflistan
Permanent länk
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annat format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annat språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf
Träffar per sida
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sortering
  • Standard (Relevans)
  • Författare A-Ö
  • Författare Ö-A
  • Titel A-Ö
  • Titel Ö-A
  • Publikationstyp A-Ö
  • Publikationstyp Ö-A
  • Äldst först
  • Nyast först
  • Skapad (Äldst först)
  • Skapad (Nyast först)
  • Senast uppdaterad (Äldst först)
  • Senast uppdaterad (Nyast först)
  • Disputationsdatum (tidigaste först)
  • Disputationsdatum (senaste först)
  • Standard (Relevans)
  • Författare A-Ö
  • Författare Ö-A
  • Titel A-Ö
  • Titel Ö-A
  • Publikationstyp A-Ö
  • Publikationstyp Ö-A
  • Äldst först
  • Nyast först
  • Skapad (Äldst först)
  • Skapad (Nyast först)
  • Senast uppdaterad (Äldst först)
  • Senast uppdaterad (Nyast först)
  • Disputationsdatum (tidigaste först)
  • Disputationsdatum (senaste först)
Markera
Maxantalet träffar du kan exportera från sökgränssnittet är 250. Vid större uttag använd dig av utsökningar.
  • 1701.
    Vahlgren, Stefan
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för telekommunikationssystem.
    Språkstöd i distanslaboratoriet på BTH2004Självständigt arbete på grundnivå (kandidatexamen)Studentuppsats (Examensarbete)
    Abstract [sv]

    To study and laborate at distance, its necessary that the coursematerial is accessible via internet. Teaching at more languages than swedish bocomes more common, why the information of courses needs to exist at several languages. As teacher, you need a way to publish and edit material of a course. It also has to be easy for the students to find the information. The distance laboratory have developed an administrative websystem that handles programme, courses and students, but misses the possibility for teachers to change content at the webpages and publish new coursematerial on a way.

  • 1702.
    Vajrapu, Rakesh Guptha
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Kothwar, Sravika
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Software Requirements Prioritization Practices in Software Start-ups: A Qualitative research based on Start-ups in India2018Självständigt arbete på avancerad nivå (masterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Context: Requirements prioritization is used in software product management and is concerned with identifying the most valuable requirements from a given set. This is necessary to satisfy the needs of customers, to provide support for stakeholders and more importantly for release planning. Irrespective of the size of the organization (small, medium and large), requirements prioritization is important to minimize the risk during development. However, few studies explore how requirements prioritization is practiced in start-ups. Software start-ups are becoming important suppliers of innovative and software-intensive products.Earlier studies suggest that requirements discovery and validation is the core activity in start-ups. However, due to limited resources, start-ups need to prioritize on what requirements to focus. If they do it wrong it leads to wasted resources.While larger organizations may afford such waste, start-ups cannot.Moreover, researchers have identified that start-ups are not small versions of large companies and the existing software development practices cannot be transferred directly due to low rigor in current studies.Thus, we planned to conduct an exploratory study on requirements prioritization practices in the context of software start-ups.

    Objectives: The main aim of our study is to explore the state-of-art of requirements prioritization practices used in start-ups.We also identify the challenges associated with the corresponding practices and few possible solutions.

    Methods: In this qualitative research, we conduct a literature review by referring to many article sources like IEEE Xplore, Scopus, and Google Scholar to identify the prioritization practices and challenges in general. An interview study is conducted by using semi-structured interviews to collect data from practitioners.Thematic analysis was used to analyze the interview data.

    Results: We have identified 15 practices from 8 different start-ups companies with corresponding challenges and possible solutions. Our results show mixed reviews in terms of the prioritization practices at start-ups. From the total of 8 companies about 6 companies followed formal methods while in the remaining 2 companies, prioritization was informal and not clear. The results show that value-based method is the dominant prioritization technique in start-ups. The results also show that customer input and return on investment aspects of prioritization play a key role when compared to other aspects.

    Conclusions: The results of this study provide an understanding of the various requirements prioritization practices in start-ups and challenges faced in implementing them.These results are validated from the answers found in the literature. The solutions identified for the corresponding challenges allow the practitioners to approach them in a better way. As this study focused only on Indian software start-up companies, it is recommended to extend to Swedish software start-up companies as well to get a broader perspective. Scaling of sample size is also recommended. This study may help future research on requirements engineering in start-ups. It may also help practitioners who have an intention to begin a software start-up company to get an idea of what challenges they may face while prioritizing requirements and can use these solutions to mitigate them.

  • 1703.
    Vaka, Kranthi
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Narla, Karthik
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    The impact of maturity, scale and distribution on software quality: An industrial case study2017Självständigt arbete på avancerad nivå (masterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Context. In this ever-changing world of software development, the process of organizations adopting distributed development is gaining prominence. Implementing various development processes in such distributed environment is giving rise to numerous issues which affects the quality of the product. These issues could be due to the involvement of architects across national borders during the process of development. In this research, the focus is to improve software quality by addressing the impact of maturity and scale between teams and its affect on code review process. Further to identify the issues behind the distribution between teams separated by geographical, temporal and cultural distances.

    Objectives. The main objective of this research is to identify how different factors such as maturity on quality of deliverables, scale and distribution that impacts the code review process affecting software quality. Based on code review comments in data set, the factors that were examined in this research are evolvability of defects and difference in the quality of software developed by mature and immature teams within code review process. Later on, the issues related to the impact of geographical, temporal and cultural distances on the type of defects revealed during distributed development are identified.

    Methods. To achieve these objectives, a case study was conducted at Ericsson. A mixed approach has been chosen that includes, archival data and semi-structured interviews to gather useful data for this research. Archival data is one of the data collection method used for reviewing comments in data set and gather quantitative results for the study. We employed approaches such as descriptive statistics, hypothesis testing, and graphical representation to analyze data. Moreover, to strengthen these results, semi-structured group interview is conducted to triangulate the data and collect additional insights about code review process in large scale organizations.

    Results. By conducting this research, it is inferred that teams with a lower level of maturity produce more number of defects. It was observed that 35.11% functional, 59.03% maintainability, 0.11% compatibility, 0.028% security, 0.73% reliability, 4.96% performance efficiency, 0.014% portability of defects were found from archival data. Majority of defects were of functional and maintainability type, which impacts software quality in distributed environment. In addition to the above-mentioned results, other findings are related to evolvability of defects within immature teams which shows that there is no particular trend in increase or decrease in number of defects. Issues that occur due to distribution between teams are found out in this research. The overall results of this study are to suggest the impact of maturity and scale on software quality by making numerical assumptions and validating these finding with interviews. Interviews are also used to inquire information about the issues from dataset related to the impact of global software engineering (GSE) distances on code review process.

    Conclusions. At the end of this research it is concluded that in these type of projects, immature teams produce more number of defects than mature teams. This is because when large-scale projects are distributed globally, it is always harder to share and acquire knowledge between teams, increase group learning and mentor teams located in immature sites. Immature developers have problems of understanding the structure of code, new architects need to acquire knowledge on the scope and real time issues for improving quality of software. Using results presented in this thesis, researchers can find new gaps easily to extend the research on various influences on code review process in distributed environment. 

  • 1704.
    Vakkalanka, Sairam
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Narayanasetty, SR Phanindra Kumar
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Investigating Research on Teaching Modeling in Software Engineering -A Systematic Mapping Study2013Självständigt arbete på avancerad nivå (masterexamen)Studentuppsats (Examensarbete)
    Abstract [sv]

    Sammanhang : Modellering är en viktig verksamhet , som används i olika faser av programvaruteknik . Utan modeller och modellering , är det nästan omöjligt att utforma och utveckla mjukvarusystem , vilket kräver behovet av modellering för att undervisas i programvaruteknik . Det finns ett antal rapporterade modeller, metoder , verktyg och språk för att undervisa modellering i programvaruteknik , vilket tyder på att det behövs en klassificering och en överblick över området . Denna forskning undersöker tillståndet av publicerad forskning om undervisning modellering i programvaruteknik för att ge en systematisk överblick och klassificering av dessa olika sätt att undervisa modellering med en insikt om deras betydelse och relevans för detta forskningsområde . Mål : Det övergripande målet med forskningen uppnåddes med att uppfylla följande mål : att förstå hur systematisk kartläggning genomförs , att utveckla en systematisk kartläggning process som riktigt kommer att ge data för att undersöka publicerad forskning , tillämpning av processen , och slutligen reflektera över resultaten av de avbildningar, som analyserar betydelsen och utvärdera relevansen av den publicerade forskningen . Metoder : En systematisk litteraturstudie användes som ett verktyg för att förstå och kontrollera hur systematisk kartläggning genomfördes inom området programvaruteknik . Baserat på resultaten av en systematisk litteraturgenomgång har nya riktlinjer som formulerats för att bedriva systematisk kartläggning . Riktlinjerna användes för att undersöka den publicerade forskning om undervisning modellering i programvaruteknik . De resultat som erhållits genom systematisk kartläggning utvärderades baserat på industriell relevans , Rigor och stämningen räkning för att undersöka deras betydelse och identifiera kunskapsluckor . Resultat: 131 artiklar klassificerades i fem klasser , t.ex. språk , kurs Design , Curriculum design, diagram , andra med hjälp av semi - manuell klassificeringssystem och klassificerings fasetter såsom typ av publiken , typ av bidrag , typ av forskning , typ av publikation , typ av årtal , typ av forskningsmetod och typ av studieinställning. Efter utvärderingen av industriell relevans , noggrannhet och stämningen ranking på de erhållna resultaten av klassificeringen , 8 processer , 4 verktyg , 3 metoder , 2 mät - mått och 1 modell extraherades att lära modellering i programvaruteknik . Även denna klassificering i jämförelse med en befintlig klassificering , som bygger på intervjuer och diskussioner , visade att vår klassificering ger en bredare överblick med en djupare insikt om de olika sätten att lära modellering i programvaruteknik . Slutsatser : Resultaten av denna systematiska kartläggning visar att det finns en ökning av forskningsverksamheten på undervisning modellering i programvaruteknik , med Unified Modeling Language ( UML ) är den brett forskningsområde. Mycket forskning framhävs att lära modellering för studenter från den akademiska världen , som indikerar en lucka forskning för att utveckla metoder, modeller , verktyg och processer för att lära modellering för studenter / utövare från branschen . Dessutom , med tanke på stämningen ranking , industriell relevans och noggrannhet av artiklarna , områden som kursdesign och utveckling av läroplaner är mycket eftersatt , vilket tyder på att det behövs mer forskning fokus.

  • 1705.
    Vamsi Appana, Vamsi
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Evaluating Industrial Relevance in Search Based Software Engineering Research: A Systematic Mapping Study and Survey2017Självständigt arbete på avancerad nivå (magisterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Search Based Software Engineering is one of the important field of software engineering. Over the past few years even though there is a lot of study performed on SBSE and its search techniques in software development areas, it appears SBSE is not very industry relevant at the moment because most of the academic work was limited towards the application of search techniques. Hence, author proposes a study to know the trend of SBSE literature over the past few years and also analyze to what degree current SBSE research is industry relevant

  • 1706.
    Varanasi, Panchajanya
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    A Perspective of Leadership Requirement in Scrum Based Software Development - A Case Study2018Självständigt arbete på avancerad nivå (magisterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Context. Software Development has been witnessing great innovations over past few years with good number of technologies, tools and practices invading the industry. Client demands and collaboration in the development process are also seen increasing. So many new practices and methodologies are coming up and Agile is one of prominent practices adopted by many. Even in Agile, Scrum methodology is picking up more demand presently. As Software Development process and practices are changing so are the leadership styles in the same. Leadership is critical for success of any team. This study intended to explore this model and requirement of leadership in Scrum based Software Development in a practical scenario.

    Objectives. Leadership, which is essential in any Software project, differs from Traditional Methodology to Scrum Methodology of Agile practices in Software Development. Through a case study, the author attempted to investigate and explore the perspective of Leadership requirement in Scrum based Software Development in a practical scenario. The study aimed to gather and analyze the Leadership model implemented in two domestic projects in an Indian company, involved in two distinctive domains, and sum up the impressions gained in the same. The study aimed to assess whether the gathered knowledge adds up to the existing body of knowledge on the phenomenon or on the contrary whether any suggestions for improvement can be given to the case units.

    Methods. Case Study method was chosen for undertaking this explorative study. A literature review was conducted prior to the case study to gain knowledge on the phenomenon, which also answered one of the Research Questions and helped partially the other. A multiple case study was conducted through semi structured personal interviews, tools analysis and direct observation in the case units. Qualitative data analysis was made using Grounded Theory on this three orders of collected data. The results were compared with the Literature and conformity or variance analyzed. This comparative analysis is used for making recommendations to the case units for improvement or for additions to the existing body of knowledge.

    Results. Through the results of Literature Review, Leadership models in Software Development including Agile Scrum were summed up. And through the results of the case study, the leadership models and features implemented in the case units have been identified. These results are further validated and contrasted with the results of the literature review. How the literature models and the case unit models of leadership differed is studied. The justification for the implemented leadership model in the practical situation is also analyzed. Following, a review of the models employed at the case environments, the perspective of leadership in the two Scrum based Software Development projects is summed up. At the end, it is assessed what effect the case study would have on the existing body of knowledge on the phenomenon and modifications that can be proposed to the case units based on the results and analysis.

    Conclusion. It is concluded that the Case Units are implementing Situational Leadership and Transformational Leadership in a mixed way. Telling and Selling models in Situational Leadership are prominent while Participating and Delegating are ranking less. Some of the important features of Transformational Leadership like Self Management, Organizational Consciousness, Adaptability and Proactive are in implementation but not all features of the model are assumed. Even Scrum is implemented in a modified way, extending only controlled autonomy with higher monitoring and it had a direct effect on the leadership. On the whole it is directive leadership that is in play with co-existence of collaborative one situationally.

  • 1707.
    Vasudev, R.Sashin
    et al.
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för för interaktion och systemdesign.
    Vanga, Ashok Reddy
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för för interaktion och systemdesign.
    Accuracy of Software Reliability Prediction from Different Approaches2008Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Many models have been proposed for software reliability prediction, but none of these models could capture a necessary amount of software characteristic. We have proposed a mixed approach using both analytical and data driven models for finding the accuracy in reliability prediction involving case study. This report includes qualitative research strategy. Data is collected from the case study conducted on three different companies. Based on the case study an analysis will be made on the approaches used by the companies and also by using some other data related to the organizations Software Quality Assurance (SQA) team. Out of the three organizations, the first two organizations used for the case study are working on reliability prediction and the third company is a growing company developing a product with less focus on quality. Data collection was by the means of interviewing an employee of the organization who leads a team and is in the managing position for at least last 2 years.

  • 1708.
    Veeramachaneni, Ramya Chowdary
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Uppalapati, Niroopa
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    A Framework for Requirements Triage Process2011Självständigt arbete på avancerad nivå (masterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    ABSTRACT Context: Requirements triage is a crucial activity in requirements engineering process for market-driven products. Triage deals with selection of appropriate requirements from large number of requirements for particular release plan. If triage is not performed initially, selection and management of a large number of requirements would be difficult in requirements engineering process. In market-driven product development triage is followed by estimation and prioritization of requirements to be selected for a particular release plan, also termed as requirements selection. Product development is done based on the set of requirements selected in requirements selection process. Objectives: The objective of the thesis is to find whether there is a need to improve existing requirements triage process or not, identify the challenges and shortcomings of the existing requirements triage and selection solutions and suggest improvements to address identified challenges and shortcomings. Methods: In order to identify existing requirements triage and selection solutions (method, model, tool, technique, process, and others), challenges addressed by existing requirements triage and selection solutions, and the shortcomings faced while implementing them, a systematic literature review has been done. A list of challenges and shortcomings, identified through the analysis of systematic literature review results, was used as an input to industrial survey to confirm most applicable (relevant) challenges and shortcomings and to identify possibilities to address those challenges and shortcomings. Results: A process framework for requirements triage has been proposed to address the challenges faced by practitioners during triage. The steps and solutions proposed within the framework also enable to alleviate the shortcomings of the existing requirements triage solutions. Conclusions: The results of the survey have been analyzed from different perspectives: size of organization, number of requirements handled per month and experience of professional doing triage. Therefore, the proposed process framework is usable and useful for both small-scale and large-scale organizations. The initial effort required to put framework process steps in place would be high, however, later the effort will reduce not only for requirements triage but also for later phases in requirements engineering. As a spin off effect the quality of triage decision is increased.

  • 1709.
    Veerla, Veena
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Subrahmanyam, Maanasa
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Influence of cultural dimensions on Agile team behavioral characteristics2011Självständigt arbete på avancerad nivå (masterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Context: Agile methodologies are widely recognized in western countries. From past few years, its practices are being successfully adopted in global settings especially in eastern countries. Across the world, teams are following its values and principles. Are all the teams behaving in the same way? Potential difficulties related to culture arise while implementing agile practices. Due to variance in backgrounds and behaviors, social cliques and issues are likely to be formed between the team mates which become a hurdle. Objectives: The study unravels the list of relationships between the agile team behavioral characteristics and Hofstede cultural dimensions. It also explores whether Indian employees working in an agile environment possess the required behavioral characteristics which are useful for the effective functioning of a team. The other objective of this study reveals the influence of the years of experience of the agile employees on behavioral characteristics. Methods: Data collection processes include a literature review and a web survey. First, in the literature review analysis of the empirical studies from year 1999-2011 was done. The review approach helped in collecting and summarizing the data. The studies were identified from the most reliable and authentic databases that are scientifically and technically peer reviewed such as Engineering village, IEEE Xplore, ACM digital library, Springer Link and Google Scholar. A survey was conducted with 33 practitioners from various multinational organizations in India. Statistical analysis was used to analyze the data. Results: Hofstede’s cultural dimensions had noticeable influence on agile team behavioral characteristics. Although, all the enabler characteristics were not seen in Indian culture, the results clearly show that some of the cultural dimensions are enabling factors to function well in an agile team and some hinder the team effectiveness. The result from the literature review shows the list of relationships between Hofstede cultural dimensions and agile team behavioral characteristics. All team behavioral characteristics were to a certain extent demonstrated by Indian agile employees, which can be known from the survey results. It is also seen from the survey results that, team behavioral characteristics can be demonstrated more effectively by the experienced agile employees. Conclusion: From this study, we have found the relationships between Hofstede cultural dimensions and agile team behavioral characteristics. List of agile team behavioral characteristics which were followed by Indian agile employees were obtained from the survey. We conclude that Indian agile employees were able to demonstrate all the agile team behavior characteristics required for an effective functioning of a team. One more interesting thing which came into our attention, after analyzing the survey was that years of experience of agile employees do have an effect on the employees which influences the demonstration of team behavior characteristics. It was clear that demonstration of these characteristics were not only dependent on individual’s nature but also on the years of experience in agile environment. The absence of relationships which were not found through literature needs to be focused. Hence we conclude that there is a need for conducting even more in-depth surveys and reviews to investigate the unfound relationships.

  • 1710.
    Velpula, Chaitanyakumar
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Requirements Negotiation and Conflict Resolution in Distributed Software Development: A Systematic Mapping Study and Survey2016Självständigt arbete på avancerad nivå (masterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    The main aim of this thesis is to explore the industrial practices of requirements negotiation and conflict resolution within distributed software development. The motivation for this study is to get insight of the industrial practices in particular interventions (Communication tools, Models, Communication media) that used by practitioners to resolve requirements negotiation and conflicts resolution between clients and suppliers, since many researchers purposed interventions in the literature for requirements negotiation and conflicts resolution in distributed software development. Context: In Requirements Engineering, requirements negotiation and conflict resolution are crucial activities to achieve a common ground between clients and suppliers, it is considered as one of the crucial factors for delivering successful software. However, the shift from traditional collocated practices to a distributed environment offers both benefits and drawbacks which were studied earlier by researcher, but surprisingly there are few studies with insight of exploring the distributed requirements negotiations and conflict resolution practices. This research investigates the state of requirements negotiation and conflict resolution activities in distributed software development with an insight on their importance and relevance to this research area.

    Objectives: Overall goal of this thesis is to understand how requirements negotiations and conflict resolution are performed in distributed software development, knowing what are the available tools to perform requirements negotiation and conflict resolution, whether these existing tools are good enough to cope up with the industrial practices, knowing most widely used tools, methods and approaches, most importantly does the present research able to bridge the gap with in distributed software development?

    Methods: This thesis study comprises of two research methodologies. 1. Systematic mapping study (SMS)- To identify the proposed interventions in the literature to perform requirements negotiation and conflict resolution activities in Industrial Software Development within a distributed environment. 2. Industrial Survey- To identify industrial practices to perform rei quirements negotiation and conflict resolution in Industrial Software Development within a distributed environment.

    Results: 20 studies were identified through systematic mapping study (SMS). After analyzing the obtained studies, the list of interventions (Preparatory activities/communication tools/ Models) were gathered and analyzed. Thereupon, an industrial survey is conducted from the obtained literature, which has obtained 41 responses. Effective communication media for preparatory activities in requirements negotiations and conflict resolution are identified, validation of communication tools for effective requirements negotiations and conflict resolution is performed. Apart from the validation, this study provided list of factors that affects the requirement negotiations and conflict resolution activities in distributed software development.

    Conclusions: To conclude, the obtained results from this study will benefit practitioner in capturing more insight towards the requirements negotiations and conflict resolution in distributed software engineering. This study identified the preparatory activities involved for effective communication to perform requirements negotiation activities, effective tools, models and factors affecting of requirements negotiations and conflict resolution. In addition to this, validation of results obtained from the literature is carried through survey. Practitioners can be benefitted from the end results of by knowing the effective requirements negotiation and conflict resolution interventions (Communicational tools/ Models/ Communication media) for early planning in distributed software development. Researchers can extend the study by looking in to the real-time approaches followed by the practitioners to perform the both activities in the direction of future studies.

  • 1711.
    Vilela, Jessyka
    et al.
    Univ Fed Ceara, BRA.
    Castro, Jaelson
    Univ Fed Pernambuco UFPE, BRA.
    Martins, Luiz Eduardo G.
    Univ Fed Sao Paulo UNIFESP, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Silva, Carla
    Univ Fed Pernambuco UFPE, BRA.
    Specifying Safety Requirements with GORE languages2017Ingår i: XXXI BRAZILIAN SYMPOSIUM ON SOFTWARE ENGINEERING (SBES 2017), Association for Computing Machinery (ACM), 2017, s. 154-163Konferensbidrag (Refereegranskat)
    Abstract [en]

    Context: A suitable representation of Safety-Critical Systems (SCS) requirements is crucial to avoid misunderstandings in safety requirements and issues in safety specification. However, current general requirements specification languages do not fully support the particularities of specifying SCS. Objective: In this paper, our goal is to identify and propose a set of important features that should be provided by requirements languages to support an early safety requirements specification. Moreover, we aim to compare the ability of the four most used Goal-Oriented Requirements Engineering (GORE) languages (i*, KAOS, GRL, NFR-Framework) in supporting the proposed features. Method: We first established a conceptual foundation and a conceptual model based on the literature, challenges elicited in previous works, and demands of safety standards at the requirements level that practitioners must satisfy in order to certify their systems. Results: We proposed a set of 15 features that requirements languages should provide to an early safety requirements specification. Regarding the comparison of GORE languages, in summary, all surveyed languages lacks explicit modeling constructs to express how hazards can occur in the system, the accidents, their impact and how they can mitigated. Conclusions: The conceptual foundation, conceptual model, and the set of features is a novelty. Finally, the features can be used to propose new requirements languages for SCS or to define extensions for the ones already available.

  • 1712.
    Vilela, Jéssyka
    et al.
    Universidade Federal de Pernambuco, BRA.
    Castro, Jaelson
    Universidade Federal de Pernambuco, BRA.
    Martins, Luiz Eduardo Galvão
    Universidade Federal de São Paulo, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Integration between requirements engineering and safety analysis: A systematic literature review2017Ingår i: Journal of Systems and Software, ISSN 0164-1212, E-ISSN 1873-1228, Vol. 125, s. 68-92Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Context: Safety-Critical Systems (SCS) require more sophisticated requirements engineering (RE) approaches as inadequate, incomplete or misunderstood requirements have been recognized as a major cause in many accidents and safety-related catastrophes. Objective: In order to cope with the complexity of specifying SCS by RE, we investigate the approaches proposed to improve the communication or integration between RE and safety engineering in SCS development. We analyze the activities that should be performed by RE during safety analysis, the hazard/safety techniques it could use, the relationships between safety information that it should specify, the tools to support safety analysis as well as integration benefits between these areas. Method: We use a Systematic Literature Review (SLR) as the basis for our work. Results: We developed four taxonomies to help RE during specification of SCS that classify: techniques used in (1) hazard analysis; (2) safety analysis; (3) safety-related information and (4) a detailed set of information regarding hazards specification. Conclusions: This paper is a step towards developing a body of knowledge in safety concerns necessary to RE in the specification of SCS that is derived from a large-scale SLR. We believe the results will benefit both researchers and practitioners.

  • 1713.
    Vilela, Jéssyka
    et al.
    Universidade Federal do Ceará, BRA.
    Castro, Jaelson
    Universidade Federal de Pernambuco, BRA.
    Martins, Luiz Eduardo Galvão
    Universidade Federal de São Paulo, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Safe-RE: A safety requirements metamodel based on industry safety standards2018Ingår i: ACM International Conference Proceeding Series, Association for Computing Machinery , 2018, s. 196-201Konferensbidrag (Refereegranskat)
    Abstract [en]

    Context: The development of Safety-Critical Systems (SCS) requires an adequate understanding of safety terms to avoid the specification of poor, incomplete or unclear safety requirements. However, there are some misunderstandings, mostly by requirements engineers, about the definition of such concepts. Hence, integration of safety concerns in the Requirements Engineering (RE) and a common nomenclature is necessary to improve the specification of these systems. Objective: To fill this gap, this paper presents Safe-RE, a safety requirements metamodel based on industry safety standards whose aim is to support the specification of safety-related concepts in the RE process. Method: We rely on safety standards as a basis for our work since companies must follow them to have their systems certified. Results: To illustrate the Safe-RE metamodel usage, we applied its concepts in an insulin infusion pump system. Conclusions: We hope that Safe-RE can contribute to improving the elicitation and specifications of such systems and therefore, reducing accidents and safety-related catastrophes. We also discuss some benefits we envision of using the metamodel, its limitations, and open issues. © 2018 Association for Computing Machinery.

  • 1714.
    Vilela, Jéssyka
    et al.
    Universidade Federal de Pernambuco, BRA.
    Castro, Jaelson
    Universidade Federal de Pernambuco, BRA.
    Martins, Luiz Eduardo
    Universidade Federal de Sao Paulo, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Assessment of safety processes in requirements engineering2018Ingår i: Proceedings - 2018 IEEE 26th International Requirements Engineering Conference, RE 2018, Institute of Electrical and Electronics Engineers Inc. , 2018, s. 358-363Konferensbidrag (Refereegranskat)
    Abstract [en]

    Context: Requirements issues tend to be mitigated in organizations with high process maturity levels since they do their business in a systematic, consistent and proactive approach. In a Safety-Critical System (SCS), requirements problems have been associated with accidents and safety incidents. Objective: This work investigates which safety practices/actions are suitable to be used in the Requirements Engineering (RE) process of SCS and how to design a safety maturity model for this area. Method: we adopted different empirical techniques to propose Uni-REPM SCS, which consists of a safety module to be included in the Unified Requirements Engineering Process Maturity Model (Uni-REPM). Results: The safety module has seven main processes, 14 sub-processes and 148 safety actions describing principles and practices that form the basis of safety processes maturity. Conclusions: Preliminary validation with two practitioners and nine academic experts indicates that the safety module can help organizations to evaluate their current safety practices with respect to their RE process. Moreover, it also offers a step-wise improvement strategy to raise their safety maturity level. © 2018 IEEE.

  • 1715.
    Vilela, Jéssyka Flavyanne Ferreira
    et al.
    Universidade Federal do Ceara, BRA.
    Castro, Jaelson Freire B.
    Universidade Federal de Pernambuco, BRA.
    Martins, Luiz Eduardo Galvão
    Universidade Federal de Sao Paulo, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Safety Practices in Requirements Engineering: The Uni-REPM Safety Module2018Ingår i: IEEE Transactions on Software Engineering, ISSN 0098-5589, E-ISSN 1939-3520Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Context: Software is an important part in safety- critical system (SCS) development since it is becoming a major source of hazards. Requirements-related hazards have been as- sociated with many accidents and safety incidents. Requirements issues tend to be mitigated in companies with high processes maturity levels since they do their business in a systematic, consistent and proactive approach. However, requirements en- gineers need systematic guidance to consider safety concerns early in the development process. Goal: the paper investigates which safety practices are suitable to be used in the Requirements Engineering (RE) process for SCS and how to design a safety maturity model for this area. Method: we followed the design science methodology to propose Uni-REPM SCS, a safety module for Unified Requirements Engineering Process Maturity Model (Uni-REPM). We also conducted a static validation with two practitioners and nine academic experts to evaluate its coverage, correctness, usefulness and applicability. Results: The module has seven main processes, fourteen sub-processes and 148 practices that form the basis of safety processes maturity. Moreover, we describe its usage through a tool. Conclusions: The validation indicates a good coverage of practices and well receptivity by the experts. Finally, the module can help companies in evaluating their current practices. IEEE

  • 1716.
    Villamizar, Hugo
    et al.
    Pontifical Catholic University of Rio de Janeiro, BRA.
    Anderlin Neto, Amadeu
    Pontifical Catholic University of Rio de Janeiro, BRA.
    Kalinowski, M.
    Pontifical Catholic University of Rio de Janeiro, BRA.
    Garcia, Alessandro Fabricio
    Pontifical Catholic University of Rio de Janeiro, BRA.
    Mendez, Daniel
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    An approach for reviewing security-related aspects in agile requirements specifications of web applications2019Ingår i: Proceedings of the IEEE International Conference on Requirements Engineering, IEEE Computer Society , 2019, s. 86-97Konferensbidrag (Refereegranskat)
    Abstract [en]

    Defects in requirements specifications can have severe consequences during the software development lifecycle. Some of them result in overall project failure due to incorrect or missing quality characteristics such as security. There are several concerns that make security difficult to deal with; for instance, (1) when stakeholders discuss general requirements in meetings, they are often unaware that they should also discuss security-related topics, and (2) they typically do not have enough expertise in security. This often leads to unspecified or ill-defined security-related aspects. These concerns become even more challenging in agile contexts, where lightweight documentation is typically involved. The goal of this paper is to design and evaluate an approach for reviewing security-related aspects in agile requirements specifications of web applications. The approach considers user stories and security specifications as input and relates those user stories to security properties via Natural Language Processing. Based on the related security properties, our approach then identifies high-level security requirements from the Open Web Application Security Project to be verified and generates a reading technique to support reviewers in detecting defects. We evaluate our approach via two controlled experiment trials. We compare the effectiveness and efficiency of novice inspectors verifying security aspects in agile requirements using our approach against using the complete list of high-level security requirements. The (statistically significant) results indicate that using our approach has a positive impact (with large effect size) on the performance of inspectors in terms of effectiveness and efficiency. © 2019 IEEE.

  • 1717.
    Vishnubhotla, Sai Datta
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Lundberg, Lars
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Supplementary Material of: "Understanding the Perceived Relevance of Capability Measures: A Survey of Agile Software Development Practitioners"2019Övrigt (Övrig (populärvetenskap, debatt, mm))
    Abstract [en]

    This document contains the supplementary material of the paper titled: "Understanding the Perceived Relevance of Capability Measures: A Survey of Agile Software Development Practitioners" 

  • 1718.
    Vishnubhotla, Sai Datta
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Which Abilities and Attitudes Matter Most?: Understanding and Investigating Capabilities in Industrial Agile Contexts2019Licentiatavhandling, sammanläggning (Övrigt vetenskapligt)
    Abstract [en]

    Background: Over the past decades, advancements in the software industry and the prevalence of Agile Software Development (ASD) practices have increased the prominence of individual and interpersonal skills. The humancentric nature of ASD practices makes it imperative to identify and to assign a capable professional to a team. While capabilities of professionals influence team performance and lead the path to a project’s success, the area of capability measurement in ASD remains largely unexplored.

    Objectives: This thesis aims to aggregate evidence from both the state of the art and practice to understand capability measurement in ASD. Further, to support research and practice towards composing agile teams, this thesis also investigates the effects of capability measures on team-level aspects (team performance and team climate) within industrial contexts.

    Method: A mixed-methods approach was employed to address the thesis’ objectives. A Systematic Literature Review (SLR) and an industrial survey were conducted to identify and gather evidence in relation to individual and team capability measures, which are pertinent to ASD context. A case study and another industrial survey were carried out to provide insights and extend support towards agile team composition.

    Results: Our SLR results showed that a major portion of former studies discussed capability measures in relation to affective, communication, interpersonal and personal aspects. Results from our survey also aligned with these findings, where, measures associated with the aforementioned aspects were observed to be widely known to practitioners and were also perceived by them as highly relevant in ASD contexts. Our case study conducted at a small-sized organization revealed multiple professional capability measures to be affecting team performance. Whereas, our survey conducted at a large-sized organization identified an individual’s ability to easily get along with other team members (agreeableness personality trait) to have a significant positive influence on the person’s perceived level of team climate.

    Conclusion: In this thesis, the empirical evidence gathered by employing mixed-methods and examining diverse organizational contexts, contributed towards better realization of capability measurement in ASD. In order to extend support towards team composition in ASD, this thesis presents two approaches. The first approach is based on developing an agile support tool that coordinates capability assessments and team composition. The second approach is based on establishing team climate forecasting models that can provide insights about how the perceived level of climate within a team would vary based on its members’ personalities. However, in order to improve both approaches, it is certainly necessary to examine the effects of diverse capability measures.

  • 1719.
    Vishnubhotla, Sai Datta
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datalogi och datorsystemteknik.
    Mendes, Emilia
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datalogi och datorsystemteknik. Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Lundberg, Lars
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datalogi och datorsystemteknik.
    An insight into the capabilities of professionals and teams in agile software development: A systematic literature review2018Ingår i: PROCEEDINGS OF 2018 7TH INTERNATIONAL CONFERENCE ON SOFTWARE AND COMPUTER APPLICATIONS (ICSCA 2018), Association for Computing Machinery , 2018, s. 10-19Konferensbidrag (Refereegranskat)
    Abstract [en]

    Background: Previous studies investigated key characteristics of software engineers and factors influencing the performance of individuals, productivity of teams and project success within agile software development (ASD). They aided in the active investigation of human aspects in ASD. However, capability measurement and prediction with respect to agile workforce, owing to its importance, is an area that needs spotlight. Objective: The objective of this paper is to present the state of the art relating to capability measurement of software engineers and teams working in ASD projects. Method: We carried out a systematic literature review (SLR) focused on identifying attributes used for measuring and predicting the capabilities of individual software engineers and teams. Results: Evidence from 16 studies showed attributes that can measure capabilities of engineers and teams, and also attributes that can be used as capability predictors. Further, different instruments used to measure those attributes were presented. Conclusions: The SLR presented a wide list of attributes that were grouped into various categories. This information can be used by project managers as, for example, a checklist to consider when allocating software engineers to teams and in turn teams to a project. Further, this study indicated the necessity for an investigation into capability prediction models. © 2018 Association for Computing Machinery.

  • 1720.
    Vishnubhotla, Sai Datta
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datalogi och datorsystemteknik.
    Mendes, Emilia
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datalogi och datorsystemteknik. Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Lundberg, Lars
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datalogi och datorsystemteknik.
    Designing a capability-centric web tool to support agile team composition and task allocation: A work in progress2018Ingår i: 2018 IEEE/ACM 11TH INTERNATIONAL WORKSHOP ON COOPERATIVE AND HUMAN ASPECTS OF SOFTWARE ENGINEERING (CHASE), IEEE Computer Society , 2018, Vol. F137813, s. 41-44Konferensbidrag (Refereegranskat)
    Abstract [en]

    A significant number of studies reported models for competence profiling, measuring capabilities of professionals and recommendation systems for roles within agile software development (ASD). These models coordinated in human resource management within ASD. However, in the light of swift, incremental and iterative nature of ASD practices, designing solutions that easily integrate capability measurements with ongoing project management routines, is an important area for investigation. With the support of interviews, grounded theory procedure and workshops, we identified the aspects valued by our industrial collaborator while allocating professionals to tasks. This information was further utilized towards devising a framework for capability-centric Web tool. This tool provides a one-stop solution for project managers to create projects, keep track of capabilities and execute allocation routines. © 2018 ACM.

  • 1721.
    Vishnubhotla, Sai Datta
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Mendes, Emilia
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Lundberg, Lars
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Investigating the relationship between personalities and team climate of software professionals in a telecom companyIngår i: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025Artikel i tidskrift (Övrigt vetenskapligt)
    Abstract [en]

    Context: Previous research found that the performance of a team not only depends on the team personality composition, but also on the interactive effects of team climate. Although investigationon personalities associated with software development has been an active research area over the past decades, there has been very limited research in relation to team climate.

    Objective: Our study investigates the association between the five factor model personality traits(openness to experience, conscientiousness, extraversion, agreeableness and neuroticism) and the factors related to team climate (team vision, participative safety, support for innovation and task orientation) within the context of agile teams working in a telecom company.

    Method: A survey was used to gather data on personality characteristics and team climate perceptions of 43 members from eight agile teams. The data was initially used for correlation analysis; then, regression models were developed for predicting the personality traits related toteam climate perception.

    Results: We observed a statistically significant positive correlation between agreeableness and participative safety (r = 0.37), and also between openness to experience and support for innovation(r = 0.31). Additionally, agreeableness was observed to be positively correlated with overall team climate (r = 0.35). Further, from regression models, we observed that personality traits accountedto less than 15% of the variance in team climate.

    Conclusion: A person’s ability to easily get along with team members (agreeableness) has a significant positive influence on the perceived level of team climate. Results from our regression analysis suggest that further data may be needed, and/or there are other human factors, in addition to personality traits, that should also be investigated with regard to their relationship with team climate. Overall, the relationships identified in our study are likely to be applicable to organizations within the telecommunications domain that use scrum methodology for software development.

  • 1722.
    Vishnubhotla, Sai Datta
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Mendes, Emilia
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Lundberg, Lars
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för datavetenskap.
    Understanding the Perceived Relevance of Capability Measures: A Survey of Agile Software Development PractitionersIngår i: Artikel i tidskrift (Övrigt vetenskapligt)
    Abstract [en]

    Context: A significant number of studies discussed various human-aspects of software engineers over the past years. However, in the light of swift, incremental and iterative nature of Agile Software Development (ASD) practices, establishing deeper insights into capability measurement is crucial, as both individual and team capability can affect software development performance and project success.

    Objective: Our study investigates how agile practitioners perceive the relevance of individual and team level measures, pertaining to professional, social and innovative aspects, for characterizing the capability of an agile team and its members.

    Method: We undertook a Web-based survey using a questionnaire built based on the capability measures identified from our previous Systematic Literature Review (SLR). This questionnaire sought information about agile practitioners’ perceptions of individual and team capability measures.

    Results: We received 60 usable responses, corresponding to a response rate of 17% from the original sampling frame. Our results indicate that 127 individual and 28 team capability measures were considered as relevant by majority of the practitioners. Our survey also identified seven individual and one team capability measure which have not been previously characterized by our SLR.

    Conclusion: In practitioners’ opinion, an agile team member’s state of being answerable or accountable for things within one's control (responsibility) and the ability to feel or express doubt and raise objections (questioning skills), are the two measures that significantly represent the member’s capability. Overall, the findings from our study shed light on the sparsely explored field of capability measurement in ASD. Our results can be helpful to practitioners in reforming their team composition decisions.

  • 1723.
    Vitoria, David
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Aligning XP with ISO 9001:2000 -TickIT Guide 5.0: A Case Study in two Academic Software Projects2004Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Since last four to five years the buzz of continuous growing of agile development has been spread all around the world, specially Extreme Programming as the most important methodology of this kind. From the other side, ISO 9001:2000-TickIT Guide 5.0 has been established mainly in Europe as one of the well-known Quality Management Systems, in order to create a continuous software process improvement throughout software organizations that is mainly related to a certi¯cation process. This thesis is developed to mainly answer the question of how Extreme Programming and the standard ISO 9001:2000 with its interpretation for software development as TickIT Guide 5.0 can be used together, in order to have a continuous software process improvement with the agility to respond quickly to environment changes and satisfy the customer needs and expectations.

  • 1724.
    Vogelsang, Andreas
    et al.
    Technical University of Berlin, DEU.
    Eckhardt, Jonas
    Tableau Software, DEU.
    Mendez, Daniel
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Berger, Moritz
    Universität Bonn, DEU.
    Views on quality requirements in academia and practice: commonalities, differences, and context-dependent grey areas2020Ingår i: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 121, artikel-id 106253Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Context: Quality requirements (QRs) are a topic of constant discussions both in industry and academia. Debates entwine around the definition of quality requirements, the way how to handle them, or their importance for project success. While many academic endeavors contribute to the body of knowledge about QRs, practitioners may have different views. In fact, we still lack a consistent body of knowledge on QRs since much of the discussion around this topic is still dominated by observations that are strongly context-dependent. This holds for both academic and practitioners’ views. Our assumption is that, in consequence, those views may differ. Objective: We report on a study to better understand the extent to which available research statements on quality requirements, as found in exemplary peer-reviewed and frequently cited publications, are reflected in the perception of practitioners. Our goal is to analyze differences, commonalities, and context-dependent grey areas in the views of academics and practitioners to allow a discussion on potential misconceptions (on either sides) and opportunities for future research. Method: We conducted a survey with 109 practitioners to assess whether they agree with research statements about QRs reflected in the literature. Based on a statistical model, we evaluate the impact of a set of context factors to the perception of research statements. Results: Our results show that a majority of the statements is well respected by practitioners; however, not all of them. When examining the different groups and backgrounds of respondents, we noticed interesting deviations of perceptions within different groups that may lead to new research questions. Conclusions:Our results help identifying prevalent context-dependent differences about how academics and practitioners view QRs and pinpointing statements where further research might be useful. © 2020 Elsevier B.V.

  • 1725.
    Vukovic, Divna
    et al.
    Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap.
    Wester, Cecilia
    Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap.
    Staff Prediction Analysis: Effort Estimation In System Test2001Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    This master thesis is made in 2001 at Blekinge Institute of Technology and Symbian, which is a software company in Ronneby, Sweden. The purpose of the thesis is to find a suitable prediction and estimation model for the test effort. To do this, we have studied the State of the Art in cost/effort estimation and fault prediction. The conclusion of this thesis is that it is hard to make a general proposal, which is applicable for all organisations. For Symbian we have proposed a model based on use and test cases to predict the test effort.

  • 1726. Wadhwani, V
    et al.
    Memon, F
    Hameed, MM
    Architecture Based Reliability and Testing Estimation for Mobile Applications2008Konferensbidrag (Refereegranskat)
    Abstract [en]

    We propose an architecture-based testing and reliability framework for mobile applications. During our literature study, we explored some of the software testing and reliability techniques available, as well as investigating the techniques that are being used by industry. This paper presents case studies of two companies that are developing mobile applications. These are helpful for finding the strengths and weaknesses of existing software testing and reliability techniques. In light of these strengths and weaknesses, we propose a framework of architecture-based software testing and reliability estimation for mobile applications.

  • 1727.
    Wadhwani, Vickey
    et al.
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Ahmed, Shoain
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Evaluating Evolutionary Prototyping for Customizable Generic Products in Industry2008Självständigt arbete på avancerad nivå (masterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Software products can be categorized into three types namely bespoke, market driven and customizable generic products. Each of these products is facing different problems in their development and to address these problems different software process models have been introduced. The use and validation of different software process models for bespoke and market driven products have been discussed in earlier work. On the other hand, less attention was paid to the customizable generic products. Our thesis will fill this gap by conducting a case study on evolutionary prototyping (EP) for customizable generic products. The main aim of the thesis is to make an initial validation of EP for customizable generic products. In order to fulfill the aforementioned aim we performed a literature study on prototyping and EP, together with development of two customizable generic products. During this development process, we used approach of EP. The results from our investigation will provide researchers and practitioners with a deep insight to the EP and also to guide them in making decision regarding the use of EP. The main findings from our investigation are as follows: • EP is not used standalone as a software process model. Rather it is used as a concept that can be augmented with some iterative software process model. • Negative and positive aspects of EP were highlighted by discussing situations where it could be a better choice, with its advantages and disadvantages. • An initial validation was performed on EP for customizable generic products. Reported results from this case study show that the selected approach is a good choice when you want to have innovative product, clear ambiguous and sketchy requirements, discover new requirements, save resources of software testing, involve and satisfy customer. EP shows vulnerabilities in documentation of product and quality of code.

  • 1728.
    Wagner, Stefan
    et al.
    Univ Stuttgart, DEU.
    Fernandez, Daniel Mendez
    Tech Univ Munich, DEU.
    Felderer, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Vetro, Antonio
    Politecn Torino, ITA.
    Kalinowski, Marcos
    Pontifical Catholic Univ Rio de Janeiro, BRA.
    Wieringa, Roel
    Univ Twente, NLD.
    Pfahl, Dietmar
    University of Tartu, EST.
    Conte, Tayana
    Universidade Federal do Amazonas, BRA.
    Christiansson, Marie-Therese
    Karlstad Univ, SWE.
    Greer, Desmond
    Queens Univ Belfast, IRL.
    Lassenius, Casper
    Aalto Univ, FIN.
    Mannisto, Tomi
    Univ Helsinki, FIN.
    Nayebi, Maleknaz
    Univ Calgary, CAN.
    Oivo, Markku
    Univ Oulu, FIN.
    Penzenstadler, Birgit
    California State University, Long Beach, USA.
    Prikladnicki, Rafael
    Pontificia Univ Catolica Rio Grande do Sul, BRA.
    Ruhe, Guenther
    Univ Calgary, CAN.
    Schekelmann, Andre
    Hsch Niederrhein, DEU.
    Sen, Sagar
    Simula, Fornebu, NOR.
    Spinola, Rodrigo
    Salvador Univ UNIFACS, BRA.
    Tuzcu, Ahmed
    zeb.rolfes.schierenbeck.associates GmbH, DEU.
    De la Vara, Jose Luis
    Carlos III Univ Madrid, ESP.
    Winkler, Dietmar
    Tech Univ Wien, AUT.
    Status Quo in Requirements Engineering: A Theory and a Global Family of Surveys2019Ingår i: ACM Transactions on Software Engineering and Methodology, ISSN 1049-331X, E-ISSN 1557-7392, Vol. 28, nr 2, artikel-id 9Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Requirements Engineering (RE) has established itself as a software engineering discipline over the past decades. While researchers have been investigating the RE discipline with a plethora of empirical studies, attempts to systematically derive an empirical theory in context of the RE discipline have just recently been started. However, such a theory is needed if we are to define and motivate guidance in performing high quality RE research and practice. We aim at providing an empirical and externally valid foundation for a theory of RE practice, which helps software engineers establish effective and efficient RE processes in a problem-driven manner. We designed a survey instrument and an engineer-focused theory that was first piloted in Germany and, after making substantial modifications, has now been replicated in 10 countries worldwide. We have a theory in the form of a set of propositions inferred from our experiences and available studies, as well as the results from our pilot study in Germany. We evaluate the propositions with bootstrapped confidence intervals and derive potential explanations for the propositions. In this article, we report on the design of the family of surveys, its underlying theory, and the full results obtained from the replication studies conducted in 10 countries with participants from 228 organisations. Our results represent a substantial step forward towards developing an empirical theory of RE practice. The results reveal, for example, that there are no strong differences between organisations in different countries and regions, that interviews, facilitated meetings and prototyping are the most used elicitation techniques, that requirements are often documented textually, that traces between requirements and code or design documents are common, that requirements specifications themselves are rarely changed and that requirements engineering (process) improvement endeavours are mostly internally driven. Our study establishes a theory that can be used as starting point for many further studies for more detailed investigations. Practitioners can use the results as theory-supported guidance on selecting suitable RE methods and techniques.

  • 1729.
    Wahlström, Simon
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Comparing Scaling Benefits of Monolithic and Microservice Architectures Implemented in Java and Go2019Självständigt arbete på grundnivå (högskoleexamen), 10 poäng / 15 hpStudentuppsats (Examensarbete)
  • 1730.
    Walczak, Wojciech
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Fractal Compression of Medical Images2008Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Medical images, like any other digital data, require compression in order to reduce disk space needed for storage and time needed for transmission. The lossless compression methods of still images can shorten the file only to a very limited degree. The application of fractal compression to medical images would allow obtaining much higher compression ratios. While the fractal magnification – an inseparable feature of the fractal compression – would be very useful in presenting the reconstructed image in a highly readable form. However, like all irreversible methods, the fractal compression is connected with the problem of information loss, which is especially troublesome in the medical imaging. A very time consuming encoding process, which can last even several hours, is another bothersome drawback of the fractal compression. Based on a survey of literature and own cogitations, the author attempts to provide an adapted to the needs of medical imaging solution that will overcome the unfavorable ailments of the fractal compression methods. The thesis does not provide only theoretical deliberations but also gives implementation of the proposed algorithm, which is used to test the suitability of the fractal compression to medical imaging. The results of the work are more than satisfying – the fidelity of the images compressed with the proposed fractal compression method meets the requirements imposed on the medical images and the fractal magnification outperforms other magnification techniques.

  • 1731.
    Wanderydz, Kristoffer
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    WEB APPLICATION SECURITY IN THE JAVA ENVIRONMENT2012Självständigt arbete på grundnivå (kandidatexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    This project focuses on web security. Some of the most famous vulnerabilities, known troubling web applications. Has been collected and analyzed. Each vulnerability collected in this project, was exploited and secured. Demon- strations from a web application prototype, developed for this project. Brings real examples for each vulnerability, both secured, and insecured. The proto- type ran on a Tomcat web server, and was developed with frameworks such as Web, Spring and Hibernate. Connected to one PostgreSQL data source. All vulnerabilities was successfully implemented in Spring framework, and they were all exploited. Every vulnerability was also secured, with different tools and methods from earlier mentioned frameworks. As a result, real examples from the prototype is used for demonstration in the project, both in a secure and an insecure state. The result views Spring as a framework with good security potential. Most of the Spring specific vulnerabilities, are logical design flaws from developers that can be avoided. Vulnerabilities not related to Spring, such as the one collected for this project. Could be prevented by using methods from the Spring framework or intelligent programming. Which leads to conclusions. Web applications are always exposed to attacks, no matter the framework in use. Creative hackers search to discover new vul- nerabilities, and update old ones all the time. Developers has a responsibility, towards the web applications users. Web applications can not just developed for normal use, but also against possible misuse. Frameworks with good reputation and well processed models, is a good ground for developing a secure application.

  • 1732.
    Wang, Cheng
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Liu, Changling
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Adopting DevOps in Agile: Challenges and Solutions2018Självständigt arbete på avancerad nivå (masterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Background. DevOps is a hot topic in recent years. It emphasizes the combination of development and operation. Agile is one of the most popular development methods, but Agile mainly focused on software development part, there is no more involvement in deployment and operations. In this case, many companies consider adopting DevOps in Agile to attempt to improve the situation.

    Objectives. The combination of two different technologies is bound to produce some challenges, whether it is for practitioners or researchers, it is very important to find these challenges and mitigate them, so this article aims to investigate the challenges of adopting DevOps in Agile, then through the systematic literature review and survey questionnaire to determine the corresponding mitigation strategy. Then, in order to detail understand the process of adopting DevOps in Agile, we use interview to research the real process of adopting DevOps in agile.

    Methods. According to our research question, we used the systematic literature review(SLR), survey questionnaire and interview as our research methodology. Through literature review, we collected data of adopting DevOps in Agile, and summary the challenges and its relevant mitigation strategies. Then survey questionnaire helped us linking the content of literature to the industry, and compare their difference. Through the interview, we explored the actual process of adopting DevOps in Agile in industry, and correspond the challenges to the actual process.

    Results. Our study summarized the software development process of adopting DevOps based on Agile and revealed 23 challenges and corresponding mitigation strategies. The report also compares the commonalities and gaps between the results from the literature and the findings of real-life adopting of DevOps challenges and mitigation strategies.

    Conclusions. In this article, we introduced the challenges and corresponding mitigation strategies for adopting DevOps based on agile and summarize the corresponding software development process. The obvious challenges and mitigation strategies were divided into four categories: 1) People 2) Project 3) Process 4) Organization, after which we conducted further discussions based on the actual conditions and compared the results of systematic literature review and the results of questionnaire to detail explore their difference.

  • 1733. Wang, Tianran
    et al.
    Wang, Shengjie
    A study on the influence of cultural differences on the behavior of software engineers/managers between Chinese and Scandinavians.2019Självständigt arbete på avancerad nivå (masterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Abstract

    Background: In the context of increasing globalization, more and more software engineers/managers work in foreign companies, and they are exposed to the culture of different countries. According to Hofstede's five cultural dimensions, culture can be divided into Individualism and Collectivism, Power Distance, Masculinity, Uncertainty avoidance, and Long-term orientation and short-term orientation. From extensive empirical research performed by Hofstede and his colleagues, we found that the cultural dimension scores of different countries are different, which shows that different countries have different cultures. Through study related papers, we find that cultural differences can affect the behavior of software engineers/managers, causing differences in the behavior of software engineers/managers, and some behavioral differences can make influences/misunderstandings between software engineers/managers. These influences/misunderstandings may have an impact on project progress and personal work during software development.

    Objectives: In this thesis, we want to understand the concrete behavioral differences in how software engineers/managers work caused by cultural differences. After getting these behavioral differences, we want to understand which influence or misunderstandings arise from the software engineers/managers' behavioral differences. Finally, we want to get some suggestions from software engineers/managers on how to prevent/solve these misunderstandings or influences, we summarized these suggestions to help them face people from Chinese or Scandinavian culture.  

    Methods: In this research, we used qualitative research. We chose a systematic literature review (SLR) to helped us answer which behavioral differences will be caused by cultural differences. Then we used questionnaire and interview the two survey methods to collect which influence or misunderstandings arise from the software engineers/managers' behavioral differences and some suggestions to help software engineers/managers to solve/prevent negative influence or misunderstandings.

    Results: Through systematic literature review, we have collected 26 papers, and classified the results from these 26 papers according to five cultural dimensions, summarizing and analyzing the behavioral differences between Chinese and Scandinavian software engineers/managers. Through questionnaires and interviews, we got 37 responses. For these responses, we use coding to classify the data, finally, we analyzed and list the influences/misunderstandings and suggestions. Finally we have collected 64 behavioral differences, 7 influences or misunderstandings, 15 preventive measures and 8 solutions to prevent or resolve these influence/misunderstanding.

    Conclusions: Our research has achieved research goals and answered research questions. Comparing the behavioral differences collected by SLR and survey, we found that survey responses can confirm that most of the behavioral differences in SLR studies experienced by Chinese and Scandinavian software engineers/managers. But there are some behavioral differences that don't appear in both the Survey and SLR data, this should be caused by the sample of our research is not large enough. For these behavioral differences, we found that respondents knew that there were cultural differences between Chinese and Scandinavian software engineers/managers. But not all respondents have been exposed to these behavioral differences. There are also individual differences in the impact of behavioral differences on software engineers/managers. We also found that the best way to solve/prevent these effects is to communicate more.

  • 1734.
    Wanganga, George
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Effective Requirements Management2004Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    In many smaller companies, requirements management is a daunting challenge. Smaller groups mean fewer resources, and many organizations focus their efforts on design, development and testing not on managing requirements. Some small organizations may perceive requirements management as an activity only for large organizations that have complex products and large staffs to support the effort. Poor and uncontrolled requirement engineering processes yield low quality, highly expensive software products. Obviously, customers are highly dissatisfied with such systems. One of the most critical requirement engineering processes that grossly contribute to this misnomer is lack of “effective requirements management” Information Technology Associates (ITA) has had many challenges resulting from some poor and uncontrolled requirements engineering processes. Lack of effective requirements traceability has also had its share in plaguing ITA in software development activities. ITA started small and so it handled its requirements documentation manually as it only dealt with few customer requirements. Time has seen the company expand, and manual handling of customer requirement became difficult. This master thesis therefore aims to investigate: ♦ The state-of-practice, regarding requirements engineering and requirements management within a medium-sized software development company. ♦ How to successfully implement effective requirement management process within the ITA Company. ♦ How to successfully migrate ITA Company into this RE process while ensuring minimum hassles.

  • 1735.
    Waqas, Ahmad
    et al.
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Kamal, Fawad
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Modeling Patterns in Software Design2007Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Software patterns provide solutions to recurring design problems, provide a way to reason about the quality attributes, and support stakeholders in understanding the system. Naturally, the use of software patterns emerges from the requirements of the software. Use Cases have been a traditional and authentic approach to document these requirements. We propose a way to mine these patterns by sing use cases and advocate their significance in saving resources and time. For this purpose, an open-source system is discussed and four design patterns are mined with the help of use cases elicited from the documentation and literature available for the selected system. Patterns mined in this system are then document in GOF format.Furthermore, the consequences of few patterns on quality attributes are studied and an additional design pattern is proposed to improve the quality of the system.

  • 1736.
    Waqas, Ahmad
    et al.
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Kamal, Fawad
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för programvarusystem.
    Modeling Patterns in Software Design2007Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Software patterns provide solutions to recurring design problems, provide a way to reason about the quality attributes, and support stakeholders in understanding the system. Naturally, the use of software patterns emerges from the requirements of the software. Use Cases have been a traditional and authentic approach to document these requirements. We propose a way to mine these patterns by sing use cases and advocate their significance in saving resources and time. For this purpose, an open-source system is discussed and four design patterns are mined with the help of use cases elicited from the documentation and literature available for the selected system. Patterns mined in this system are then document in GOF format.Furthermore, the consequences of few patterns on quality attributes are studied and an additional design pattern is proposed to improve the quality of the system.

  • 1737.
    Wasilewski, Dominik
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Modeling of Enterprise Portals with Domain-Specific Language2012Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Enterprise portals are comprehensive solutions that enable centralized access to information and employees. They also support the business processes taking place in companies. The diversity of functionality offered by enterprise portals is the source of the complexity of the manufacturing process of such applications. Domain-Specific Languages (DSL) are a novel approach to solving problems associated with the software development. By limiting the possibilities of expression to the concepts related to a specific area Domain-Specific Languages are more focused on solving specific problems. The subject of this thesis is DSL SharePoint – Domain-Specific Language which supports the production of enterprise portals on Microsoft SharePoint platform. Language was developed with respect to the newest achievements in area of building DSLs. By applying the language in the industry, it was possible to verify the hypothesis that its usage positively affects the quality of software products. To this end, the quality model was built, and products made with the support of language have been compared to those developed in the traditional manner.

  • 1738.
    Wei, Wenyang
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Private User’s Trust on Data sharing in e- health Applications2017Självständigt arbete på avancerad nivå (masterexamen), 20 poäng / 30 hpStudentuppsats (Examensarbete)
    Abstract [en]

    Context. One of the challenges in requirement engineering is the ability using survey as a requirement-engineering tool towards the software to refine user’s requirements. For instance, with the development of the way of healthcare, many advances in technology transformed the way of healthcare. E-health application is one of the technologies. As more and more health information that is stored electronically, e- health applications have given rise to trust issue in the area of data sharing. Identified the relationship between trust and data sharing based on the survey method is a valid approach, but the current studies still do not give a definite guideline about how requirement engineering should use a survey method step-by-step to refine the needs of users’ trust into software attributes. Based on the mentioned situation in e-health, defining a method to design survey to elicit requirements is needed.

    Objective. In this paper, the aim of the study is to design a survey method for refining user’s requirements of trust in requirement engineering based on the current state-of-art. The paper present the research on data sharing in e-health application. Methods. This study presented an action research, which identified the way about how to refine user’s requirement of trust. Survey was the main approach to do investigation among the e-health applications. Three cycles of AR were conducted in this paper, and three versions of questionnaires were designed in the research process in order to identify the factors that affected user’s trust in data sharing in e-health applications.

    Results. Through the action research, I found out three factors that affected user’s trust in data sharing, then the factors were identified, analysis and summarized, and the relationship between trusts and the factors is describe based on analysis results of the collected data, which obtain from the improved questionnaires. To find out the relationship between trust and the factors help present the process that how to design an accurate survey to refine user’s requirements.

    Based on the process and results of the action research, the survey guideline to refine user’s requirements of trust is designed and described. Conclusions. Based on the results that obtained in this study, I designed a preliminary survey guideline for refining user’s requirements of trust. This study will help requirement engineering to elicit requirement of trust in e-health based on a new and specific survey method. 

  • 1739.
    Wester, Alfred
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Fredriksson, Olof
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Jämförelse av Mysql och MongoDb2012Självständigt arbete på grundnivå (kandidatexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    Speed is a very important factor in websites and other types of applications and almost all applications stores some type of data, normally in a database. For an example a blog typically saves users, posts and comments. There’s a high risk that as the amount of data in the database grows, the time for inserting and requesting specific data increases. If it takes more than some seconds to view a specific page, a user will normally leave the site. However, it’s a fact that the database will grow while the application will become more popular but it’s possible to save a lot of time if using right database, and structure. In this thesis MongoDB and MySQL will be compared with focus on time consumption. SQL (Structured Query Language) is the language which most databases use. This kind of database stores data in structured tables and noting can be added to them if the type of data is incorrect. SQL also support relations between tables. MySQL is a very popular relational database management system (RDBMS) which for example websites frequently makes use of. NoSQL is a new type of databases where the data is stored in collections without any kind of structure, unlike the well known SQL databases where the data is stored in structured tables. Because of the non-structure, these types of databases are designed to be fast and scalable over multiple machines. Mongodb is a such kind of NoSql-database. Tests has been done both on inserting and processing when handling up to 4 millions entities, MongoDB performs better in almost every test. Results shows that the processing time is shorter using MongoDb in the cases that this thesis is covering, and that it’s possible to implement a much fast application when using MongoDb instead of Mysql as database.

  • 1740.
    Westman, Adam
    et al.
    Blekinge Tekniska Högskola, Sektionen för planering och mediedesign.
    Gransing, Jonas Chanasima
    Blekinge Tekniska Högskola, Sektionen för planering och mediedesign.
    Palm, Mikael
    Blekinge Tekniska Högskola, Sektionen för planering och mediedesign.
    Malmgren, Tommie
    Blekinge Tekniska Högskola, Sektionen för planering och mediedesign.
    Spelskapande men en komponentbaserad arbetsprocess2011Självständigt arbete på grundnivå (kandidatexamen)Studentuppsats (Examensarbete)
    Abstract [sv]

    Syftet med detta kandidatarbete är att testa en arbetsmetod som skiljer sig ifrån det en mindre grupp i vanliga fall använder sig av: en komponentbaserad arbetsprocess för att utforska och sammanställa arbetserfarenheten med den komponentbaserade arbetsmetoden, utvecklar vi därför ett digitalt spel.

  • 1741.
    Westman, Joakim
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Marinescu, Teodor
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    C, C++, Java och Python: En prestandajämförelse mellan fyra programmeringsspråk2011Självständigt arbete på grundnivå (kandidatexamen)Studentuppsats (Examensarbete)
    Abstract [sv]

    In today’s society computers are getting a much more important role. To get a computer to work as intended it has to be programmed. A computer program is written with programming languages. There is an abundance of programming languages available today and there are many differences and similarities between them. The different languages have their advantages and their disadvantages where some of them are intended for fast performance, some to be cheap on memory usage, and some are developed to be easy to program on. In our thesis we have chosen to compare four of todays most common languages, C, C++, Java and Python. These languages were chosen because we have worked with three of them during our study period (C, C++ and Java). Python was chosen because it is an interpreted language and not a compiled one. It also have a very different syntax compared to the other languages which makes it interesting. Our comparison, which focuses on performance, has its foundation in the tests we have made, but also on results from a research survey that we also made. I this survey forty software developers, from Swedish companies, have participated. The tests we have made measure the languages performance, regarding time, by implementing and running two common algorithms. During these tests vi have also chosen to register the amount of memory these algorithms use during runtime. The results we have extracted from our tests and our survey are compiled, and these results are then analysed to be able to compare the four programming languages to each other. The tests that have been done show that Java is the language that performs best, with C and C ++ second best and then Python performing the worst. Our survey answers, on the other hand, indicates that C and C++ should have outperformed Java.

  • 1742.
    Widell, Sanna
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Levin, Linnéa
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Möjligheter och begränsningar i molnet2014Självständigt arbete på grundnivå (kandidatexamen)Studentuppsats (Examensarbete)
    Abstract [sv]

    Idag väljer många företag och kommuner att placera data i molnet istället för på en lokal server, detta medför nya problem som tidigare inte varit aktuella. Datainspektionen har påpekat brister i hur två kommuner använder molntjänster för att lagra personlig data då de ställer sig tveksamma till molnleverantörernas hantering av data samt insynen till molnleverantörerena. I detta arbete kommer det undersökas hur den svenska personuppgiftslagen fungerar när data läggs ut i en molntjänst. Resultatet av uppsatsen kommer även visa på de olika säkerhetshoten som finns i molnet och se vad säkerhetsexperter säger för att ta reda på om kommuner och företag är medvetna om och uppmärksammar samma hot. För att ta reda på detta har intervjuer genomförts med en svensk molnleverantör, företag som utvecklar tjänster mot molnet, privatpersoner som nyttjar molnet och experter inom säkerhet från Blekinge Tekniska Högskola, BTH. Resultatet av studien visar att det är svårt att se om en amerikansk leverantör uppfyller de svenska lagarna för personuppgifter, det visar också att det är teoretiskt möjligt att anlita en svensk leverantör och uppfylla lagen. Det har även visat sig att den största oron gällande molnet är bristen på kontroll av data.

  • 1743.
    Wikstrand, Greger
    et al.
    Umeå universitet, Institutionen för datavetenskap.
    Börstler, Jürgen
    Umeå universitet, Institutionen för datavetenskap.
    An Analysis of Success Factors for a Team-Project Software Development Course2006Konferensbidrag (Refereegranskat)
    Abstract [en]

    Team project courses are important elements in most Computer Science and Software Engineering programs. For many students, the team project course represents the only non-trivial software development experience before graduation. The team project should be used to introduce them to important project and process issues that otherwise are very difficult to teach. Sloppy documentation, poor project planning and tracking or ineective communication will eventually affect the teams and teach the students a important lessons for their future work.

    In this paper, we investigate how students select, carry out and complete their projects. The results show that students tend to select mainstream projects with good specifications and that certain project types are less suitable for the course. The results also show that process related deliverables are crucial to the final outcome of the projects. Among the hardest, but also most important, deliverables we find the project plan.

  • 1744. Wikstrand, Greger
    et al.
    Feldt, Robert
    Gorantla, JK
    Zhe, Wang
    White, Conor
    Dynamic Regression Test Selection Based on a File Cache: An Industrial Evaluation2009Konferensbidrag (Refereegranskat)
    Abstract [en]

    This paper presents a simple method that computes test case coverage information from information on what files were updated to fix a fault found by the test case. It uses a cache to monitor fault-prone files and recommends test cases to rerun to cover updated files. We present an evaluation of the method during two months of development of a large, industrial, embedded, real-time software system. Our results show that the method is effective, reaching weekly cache hit rates in the range 50-80%.

  • 1745.
    Williamsson, Ia
    Blekinge Tekniska Högskola, Sektionen för teknik, Avdelningen för för interaktion och systemdesign.
    Total Quality Maintenance (TQMain) A predictive and proactive maintenance concept for software2006Självständigt arbete på avancerad nivå (magisterexamen)Studentuppsats (Examensarbete)
    Abstract [en]

    This thesis describes an investigation of the possibility to apply a maintenance concept originally developed for the industry, on software maintenance. Today a large amount of software development models exist but not many of them treat maintenance as a part of the software life cycle. In most cases maintenance is depicted as an activity towards the end of the software life cycle. The high cost ascribed to software maintenance motivates for improvements. The maintenance concept TQMain proposed in this thesis distinguishes from other maintenance concepts by its use of preventive, predictive and proactive maintenance strategies. TQMain uses a common database to store real-time data from various departments and uses it for analyse and assessment to track the development of deviations in the condition of the production process and product quality at an early stage. A continuous cyclic improvement of the maintenance strategy is reached by comparing the data from the real-time measurements with data from the database. The ISO/IEC Software engineering – Product qualities is used as a source of empiric data to conclude that the correct quality characteristics are used for identifying software product quality and its characteristics and compare them with the characteristics of industrial product quality. The results presented are that in the conceptual outline of TQMain measures are obviously not the same as in software maintenance, but the aspect of product quality is common for both. The continuous cyclic improvement of the product quality that TQMain features together with the aspect of detecting potential failures before they occur would, judging from the conceptual outline of TQMain be applicable on software maintenance.

  • 1746.
    Wilson, Magnus
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Wnuk, Krzysztof
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Business modeling and flexibility in software-intensive product development: A systematic literature review2018Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), Springer Verlag , 2018, Vol. 11195, s. 292-304Konferensbidrag (Refereegranskat)
    Abstract [en]

    Continuously achieving and maintaining competitive advantage is the critical survival factor for software-intensive product development companies undergoing digitalization transformation. These companies remain uncertain if investments in business modeling is sufficient to cope with rapidly changing business models, technology, and customer demands. We conducted a Systematic Literature Review using the snowballing methodology to explore the effects of business modeling on business flexibility and variability in the realization. Our results confirm a research gap regarding translating desired strategic flexibility into business options that can efficiently and effectively be implemented using software-based variability in the realization. We conclude that more research is needed consolidating business model innovation, experimentation, and operationalization. Building on theories for learning and knowledge creation, we propose a framework for describing change and analyzing strategic, tactical and operational choices in business model experimentation. © IFIP International Federation for Information Processing 2018.

  • 1747.
    Wilson, Magnus
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik. Ericsson AB.
    Wnuk, Krzysztof
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    The implications of digitalization on business model changeIngår i: Business & Information Systems Engineering, ISSN 1867-0202Artikel i tidskrift (Övrigt vetenskapligt)
    Abstract [en]

    Many software-intensive product development companies are still struggling with the alignment of business and technology changes to find an optimal balance between products and services while remaining agile, effective, and efficient. Business model alignment is highlighted as a new business model research area for understanding the relationships between the dynamic nature of business models, organization design, and the value creation in the business model activities.

    In this paper, we synthesize the impact of digitalization on business model change for the software-intensive product development industry. Based on established theories, we link effectiveness and efficiency, to value creation in business model activities and organizational learning, in a step towards conceptualizing business model change as a significant part of developing software architectural support for a business model change in a learning organization.  

    Our unit of analysis is the value created in a transaction between two actors in a business model activity, and how that value is supporting transforming a capability into an efficient ability. Based on our results and to facilitate the cross-disciplinary analysis of business model dynamics, we present seven propositions and a conceptual model linking effectiveness, efficiency, value, transaction, and organizational learning to business model change via the \textit{value membrane}. 

  • 1748.
    Wilson, Magnus
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Wnuk, Krzysztof
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Silvander, Johan
    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 Literature Review on the Effectiveness and Efficiency of Business Modeling2018Ingår i: e-Informatica Software Engineering Journal, ISSN 1897-7979, E-ISSN 2084-4840, Vol. 12, nr 1, s. 265-302Artikel, forskningsöversikt (Refereegranskat)
    Abstract [en]

    Background: Achieving and maintaining a strategic competitive advantage through business and technology innovation via continually improving effectiveness and efficiency of the operations are the critical survival factors for software-intensive product development companies. These companies invest in business modeling and tool support for integrating business models into their product development, but remain uncertain, if such investments generate desired results. Aim: This study explores the effects of business modeling on effectiveness and efficiency for companies developing software-intensive products. Method: We conducted a systematic literature review using the snowballing methodology, followed by thematic and narrative analysis. 57 papers were selected for analysis and synthesis, after screening 16 320 papers from multiple research fields. Results: We analyzed the literature based on purpose, benefit, challenge, effectiveness, and efficiency with software and software-intensive products as the unit of analysis. The alignment between strategy and execution is the primary challenge, and we found no evidence that business modeling increases effectiveness and efficiency for a company. Any outcome variations may simply be a result of fluctuating contextual or environmental factors rather than the application of a specific business modeling method. Therefore, we argue that governance is the fundamental challenge needed for business modeling, as it must efficiently support simultaneous experimentation with products and business models while turning experiences into knowledge. Conclusion: We propose a conceptual governance model for exploring the effectiveness and efficiency of business modeling to occupy the missing link between business strategy, processes and software tools. We also recommend managers to introduce a systematic approach for experimentation and organizational learning, collaboration, and value co-creation.

  • 1749.
    Winqvist, Mikael
    et al.
    Blekinge Tekniska Högskola, Fakulteten för teknikvetenskaper, Institutionen för industriell ekonomi.
    Jolhammar, Jonas
    Blekinge Tekniska Högskola, Fakulteten för teknikvetenskaper, Institutionen för industriell ekonomi.
    Personality traits and preference for media richness in the software engineering profession2019Självständigt arbete på avancerad nivå (masterexamen), 10 poäng / 15 hpStudentuppsats (Examensarbete)
  • 1750. Winter, Jeff
    Measuring usability - balancing agility and formality: for stakeholders’ needs in software development2009Licentiatavhandling, sammanläggning (Övrigt vetenskapligt)
    Abstract [en]

    The main focus of the research presented in this thesis is a usability evaluation framework for mass market mobile devices, allowing measurement, comparison and presentation of the usability of hand held devices. The research has been a cooperation between an academic and an industrial partner, based on an action research approach, following the processes of Cooperative Method Development (CMD). It has used a case study approach, where the data has been analysed using techniques taken from grounded theory. Ethnography and participatory design have been central to both the research and the cooperation. With its basis in the evaluation framework, and its use of quantitative measurements and qualitative judgments framed by a focus on usability testing, this thesis contributes to aspects related to capturing real world usage in a continuously changing society, and supporting information needs in the process of building software. The evaluation framework can be used as a quality assurance tool in a wide perspective. It measures usability and the user experience, quickly and flexibly, and in so doing measures aspects of quality in use. It has been tested in a complex industrial development project and is a valuable and flexible tool that is easy for a usability expert to learn and use, to measure and help build quality on the customer’s terms. The results we have arrived at are of practical and theoretical interest within software engineering and the industrial telecom sphere. Several features and aspects of the evaluation framework are new and challenging. These are: its mix of qualitative and quantitative methods, allowing it to target many different stakeholders; experience in applying these methods in the technology-focused and rapidly changing mobile phone area; the challenge of addressing end users in a mass market; the challenge of finding presentation models for the many different stakeholders; the challenge of making sure the framework can be used in different stages in the industrial software development process. The framework is related to three areas of software engineering, Market Driven Requirements Engineering, Statistical Usage Testing, and Organisation and Product Together. Our work includes a discussion of the need for agility, which has not so far been focused upon and discussed within the area of software engineering and usability. The combination of factors included in the framework means that is unique in solving a number of the problems that are found in these different areas within software engineering, especially in a rapidly changing marketplace. We also contribute to the field, through the qualitative element of the evaluation framework, which is inspired by ethnography and participatory design. It thereby makes a contribution that can improve practice in the field of software engineering, and that contributes to the theoretical work that is being performed within these different research areas.

32333435363738 1701 - 1750 av 1886
RefereraExporteraLänk till träfflistan
Permanent länk
Referera
Referensformat
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Annat format
Fler format
Språk
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Annat språk
Fler språk
Utmatningsformat
  • html
  • text
  • asciidoc
  • rtf