EDBT 2026 Demo / reviewers in the wild / expert
Mark J. Christensen
dblp:96/6025
· DBLP profile ↗
3ranked-venue papers
1as first author
0since 2021 · last 2003
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 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 |
Requirements engineering and software design · 50% Software maintenance and evolution · 50% | |
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution
change management |
0.0 | 1 | 2003 | Event-Based Traceability for Managing Evolutionary Change · IEEE Trans. Software Eng. 2003 |
Requirements engineering and software design
requirements traceability |
0.0 | 1 | 2003 | Event-Based Traceability for Managing Evolutionary Change · IEEE Trans. Software Eng. 2003 |
Distributed systems
distributed software development |
0.0 | 1 | 2003 | Event-Based Traceability for Managing Evolutionary Change · IEEE Trans. Software Eng. 2003 |
Methods — techniques the papers use, named apart from their topics
event-based traceability · 0.1event notification · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2003 | Event-Based Traceability for Managing Evolutionary ChangeabstractAlthough the benefits of requirements traceability are widely recognized, the actual practice of maintaining a traceability scheme is not always entirely successful. The traceability infrastructure underlying a software system tends to erode over its lifetime, as time-pressured practitioners fail to consistently maintain links and update impacted artifacts each time a change occurs, even with the support of automated systems. This paper proposes a new method of traceability based upon event-notification and is applicable even in a heterogeneous and globally distributed development environment. Traceable artifacts are no longer tightly coupled but are linked through an event service, which creates an environment in which change is handled more efficiently, and artifacts and their related links are maintained in a restorable state. The method also supports enhanced project management for the process of updating and maintaining the system artifacts. Jane Cleland-Huang, Carl K. Chang, Mark J. Christensen |
IEEE Trans. Software Eng. | 3 |
| 1998 | Software Project Management Net: A New Methodology on Software ManagementabstractManaging the development of large-scale software systems is a challenge to all software project managers due to the ever-increasing complexity inherent in the software development life-cycle. In this paper, a formalism intended to capture the concurrent and iterative nature of software development, called Software Project Management Net (SPMNet), is proposed in order to model software development projects. By augmenting and applying genetic algorithms in an innovative manner by sharply reducing the solution search-space complexity, SPMNet provides optimal or near-optimal solutions to the resource allocation and project scheduling problems. Results collected from simulation runs clearly support our approach for practical applications. Carl K. Chang, Chikuang Chao, Thinh T. Nguyen, Mark J. Christensen |
COMPSAC | 4 |
| 1998 | Panel on software component architectures
Mark J. Christensen |
COMPSAC | 1 |