ACM Home Page
Please provide us with feedback. Feedback
Recommendations for software engineering education
Full text PdfPdf (381 KB)
Source Technical Symposium on Computer Science Education archive
Proceedings of the eighteenth SIGCSE technical symposium on Computer science education table of contents
St. Louis, Missouri, United States
Pages: 228 - 232  
Year of Publication: 1987
ISBN:0-89791-217-9
Also published in ...
Author
Doris L. Carver  Department of Computer Science, Louisiana State University, Baton Rouge, Louisiana
Sponsor
SIGCSE: ACM Special Interest Group on Computer Science Education
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 33,   Citation Count: 4
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/31820.31763
What is a DOI?

ABSTRACT

The increasing emphasis on software engineering in the computer science curricula directly correlates with the expansion of the area of software engineering. The increased occurrence of software engineering courses has produced significant discrepancies in the content of the courses at the undergraduate level. These discrepancies have percipitated the need for recommendations for the inclusion of software engineering in the curriculum. The recommendations presented in this paper include both the integration of software engineering principles throughout the undergraduate curriculum and the content of a separate software engineering course. The recommendations for course content are based on a survey of the contents of recently published software engineering textbooks.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
B.D. Shriver, "Firmware: The lessons of software engineering", Computer, vol. 11, no. 5, pp. 19-20, May 1978.
 
2
B.W. Boehm, "Software engineering", IEEE Trans. Computers, vol. C-25, no. 12, pp. 1226-1241, December 1976.
3
 
4
T.L. Booth, "Taylor L. Booth on computers: software is the limitation," IEEE Spectrum, vol. 21, no. 1, pp. 36-37, January 1984.
5
6
7
8
9
10
 
11
 
12
R.W. Jensen and C. C. "Ionic's, Software Engineerng. Englewood Cliffs, NJ.: Prentice-Hall, Inc., 1979.
 
13
 
14
 
15
 
16
 
17
 
18
 
19
 
20
 
21
 
22
 
23
C. Bentley, Computer Project Management. New York: John Wiley and Sons, 1984.
 
24
W.P. Stevens, Using Structured Design. New York: John Wiley and Sons, 1981.
 
25
B. Dickinson, Developing Structured Systems. New York: Yourdon Press, 1980.
 
26
 
27
 
28
 
29
 
30
31
32
33
 
34
 
35
G. M Weinberg and D. P. Freedman, "Reviews, walkthroughs, and inspections," IEEE Trans. Software Eng., vol. SE-10, pp. 68-72, January 1984.
 
36
 
37
B.W. Boehm, "Verifying and validating software requirements and design specifications," IEEE Software, vol. 1, no. 1, pp. 75-88, January 1984.
 
38
F.W. Beichter, O. Herzog, and H. Petzsch, "SLAN-4--A software specification and design language," IEEE Trans. Software Eng., vol. SE-10, pp. 155-162, March 1984.
 
39
I.J. Hayes, "Applying formal specification to software development in industry," IEEE Trans. Software Eng., vol. SE-11, pp. 169-178, February 1985.
 
40
H.A. Jensen and K. Vairavan, "An experminental study of software metrics for real-time software," IEEE Trans. Software Eng., pp. 231-234, February 1985.
 
41
T. Anderson, P. A. Barrett, D. N. Halliwell, and M. R. Moulding, "Software fault tolerance: An evaluation," IEEE Trans. Software Eng., vol. SE-11, pp. 1502-1510, December 1985.
 
42
 
43