Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Marek Leszak

dblp:04/3840 · DBLP profile ↗
← Back
4ranked-venue papers
4as first author
0since 2021 · last 2007
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 4 first-author

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
Software maintenance and evolution · 100%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › software quality assurance
defect analysis
0.012000
A case study in root cause defect analysis · ICSE 2000
Software maintenance and evolution › software quality assurance
defect prevention
0.012000
A case study in root cause defect analysis · ICSE 2000

Methods — techniques the papers use, named apart from their topics

case study · 0.0
YearPublicationVenuePosition
2007 Successful Global Development of a Large-scale Embedded Telecommunications Product
abstract
This paper describes a success story in large-scale global systems & software development. Carried out at several company locations and associated supplier sites, we describe how we manage and develop a complex embedded product in a global dynamic environment. Main acting locations are at Germany and China. Organizational key success factors include very experienced project management team, partnership-based collaboration in cross-functional teams across locations, and well-defined roles & responsibilities on all project levels. Sociological key factors include frequent cross-site visits on engineering and management level, cross-cultural trainings, and high process and quality focus of the whole project team. Technical key factors include feature-driven and timeboxing based iterative process, effective multi-site tools for configuration control, for change management, for joint asynchronous reviews, for software integration and release, and full traceability of all product changes. Evidence by some process measurements is provided supporting our view that our project is very successful.
Marek Leszak, Manfred Meier
ICGSE1
2005 Software Defect Analysis of a Multi-release Telecommunications System
Marek Leszak
PROFES1
2002 Classification and evaluation of defects in a project retrospective
Marek Leszak, Dewayne E. Perry, Dieter Stoll
J. Syst. Softw.1
2000 A case study in root cause defect analysis
abstract
There are three interdependent factors that drive our software development processes: interval, quality and cost. As market pressures continue to demand new features ever more rapidly, the challenge is to meet those demands while increasing, or at least not sacrificing, quality. One advantage of defect prevention as an upstream quality improvement practice is the beneficial effect it can have on interval: higher quality early in the process results in fewer defects to be found and repaired in the later parts of the process, thus causing an indirect interval reduction.
Marek Leszak, Dewayne E. Perry, Dieter Stoll
ICSE1