https://istlab.dmst.aueb.gr/wiki/api.php?action=feedcontributions&feedformat=atom&user=195.251.255.78 2026-11-15T06:54:42Z User contributions MediaWiki 1.43.9 https://istlab.dmst.aueb.gr/wiki/index.php?title=Tushar_Sharma_publication_plan&diff=4630 2016-02-24T10:48:32Z

<p>195.251.255.78: </p> <hr /> <div>== Under development ==<br /> * [https://github.com/tushartushar/smellsEmpiricalStudy Empirical study on smell in C# repositories] (with Marios and Prof. Spinellis; ICSE?)<br /> <br /> == Pending ==<br /> * Does your configuration code smell? (with Prof. Spinellis and Marios; MSR)<br /> <br /> == Resubmit ==<br /> * Augur: Incorporating Hidden Dependencies and Variable Granularity in Change Impact Analysis (with Girish Suryanarayana, ICSME)<br /> <br /> == To appear ==<br /> * Tushar Sharma, Pratibha Mishra, Rohit Tiwari. Designite - A Software Design Quality Assessment Tool. In BRIDGE workshop ICSE '16: Proceedings of the 38th International Conference on Software Engineering, New York, May 2016. Association for Computing Machinery. To appear. <br /> <br /> == Recently published ==<br /> * Tushar Sharma, Girish Suryanarayana, Ganesh Samarthyam. Challenges to and Solutions for Refactoring Adoption: An Industrial Perspective. IEEE Software, 32(6):44-51, Nov-Dec. 2015. (doi: 10.1109/MS.2015.105)<br /> <br /> == Dropped ==</div>

195.251.255.78 https://istlab.dmst.aueb.gr/wiki/index.php?title=Tushar_Sharma_publication_plan&diff=4629 2016-02-24T10:47:50Z

<p>195.251.255.78: Initial fill</p> <hr /> <div>== Under development ==<br /> * [https://github.com/tushartushar/smellsEmpiricalStudy Empirical study on smell in C# repositories] (with Marios and Prof. Spinellis; ICSE?)<br /> <br /> == Pending ==<br /> * Does your configuration code smell? (with Prof. Spinellis and Marios; MSR)<br /> <br /> == Resubmit ==<br /> * Augur: Incorporating Hidden Dependencies and Variable Granularity in Change Impact Analysis (with Girish Suryanarayana, ICSME)<br /> <br /> == To appear ==<br /> * Tushar Sharma, Pratibha Mishra, Rohit Tiwari. Designite - A Software Design Quality Assessment Tool. In BRIDGE workshop ICSE '16: Proceedings of the 38th International Conference on Software Engineering, New York, May 2016. Association for Computing Machinery. To appear. <br /> <br /> <br /> == Recently published ==<br /> * Tushar Sharma, Girish Suryanarayana, Ganesh Samarthyam. Challenges to and Solutions for Refactoring Adoption: An Industrial Perspective. IEEE Software, 32(6):44-51, Nov-Dec. 2015. (doi: 10.1109/MS.2015.105)<br /> <br /> <br /> == Dropped ==</div>

195.251.255.78 https://istlab.dmst.aueb.gr/wiki/index.php?title=SENSE_publication_plans&diff=4628 2016-02-24T10:23:14Z

<p>195.251.255.78: /* Plans of individual members */</p> <hr /> <div>A good publication record doesn't happen by chance. It requires careful planning and execution. Given the fact that publishing to a top journal can take as much as three years, you can't afford to send a publication off, and then wait for a reply. At any time you should have a pipeline filled with publications in three stages of progress.<br /> <br /> * Publications under development. These may be new contributions or papers that you improve following review comments.<br /> * Publications under review.<br /> * Publications that have been accepted and are (often slowly) moving toward publication.<br /> <br /> Keeping all stages of the pipeline full ensures that publishers, reviewers, and yourself are always busy, with no time being lost in idle waiting. Also, try to have in your pipeline a mix of different paper types: conference papers for rapid dissemination of results; journal articles for advancing your academic career. Publication delays being what they are, your first aim in your plan is to keep reviewers and publishers busy. Don't sit on papers that have been accepted with revisions: revise them as soon as possible. If you ever notice that a stage of your pipeline is empty, you're in trouble. Make it your priority to fill it up, or prepare to cry over an empty hole in your CV's publication record.<br /> <br /> == Plans of individual members ==<br /> * [[Publication plan template]]<br /> * [[Diomidis Spinellis publication plan|Diomidis Spinellis]]<br /> * [[Giorgos Gousios publication plan|Giorgos Gousios]]<br /> * [[Vassilios Karakoidas publication plan|Vassilios Karakoidas]]<br /> * [[Panos Louridas publication plan|Panos Louridas]]<br /> * [[Stephanos Androutsellis publication plan|Stephanos Androutsellis]]<br /> * [[Kostas Stroggylos publication plan|Kostas Stroggylos]]<br /> * [[Dimitris Mitropoulos publication plan|Dimitris Mitropoulos]]<br /> * [[Tushar Sharma publication plan|Tushar Sharma]]<br /> <br /> == Discussion ==<br /> ===Isn't it risky to open-up my publication plan? Somebody might steal my idea.===<br /> We are researchers, not the CIA. The risk isn't our ideas leaking into the open, but our ideas not getting disseminated. Also, ideas are cheap, execution is difficult. So publish your plan, and concentrate on getting your results quickly published.<br /> <br /> [[Category:SENSE]]</div>

195.251.255.78