User Tools

Site Tools


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:26] 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]] 
  
  
- +===== Info =====
- +
-====== Info ======+
  
   * Quizzes every week during labs.    * Quizzes every week during labs. 
Line 46: Line 44:
     * [[https://wiki.eecs.yorku.ca/project/eiffel/bon:|BON]] (Business Object Notation). The BON method for analysis and design of object-oriented software is a means of extending the higher-level concepts of the Eiffel programming language into the realm of analysis and design aided by a graphical notation akin to but different from UML. BON is described in depth in the book //Seamless Object-Oriented Software Architecture//, Prentice Hall 1994, by Kim Waldén and Jean-Marc Nerson.  The book is out of print but is available as a [[http://www.bon-method.com/book_print_a4.pdf|pdf]]. There is a template in Visio to do nice BON diagrams.     * [[https://wiki.eecs.yorku.ca/project/eiffel/bon:|BON]] (Business Object Notation). The BON method for analysis and design of object-oriented software is a means of extending the higher-level concepts of the Eiffel programming language into the realm of analysis and design aided by a graphical notation akin to but different from UML. BON is described in depth in the book //Seamless Object-Oriented Software Architecture//, Prentice Hall 1994, by Kim Waldén and Jean-Marc Nerson.  The book is out of print but is available as a [[http://www.bon-method.com/book_print_a4.pdf|pdf]]. There is a template in Visio to do nice BON diagrams.
  
-====== Getting Started ======+===== Getting Started =====
 * **Important**: Subscribe to the forum for the latest announcements. Please ask all questions relating to the course material on the forum (not via email). For all other questions, see the course instructor during office hours.  * **Important**: Subscribe to the forum for the latest announcements. Please ask all questions relating to the course material on the forum (not via email). For all other questions, see the course instructor during office hours. 
  
Line 57: Line 55:
   *  Examples and useful slides from [[http://www.cse.yorku.ca/course_archive/2014-15/F/3311/|other instructors]] for this course.   *  Examples and useful slides from [[http://www.cse.yorku.ca/course_archive/2014-15/F/3311/|other instructors]] for this course.
  
-====== Workload ======+===== Workload =====
  
 The work load in this course, as in many computer science and engineering courses, is high. The course has a scheduled weekly laboratory component to it which involves designing and coding (in Eiffel). You should be prepared to devote 12 hours a week on average to the course; this includes class time and labs. With proper planning and discipline, you can spread most of the work load fairly evenly throughout the course. The work load in this course, as in many computer science and engineering courses, is high. The course has a scheduled weekly laboratory component to it which involves designing and coding (in Eiffel). You should be prepared to devote 12 hours a week on average to the course; this includes class time and labs. With proper planning and discipline, you can spread most of the work load fairly evenly throughout the course.
Line 63: Line 61:
 It is up to you to read and study relevant material without explicit instructions. You are expected to find the required readings in the references and any other sources you can find. Part of the university experience is to acquire a measure of self reliance. The instructor for the course can only guide you as to what is useful to learn; the effort must come from you. The course classes will not cover all the topics in detail. Instead, the classes will cover the most important points and give you pointers as to how the rest of the material can be studied. It is up to you to read and study relevant material without explicit instructions. You are expected to find the required readings in the references and any other sources you can find. Part of the university experience is to acquire a measure of self reliance. The instructor for the course can only guide you as to what is useful to learn; the effort must come from you. The course classes will not cover all the topics in detail. Instead, the classes will cover the most important points and give you pointers as to how the rest of the material can be studied.
  
-====== 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 (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. 
start.1515374771.txt.gz · Last modified: 2018/01/08 01:26 by jonathan