http://wiki.msoe.us/ 2010-03-11T19:15:18+00:00 http://wiki.msoe.us/ http://wiki.msoe.us/lib/images/favicon.ico text/html 2010-03-10T04:17:18+00:00 Chris Taylor http://wiki.msoe.us/cs2852/iterators?rev=1268194638&do=diff * Data structures typically contain a collection of elements. * It is often useful to be able to traverse that collection of elements. * It is possible to get an iterator from any collection that implements the Iterable<T> interface. * The Iterable<T> interface is quite simple: Iterator<T> iterator(); text/html 2010-03-10T04:14:04+00:00 Chris Taylor http://wiki.msoe.us/cs2852/jcf?rev=1268194444&do=diff * Storing collections (groups) of similar objects is a common programming task. * A text document is a collection of paragraphs. Each paragraph is a collection of words. Each word is a collection of characters. * The computer's file system is a collection of files. * A browser's bookmark list contains a collection of URLs. * etc... text/html 2010-03-10T04:08:36+00:00 Chris Taylor http://wiki.msoe.us/cs2852/arraylist?rev=1268194116&do=diff Array Review * An array is a collection of similar objects. Actually, one of two things: * A collection of primitives, all of the same type int[] integers; integers = new int[20]; * The first line declares a reference to an array of ints, called integers. * The second line allocates space for an array of twenty ints and makes integers point to this newly allocated array. text/html 2010-03-09T18:00:19+00:00 Chris Taylor http://wiki.msoe.us/cs2852/list?rev=1268157619&do=diff * Storing collections (groups) of similar objects is a common programming task. * A text document is a collection of paragraphs. Each paragraph is a collection of words. Each word is a collection of characters. * The computer's file system is a collection of files. * A browser's bookmark list contains a collection of URLs. * etc... text/html 2010-03-08T04:06:18+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/fogbugz?rev=1268021178&do=diff FogBugz * Learn FogBugz short-cuts FogBugz has a number of different ways to do the same thing. Here is a short video describing what I've found to be the most efficient way for adding new cases to FogBugz. * Make rough estimates, later fill in subcases. When planning for a given cycle, it may be difficult to break down all of the work into cases that are 3 - 5 hours in length. That's okay. Create a more generic case with a given estimate. When you get closer to actually working on it,… text/html 2010-03-08T04:01:47+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/main?rev=1268020907&do=diff Senior design consists of a three quarter sequence in which students work in teams of 3 to 5 students to propose, implement, test, document, and deploy an engineering project. During this sequence, students will develop a project from inception to completion using sound engineering practices. Senior design is an opportunity for students to demonstrate mastery of their discipline as well as an opportunity for additional mentoring. text/html 2010-03-08T03:59:19+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/deliverables/presentation?rev=1268020759&do=diff The oral presentations required each quarter serve a number of purposes: * Inform other senior design teams of your project and the progress you are making * Provide an opportunity for you to distill the important components from your project and describe them in a clear and concise manner. * Prepare to present your project to the public. text/html 2010-03-08T02:46:24+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/course/scheduleconflicts?rev=1268016384&do=diff While senior design is scheduled to meet four hours per week, we only meet as a group a few times per quarter. In general. Scheduling conflicts with senior design may be allowed on a case-by-case basis, and should overlap senior design by no more than two hours per week. The following policies apply: