Differences

This shows you the differences between two versions of the page.

--- whats_new [2008/03/19 18:21] – bil
+++ whats_new [2008/04/28 16:44] (current) – bil
@@ Line 99: / Line 99: @@
 The zip file **mml_graph_and_map_examples.zip** in the Code directory contains an update to the MML library. The library now has class MML_GRAPH that also has queries to assert whether the graph is a tree. Mathematically, a graph G = [N, E] where N is a set of nodes and E is just a binary relation on the set of nodes. In Eiffel, we would write //graph//: MML_PAIR[MML_SET[G], MML_REL[G,G]]. A relation G<->G is called an endorelation. You will also find a MAP class with object and reference comparisons contracted in this new version of MML. You may use this MML cluster in Assignment 3 if you choose.
 ===== March 19, 2008 =====
 Assignment 4 is now posted under Notes.
+===== March 25, 2008 =====
+Grades for assignment 2 are now available under ePost
+===== April 3, 2008 =====
+Grades for assign 3 were posted yesterday. For both sections, assignments can be picked up from outside the SEL (cseb2056) on Monday April 7th, noon to 5pm. The instructor for section Z will be available for office hours on Thursday April 10th from 4-6pm.
+===== April 8, 2008 =====
+The exam is closed book. A single data sheet (US letter size) will be allowed, but nothing else.
+Everything covered in class, in the slides, the test, the assignments and the readings in the text (OOSC2) is required for the exam.
+Software development is a process of eliciting **Requirements**, coming up with a **Design** and then **Implementation** of the design in code.
+The focus of this course is Design. In Design we need to make the following design decisions:
+  * what modules (classes) do we need to satisfy the Requirements;
+  * the API (features and their signatures for each module);
+  * how the modules (classes) are organized and relate to each other (e.g. via client-supplier and inheritance relations.
+Contracts, scenario & unit tests and BON static and dynamic diagrams are all important tools for describing the Design.
+**Contracts** and tests are specifications that allow us to assess the correctness of the implementation, i.e. the code that implements a software component. Both classical contracts and **MML** contracts are important tools. Without these tools we would have no way of knowing if our implementations are correct (i.e. satisfy their specifications).
+**Design Patterns**. Another vital component of understaning Design is understanding some of the important design patterns. Good software developers have struggled with the same design problem that you may face -- and they have already solved something like your problem. Knowing these road-tested patterns allows you take advantage of best practices and to communicate aspects of your design to others. BON static and dynamic diagrams and contracts are useful for describing design patterns.
+===== April 28, 2008 =====
+All grades for the course are now posted through ePost.
+You can pick up Assignment 4 from CSEB 2056 at 12-5 on Thursday, May 1.