Notes From Class

Week 1: January 26 and 28, 2016.

• Lecture slides: Introduction, Motivation and Drivers .

• Reading: Mary Meeker, Internet Trends , D10 Conference, 2012.

• Class Reader

  NOW AVAILABLE !!
  Please purchase a copy of the Class Reader from the Engineering Copy Center.
  Cost: $55.00.

• Lecture slides: Software Design and Development .

• Lecture slides: Introduction to Java .

• Lecture slides: The Java Language .

• Homework 1
  Due date: February 18.

  I have decided to partition the homework into three lavels. You decide what level you fit into -- hand in solutions to four problems.

  Absolute Java Novice. i.e., I have never written a Java program before?

  Solve Problems: 7.3, 7.4, 7.9 and 7.13 in the class reader.

  Java Rusty. i.e., I took a Java class several years ago.

  Solve Problems: 7.9, 7.13, 7.17 and 7.20 in the class reader.

  Hand in either a document of your homwork that includes input files, output and source code, or, a zip file of the source code for your program along with a document summarizing the source code and samples of output.

  Java Knowledgeable. i.e., Yeah, I have written a bunch of Java programs...

  Solve the same problems as "Java Rusty" but do it in Python.

• Thursday: We will finish our discussion on basic features of the Java Language.

• Lecture slides: Working with Objects and Classes .

• Here are the problems for Homework 1.

• Lecture slides: Working with Abstract Classes and Interfaces .

Week 5: February 23 and 25, 2016.

• Lecture slides: Working with Packages, JAR, and Ant .

• Homework 2
  Due date: March 3.

  The purpose of this assigment is learn how to write programs that use classes and objects -- hand in solutions to four problems, coded in either Java or Python.

  Programming in Java.

  Solve Problems: 8.1, 8.2, 8.4 and 8.6 in the class reader.
  Problem 8.4 refers to the "rainfall analysis program" -- see Problem 7.21 on pages 199--200 of the class reader for details.
  Click here to download a copy of Complex.java.

  Programming in Python.

  Solve Problems: 8.1, 8.2, 8.4 and 8.6 in the class reader, but code your solutions in python and/or jython. For problem 8.4, your jython code should call the java version of DataArray.java and then use PtPlot to create a histogram of rainfall measurements. For problem 8.6, use Python's complex data type -- I assume that the solution will be really short!

• Here are the problems for Homework 2.

Week 6: March 1 and 3, 2016.

• Lecture Slides: Java Collections Framework .

• Here are the solutions to Homework 1.

Week 7: March 8 and 10, 2016.

• Homework 3
  Due date: March 24.

  This homework will give you some practice at designing and implementing relationships among classes for a program that requires a handful of classes.

  1. Use either Java or Python to solve problems 11.1 and 11.2 in the class notes.

  2. Click here to download a short set of slides on relationships among classes: association, aggregation and inheritance. On slide numbers 47 and 48 you will find a class diagram and scenario for the operation of games in a small casino.

     Develop a set of Java (or Python) class relationships to refect the structure shown in slide 47. Try to use abstract classes and interfaces where you think that it makes sense.

     Note. You do not need to write code for what each method would do -- just provide the method declarations and perhaps a simple print message.

  3. Organize your solutions to the homework into a collection of packages, and develop an ant build.xml to control the compilation and execution of each part of the homework.

Week 8: March 15 and 17, 2016.

Week 9: March 22 and 24, 2016.

• Here are the midterms exams from 2012 and 2013 .

• In class we will cover the modeling of association relationships in class, which you might find useful in solutions to Homework 3.

• Presentation Slides: Parastoo Delgoshaei, Software Patterns for Traceability of Requirements to Finite State Machine Behavior: Application to Rail Transit System Design and Management , INCOSE, Rome, Italy, 2012.

• Presentation Slides: Eddie Tseng, Computational Framework for Parametric Modeling and System-Level Assessment of Building Floorplans , MS Thesis Presentation, April, 2015.

• Lecture Slides: Structural Design Patterns .

• Support Material: J2EE Patterns , Sun Services, SUN Microsystems, 2003.

Week 10: March 29 and 31, 2016.

• Here are the solutions to Homework 2.

• Midterm Exam. March 31, open book and open notes.
  Duration: 1 1/2 hrs.
  Three questions covering various aspects of Java and Java Collections.

Week 11: April 5 and 7, 2016.

• Lecture Slides: Modeling Real-World Networks .

Week 13: April 19 and 21, 2016.

• Lecture Slides: Chapter 15: Behavior Modeling Abstractions and Software Design Patterns

Week 13: April 26 and 28, 2016.

• Lecture Slides: Chapter 14: Modeling of Three-Dimensional Solids

• Here is a nice writeup on the Euler-Poincare Formula.

• See note below on adjustments to the final exam and due date for the final project (this rearrangement should provide more time for working on the term project).

Week 14: May 3 and 5, 2016.

• Project Development.
  I will come to class at 5 pm on both Tuesday and Thursday.
  If you are having trouble getting parts of your software to work,
  let me know and we will work things out!

• Here are the final exams from 2012 and 2013 .

Week 16: May 10, 2016.

• Final Exam. May 10, 5-7 pm in our regular classroom.
  The final exam will be open book and open notes,
  and will have the same style as the midterm exam.
  

  Update: The exam will be one question, with parts [1a] through [1p].
  It's a bit long so if some people need extra time that will be okay.

  Make sure that you look at the final exams from 2012 and 2013, and the chapter on Java Collections.

Project Report , Due: May 16 (no extensions)

Write a 10-15 page report on your project that includes:

1. A problem statement.
   What problem (or class of problems) does your software development address?
2. The software architecture. Describe the use of packages,
   arrangement of user-defined classes and interface classes, graphs and Java collections in your program.
3. Screendumps of your graphical user interface.
4. Brief conclusions and steps for future work (if you had more time).

Hand in the project report and a zip file of your code.

Last Modified: May 3, 2016.
Copyright © 2016, Institute for Systems Research, University of Maryland.