A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Recommendations for software engineering education
SIGCSE '87 Proceedings of the eighteenth SIGCSE technical symposium on Computer science education
Software engineering concepts
Teaching documentation and style in Pascal
ACM SIGCSE Bulletin
Software engineering standards
Software engineering standards
Anatomy of a software engineering project
SIGCSE '88 Proceedings of the nineteenth SIGCSE technical symposium on Computer science education
A controlled experiment in program testing and code walkthroughs/inspections
Communications of the ACM
Exploratory experimental studies comparing online and offline programming performance
Communications of the ACM
Software aspects of strategic defense systems
ACM SIGSOFT Software Engineering Notes
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
An evaluation of a CASE-based approach to teaching undergraduate software engineering
SIGCSE '90 Proceedings of the twenty-first SIGCSE technical symposium on Computer science education
| Hi-index | 0.00 |
There has been considerable interest in a one-semester course in software engineering [Bullard88, Carver87, Gibbs87]. Faculty members of departments of computer science are introducing courses that involve team projects, in an effort to provide students some experience with large programs. However, software professionals are still concerned that most computer science graduates have little understanding of what is involved in the development of large, complex systems. Too often, code alone is regarded as the primary product without proper consideration of the necessary standards and procedures of the controlling disciplines. This paper describes a course that shifted the emphasis from coding by having students perform supporting activities and maintenance on a large Ada project.