COSC345
Software Engineering
COSC345 - Software Engineering
Full year, 2011
Instructors
Richard O'Keefe and Andrew Trotman.
Description
This paper covers the development of large-scale, reliable, and maintainable software systems. Topics include software specification; software design; system design; formal specification; prototypes; system maintenance; code reading and browsing; software reuse; project management; human factors; documentation; standards for software and documentation; verification and validation; configuration management; and software evolution.
Assignment work conists of a major project completed in teams of three or four people, to build, maintain, extend, (and document) a substantial piece of code.
Textbook
S. McConnell, Code Complete 2nd edition, Microsoft Press, 2004.
E-mail concerning the course is frequently sent to the cosc345 mailing list. You should be checking your e-mail regularly so that you see any such messages.
Details
For lecture plan and resources, see the old but updated page.
Plagiarism
Student Administration have asked us to add this note on Plagiarism:
"Students should make sure that all submitted work is their own.
Plagiarism is a form of dishonest practice. Plagiarism is defined as
copying or paraphrasing another's work, whether intentionally or
otherwise, and presenting it as one's own (approved University Council,
December 2004). In practice this means plagiarism includes any attempt
in any piece of submitted work (such as an assignment or test) to present
as one's own work the work of another (whether of another student or a
published authority). Any student found responsible for plagiarism in
any piece of work submitted for assessment shall be subject to the
University's dishonest practice regulations which may result in various
penalties, including forfeiture of marks for the piece of work
submitted, a zero grade for the paper, or in extreme cases exclusion
from the University."
