CS 342 - Software Design

Spring 2016

Assignments

Programming Projects

• Programming Project 1 - Due 2/4/16
  • proj1.pdf
  • Turn in project via Submission Link added to Blackboard
  • You should zip all of your files together and submit that ONE zip file.
  • If you submit multiple times, we will grade the last file submitted.

• Programming Project 2 - Due 2/23/16
  • CS342Proj2.pdf
  • Partner Assignments are available in Blackboard in the Course Information Section.
    • Contact your partner immediately!
    • Primary item to verify is whether your partner is still in the class.
    • If you assigned partner has dropped, let Prof. Troy know and he will reassign you once this has been verified.

• Programming Project 3 - Due 3/15/16
  • proj3s16.pdf
  • Partner Assignments are available in Blackboard in the Course Information Section.
    • Contact your partner immediately!
• Examples of Files

• • • rsamessage.txt
    • prikey
    • pubkey
    • rsablocked1.txt
    • rsablocked2.txt
    • rsablocked4.txt
    • rsablocked8.txt

• Programming Project 4 - Due 4/7/16
  • proj4s16.pdf

• Design Document for Programming Project 1 - Due 2/11/14 at 11:59pm
  
  • Submit as a PDF Document to Submission Link in Blackboard
  • Use the Template as Described in: Writing an Effective Design Document
  • Word Document with the Template: Design_Document_Template.docx
  • Note - this is NOT a "Programming Assignment", so late assignments are NOT accepted.
  • UML Diagrams Explained: http://www.uml-diagrams.org/ or http://www.agilemodeling.com/essays/umlDiagrams.htm
    • UML Component Diagrams:
      • http://www.uml-diagrams.org/component-diagrams.html
      • http://agilemodeling.com/style/componentDiagram.htm
      • http://www.ibm.com/developerworks/rational/library/dec04/bell/
    • UML Class Diagrams:
      • http://www.uml-diagrams.org/class-diagrams-overview.html
      • http://agilemodeling.com/style/classDiagram.htm
    • UML Activity Diagrams:
      • http://www.uml-diagrams.org/activity-diagrams.html
      • http://agilemodeling.com/style/activityDiagram.htm

• Unit Testing for Project 2 - Dues Tuesday 3/1/16 at 11:59pm
  • Write at least 15 Unit Tests using the JUnit Framework for the Code developed by your group for Project 2. This is a group project, to be performed by the same group pairs as was used for Project 2.
  • Note: This is NOT a programming assignment, so late submissions are not accepted.
  • Follow the Tests written in the Example: CalculateTest.java
    • The above code assume the existing of the "production code" of: Calculate.java
    • The test would be run using a JUnit plug-in in an IDE or via the command line using: JunitRunner.java
  • Your submission is to be a zip file sent through Blackboard that contains your XXXTest.java file, one or more .java files from Project 2 that contains the unit code being tested, and the modified version of JunitRunner.java that would run your Tests from the command line.
  • The JUnit home page can be found at: http://junit.org/
  • JUnit Reference Web Pages can be found at:
    • http://www.vogella.com/tutorials/JUnit/article.html
    • http://www.tutorialspoint.com/junit/junit_test_framework.htm
    • http://junit.sourceforge.net/doc/testinfected/testing.htm
    • http://www.javacodegeeks.com/2014/11/junit-tutorial-unit-testing.html

• Design Document for Programming Project 3 - Due 3/8/16 at 11:59pm
  
  • Submit as a PDF Document to Submission Link in Blackboard
  • Use the Template as Described in: Writing an Effective Design Document
  • Word Document with the Template: Design_Document_Template.docx
  • Note - this is NOT a "Programming Assignment", so late assignments are NOT accepted.
  • UML Diagrams Explained: http://www.uml-diagrams.org/ or http://www.agilemodeling.com/essays/umlDiagrams.htm
    • UML Component Diagrams:
      • http://www.uml-diagrams.org/component-diagrams.html
      • http://agilemodeling.com/style/componentDiagram.htm
      • http://www.ibm.com/developerworks/rational/library/dec04/bell/
    • UML Class Diagrams:
      • http://www.uml-diagrams.org/class-diagrams-overview.html
      • http://agilemodeling.com/style/classDiagram.htm
    • UML Activity Diagrams:
      • http://www.uml-diagrams.org/activity-diagrams.html
      • http://agilemodeling.com/style/activityDiagram.htm

Items to remember For Programming Assignments

Late assignments will be accepted with the following penalties:

One Day Late: 10% penalty

Two Days Late: 30% penalty

Three Days Late: 60% penalty

Four+ Days Late: 100% penalty (i.e. a score of 0 is recorded)

Programs that do not compile will receive a grade of 0. (Warning messages from the compiler are acceptable but should be resolved.) Programs that terminate unexpectedly (throw an uncaught exception or cause a core dump) will not receive any credit for the portion of code being tested.

Your program must be written in good programming style. This includes (but is not limited to) meaningful identifier names, a file header at the beginning of each source code file, a function/method header at the beginning of each function/method, proper use of blank lines and indentation to aide in the reading of your code, explanatory "value-added" in-line comments, etc.

-- troy - 2016-01-20

Comments