EECS3311

User Tools

Site Tools

You are here: EECS3311 - Software design - Winter 2017 » Course Outline
Trace:
course_outline

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
course_outline [2015/04/17 16:10] – jonathancourse_outline [2016/12/26 22:35] – jonathan
Line 3: Line 3:
 ===== Calendar Description ===== ===== 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 ==== ==== Learning Outcomes ====
Line 15: Line 15:
 3. **Testing**: Develop systematic approaches to organizing, writing, testing and debugging software. 3. **Testing**: Develop systematic approaches to organizing, writing, testing and debugging software.
  
-4. **Analysis**: Develop insight into the process of moving from an ambiguous problem statement to a well-designed solution (analysis).+4. **Analysis**: Develop insight into the process of moving from an ambiguous problem statement to a well-designed solution.
  
-5. **Architecture**: Design software using appropriate abstractions, modularity, information hiding, and design patterns (design).+5. **Architecture**: Design software using appropriate abstractions, modularity, information hiding, and design patterns.
  
 6. **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. 6. **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.
Line 32: Line 32:
   * Debugging, Unit Testing and Test Driven Development   * Debugging, Unit Testing and Test Driven Development
   * Abstract Data Types, Modularity and Information Hiding   * 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   * 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.  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. 
course_outline.txt · Last modified: 2017/05/02 16:17 by jonathan