Ändra sökning
Avgränsa sökresultatet
1 - 24 av 24
RefereraExporteraLänk till träfflistan
Permanent länk
Referera
Referensformat
  • apa
  • harvard1
  • 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.
  • 1.
    Alégroth, Emil
    et al.
    Chalmers, SWE.
    Gustafsson, Johan
    SAAB AB, SWE.
    Ivarsson, Henrik
    SAAB AB, SWE.
    Feldt, Robert
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Replicating Rare Software Failures with Exploratory Visual GUI Testing2017Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 34, nr 5, s. 53-59, artikel-id 8048660Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Saab AB developed software that had a defect that manifested itself only after months of continuous system use. After years of customer failure reports, the defect still persisted, until Saab developed failure replication based on visual GUI testing. © 1984-2012 IEEE.

  • 2.
    Britto, Ricardo
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Šmite, Darja
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Damm, Lars-Ola
    Ericsson, SWE.
    Software Architects in Large-Scale Distributed Projects: An Ericsson Case Study2016Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 33, nr 6, s. 48-55, artikel-id 7725230Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Software architects are key assets for successful development projects. However, not much research has investigated the challenges they face in large-scale distributed projects. So, researchers investigated how architects at Ericsson were organized, their roles and responsibilities, and the effort they spent guarding and governing a large-scale legacy product developed by teams at multiple locations. Despite recent trends such as microservices and agile development, Ericsson had to follow a more centralized approach to deal with the challenges of scale, distribution, and monolithic architecture of a legacy software product. So, the architectural decisions were centralized to a team of architects. The team extensively used code reviews to not only check the code's state but also reveal defects that could turn into maintainability problems. The study results also suggest that the effort architects spend designing architecture, guarding its integrity and evolvability, and mentoring development teams is directly related to team maturity. In addition, significant investment is needed whenever new teams and locations are onboarded.

  • 3. Fricker, Samuel
    et al.
    Gorschek, Tony
    Byman, Carl
    Schmidle, Armin
    Handshaking with Implementation Proposals: Negotiating Requirements Understanding2010Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 27, nr 2, s. 72-80Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Requirements engineering focuses on good specification practices but has yet to find working solutions for effective requirements communication. Inadequate communication and tacit assent to a demanding customer's requests make it hard to fully understand a project's requirements. A negotiation process, called handshaking with implementation proposals, has been used to communicate requirements effectively—even in situations where almost no written requirements exist and where distance separates the customer from developers. Handshaking is an efficient, flexible technique that uses architectural options to understand requirements, to make implementation decisions that create value, and to establish the foundation for a stable project. This article describes the communication challenges, solutions, and lessons learned in developing the handshaking process and applying it in industrial practice.

  • 4.
    Garousi, Vahid
    et al.
    Wageningen University, NLD.
    Giray, Görkem
    Kokteyl A, , TUR.
    Tuzun, Eray
    Bilkent Üniversitesi, TUR.
    Catal, Cagatay
    Wageningen University, NLD.
    Felderer, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Closing the Gap Between Software Engineering Education and Industrial Needs2019Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    According to different reports, many recent software engineering graduates often face difficulties when beginning their professional careers, due to misalignment of the skills learnt in their university education with what is needed in industry. To address that need, many studies have been conducted to align software engineering education with industry needs. To synthesize that body of knowledge, we present in this paper a systematic literature review (SLR) which summarizes the findings of 33 studies in this area. By doing a meta-analysis of all those studies and using data from 12 countries and over 4,000 data points, this study will enable educators and hiring managers to adapt their education / hiring efforts to best prepare the software engineering workforce. IEEE

  • 5.
    Garousi, Vahid
    et al.
    Wageningen Univ, NLD.
    Kucuk, Baris
    Proven Informat Technol, TUR.
    Felderer, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    What We Know About Smells in Software Test Code2019Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 36, nr 3, s. 61-73Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Test smells are poorly designed tests and negatively affect the quality of test suites and production code. We present the largest catalog of test smells, along with a summary of guidelines, techniques, and tools used to deal with test smells.

  • 6. Giardino, Carmine
    et al.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Paternoster, Nicolo
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Abrahamsson, Pekka
    VOICE OF EVIDENCE What Do We Know about Software Development in Startups?2014Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 31, nr 5, s. 28-32Artikel i tidskrift (Refereegranskat)
  • 7. Giardino, Carmine
    et al.
    Unterkalmsteiner, Michael
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Paternoster, Nicoló
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Abrahamsson, Pekka
    What do we know about software development in startups?2014Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 31, nr 5, s. 28-32Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    An impressive number of new startups are launched every day as a result of growing new markets, accessible technologies, and venture capital. New ventures such as Facebook, Supercell, Linkedin, Spotify, WhatsApp, and Dropbox, to name a few, are good examples of startups that evolved into successful businesses. However, despite many successful stories, the great majority of them fail prematurely. Operating in a chaotic and rapidly evolving domain conveys new uncharted challenges for startuppers. In this study, the authors characterize their context and identify common software development startup practices.

  • 8. Gorschek, Tony
    et al.
    Fricker, Samuel
    Palm, Kenneth
    Kunsman, Steven
    A Lightweight Innovation Process for Software-Intensive Product Development2010Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 27, nr 1, s. 37-45Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    The product development environment facing most companies today requires a long-term perspective featuring the conception and development of long-term innovations. This can be hard when close quarter bottom-line results dominate. Without innovation, competitive advantages decrease over time. This is especially true for companies producing software-intensive systems. Software is becoming a large part of the competitive advantage of traditionally hardware-focused systems such as cars, robots, or power systems, where feature sets traditionally offered and controlled by hardware are transferred to software. As software's impact and influence grows, so do the possibilities for innovation and increasing the competitive advantage through software. Star Search is a lightweight innovation model based on best practices from innovation management literature as well as two industry cases. It employs face-to-face screening and idea refinement using heterogeneous audition teams. Star Search was developed in collaboration with, and subsequently piloted at, two companies. It has helped increase the long-term perspective of product development by increasing the level of new ideas that make it to product planning and development

  • 9. Gorschek, Tony
    et al.
    Garre, Per
    Larsson, Stig
    Wohlin, Claes
    A Model for Technology Transfer in Practice2006Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 23, nr 6, s. 88-95Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Technology transfer, and thus industry-relevant research, involves more than merely producing research results and delivering them in publications and technical reports. It demands close cooperation and collaboration between industry and academia throughout the entire research process. During research conducted in a partnership between Blekinge Institute of Technology and two companies, Danaher Motion Saro AB (DHR) and ABB, we devised a technology transfer model that embodies this philosophy. We initiated this partnership to conduct industry-relevant research in requirements engineering and product management. Technology transfer in this context is a prerequisite: it validates academic research results in a real setting, and it provides a way to improve industry development and business processes

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

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

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

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

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

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

  • 12.
    Martins, Luiz Eduardo G.
    et al.
    Univ Fed Sao Paulo, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    AN AGENDA FOR THE COMING YEARS2017Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 34, nr 4, s. 56-57Artikel i tidskrift (Refereegranskat)
  • 13.
    Martins, Luiz Eduardo Galvão
    et al.
    Universidade Federal de Sao Paulo, BRA.
    Gorschek, Tony
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Requirements Engineering for Safety-Critical Systems: Overview and Challenges2017Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 34, nr 4, s. 49-57, artikel-id 7974683Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    In a world that depends increasingly on complex, critical, and intertwined systems, requirements engineering is crucial to developing and maintaining safety-critical systems (SCSs). Researchers studied the state of the art (through the literature) and the state of the practice (through in-depth interviews with practitioners) to discover what approaches are available for capturing, specifying, and communicating safety requirements throughout the SCS lifecycle and to determine the remaining challenges. © 2017 IEEE.

  • 14.
    Penzenstadler, Birgit
    et al.
    Calif State Univ Long Beach, USA.
    Duboc, Leticia
    La Salle Univ Ramon Llull, ESP.
    Venters, Colin C.
    Univ Huddersfield, GBR.
    Betz, Stefanie
    Furtwangen Univ, DEU.
    Seyff, Norbert
    Univ Appl Sci & Arts Northwestern Switzerland, CHE.
    Wnuk, Krzysztof
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik. Blekinge Inst Technol, Software Engn Res Grp, Karlskrona, Sweden..
    Chitchyan, Ruzanna
    Univ Bristol, GBR.
    Easterbrook, Steve M.
    Univ Toronto, CAN.
    Becker, Christoph
    Univ Toronto, CAN.
    Software Engineering for Sustainability Find the Leverage Points!2018Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 35, nr 4, s. 22-33Artikel i tidskrift (Refereegranskat)
  • 15.
    Unterkalmsteiner, Michael
    et al.
    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.
    Process Improvement Archaeology: What led us here and what’s next?2018Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 35, nr 4, s. 53-61Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    While in every organization corporate culture and history change over time, intentional efforts to identifyperformance problems are of particular interest when trying to understand the current state of an organization.The results of past improvement initiatives can shed light on the evolution of an organization, and represent,with the advantage of perfect hindsight, a learning opportunity for future process improvements. Weencountered the opportunity to test this premise in an applied research collaboration with the SwedishTransport Administration (STA), the government agency responsible for the planning, implementation andmaintenance of long-term rail, road, shipping and aviation infrastructure in Sweden.

  • 16. Wohlin, Claes
    The infamous ratio measure [1]2010Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 27, nr 1Artikel i tidskrift (Övrigt vetenskapligt)
  • 17.
    Wohlin, Claes
    et al.
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Aurum, Aybueke
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Angelis, Lefteris
    Phillips, Laura
    Dittrich, Yvonne
    Gorschek, Tony
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Grahn, Håkan
    Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation.
    Henningsson, Kennet
    Kågström, Simon
    Low, Graham
    The Success Factors Powering Industry-Academia Collaboration2012Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 29, nr 2, s. 67-73Artikel i tidskrift (Refereegranskat)
  • 18.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Calefato, Fabio
    Wohlin, Claes
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Cost Savings in Global Software Engineering Where's the Evidence?2015Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 32, nr 4, s. 26-32Artikel i tidskrift (Övrigt vetenskapligt)
  • 19.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Kuhrmann, Marco
    Keil, Patrick
    Virtual Teams: Guest Editor’s Introduction2014Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 31, nr 6, s. 41-46Artikel i tidskrift (Övrigt vetenskapligt)
  • 20.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Moe, Nils Brede
    SINTEF, Trondheim, NOR.
    Levinta, Georgiana
    Spotify, SWE.
    Floryan, Marcin
    Spotify, SWE.
    Spotify Guilds: How to Succeed With Knowledge Sharing in Large-Scale Agile Organizations2019Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 36, nr 2, s. 51-57, artikel-id 8648260Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    The new generation of software companies has revolutionized the way companies are designed. While bottom-up governance and team autonomy improve motivation, performance, and innovation, managing agile development at scale is a challenge. We describe how Spotify cultivates guilds to help the company share knowledge, align, and make collective decisions.

  • 21.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    Solingen, Rini Van
    Delft University of Technology, NLD.
    Chatzipetrou, Panagiota
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    The Offshoring Elephant in the Room: Turnover Strategies for Addressing Turnover When Offshoring to India2019Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Staffing software projects with engineers from best-cost locations has become a commonality. However, distributed development remains practically challenging with many recurring problems, such as decreased productivity, low quality, and high unforeseen extra costs. One main underlying reason for these challenges is high employee turnover, although often overlooked. In developing locations such as India turnover is significantly large due to personal benefits from ‘job-hopping’. Why is turnover such a problem? Should companies stop sourcing to countries with high turnover or are there known remedies? This research puts turnover of software engineers in India in the spotlight and derives strategies to address it. We share experiences from two industrial cases, discuss important variables for portraying the actual turnover state and its negative impacts. Furthermore, we put forward ten recommendations for actively reducing turnover itself and lowering its negative consequences. IEEE

  • 22.
    Šmite, Darja
    et al.
    Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, Institutionen för programvaruteknik.
    van Solingen, Rini
    What's the True Hourly Cost of Offshoring?2016Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 33, nr 5, s. 60-70Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    An offshore team's hourly costs took three years to become comparable with the in-house team's costs. Getting close to breaking even took five years. Learning costs due to offshore employee turnover were the primary cost factor to get under control.

  • 23. Šmite, Darja
    et al.
    Wohlin, Claes
    A Whisper of Evidence in Global Software Engineering2011Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 28, nr 4, s. 15-18Artikel i tidskrift (Övrig (populärvetenskap, debatt, mm))
  • 24. Šmite, Darja
    et al.
    Wohlin, Claes
    Strategies Facilitating Software Product Transfers2011Ingår i: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 8, nr 5, s. 60-66Artikel i tidskrift (Refereegranskat)
    Abstract [en]

    Globalization of software work has become common in today's market. As part of cost-reduction strategies, many product-focused software companies started shipping their product development to insourcing and outsourcing offshore locations. Unfortunately, moving software products from one site to another isn't always a good business strategy for either the organization or the product. In this article, the authors discuss findings from studying software insourcing transfers at Ericsson, a large software product development company headquartered in Sweden. Their findings suggest that certain product, personnel, and process characteristics can facilitate the execution of an offshore insourcing transfer. On the basis of research conducted together with the company, they share a list of critical factors alleviating transfer difficulties and seven strategies facilitating transition of software work across sites.

1 - 24 av 24
RefereraExporteraLänk till träfflistan
Permanent länk
Referera
Referensformat
  • apa
  • harvard1
  • 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