![[Return to the WPI Homepage]](index_files/seal.gif)
![[Return to the CS Homepage]](index_files/new_cs.gif)
First of all, read the MQP Guidelines that I have written for my projects. This will help ease the stress of getting started and producing high-quality results.
you should get the MQP report template.
Every one of my MQP teams should use this template. The blue text
provides information about what you should put in the different
sections. You will remove that text and replace it with your content.
All team members will usually receive the same grade. If a team member is not pulling his or her weight, it reflects badly on everyone. If this situation cannot be worked out among yourselves, be sure to discuss it with me.
Upon completion of the project, students will receive an overall project grade. It is important to note that this grade reflects not only the final products of the project (results, report, etc), but also the process by which they were attained. No amount of last-minute effort will turn a mediocre project effort into an A.
Final grades will be assigned as follows:
A: denotes consistently excellent effort that attains the project
goals.
B: denotes consistently good effort that attains the project goals.
C: denotes acceptable effort that partially attains the project goals.
Each term a student is registered for a project, a grade will be given to the student reflecting a judgement of accomplishments for that term. The same guidelines given above will be used to assign a grade for progress during the term. Term grades are independent of each other and an indication, but not an absolute determinant of the final grade. In addition, the grade SP may be given for a term grade when acceptable effort has been done to earn credit, but the quality of the work cannot be judged. The grade NAC will be given for unacceptable effort and the grade NR for situations where credit cannot be given, but a grade should not be placed on the student's transcript.
A word of caution: Do not get overly concerned about the ``grade'' you receive for the project as much as doing the project work to the best of your ability. Rather than concentrate on the grade, think about the impression your work on the project will leave with me and others as you will be seeking recommendations for future employment and school. It is not only important what you do, but how you do it.
My view as to what constitutes and A, B, or C project follows:
An 'A' project is one that consistently shows excellent effort, organization, and results. Such a project must exhibit individual learning and the ability of the project members to find, understand, and apply knowledge from several sources. A project that receives an A will exceed the project goals. I expect a project in this category to produce material that can be used for publication. This does not mean that it must be published, but that it could be published in a journal, magazine, or other publication. An A project will also have solid empirical results to back up its results.
A 'B' project is one that meets all of the project goals and exhibits a consistent good effort by the team members towards attaining the goals. A project in this category will have demonstrated the ability to apply knowledge they have learned in their courses and should have some application of knowledge that they learned outside of course work while completing the project. A B project will have some supporting data to show that the work was evaluated and that it meets the project goals.
A 'C' project is one that completes most of the project goals and produces an acceptable report. Students who receive a grade of C are expected to show that they have been able to apply knowledge learned in their course work. A project in this category will have some data to support the results, even if this data is anecdotal.
Kerri Edlund and Sarah Pickett are building an Eclipse plug-in, based upon the Eclipse Communication framework. This plug-in will allow distributed teams to hold on-line meetings, store the transcripts of their meetings in a SourceForge project, and create SourceForge tasks based upon the meeting transcript. This work will end up in the Webfoot project.
Brandon Greenwood and Mike Hlasyszyn are creating an Eclipse plug-in that will interface with SourceForge to make task management transparent between SourceForge and Eclipse. The goal is to be able to create, edit, and view tasks from SourceForge or Eclipse and to keep the two synchronized. This will be part of the Webfoot project.
This is another MQP that will contribute to the Webfoot project. Jonathan Bolt and Chris Fontana are working on this project. This effort will define artifacts in SourceForge to represent user stories. They will then create the appropriate Eclipse plug-in to interact with the user stories and keep SourceForge and Eclipse synchronized.
EMC SIMM API Phase II
Josh Anderson and Chris Cooper are working on this project, sponsored by EMC Corporation. This is a continuation of the EMC On-the-Fly Configuration project completed by Andrew Ralich in the B05 term.
Alex White is taking his love of running and building a system that will allow runners to log their mileage and other training information and then predict the runner's times at various distances. The project investigates different prediction models and analyzes several data sets to determine the most effective predictors.
Three students, Mike Anastasia, Jeremiah Chaplin, and Micah Gaulin-McKensie are working on a DSL for war gaming. The goal is to be able to represent appropriate game concepts and produce some or all of a war game's code.
Ben Mohlenhoff and Damon Bussey are developing a plug-in to work with the Eclipse-based Object Bench. The plug-in will capture the user interactions with the object-bench and generate JUnit test cases.
Jim Schementi and Andrew Sutman are developing a domain-specific language and framework for game developers. The language and framework will allow a developer to build games that have 2-dimensional playing spaces by using familiar terminology and reusable components.
Craig Andrews, Mike Itz, Matthew Meyer, Alex White
This project is exploring the use of a spoken language as a possible interface to computer systems. The language under consideration is the logban language. This project is co-advised with Prof. Dan Dougherty.
Jason McInnes.
Jason is implementing a tool for software developers who are creating active web pages to easily construct them through a domain-specific visual language.
Justin Braga and Liam Morley
This project is an Eclipse plug-in that implements an object bench that lets Java programmers interact with Java objects without needing a complete program. It lets you write a class and, when it has compiled successfully, create one or more instances of that class, call methods, and inspect the state of the objects, all within the Eclipse environment.
Alex Lash, Seth Voltz
This project is an implementation of a personal media system built entirely from open source components.
Jarrod Bellmore and Evgeny Rahman
This project is defining a process for analyzing and developing domain-specific languages. The process is designed as an extension to the Rational Unified Process®, RUP®.
Chuck Haines and Scott Battocchi
This project is a collaboration between a CS student and an ECE student to design and implement LED lighting that can be programmatically controlled.
Justin Crafford and Peter Gordon
This project is being done in collaboration with Ken Arnold on extending capabilities he initially put into his Napkin Look-and-feel open source project on SourceForge.
This team helped Friendly House, a Worcester social services organization, select a software package that would meet their needs and their sponsors' needs for the current period and future.
Jimmy Schementi worked alone on this IQP, setting up the hardware and system software that would enable Friendly house to begin using the software package selected by the first team.
Modified: 25-Aug-2011
Gary
Pollice