2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C)

14-22 May 2016

Filter Results

Displaying Results 1 - 25 of 179
  • [Title page i]

    Publication Year: 2016, Page(s): i
    Request permission for commercial reuse | |PDF file iconPDF (17 KB)
    Freely Available from IEEE
  • [Title page iii]

    Publication Year: 2016, Page(s): iii
    Request permission for commercial reuse | |PDF file iconPDF (90 KB)
    Freely Available from IEEE
  • [Copyright notice]

    Publication Year: 2016, Page(s): iv
    Request permission for commercial reuse | |PDF file iconPDF (133 KB)
    Freely Available from IEEE
  • Table of contents

    Publication Year: 2016, Page(s):v - xx
    Request permission for commercial reuse | |PDF file iconPDF (160 KB)
    Freely Available from IEEE
  • Welcome Message from the Chairs

    Publication Year: 2016, Page(s):xxi - xxvi
    Request permission for commercial reuse | |PDF file iconPDF (1213 KB)
    Freely Available from IEEE
  • Software Engineering in Practice (SEIP) Committee

    Publication Year: 2016, Page(s):xxvii - xxix
    Request permission for commercial reuse | |PDF file iconPDF (83 KB)
    Freely Available from IEEE
  • Software Engineering Education and Training (SEET) Committee

    Publication Year: 2016, Page(s): xxx
    Request permission for commercial reuse | |PDF file iconPDF (71 KB)
    Freely Available from IEEE
  • Software Engineering in Society (SEIS) Committee

    Publication Year: 2016, Page(s):xxxi - xxxii
    Request permission for commercial reuse | |PDF file iconPDF (80 KB)
    Freely Available from IEEE
  • Demonstrations Committee

    Publication Year: 2016, Page(s): xxxiii
    Request permission for commercial reuse | |PDF file iconPDF (71 KB)
    Freely Available from IEEE
  • ACM Student Research Competition (SRC) Committee

    Publication Year: 2016, Page(s): xxxiv
    Request permission for commercial reuse | |PDF file iconPDF (69 KB)
    Freely Available from IEEE
  • Poster Track Committee

    Publication Year: 2016, Page(s): xxxv
    Request permission for commercial reuse | |PDF file iconPDF (72 KB)
    Freely Available from IEEE
  • Visions of 2025 and Beyond (V2025) Committee

    Publication Year: 2016, Page(s):xxxvi - xxxvii
    Request permission for commercial reuse | |PDF file iconPDF (78 KB)
    Freely Available from IEEE
  • Doctoral Symposium (DS) Committee

    Publication Year: 2016, Page(s): xxxviii
    Request permission for commercial reuse | |PDF file iconPDF (71 KB)
    Freely Available from IEEE
  • Technical Briefings (TB) Committee

    Publication Year: 2016, Page(s): xxxix
    Request permission for commercial reuse | |PDF file iconPDF (69 KB)
    Freely Available from IEEE
  • Student Contest on Software Engineering (SCORE) Committee

    Publication Year: 2016, Page(s): xl
    Request permission for commercial reuse | |PDF file iconPDF (76 KB)
    Freely Available from IEEE
  • Video Contest Committee

    Publication Year: 2016, Page(s): xli
    Request permission for commercial reuse | |PDF file iconPDF (63 KB)
    Freely Available from IEEE
  • NSF ICSE 2016 Travel Award Committee

    Publication Year: 2016, Page(s): xlii
    Request permission for commercial reuse | |PDF file iconPDF (67 KB)
    Freely Available from IEEE
  • Sponsors and supporters

    Publication Year: 2016, Page(s):xliii - xliv
    Request permission for commercial reuse | |PDF file iconPDF (294 KB)
    Freely Available from IEEE
  • Progress toward an Engineering Discipline of Software

    Publication Year: 2016, Page(s):3 - 4
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (194 KB) | HTML iconHTML

    Is "software engineering" really engineering? The term was coined in 1968 to call attention to problems with software production. Both theory and practice for software have evolved since then, but do we yet have a true engineering discipline? This keynote sketches the evolution of software engineering, drawing on civil engineering and software architecture for examples that show the progressive co... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Investing in the Impending Digital Quake 80% Jobs/Companies/Research Disrupted?

    Publication Year: 2016, Page(s):5 - 6
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (185 KB) | HTML iconHTML

    The innovation and start-up investment community want to fund SMART (specific, measurable, achievable, relevant, time-bounded) research and education leading to sustainable global impact. The research community can tap into $100B plus in venture funding or use research to join more than 160 Unicorns (startups valued at $1B plus) worth over half a trillion dollars.All domains and subdomains (scienc... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Programming Dangerously! Can Formal Methods and Empirical Software Engineering Come to the Rescue?

    Publication Year: 2016, Page(s): 7
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (150 KB) | HTML iconHTML

    Summary form only given. This award prompts me to reflect on how my team at Microsoft Research was able to bring research in formal methods and empirical software engineering into practice. How did I select the topics for my teams and my research? How did we conduct the research and which methods did we choose? How did we show progress, and equally important when did we decide to stop? I will also... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Is Continuous Adoption in Software Engineering Achievable and Desirable?

    Publication Year: 2016, Page(s): 8
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (206 KB) | HTML iconHTML

    Continuity in software development is all about shortening cycle times. For example, continuous integration shortens the time to integrating changes from multiple developers and continuous delivery shortens the time to get those integrated changes into the hands of users. Although it is now possible to get multiple new versions of complex software systems released per day, it still often takes yea... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • CloudBuild: Microsoft's Distributed and Caching Build Service

    Publication Year: 2016, Page(s):11 - 20
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (1600 KB) | HTML iconHTML

    Thousands of Microsoft engineers build and test hundreds of software products several times a day. It is essential that this continuous integration scales, guarantees short feedback cycles, and functions reliably with minimal human intervention. This paper describes CloudBuild, the build service infrastructure developed within Microsoft over the last few years. CloudBuild is responsible for all as... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Continuous Deployment at Facebook and OANDA

    Publication Year: 2016, Page(s):21 - 30
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (751 KB) | HTML iconHTML

    Continuous deployment is the software engineering practice of deploying many small incremental software updates into production, leading to a continuous stream of 10s, 100s, or even 1,000s of deployments per day. High-profile Internet firms such as Amazon, Etsy, Facebook, Flickr, Google, and Netflix have embraced continuous deployment. However, the practice has not been covered in textbooks and no... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An Empirically Developed Method to Aid Decisions on Architectural Technical Debt Refactoring: AnaConDebt

    Publication Year: 2016, Page(s):31 - 40
    Request permission for commercial reuse | Click to expandAbstract |PDF file iconPDF (575 KB) | HTML iconHTML

    Architectural Technical Debt is regarded as sub-optimal architectural solutions that need to be refactored in order to avoid the payment of a costly interest in the future. However, decisions on if and when to refactor architecture are extremely important and difficult to take, since changing software at the architectural level is quite expensive. Therefore it is important, for software organizati... View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.