http://wiki.msoe.us/ 2012-02-06T07:19:02+00:00 http://wiki.msoe.us/ http://wiki.msoe.us/lib/images/favicon.ico text/html 2011-04-29T16:52:17+00:00 Chris Taylor http://wiki.msoe.us/cs2852/bst?rev=1304095937&do=diff You should start by reading about binary search before reading this page. It assumes you understand that page. Briefly, we applied binary search by recursively partitioning a sorted array into two pieces, doing one comparison, and then eliminating one (or both, if we found what we were looking for) partition. text/html 2011-04-29T04:52:18+00:00 Chris Taylor http://wiki.msoe.us/cs2852/binarysearch?rev=1304052738&do=diff Suppose we wish to know whether or not a particular value is stored in an array of integers. Consider the following array: [Sorted Array with Seven Elements] * With just seven elements is very easy to just scan the array looking for a match on a particular value. * This is the standard brute-force approach which would require, at most, seven comparisons * The brute-force search is an algorithm, where is the size of the array, since we must visit each element in the array. * If doin… text/html 2011-03-30T04:04:28+00:00 Chris Taylor http://wiki.msoe.us/cs2852/linkedlist?rev=1301457868&do=diff A LinkedList is a data structure that organizes the data contained within it by making each location, called a node, responsible for holding references to its immediate neighbors in the list (along with the actual data we wish to store in the list). It's a fascinating data structure, but before we get too far, it's time for a quiz. text/html 2010-09-09T15:33:45+00:00 Chris Taylor http://wiki.msoe.us/cs2852/jcf?rev=1284046425&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-05-11T12:27:32+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/fogbugz?rev=1273580852&do=diff FogBugz and Kiln are tools that serve to facilitate project management and communication within your senior design team. In addition, your senior design advisor will monitor Kiln commit logs and a number of features within FogBugz to help provide useful feedback to the team and to help assess the contributions of each team member. text/html 2010-05-11T10:02:24+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/dates?rev=1273572144&do=diff Typically senior design students do not meet during the regularly scheduled senior design meeting times. Instead, each team meets individually with their advisor at a time that works well for the advisor and team. Joint Meetings We will meet with all senior design teams in S-341 as follows: text/html 2010-05-11T09:54:27+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/spring?rev=1273571667&do=diff The spring quarter of senior design is where everything comes together. The team must write test plans, perform integration testing, polish documentation, and prepare for deployment. The spring quarter is composed of multiple milestones. The detailed plan for the spring quarter should be developed as part of the cycle II report in the winter quarter. This plan should consist of one milestone for each phase and multiple cases associated with each milestone. A broad overview of the spring qua… text/html 2010-05-11T09:52:18+00:00 Chris Taylor http://wiki.msoe.us/seniordesign/delverables/showabstract?rev=1273571538&do=diff All teams will need to prepare a short description of their project for inclusion in the Student Projects Show booklet. For reference, take a look at this page for a summary of the student projects show. That page also includes a link to a previous year's booklet. Use entries in the booklet as a guide for generating your team's description.