EECS3311

User Tools

Site Tools

You are here: EECS3311 - Software design - Winter 2018
Trace:
start

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
start [2018/01/08 01:23] – jonathanstart [2018/01/08 01:29] (current) – jonathan
Line 31: Line 31:
 ===== Fall 2017 Slides and Videos ===== ===== Fall 2017 Slides and Videos =====
  
- +[[https://www.eecs.yorku.ca/~jackie/teaching/lectures/index.html#EECS3311_F17|Fall version of the course]]. The topics, slides and recorded lectures are relatively close to the Winter section. 
-[[https://www.eecs.yorku.ca/~jackie/teaching/lectures/index.html#EECS3311_F17|Fall version of the course]] +
  
  
Line 39: Line 37:
 ===== Info ===== ===== Info =====
  
-  
   * Quizzes every week during labs.    * Quizzes every week during labs. 
   * **Textbooks**: the following texts are highly recommended and are available on reserve in the Library:   * **Textbooks**: the following texts are highly recommended and are available on reserve in the Library:
Line 52: Line 49:
   *See bottom** ↓** of this page for login with your Prism password. Slides are available from the SVN repository (see link in the sidebar, once you have logged on).   *See bottom** ↓** of this page for login with your Prism password. Slides are available from the SVN repository (see link in the sidebar, once you have logged on).
  
-  * Office hours: A TA will be available during the Lab hour (5.30pm to 7pm) on Mondays in LAS1006. +  * Office hours: See Office Hours on the sidebar 
  
   * Get started using the Eiffelstudio IDE on the first day of class ([[https://wiki.eecs.yorku.ca/project/eiffel/getting_started:start|here]]). Compile and execute a hello world program. Then use the ESpec library to write and execute your first test. You might want to run through this [[http://tecomp.sourceforge.net/index.php?file=doc/lang/tutorial.txt|introductory tutorial]].   * Get started using the Eiffelstudio IDE on the first day of class ([[https://wiki.eecs.yorku.ca/project/eiffel/getting_started:start|here]]). Compile and execute a hello world program. Then use the ESpec library to write and execute your first test. You might want to run through this [[http://tecomp.sourceforge.net/index.php?file=doc/lang/tutorial.txt|introductory tutorial]].
Line 68: Line 65:
 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.  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 =====
  
 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: 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:
Line 86: Line 83:
 7. **Documentation**: Develop the ability to write precise and concise software documentation that also describes the design decisions and why they were made. 7. **Documentation**: Develop the ability to write precise and concise software documentation that also describes the design decisions and why they were made.
  
-==== Topics ====+===== Topics =====
 1. Unit Tests, regression testing, using testing tools and debugging 1. Unit Tests, regression testing, using testing tools and debugging
  
start.1515374624.txt.gz · Last modified: 2018/01/08 01:23 by jonathan