Differences

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

--- course_outline [2015/03/25 23:00] – jonathan
+++ course_outline [2017/05/02 16:17] (current) – jonathan
@@ Line 3: / Line 3: @@
 ===== Calendar Description =====
-A study of design methods and their use in the correct implementation, maintenance and evolution of software systems. Topics include design, implementation, testing, documentation needs and standards, support tools. Students design and implement components of a software system. Weekly 1.5 hour laboratory. Prerequisites: General prerequisites; including SC/MATH 1090 3.00; LE/EECS 2031 3.00.
+A study of design methods and their use in the correct implementation, maintenance and evolution of software systems. Topics include design, implementation, testing, documentation needs and standards, support tools. Students design and implement components of a software system. Weekly 1.5 hour laboratory (starting 2017). Prerequisites: General prerequisites; including SC/MATH 1090 3.00; LE/EECS 2031 3.00.
 ==== Learning Outcomes ====
@@ Line 9: / Line 9: @@
 Software designers are experts at developing software products that are correct, robust, efficient and maintainable. Correctness is the ability of software products to perform according to specification. Robustness is the ability of a software system to react appropriately to abnormal conditions. Software is maintainable if it is well-designed according to the principles of abstraction, modularity, and information hiding. At the end of the course, students will be able to:
-. Describe software specifications via Design by Contract, including the use of preconditions, postconditions, class invariants, loop variants and invariants
+. **Specification**: Describe software specifications via Design by Contract, including the use of preconditions, postconditions, class invariants, loop variants and invariants
-. Implement specifications with designs that are correct, efficient and maintainable.
+. **Construction**: Implement specifications with designs that are correct, efficient and maintainable.
-. Develop systematic approaches to organizing, writing, testing and debugging software.
+. **Testing**: Develop systematic approaches to organizing, writing, testing and debugging software.
-. Develop insight into the process of moving from an ambiguous problem statement to a well-designed solution (analysis).
+. **Analysis**: Develop insight into the process of moving from an ambiguous problem statement to a well-designed solution.
-. Design software using appropriate abstractions, modularity, information hiding, and design patterns (design).
+. **Architecture**: Design software using appropriate abstractions, modularity, information hiding, and design patterns.
-. Develop facility in the use of an IDE for editing, organizing, writing, debugging, testing and documenting code including the use of BON/UML diagrams for documenting designs. Also the ability to deploy the software in an executable form.
+. **Tools**: Develop facility in the use of an IDE for editing, organizing, writing, debugging, testing and documenting code including the use of BON/UML diagrams for documenting designs. Also the ability to deploy the software in an executable form.
-. Develop the ability to write precise and concise software documentation that also describes the design decisions and why they were made.
+. **Documentation**: Develop the ability to write precise and concise software documentation that also describes the design decisions and why they were made.
 ==== Topics ====
@@ Line 33: / Line 32: @@
   * Debugging, Unit Testing and Test Driven Development
   * Abstract Data Types, Modularity and Information Hiding
-  * Design Patterns
+  * Design Patterns (Singleton, Iterator, Observer, Decorator, Visitor, Composite, Undo/Redo)
   * Documenting Design Decisions and demonstrating that code satisfies the design
-===== Detailed Topics =====
+===== Detailed Topics from last year (2015W) =====
 The suggested textbooks should help you do self-paced learning, a requirement for this course. The lectures, Labs, assignments and Project will exercise your understanding that you should develop by reading and working on your own.
@@ Line 62: / Line 61: @@
   * What is a Class? It's static structure
   * What is an Object? It's dynamic structure
-  * Representing system architecture via BON (and UML) class diagrams.
+  * Representing system architecture via BON and UML class diagrams.
   * Relationships between classes: Client-Supplier (associations) and Inheritance
-  * Uniform Acces Principle (and information hiding)
+  * Uniform Acces Principle and information hiding
-  * Using Eiffel for DbC
+  * Design by Contract in depth
   * Using the EiffelStudio Debugger for Testing, and ECF files for clusters and libraries
   * Using the EiffelStudio BON diagraming tool
@@ Line 74: / Line 73: @@
   * Void Violation Cases and Void Safety
   * What is Design? Architecture and Specifications
-  * The BON diagram notation for Architecture
+  * BON and UML diagram notations for Design & Architecture
   * Information Hiding
   * Abstraction and abstract (deferred) classes
@@ Line 121: / Line 120: @@
   * Event Based Programming and Publish-subscribe (EVENT_TYPE abstraction using agents)
-=== Slides 12 ===
+=== SDD -- Software Design Document ===
 SDD -- Software Design Document
   *See [[https://wiki.eecs.yorku.ca/project/sel-students/p:tutorials:sdd:start|SDD overview and templates]]
-  * Koopman and Toyota Unintended acceleration (see )
+  * Koopman and Toyota Unintended acceleration (see video and slides [[https://mediatech-stream.andrew.cmu.edu/Mediasite/Play/7c2451b6ec764be4bee295095a642c691d?catalog=35969fb7-4f63-4ebb-85d2-5b5a17a3b979|here]]). Note the need for testing, static analysis (typing) and the V model (see Lab3).
+=== Slides 12 ===
+Design Pattern: Decorator and Open-Closed Design Principle. Static Class Digram and Dynamic Sequence Diagram. See Code sample.
+=== Slides 13 ===
+Design Pattern: Composite. See code sample. UML inheritance (generalization) and client-supplier (associations, aggregation and composition).
+=== Slides 14 ===
+Design Pattern: Visitor. See code sample. Static and Dynamic sequence diagram.
+=== Slides 15 ===
+Design by Contract and Exceptions. An exception is a violation of the contracts not a normal sequencing mechanism. The problem with using exceptions in place of preconditions in Java, C# etc. (a) An exception is the negation of the precondition, but is the precondition that the client needs to know. (b) An exception may appear in a Java interface (e.g Arithmetic-Exception), but is it is non-specific. It does not document for the client how it could have been avoided.
+=== Slides 16 ===
+Correctness: (a) Hoare logic and (b) Design by Contract and loop variants and invariants. %%(c)%% **Tolerant** (involving defensive programming) and **Demanding** routines, depend on the strength of the preconditions. (d) The difference between **abstract algorithms** and their **program implementations**.
+[[https://bertrandmeyer.com/2014/12/07/
+lampsort/|Lampsort]]. Algorithms such as Quicksort are normally presented too close to implementation (e.g. as a recursive routine). But Quicksort is really a divide-and-conquer at the abstract level that can be refined to a recursive, iterative or concurrent implementation. Eiffel (and loop variants/invariants) can describe the more **abstract algorithm** rather than its too **detailed implementation**.
+The Eiffel method treats the whole
+process of software development as a continuum; unifying
+the concepts behind activities such as requirements,
+specification, design, implementation, verification,
+maintenance and evolution; and working to resolve the
+remaining differences, rather than magnifying them.
+Formal specification languages look remarkably like
+programming languages; to be usable for significant
+applications they must meet the same challenges: defining a
+coherent type system, supporting abstraction, providing
+good syntax (clear to human readers and parsable by tools),
+specifying the semantics, offering modular structures,
+allowing evolution while ensuring compatibility.
+The same kinds of ideas, such as an objectoriented
+structure, help on both sides. Eiffel as a
+language is the notation that attempts to support
+this seamless, continuous process, providing tools
+to express both **abstract specifications** and **detailed
+implementations**.