Advances in software inspections
IEEE Transactions on Software Engineering
Precise Documentation of Well-Structured Programs
IEEE Transactions on Software Engineering
Functional documents for computer systems
Science of Computer Programming
Active design reviews: principles and practices
ICSE '85 Proceedings of the 8th international conference on Software engineering
A technique for software module specification with examples
Communications of the ACM
On the criteria to be used in decomposing systems into modules
Communications of the ACM
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
Software Inspection
Supporting industrial hyperwebs: lessons in scalability
Proceedings of the 21st international conference on Software engineering
Commentary on James E. Tomayko, "software as engineering"
ICHC Proceedings of the international conference on History of computing: software issues
Software modernization and replacement decision making in industry: a qualitative study
EASE'06 Proceedings of the 10th international conference on Evaluation and Assessment in Software Engineering
| Hi-index | 0.00 |
Rumination about what makes research successful is a strong indication that a researcher will not continue to do successful research. Nonetheless, the invitation to publish a short article in SEN on the occasion of being honoured by receiving SIGSOFT's "Outstanding Research Award" has led me to reflect on what I have done. I have been active in research on software design for more than 35 years; perhaps this is the time to pause and look back. I also want to look forward; I have some concerns about the direction being taken by many researchers in the software community and would like to offer them my (possibly unwelcome) advice.