Per Leion

dblp:29/927 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2000
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 62% Requirements engineering and software design · 38%

Topics — the 4 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software product lines
feature-oriented software development
0.012000
Daily build and feature development in large distributed projects · ICSE 2000
Empirical software engineering
software engineering practice
0.012000
Daily build and feature development in large distributed projects · ICSE 2000
Empirical software engineering
agile software development
0.012000
Daily build and feature development in large distributed projects · ICSE 2000
Empirical software engineering › agile software development
extreme programming
0.012000
Daily build and feature development in large distributed projects · ICSE 2000
YearPublicationVenuePosition
2000 Daily build and feature development in large distributed projects
abstract
Daily build is a software development paradigm that originated in the PC industry to get control of the development process, while still allowing the focus on end user requirements and code. The PC industry used daily build to avoid chaos in increasingly larger applications in an environment without a strong development process. Ericsson Radio Systems has chosen to implement daily build to increase the focus on end user requirements and code, but from a different starting point with a traditionally strong development process. In this article we discuss our experiences with daily build and feature oriented development in this context. We also relate our experience to the concept of extreme programming, arguing that our ideas can help extend the applicability of extreme programming beyond small co-located projects.
Even-André Karlsson, Lars-Göran Andersson, Per Leion
ICSE3