I am sorry to inform you that your submission (paper 174, Bridging Javadoc and design documentation via UML diagram image maps) has not been chosen as a short paper for the ACM Hypertext 2003 conference. The quality has remained high with 25% of submissions being accepted, and despite the short timescale, most submissions were reviewed by four referees. Thank you for your interest in HT03. We are anticipating a lively conference and would value your participation. --- Les Carr & Lynda Hardman HT03 PC CoChairs ===================== REVIEWS ==================== Score: 4 Whilst the approach sounds interesting, many of the details that would really be useful have not been included in the paper. For example, the process for indentifying and managing the document links is largely ignored. It is also unclear whether the approach for constructing the diagrams etc. is predominantly manual (in which case it would seem prohibitively expensive except in trivial cass where it is not needed). There is also no information on an evaluation of the usefulness to users etc. Score: 5 Sort of a nifty project in some senses, but on te other hand, hard to see if this is really a research contribution or not... Score: 7 Score: 4 First, let me say that I really enjoyed reading this paper. I liked your style. I found the illustrations refreshing. I found your motivation in the introduction right on the mark --- and: I would love to have this solution for our developments. All said, I had many reasons why I would have liked to accept this paper. The problem is that the entire paper, as written, should serve as the introduction to the real paper that you should have written. The HT paper that I would have accepted would have devoted 1 page describing your approach and one page providing *results* - showing that this approach really improves the development. This is the real contribution of your research. You spend great detail on the tool and its relevance for software development. But your domain is Software Engineering and Hypertext. You describe how to navigate to the relevant UML-designs, but almost nothing addresses its impact on the development. I am pretty sure that the implementation was quite a lot of work, but