Home

Online Learning

Degrees

FAQ

Schedule of Courses

Contact Us

Texts

Software

Other Resources

Catalog Description

Course Objectives

Prerequisites

Class Location

Grading

Assignments

Additional Information

Schedule of Assignments and Events

Contact Information/Office Hours

Texts

• 24 Deadly Sins of Software Security: Programming Flaws and How to Fix Them (1st ed.) by Michael Howard et al., McGraw-Hill (2009) ISBN 978-0071626750 (Required).
• Web Application Security, A Beginner's Guide (1st ed.) by Brian Sullivan and Vincent Lu, McGraw-Hill Osborne Media (2011) ISBN 978-0071776165 (Required).
• (Deleted)

Software

• A software development environment for your language of choice (C++, C#, Java, Python, Ruby, PHP, Perl, ask regarding others) (Required, but your choice.)
• "Secure Programming for Linux and Unix HOWTO -- Creating Secure Software", http://www.dwheeler.com/secure-programs/ . (Required, but only for people doing this course in Linux or Unix. Note that Mac OS X is a variation of Unix .)

Other Resources

TBD

Please see the Online Learning page for more information regarding expected student student access to the internet, and corresponding software.

Please see the Mercer's Distance Learning page for more information regarding expected student student access to the internet, and corresponding software.

Course Description

Topics in software security.

This Online Learning course begins on June 22, 2029 at 8:00 am Eastern time. All assignments are due by the end (11:59:59 pm) of the specified calendar day in the Eastern time zone. This course ends at 11:59:59 pm on July 25, 2020, in the Eastern time zone.

Back to Top

Course Objectives

Breadth and Depth in Defining, Analyzing, and Solving Complex Problems:

• After successfully completing this course, you should be able to demonstrate a basic capability to apply software security techniques to solve complex problems.

Communicate Technical Aspects of the Solution for Complex Software Engineering Problems to a Technical Audience:

• After successfully completing this course, you should be able to demonstrate a basic ability to communicate regarding the application of software security techniques to a technical audience.

Back to Top

Prerequisite(s)

SSE 550 or permission of the program director.

This prerequisite provides one graduate-level 3 semester hour course in C++ or Java or C#.

Please see the Online Learning page for more information regarding expected student abilities and aptitudes.

Back to Top

Class Location

• This course is entirely online.
• Please see the Canvas page for information regarding access to Canvas, Mercer's online learning system. Please note that the Canvas contents for this course are in addition to this syllabus, and do not substitute for this syllabus.

Back to Top

Grading

Item	Percent of Term Grade
Project 1	10
Project 2	35
Project 3	50
Canvas Discussion Contributions	5

More information about project grading is contained in the General Project Rubric .

Canvas Discussion Contributions are graded as follows:

• They must be substantive contributions, useful and informative to people in the course, on topic with the course material.
• They must be posted in Canvas while the course is in session (June 22 - July 25, 2020).
• They must be at least three in number.

Credit will be given only for original work.

The Office of the Provost's "Academic Integrity page includes a link to the Graduate Honor Code, which covers issues such as plagiarism. Please take a good, careful look at the Graduate Honor Code. Plagiarism is not acceptable in this, or any, course.

Project reports are to be submitted complete, not as incremental partial submissions.

Instruction Time

All course work time is categorized as either Direct or Non-Direct (but not both). More information about the Direct and Non-Direct categories is contained in the Direct and Non-Direct and Report Logs. Please read these pages very carefully.

The SACSCOC (our accrediting agency's) standard (minimum) for a three credit course such as this is 2250 minutes of direct activity and 4500 minutes of non-direct activity per semester. These minima add up to 6750 minutes of activity per semester.

Please begin logging your time as specified on these pages, starting wherever you are in the course when you receive this notice (via Canvas). These logs will not be deliverables for this course.

All deliverables are due on their assigned dates .

• Deliverables submitted no more than one day late may be graded, but with a 10 point penalty .
• Deliverables submitted more than one day (24 hours) late will receive a grade of zero.

Manage your time and keep on schedule. You should schedule your work evenly throughout the term.

If you have a question about any of this, please ask.

Back to Top

Assignments

• Purpose of projects:
• Use the projects to develop your capabilities, and
• Use the projects to demonstrate your capabilities.
• Deliverables for all projects:
  • Projects shall be delivered via Canvas.
  • Project reports should each be a single, standalone .pdf document, with the Bookmark feature used to support easy document navigation. Note that both MS Word and LibreOffice Write (which is free open-source software) support bookmarks, and will carry the bookmarks over into the pdf document when they convert your .docx, .odf, or whatever file type to PDF.
  • Project reports should focus on the development and/or maintenance that you actually do. Reports should not focus on summarizing or explaining the text or other materials.
  • Inclusion of screenshots demonstrating your work, such as showing test execution and results, is appropriate. But code must not be presented in screenshots. Code must be presented as text which can be searched using the "find" or "search" capability of the app (e.g., Acrobat Reader) that will be used to read your report. Long code listings can be placed in appendices if doing so does not interfere with you presenting your work on that code in the body of the text.
  • Your report should be organized in such a way as to make the topics that you want credit for covering easy to find, and demonstrate your capabilities clearly and convincingly. Everything you want considered for credit, including code and tests (including test results), should be included in the report.
  • Each project can be a single, integrated project that tries to actually do something, or a collection of exercises that demonstrate your capabilities but don't accomplish anything else, or any combination of these two alternatives that you find convenient, unless otherwise specified in the assignment.
  • You may include other material outside of the report, if you wish, but this material may or _may not_ be considered in evaluating your work.
  • For each capability that you demonstrate within a report or major section of that report, you may present only the final result of your work; you need not demonstrate every step in the development of that result.
  • Use IEEE standards to cite references How to Cite References: IEEE Documentation Style. Careful attention to this will help you to avoid plagiarism.
  • Some suggestions for doing a project are contained in the One Way to Do a Project page.
  • You may arrange the teamwork pretty much as you please. The team members may develop a single deliverable (code, report, etc.), or multiple deliverables, one per member. In this latter case, team members should perform substantive peer reviews of each others's work as that work progresses, to help their team mates to do better work. Persuasive evidence of these reviews must be included in the reports.
• Project 1 (solo):
  • Software security is too large an area to cover in one course, so you will need to make a plan to study and develop capabilities in some subset of the topics in this area.
  • Skim the Tables of Contents of your two texts. Look into chapters that are of particular interest to you.
  • Based on topics/chapters of interest to you, plan your work for Project 2. You can change this plan later if you find that to be a good idea, but at least start out with a written plan in mind.
  • Document your plan; this document is your Project 1 report. It need not be long, but it should have some substance and detail.
• Project 2 (solo):
  • Execute your plan, and document the results of your next step as your Project 2 report.
• Project 3 (team):
  • Form a team (two people per team preferred, three may be allowed with my prior permission).
  • Plan your team's Project 3, and report your plan via the course Canvas discussions.
  • Your team should now execute the plan, and report the results in the Project 3 report.
• Please raise questions and issues via the course Canvas discussions.

Back to Top

Additional Information

• Asynchronous Learning Nets (ALNs):
• Self Study: You study the texts and any other course study material on your own.
• Collaborative Projects: After your self-study, you collaborate (communicating via whatever means the team members find acceptable) with your partner(s) to produce a team product. Your collaborative work is substantial, asynchronous, and rapid.
• This course is an online learning course. Please read this Online Learning web page regarding online learning in this course and this program.

Back to Top

• What Do I Do?

• Login in to the course on Canvas before the second day of class.
• Study the assigned material.
• Write and read Canvas messages about ideas, problems and solutions to do with the assigned study material.
• Do the assigned work, deliver the assigned deliverables.
• Write and read Canvas messages about ideas, problems, projects, and solutions to do with the assigned homework.
• Review the deliverables, which will be made available in the "Files" section of the course on Canvas, produced by other people.

Changes to this Syllabus:

There will be changes to this syllabus, so check back frequently, and don't forget to hit "Reload" or "Refresh".

Back to Top

Schedule of Assignments and Events (tentative)

Start Date	End Date	Activity/Event
June 22, 2020	July 25, 2020	Course in Progress
	June 22, 2020	Login in to the course on Canvas.
June 22, 2020	June 26, 2020	Work on Project 1
	June 26, 2020	Project 1 due
	July 8, 2020	Project 2 due
	July 25, 2020	Project 3 due Course ends

Notes: The course begins at 8:00 am on the first day of class (see schedule above), and ends at 11:59:00 pm on the last day of class. Assignments are due at any time during the day specified on the schedule, that is, before 11:59:00 pm on that day. All times are Macon, Georgia (Eastern time zone) times.

Back to Top

---

Contact Information

• My Name: Dr. Paul E. MacNeil
• My E-mail: macneil_pe@mercer.edu .
• OfficeHours
• My Office Phone: 478 301-2185
• US Mail:
 
• Dr. Paul E. MacNeil
• School of Engineering
• Mercer University
• 1501 Mercer University Drive
• Macon, GA 31207

Back to Top

Important Additional Information:

"Disability Statement for Syllabus"

"Students in need of accommodation due to a disability should contact the Access and Accommodation Office to complete the verification process to become approved for services. In order to receive accommodations, each term, students will request accommodation and faculty notification forms through the Access Office online system Accommodate. Students are strongly encouraged to schedule a meeting with each professor in a timely manner to discuss arrangements. Accommodations are not retroactive in nature. Note - Disability accommodations or status are not reflected on academic transcripts. Students with a history of a disability, perceived as having a disability or with a current disability who do not wish to use academic accommodations are also strongly encouraged to complete the verification process with the Access Office. Students must request accommodations in a timely manner to receive accommodations in a timely manner."

"Mental Health and Wellness Statement for Syllabus"

"Mental Health and Wellness: Mercer University faculty and staff recognize that mental health concerns can impact academic performance and interfere with daily life activities. Please notify your faculty member or academic advisor for academic assistance, as needed. CAPS can also provide support if you’re feeling stressed, overwhelmed, anxious, depressed, lost or are struggling with personal issues. Please call or visit the Counseling and Psychological Services (CAPS) website for more information. These services are free and confidential, and support non-traditional, graduate, and undergraduate students. Students at Regional Academic Center locations may call a CAPS Office for assistance in finding local services (that may charge for their services) if distance to either campus creates challenges. CAPS locations include: MACON – Linden House (attached to the MEP Residence Hall), 478-301-2862; ATLANTA – 215 Sheffield Student Center, 678-547-6060."

---

Accreditation: Mercer University is accredited by SACSCOC.