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
Demo Data from EDBT 2026 / reviewers in the wild / expert

Michal Iglewski

dblp:54/4302 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 1997
0000-0002-0236-660XORCID · corroborated

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

Software engineering, systems software and programming languages · 2 · 1 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 · 56% Requirements engineering and software design · 44%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › specification
functional specification		 0.011994
Precise Documentation of Well-Structured Programs · IEEE Trans. Software Eng. 1994
Software maintenance and evolution
software documentation		 0.011994
Precise Documentation of Well-Structured Programs · IEEE Trans. Software Eng. 1994
Software maintenance and evolution
program comprehension		 0.011994
Precise Documentation of Well-Structured Programs · IEEE Trans. Software Eng. 1994

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

tabular documentation · 0.0functional specification · 0.0
YearPublicationVenuePosition
1997 Internal Design of Modules Specified in the Trace Assertion Method
Michal Iglewski, Janina Mincer-Daszkiewicz
 Sci. Comput. Program.1
1994 Precise Documentation of Well-Structured Programs
abstract
Describes a new form of program documentation that is precise, systematic and readable. This documentation comprises a set of displays supplemented by a lexicon and an index. Each display presents a program fragment in such a way that its correctness can be examined without looking at any other display. Each display has three parts: (1) the specification of the program presented in the display, (2) the program itself, and (3) the specifications of programs invoked by this program. The displays are intended to be used by software engineers as a reference document during inspection and maintenance. This paper also introduces a specification technique that is a refinement of H.D. Mills's (1975) functional approach to program documentation and verification; programs are specified and described in tabular form.>
David Lorge Parnas, Jan Madey, Michal Iglewski
 IEEE Trans. Software Eng.3