mdh.sePublications
Change search
Refine search result
1 - 6 of 6
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Rows per page
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sort
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
Select
The maximal number of hits you can export is 250. When you want to export more records please use the Create feeds function.
  • 1.
    Crnkovic, Ivica
    et al.
    Mälardalen University, School of Innovation, Design and Engineering.
    Stafford, Judith
    Tufts Univ, USA.
    Szyperski, Clemens
    Microsoft Corp.
    Software Components beyond Programming: From Routines to Services2011In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 28, no 3, p. 22-26Article in journal (Refereed)
    Abstract [en]

    Software engineering (SE) conference in 1968, Doug Mc Ilroy introduced the concept of software components during his keynote speech, "Mass-Produced Software Components." That components hold such an esteemed place in SE history should come as no surprise: componentization is a fundamental engineering principle. Top-down approaches decompose large systems into smaller parts-components and bottom-up approaches compose smaller parts components into larger systems. Since 1968, components have played a role in both SE research and practice. For example, components have been an immanent part of software architecture from its early days.2 In 1998, the In ternational Conference on Software Engineering introduced component based software engineering (CBSE) as a specific area within SE at the first workshop on CBSE.

  • 2.
    Gorschek, Tony
    et al.
    Blekinge Institute of Technology.
    Garre, Per
    Sony Ericcson Mobile Communications.
    Larsson, Stig
    ABB Corporate Research.
    Wohlin, Claes
    Blekinge Institute of Technology.
    A Model for Technology Transfer in Practice2006In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 23, no 6, p. 88-95Article in journal (Refereed)
    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.

  • 3.
    Graydon, Patrick
    et al.
    University of York, United Kingdom.
    Habli, Ibrahim
    University of York, United Kingdom.
    Hawkins, Richard
    University of York, United Kingdom.
    Kelly, Tim
    University of York, United Kingdom.
    Knight, John
    University of Virginia, United States .
    Arguing Conformance2012In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 29, no 3, p. 50-57Article in journal (Refereed)
    Abstract [en]

    Conformance to software standards plays an essential role in establishing confidence in high-integrity software systems. However, standards conformance suffers from uncertainty about its meaning for three reasons: because requirements of the standard must be interpreted to fit the specifics of the application; because standards can deliberately leave options for developers; and because goal-based software standards exist that simply specify the high-level principles of software assurance without prescribing a specific means of compliance. The overall effect of these issues is that when conformance to a software assurance standard is claimed, there can be a lack of clarity as to exactly what the claim entails. This article draws on principles and practice from the domain of safety argument construction to describe the use of explicit and structured conformance arguments to help address this problem.

  • 4.
    Kienle, Holger
    Mälardalen University, School of Innovation, Design and Engineering.
    Tools of the Trade It's About Time to Take Java Script (More) Seriously2010In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 27, no 3, p. 60-62Article in journal (Refereed)
    Abstract [en]

    JavaScript is a scripting language, of course. The drawbacks and benefits of scripting languages compared to full-fledged programming languages have been explored before. In a previous installment of this column, Diomidis Spinellis points out that with scripting languages, users can benefit from flexible syntax, loose type systems, powerful reflection mechanisms, and shorter build cycles. Scripting languages have proven their usefulness in various application areas. Unix relies heavily on shell scripting to accomplish many complex tasks. Visual Basic, in combination with ActiveX, provides a low-entry barrier into the world of component-based programming. Tcl/Tk is still popular to rapidly develop GUI-based applications. And then there's JavaScript, which has gained considerable importance in realizing clientside functionality on Web apps. In a survey on the most popular programming languages, JavaScript made it to the Top 10.

  • 5.
    Land, Rikard
    et al.
    Mälardalen University, School of Innovation, Design and Engineering.
    Crnkovic, Ivica
    Mälardalen University, School of Innovation, Design and Engineering.
    Oh Dear, We Bought Our Competitor: Integrating Similar Software Systems2011In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 28, no 2, p. 75-82Article in journal (Refereed)
    Abstract [en]

    How do you transition from several functionally overlapping systems to just one? A look at 10 case studies addresses the technological, personnel, and organizational challenges.

  • 6.
    Strandberg, Per
    et al.
    Westermo Research and Development, Sweden.
    Afzal, Wasif
    Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems.
    Ostrand, Thomas
    Weyuker, Elaine
    Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems.
    Daniel, Sundmark
    Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems.
    Automated System Level Regression Test Prioritization in a Nutshell2017In: IEEE Software, ISSN 0740-7459, E-ISSN 1937-4194, Vol. 34, no 4, p. 30-37, article id 7974685Article in journal (Refereed)
    Abstract [en]

    Westermo Research and Development has developed SuiteBuilder, an automated tool to determine an effective ordering of regression test cases. The ordering is based on factors such as fault detection success, the interval since the last execution, and code modifications. SuiteBuilder has enabled Westermo to overcome numerous regression-testing problems, including lack of time to run a complete regression suite, failure to detect bugs in a timely manner, and repeatedly omitted tests. In the tool's first two years of use, reordered test suites finished in the available time, most fault-detecting test cases were located in the first third of suites, no important test case was omitted, and the necessity for manual work on the suites decreased greatly. 

1 - 6 of 6
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf