<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://wiki.msoe.us/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://wiki.msoe.us/feed.php">
        <title>TaylorWiki</title>
        <description></description>
        <link>http://wiki.msoe.us/</link>
        <image rdf:resource="http://wiki.msoe.us/lib/images/favicon.ico" />
       <dc:date>2010-08-01T05:38:53+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/fogbugz?rev=1273580852&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/dates?rev=1273572144&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/spring?rev=1273571667&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/delverables/showabstract?rev=1273571538&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/deliverables/poster?rev=1273570771&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/winter?rev=1273568773&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/proposal?rev=1273566955&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/deliverables/cyclereports?rev=1273566927&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.msoe.us/seniordesign/deliverables/finalreport?rev=1273508804&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://wiki.msoe.us/lib/images/favicon.ico">
        <title>TaylorWiki</title>
        <link>http://wiki.msoe.us/</link>
        <url>http://wiki.msoe.us/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://wiki.msoe.us/seniordesign/fogbugz?rev=1273580852&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T12:27:32+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:fogbugz</title>
        <link>http://wiki.msoe.us/seniordesign/fogbugz?rev=1273580852&amp;do=diff</link>
        <description>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.</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/dates?rev=1273572144&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T10:02:24+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:dates</title>
        <link>http://wiki.msoe.us/seniordesign/dates?rev=1273572144&amp;do=diff</link>
        <description>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:</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/spring?rev=1273571667&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T09:54:27+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:spring</title>
        <link>http://wiki.msoe.us/seniordesign/spring?rev=1273571667&amp;do=diff</link>
        <description>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…</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/delverables/showabstract?rev=1273571538&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T09:52:18+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:delverables:showabstract - created</title>
        <link>http://wiki.msoe.us/seniordesign/delverables/showabstract?rev=1273571538&amp;do=diff</link>
        <description>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.</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/deliverables/poster?rev=1273570771&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T09:39:31+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:deliverables:poster - created</title>
        <link>http://wiki.msoe.us/seniordesign/deliverables/poster?rev=1273570771&amp;do=diff</link>
        <description>Senior Design Show Poster


The preparation of a poster describing your senior design project is one of the requirements in the spring quarter of senior design. Samples of past CE and SE senior design posters are displayed on the 3rd floor of the library building. Samples of past EE senior design posters are displayed on the 3rd floor of the Science Building.  Your poster may be placed on display in the library building after you graduate.</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/winter?rev=1273568773&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T09:06:13+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:winter</title>
        <link>http://wiki.msoe.us/seniordesign/winter?rev=1273568773&amp;do=diff</link>
        <description>The winter quarter of senior design is where teams must implement and unit test the various components of their project.  The winter quarter will be composed of multiple milestones.  The detailed plan for the winter quarter should be developed as part of the cycle I report in the fall quarter.  This plan should consist of one milestone for each phase and multiple cases associated with each milestone.  A broad overview of the winter quarter is shown graphically below:</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/proposal?rev=1273566955&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T08:35:55+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:proposal</title>
        <link>http://wiki.msoe.us/seniordesign/proposal?rev=1273566955&amp;do=diff</link>
        <description>Project Proposal

Proposal Content

Team Composition


The preferred team size is four members. Teams of three or five are allowed with instructor permission only.

The proposal should include the names and majors of team members.

Project Alternatives


Each team must submit at least two project ideas (one primary and at least one backup).
For each possible project, the following information should be included:</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/deliverables/cyclereports?rev=1273566927&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-11T08:35:27+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:deliverables:cyclereports</title>
        <link>http://wiki.msoe.us/seniordesign/deliverables/cyclereports?rev=1273566927&amp;do=diff</link>
        <description>The goal of the cycle report is to provide a reflective assessment of the project over the last cycle (generally the last quarter). While similar to the weekly status reports, it should be more thoughtful and take into account the cycle's accomplishments with respect to the “big picture.” This is also an opportunity to revisit your Development Plan and make revisions as necessary.</description>
    </item>
    <item rdf:about="http://wiki.msoe.us/seniordesign/deliverables/finalreport?rev=1273508804&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-05-10T16:26:44+00:00</dc:date>
        <dc:creator>Chris Taylor</dc:creator>
        <title>seniordesign:deliverables:finalreport - created</title>
        <link>http://wiki.msoe.us/seniordesign/deliverables/finalreport?rev=1273508804&amp;do=diff</link>
        <description>A separate repository should be created to house all of the final project deliverables.  The final report should summarize many of these and include references when appropriate.  The repository should be organized and easy to navigate.  The final report itself should contain:</description>
    </item>
</rdf:RDF>
