|Professor||Bill Arbaugh (email@example.com)|
|TA||Seong-Wook Joo : Office
|Time||MW: 2:00 - 3:15
|Office hours||MW: 1:00 - 2:00 and by appointment (AVW 4137)|
|Text||Computer Security: Art and Science by Matt Bishop
The text will also be supplemented with additional papers from links on this page.
||It is highly recommended that
you use CVS for version control. Information about CVS can be found here.
We will be using J2ME for ALL programming assignments. J2ME is a restricted version of Java designed to run on PDA's and cell phones. The course project will require you to program using J2ME so the homework assignments will give you experience using this development environment. A good text on J2ME is Java2 Micro Edition by James P. White and David A. Hemphill.
Student accounts are available for the Linux Cluster located in the CSI building. More on the lab can be found here. These machines will have the J2ME development environment loaded. You can, of course, download the development environment to your own machine should you desire to do so.
|A grade of C or better in CMSC 311 and CMSC
NOTE: This course will cover a wide range of topics within computer science. If you are unable to quickly grasp these issues, you will have difficulty in the class. Review the course material here to ensure you're comfortable with the level. Also, all of the homework will include programming projects in java. If you are not comfortable programming, you will have great difficulty in this class.
|Until recently, information systems security has
only been a focus of the military, and the financial communities. With
the recent explosive growth and merging of telecommunications and
computing, security has become an integral element of any reliable and
robust information systems environment. Unfortunately, most current
commercial products ignore security in favor of a user friendly
environment and performance. The side-effects of this decision are now
well documented in the press.
This class will cover information systems security at the under graduate level.
|There will be several homework assignments
(written and programming) as well as mid-term, and final examinations. A
systems oriented term project will also be required.
NOTE: All work that you submit in this course must be your
own; unauthorized group efforts are considered academic dishonesty. See
the Undergraduate Catalog for definitions and sanctions.
NOTE: Failing to submit two or more homework assignments is
cause for failure of the course.
Details for the submission of each assignment will be included in the assignment.
Late assignments will only be accepted under exceptional circumstances AND with prior arrangement. A penalty may apply.
|Final grades will be determined using the following distribution:|
Programming assignments and the course project will be graded on correctness as well as documentation. A project that fails on the provided test cases (and those used in grading) will not receive a favorable grade. A project that passes all tests, but does not contain reasonable documentation will also not receive a favorable grade. Security is a subset of reliability- good design and documentation increases the reliability of your code and thus the security.
Your class participation grade will be determined by your on time attendance to class, your participation in classroom discussions, and your scores on pop quizzes. Pop quizzes, when given, will cover material previously covered in class, previous reading assignments, and simple questions on the days reading assignment.
Please read Making the
Grade by Kurt Wiesenfeld and keep his views (which I share) in mind
when deciding how much effort to invest in your coursework. The
only reason why I have (or will) raise a grade is when I or the TA make
an error in grading.
|Schedule of Classes|