Will Johnny/Joanie make a good software engineer? Are course grades showing the whole picture?

Software Engineering Education Conference, Proceedings

Volumn 2006, Issue , 2006, Pages 175-182

  Hayes, Jane Huffman ^a   Dekhtyar, Alex ^a   Holbrook, Ashlee ^a   Dekhtyar, Olga ^b   Sundaram, Senthil ^a  

^a UNIVERSITY OF KENTUCKY   (United States)

^b UNIVERSITY OF KENTUCKY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COURSE GRADES; PROJECT ARTIFACTS; SOFTWARE ENGINEERING COURSE; TRACEABILITY;

CURRICULA; PROJECT MANAGEMENT; SOFTWARE ENGINEERING; STUDENTS; TEACHING;

ENGINEERING EDUCATION;

EID: 33750121809     PISSN: 10930175     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/CSEET.2006.42     Document Type: Conference Paper

References (23)

1. Alexander, S., Clark, M., Loose, et.al. 2003. Case studies in admissions to and early performance in computer science degrees. In Working Group Reports From ITiCSE on innovation and Technology in Computer Science D. Finkel, Ed. ITiCSE-WGR '03. ACM Press, New York, NY, 137-147.
2. Baeza-Yates, R., B. Ribeiro-Neto. Modern Information Retrieval, Addison-Wesley, 1999.
3. Brown, T., Reeves, T., and Scott, T. 2003. Assigning and grading computer programs. J. Comput. Small Coll. 19, 1 (Oct. 2003), 167-168.
4. Chmura, G. A. 1998. What abilities are necessary for success in computer science. SIGCSE Bull. 30, 4 (Dec. 1998), 55-58.
5. Clive C.H. Rosen. "Individual Assessment of Group Projects in Software Engineering: A Facilitated Peer Assessment Approach," Proc. 9th Conference on Software Engineering Education (CSEE), p.68 1996.
6. Conklin, J.: "Design Rationale and Maintainability"; Proc. 22nd Hawaii International Conference on System Science, Los Alamitos: IEEE Computer Society Press, Vol. 2 1989), pp. 533-539.
7. Klappholz, D. Bernstein, L. Port, D. "Assessing Attitude Towards, Knowledge of, and Ability to Apply, Software Development Process," Proc. 16th Conference on Software Engineering Education and Training (CSEE&T 2003), p. 268 2003.
8. "Do grades make the grade for program assessment?" ABET Quarterly News Source, (Fall/Winter):8-9, 2003.
9. Dömges, R. and Pohl, K.. "Adapting Traceability to Project-SP." Comm. of the ACM, 41(12):54-62, Dec. 1998.
10. Egyed, A. "A Scenario-Driven Approach to Traceability." Proc. of the 23rd international Conference on Software Engineering, 123-132, 2001.
11. Hayes, J.H., Dekhtyar, A., and Osborne, J. Improving Requirements Tracing via Information Retrieval, in Proceedings, 11th International Requirements Engineering Conference (RE 2003), September 2003, Monterey Bay, CA.
12. Hayes, J.H., Dekhtyar, A., Sundaram, S.K, and Howard, S. Helping Analysts Trace Requirements: An Objective Look (2004), in Proceedings, 12th International Requirements Engineering Conference (RE 2004), pp. 249-261, September 2004, Kyoto, Japan.
13. Hayes, J.H., Lethbridge, T and Port, D. "Evaluating Individual Contribution Toward Group Software Engineering Projects," in Proc. of the International Conference on Software Engineering (ICSE), Portland, Oregon, May 2003, pp. 622-627.
14. Hazzan, O. 2003. Computer science students' conception of the relationship between reward (grade) and cooperation. In Proc.of the 8th Annual Conference on innovation and Technology in Computer Science Education (Thessaloniki, Greece, June 30 - July 02, 2003). D. Finkel, Ed. ITiCSE '03. ACM Press, New York, NY, 178-182.
15. Howatt, J. W. 1994. On criteria for grading student programs. SIGCSE Bull. 26, 3 (Sep. 1994), 3-7.
16. Hostetler, T. R. 1983. Predicting student success in an introductory programming course. SIGCSE Bull. 15, 3 (Sep. 1983), 40-43.
17. Miller, N. E. and Peterson, C. G. 1980. A method for evaluating student written computer programs in an undergraduate computer science programming language course. SIGCSE Bull. 12, 4 (Dec. 1980), 9-17.
18. Newsted, P. R. 1975. Grade and ability predictions in an introductory programming course. SIGCSE Bull. 7, 2 (Jun. 1975), 87-91. DOI= http://doi.acm.org/10.1145/382205.382897
19. Ramesh, B T. Powers, C. Stubbs, M. Edwards. "Implementing requirements traceability: a case study," re, p. 89, 2nd IEEE International Symposium on Requirements Engineering, 1995.
20. Rountree, N., Rountree, J., and Robins, A. 2002. Predictors of success and failure in a CS1 course. SIGCSE Bull. 34, 4 (Dec. 2002), 121-124.
21. U.S. Department of Defense, "Military Standard: Defense Systems Software Development, DOD-DTD-2167A," February 1988.
22. Walker, H. M. 2000. Notes on grading. SIGCSE Bull. 32, 2 (Jun. 2000), 18-19.
23. Wilson, B. C. and Shrock, S. 2001. Contributing to success in an introductory computer science course: a study of twelve factors. In Proceedings of the Thirty-Second SIGCSE Technical Symposium on Computer Science Education (Charlotte, North Carolina, United States). SIGCSE '01. ACM Press, New York, NY, 184-188.