ACM Home Page
Please provide us with feedback. Feedback
Distribution of software engineering concepts beyond the software engineering course
Full text PdfPdf (353 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: 233 - 237  
Year of Publication: 1987
ISBN:0-89791-217-9
Also published in ...
Author
James Calhoun  Department of Computer Science, Western Illinois University, Mecomb, Illinois
Sponsor
SIGCSE: ACM Special Interest Group on Computer Science Education
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 14,   Citation Count: 1
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.31764
What is a DOI?

ABSTRACT

The importance of the role of documentation in the development and maintenance of software is not in dispute among computer professionals. Within the profession, software has come to mean more than just the source or object code which is produced. A modern definition of software includes documents as a vital component. The largest part of such documentation is external to the program and records the history of the project. Included could be project plans, requirements specification, preliminary detailed code design, user-directed manuals and maintenance journals.All too often the computer science curriculum, whether by design or default, limits student experience with external documentation to specialized courses such as software engineering. While the documentation experience provided by these courses may prove valuable, its quality may be limited by the student's attitude. If the student's previous experience has been limited to internal documentation, there is a good chance that he has come to view documentation as an add-on, something to be completed after the project is really finished. It is difficult to alter this mind-set.Identification of a solution to this problem may require not only a reevaluation of the documentation requirements for student software projects but an examination of the availability of programming languages and design tools which support the documentation effort. This paper reports the development of several design tools which are intended for student use in the preparation of preliminary project documentation. Special among these is an interactive graphics editor to be used to assist in the design, documentation and implementation of programs.


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
King, David, C~Tr~_nt. Pra_cti~s In Softwaci l)=velc~nent: A ~_,i~ to successful sustems. Ymlrdoh Press, 1984.
 
2
Ilo~-Romli, Mohd Rals, "IGED-MODULA2o An interactive 8raphtcs Editor', 8roduate Project Report, Western illinois University, 1986.
 
3
 
4
Pressnmn, Roger S., Softw__sre E~lneerlno: A Pre_ctltl~s AD~. Mc6raw Hill, 1982.
 
5
Sonmmrvllleo Ion, Software Eno_lneerll~_ Addison_Wesley, Second Edition, 1905.