Timetable

Final Deliverables

Possible Projects

1. A rework of the Loyola records/administration website around a task related breakdown.
2. A recipe management program for cooks. It will allow the user to create a recipe entry with the ingredients and their measurments as well as the steps in cooking. The user can rate the recipe and add informational notes to each. The recipes will also be able to handle conversion to metric units and to scale the recipe for differing amounts of servings. The user can search for a recipe by meal type, ingredient, by number of servings, by occasion, by rating and by keyword. The recipe program can integrate with a calendaring system wherein the cook can plan a day, week or month's meals. From the meal plan, the recipe management program can generate a shopping list.
3. A software program that allows students to sell used textbooks to one another. It would work for both graduate and undergraduate courses. Students could enter information on books they want to sell into the computer along with a price as well as search the site for textbooks that they need. They could search by department, course name, number, or alphabetically for courses and books. They could compare prices as well as the seller's description of the books, and if interested contact the student. If a sale is made, the book would be removed from the site.
4. A cell phone interface the allows the user to order take-out at their favorite restaurants, such as Chili's, Appleby's, or Outback. The interface needs to be able to query for a local restaurant. The user then selects the restaurant and requests a menu. From the menu, the user can request descriptions or the items or order the items. The system needs to be able to store the user's zip code and credit card information. Security is required to protect the user's information.
5. A file categorization program. The program could allow the user to create categories and put the files into those categories. A given file could be in multiple categories at once, and the pogram would allow a user to perform opertions such as unioning on the categories. For instance, a user could make a category "Christmas Pictures" and a category called "Dog Pictures" then perform an operation to get the intersection of those categories (which hopefully results in all the pictures of the dog at Christmas).
6. Time tracking program - The functionality of this kind of took is pretty straight forward and doesn't vary much, but the interfaces are usually cumbersome at best. Design a tool that could, through a well-suited interface, make it very easy for an employee (in a consulting environment) to track time worked for a particular client, tast, or project.
7. A tool that allows businesses to convert various knowledge sources into RSS feeds. RSS feeds increase the efficiency of performing duties. Provide a simple UI with which managers or tech leads could construct RSS feeds from exisiting repositories of project knowledge. Supported source formats could include SQL databases, XML document libraries and web services, CVS and SVN repositories, newsgroups and listservs. Each type would need a specific UI, although all types would have common attributes.
8. Evaluate the current Microsoft Visual Studio and consider improvements.
9. Design a new product that combines the following items into one item:
   • AM-FM radio
   • Cassette player
   • CD player
   • Alarm clock (the alarm can make an alarm melody or turn on a radio, cassette, or CD)
   The interface should provide the basic and normal functions of each component of the product. (For example, play, rewind, fast forward, stop and record would be some basic functions for the cassette player.)
10. Design the facility control panel for a teaching theater. The purpose is to make it easy to use even for novice users. The control panel is used by the instructor to control and monitor the status of the following facilities:
    • There is one instructor computer screen, a keyboard, and a mouse. There are also 20 student computer screens, keyboards, and mice (numbered from 1 to 20, and each computer also has a 6-alphanumeric-character name). Finally, there is one projector which projects the computer display to a large whiteboard. The instructor should have full control of them, including but not limited to:
      • Sending the content on the instructor's screen to all the students' screens and/or the projector.
      • Taking a student's screen content (by specifying the number or the name) and sending it to all the other students' screens and/or the instructor's screen, and/or the projector.
      • Taking a student's keyboard and/or mouse (by specifying the number or the name), which means the keyboard input and/or the mouse input to the student's will be from the instructor's keyboard and/or mouse.
      • Releasing all control so each student has full control of his screen, keyboard, and mouse.
    • The instructor should also be able to control the intensity of the lights in the room. There should be nine lighting levels, ranging from high to low.
11. "The aim of palliative care is to alleviate as many of the patient's symptoms as possible, and in that way, provide the best quality of life for patients and their families. To achieve this goal, the doctor must have precise knowledge about the patient's conditions and needs. If a symptom is not mentioned to the doctor, it is unlikely to be treated. Therefore, good symptom assessment is one of the most important components of delivering effective care to palliative patients." (Hallgren, 2002).
    
    There are two typical ways doctors currently receive information about their patients. Usually, the doctor will learn about the symptoms when speaking to the patient, relatives or other caregivers. The second way to measure symptoms is to use an established symptom questionnaire. Develop a novel third way: a computer interface that will allow the patient to submit his or her symptoms directly to the doctor.
    
    Interface Requirements
    As a part of the interface, there is a minimum amount of information collected from the patient. The information includes:
    Patient Information
    • Patient's Name
    • Patient's Date of Birth
    • Name of Patient's doctor
    • The person using the interface (The only valid input for this question should be 'Patient' or 'Caregiver')
    Symptom Assessment
    The patient must answer the following three questions on a scale of zero to ten
    • Wellbeing (0 = 'Best Feeling of Wellbeing', 10 = 'Worst Feeling of Wellbeing')
    • Tired (0 ='Not Tired', 10='Worst Possible Tiredness')
    • Pain (0='No Pain', 10='Worst Possible Pain')
    Pain Assessment
    Since many palliative patients have major problems with pain, specific pain assessment questions could be useful. Allow the user to specify exactly where he or she is feeling pain. At the very least, pain should be able to be specified in the following places:
    
    • Shoulders, Left Arm, Right Arm, Chest, Stomach, Right Leg, Left Leg, Back
    Gather the following information about the pain:
    • The time of the day the pain hurts (Morning/Afternoon/Night/All day)
    • Does movement influence pain? (Yes / No)