Differences

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

--- course_outline [2013/03/24 18:51] – jonathan
+++ course_outline [2013/04/14 02:01] (current) – jonathan
@@ Line 7: / Line 7: @@
 **Learning Outcomes**:
-Software is code that is developed by one time to be used and maintained by others. Students are thus expected to nderstand how to develop software so that it is:
+Software products are programs developed by one team to be used and maintained by others. The original development team may not be around to maintain the product. Students are thus expected to understand how to develop software so that it is:
   - Correct
   - Efficient
   - Maintainable
-Software cannot be **correct** without a **specification**. So we need to master skills that allow us to write a specification, and we must also understand how to implement a specification that we receive from others. For precision, specifications will often require the use of mathematics. Design by Contract and Unit Testing are fundamental skills needed to achieve correctness. So we need to understand how to use Design by Contract to specify software via meaningful preconditions, postconditions and class invariants; given these, we have a precise notion of the correctness of a class (or module).
+Software cannot be **correct** without a **specification**. So we need to master skills that allow us to write a specification, and we must also understand how to read, understand, and implement a specification that we receive from others. For precision, specifications will often require the use of mathematics. Design by Contract and Unit Testing are fundamental skills needed to achieve correctness. So we need to understand how to use Design by Contract to specify software via meaningful preconditions, postconditions and class invariants; given these, we have a precise notion of the correctness of a class (or module). Software is **reliable** if it is **correct** (works according to specification) and **robust** (reacts appropriately to abnormal conditions).
 For software to be efficient we need to understand the appropriate use of algorithms and data structures. Loop variants and invariants help to ensure that loops terminate, bound their complexity, and ensure that they terminate correctly.
@@ Line 71: / Line 71: @@
   * Decorator Pattern
   * Visitor Pattern
-  * Some others
+  * Composite, Adapter, and Facade
 We stress information hiding (as in famous paper by Parnas) and the criteria by which to decompose a system into modules. What are the features? Which features belong together coherently in a module (class)? How are modules related to each other (client supplier and inheritance relationships)? How are modules grouped into clusters? What is the system architecture? How do we choose between one design and another?
@@ Line 84: / Line 84: @@
  ====== DbC: Exceptions ======
-See slides and OOSC2
+See slides and OOSC2. How to make software products robust.
+ ====== Quality First ======
+See the Osmonde curve and the slides.