메뉴 건너뛰기




Volumn , Issue , 2003, Pages 726-736

Writing good software engineering research papers

Author keywords

Research design; Research paradigms; Software profession; Technical writing; Validation

Indexed keywords

ENGINEERING RESEARCH; PROFESSIONAL ASPECTS; SOCIETIES AND INSTITUTIONS; TECHNICAL WRITING;

EID: 0037587229     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/icse.2003.1201262     Document Type: Conference Paper
Times cited : (223)

References (26)
  • 1
    • 85043264571 scopus 로고    scopus 로고
    • The experimental paradigm in software engineering
    • H. Dieter Rombach, Victor R. Basili, and Richard Selby (eds), published as Lecture Notes in Computer Science #706, Springer-Verlag 1993
    • Victor R. Basili. The experimental paradigm in software engineering. In Experimental Software Engineering Issues: Critical Assessment and Future Directives. Proc of Dagstuhl-Workshop, H. Dieter Rombach, Victor R. Basili, and Richard Selby (eds), published as Lecture Notes in Computer Science #706, Springer-Verlag 1993.
    • Experimental Software Engineering Issues: Critical Assessment and Future Directives. Proc of Dagstuhl-Workshop
    • Basili, V.R.1
  • 6
    • 0038620219 scopus 로고    scopus 로고
    • ICSE 2002 Program Committee
    • ICSE 2002 Program Committee. Types of ICSE papers. http://icse-conferences.org/2002/info/paperTypes.html
    • Types of ICSE Papers
  • 9
    • 84988257497 scopus 로고    scopus 로고
    • How to get a paper accepted at OOPSLA
    • Ralph E. Johnson & panel. How to Get a Paper Accepted at OOPSLA. Proc OOPSLA'93, pp. 429-436, http://acm.org/sigplan/oopsla/oopsla96/how93.html
    • Proc OOPSLA'93 , pp. 429-436
    • Johnson, R.E.1
  • 10
    • 0037943968 scopus 로고    scopus 로고
    • How to get your SIGGRAPH paper rejected
    • Jim Kajiya. How to Get Your SIGGRAPH Paper Rejected. Mirrored at http://www.cc.gatech.edu/student.services/phd/phd-advice/kajiya
    • Kajiya, J.1
  • 11
    • 0038281219 scopus 로고
    • How (and how not) to write a good systems paper
    • (July)
    • Roy Levin and David D. Redell. How (and How Not) to Write a Good Systems Paper. ACM SIGOPS Operating Systems Review, Vol. 17, No. 3 (July, 1983), pages 35-40. http://ftp.digital.com/pub/DEC/SRC/other/SOSPadvice.txt
    • (1983) ACM SIGOPS Operating Systems Review , vol.17 , Issue.3 , pp. 35-40
    • Levin, R.1    Redell, D.D.2
  • 14
    • 0038620217 scopus 로고    scopus 로고
    • How to get your paper accepted at OOPSLA
    • OOPSLA '91 Program Committee
    • OOPSLA '91 Program Committee. How to get your paper accepted at OOPSLA. Proc OOPSLA '91, pp. 359-363. http://acm.org/sigplan/oopsla/oopsla96/how91.html
    • Proc OOPSLA '91 , pp. 359-363
  • 15
    • 0038281226 scopus 로고    scopus 로고
    • How to increase the chances your paper is accepted at ACM SIGCOMM
    • Craig Partridge. How to Increase the Chances your Paper is Accepted at ACM SIGCOMM. http://www.acm.org/sigcomm/conference-misc/author-guide.html
    • Partridge, C.1
  • 16
    • 0037943963 scopus 로고
    • William Pugh and PDLI; Program Committee
    • William Pugh and PDLI 1991 Program Committee. Advice to Authors of Extended Abstracts. http://acm.org/sigsoft/conferences/pughadvice.html
    • (1991) Advice to Authors of Extended Abstracts
  • 20
    • 84896693849 scopus 로고    scopus 로고
    • What makes good research in software engineering? Presented at ETAPS 02, appeared in opinion corner department
    • DOI 10.1007/s10009-002-0083-4, June
    • Mary Shaw. What makes good research in software engineering? Presented at ETAPS 02, appeared in Opinion Corner department, Intl'l Jour on Software Tools for Tech Transfer, vol 4, DOI 10.1007/s10009-002-0083-4, June 2002.
    • (2002) Intl'l Jour on Software Tools for Tech Transfer , vol.4
    • Shaw, M.1
  • 21
    • 0038281233 scopus 로고    scopus 로고
    • SigGraph 2003 Call for Papers
    • SigGraph 2003 Call for Papers. http://www.siggraph.org/s2003/cfp/papers/index.html
  • 22
    • 0029230328 scopus 로고
    • Experimental evaluation in computer science: A quantitative study
    • W. F. Tichy, P. Lukowicz, L. Prechelt, & E. A. Heinz. "Experimental evaluation in computer science: A quantitative study." Journal of Systems Software, Vol. 28, No. 1, 1995, pp. 9-18.
    • (1995) Journal of Systems Software , vol.28 , Issue.1 , pp. 9-18
    • Tichy, W.F.1    Lukowicz, P.2    Prechelt, L.3    Heinz, E.A.4
  • 23
    • 0038281221 scopus 로고    scopus 로고
    • Should computer scientists experiment more? 16 reasons to avoid experimentation
    • May
    • Walter F. Tichy. "Should computer scientists experiment more? 16 reasons to avoid experimentation." IEEE Computer, Vol. 31, No. 5, May 1998
    • (1998) IEEE Computer , vol.31 , Issue.5
    • Tichy, W.F.1
  • 24
    • 0031337731 scopus 로고    scopus 로고
    • Experimental validation in software engineering
    • Marvin V. Zelkowitz and Delores Wallace. Experimental validation in software engineering. Information and Software Technology, Vol. 39, no 11, 1997, pp. 735-744.
    • (1997) Information and Software Technology , vol.39 , Issue.11 , pp. 735-744
    • Zelkowitz, M.V.1    Wallace, D.2
  • 25
    • 0032074438 scopus 로고    scopus 로고
    • Experimental models for validating technology
    • Marvin V. Zelkowitz and Delores Wallace. Experimental models for validating technology. IEEE Computer, Vol. 31, No. 5, 1998, pp. 23-31.
    • (1998) IEEE Computer , vol.31 , Issue.5 , pp. 23-31
    • Zelkowitz, M.V.1    Wallace, D.2
  • 26
    • 25344467077 scopus 로고    scopus 로고
    • How to have your abstract rejected
    • Mary-Claire van Leunen and Richard Lipton. How to have your abstract rejected. http://acm.org/sigsoft/conferences/vanLeunenLipton.html
    • Van Leunen, M.-C.1    Lipton, R.2


* 이 정보는 Elsevier사의 SCOPUS DB에서 KISTI가 분석하여 추출한 것입니다.