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

Juri Urbainczyk

dblp:35/3860 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1998
—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
Requirements engineering and software design · 56% Software maintenance and evolution · 44%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software process
software process modeling
0.011998
Software Process Modeling and Enactment: An Experience Report Related to Problem Tracking in an Industrial Project · ICSE 1998
Requirements engineering and software design › software process
process model enactment
0.011998
Software Process Modeling and Enactment: An Experience Report Related to Problem Tracking in an Industrial Project · ICSE 1998

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

state transition diagram · 0.0FUNSOFT nets · 0.0
YearPublicationVenuePosition
1998 Software Process Modeling and Enactment: An Experience Report Related to Problem Tracking in an Industrial Project
abstract
The paper provides an overview of process research and the application of research results to practice and then describes process models using FUNSOFT nets and a workflow management system LEU. The example from which the experience is drawn is that of a problem tracking system and the components of the model are described and illustrated. The experience reported comes in three flavors: the appropriateness of FUNSOFT nets as a modeling mechanisms and the alternative use of state transition diagrams; the benefits of the model and its support of the business process; and finally some implications for process research.
Volker Gruhn, Juri Urbainczyk
ICSE2