Changing the paradigm of software engineering

Communications of the ACM

Volumn 49, Issue 8, 2006, Pages 67-70

  Rajlich, Václav ^a  

^a Wayne State University   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

DYNAMIC CATEGORIES; INCREMENTAL CHANGE (IC); RESEARCH ISSUES; SOFTWARE SOURCE CODES;

CODES (SYMBOLS); COGNITIVE SYSTEMS; ENGINEERING RESEARCH; ITERATIVE METHODS;

SOFTWARE ENGINEERING;

EID: 33747156640     PISSN: 00010782     EISSN: 00010782     Source Type: Journal    
DOI: 10.1145/1145287.1145289     Document Type: Review

References (12)

1. Beck, K. Extreme Programming Explained. Addison Wesley, Reading, MA, 2000.
2. Brooks, F.P. The Mythical Man-Month. Addison-Wesley, Reading, MA, 1982.
3. Cusurnano, A.M. and Selby, R.W. How Microsoft builds software. Commun ACM 40, 6 (June 1997), 53-61.
4. Eick, S.G., Graves, T.L., Karr, A., Marron, J.S., and Mockus, A. Does code decay? Assessing the evidence from change management data. IEEE Trans. Software Engineering 27, 1 (2001), 1-12.
5. Fowler, M. Refactoring: Improving the Design of Existing Code, Addison Wesley, Reading, MA, 1999.
6. Jacobson, I., Booch, G. and Rumbaugh, J. The Unified Software Development Process, Addison Wesley, Reading, MA, 1999.
7. Johnson, J.H. The CHAOS Report, The Standish Group International, Inc., (1994); www.standishgroup.com/sample_research/index.php.
8. Kuhn, T.S. The Structure of Scientific Revolutions. The University of Chicago Press, Chicago, 1996.
9. Rajlich, V. and Bennett, K. A staged model for the software lifecycle. Computer 33, 7 (July 2000) 66-71.
10. Rajlich, V. and Gosavi, P. Incremental change in object-oriented programming. IEEE Software 21 (July/Aug. 2004), 62-69.
11. Xu, S., Rajlich, V., and Marcus, A. An empirical study of programmer learning during incremental software development. In Proceedings of the IEEE International Conference on Cognitive Informatics (2005), 340-349
12. Wilde, N., Buckellew, M., Page, H., Rajlich, V. and Pounds, L. A comparison of methods for locating features in legacy software. J. Systems and Software 65, 2 (Feb. 2003), 105-114.