PROBLEM TWO

(Due: Mar 20-22)

 

GENERAL ITEMS

 

For team project - I must have an individual grade component as well as a team product component

 

INDIVIDUAL

Keep a design journal of your activities. The journal will document

(1)   cogent issues encountered as you progress through each component of the team project

(2)   specific instances of what you have learned

(3)   elements of enthusiasm or distaste for working on a team and in turn how it could be improved. I will evaluate the journal qualitatively looking for these elements to be preeminent. The design journal will be your own guide to working through the project and will provide you with notes, rationale, issues, and process to be used as one basis for groupwork.

 

TEAM

(4)   how well the final product and presentation go – this means the extent to which the idea has been explored with real world users and elaboration of the constraints of a selected information domain as well as how a team shows integration of work effort as evident during final presentation, and is also very dependent upon the substance of the task analysis and concept demonstration (eg. how much multimedia and information  scitech was used. I value creativity so jump outside the blackbox.

(5)   Your project presentation will be 20 mins per group = 3 groups per class

 

 

 

SPECIFIC ITEMS

 

Purpose

 

To provide you and your team members with some guidance on the project and to give further information on what to expect I will be looking for in evaluating the project.

 

What does the project consist of?

 

The project has 2 components: 1) an individual element 2) and a team element. Please refer to the syllabus, which already outlines the responsibilities for individuals and teams. The project is heavily grounded in problem finding - problem representation and analysis, and implementing problem solving solutions. The intent is not just to find a problem but to understand the constraint space of a problem, create useful information science / information technology solutions, and then insure the solutions have a high degree of usability. Please refer to the 3 U's, understanding, usefulness and usability, which will be further discussed in class. In this project the team must consider the 3U's as well in order to implement a viable concept demonstration. You will be assessed in terms of how well you illustrate each of these areas in your individual journal and how well the team addresses these problems in the presentation.

 

 

How do I get our team's project started?

 

After you are assigned to a team, you must begin the team process by deciding on a problem that is feasible, doable in terms of the time you have, and amenable in terms of allowing information systems as a solution point. You might start your team off by discussing ideas that members have about problems that could be addressed with the use of some of the areas of technology presented in the readings or discussed in class. If you can't immediately propose a problem domain that other members agree with then you may need to do some exploration. I may also mention possibilities in class of project domains that would be interesting to pursue (e.g., I have mentioned the idea of how would go about providing a computer-supported distance learning implementation for the Jasper problem solving video. I want your problem domains to be as real as practical and for you to actually deal with real world context and users. This may mean that you are close to a problem area (personal experience) and thus can use experience to understand it; or alternative the problem domain may be one that others in your group share (e.g., problems associated with college life - registration, libraries, dorm-life, Hub experiences). Alternatively, I would encourage you to do some interviews of experts in a given area and discover some of their problems and select one for experimentation. Remember the goal is not to jump into an immediate solution and program up a concept demonstation - that almost always results in failure/error associated with not addressing the 3 U's. Some interview, do a work analysis, create concept maps and storyboards, before locking on to a quick solution. I will look for these kind of things as a basis for seeing the design rationale for your solution. If you are hung up finding a problem I could refer you to some sources from small business projects to give you seed thoughts to help as well. But there are a variety of areas to think about: medicine, business, military, educational, criminal, and so on. BE CREATIVE! You might want to think about a given expert and their problems, e.g., fire fighters, fighter pilots, dentists, radio announcers, audiologists, race car drivers, ship captains, pre-school teachers, stock brokers, and so on to begin thinking about new areas of application of information systems to problems experienced. These are just ideas to get you jump started.

 

 

How does the grading break itself down?

 

Grading (20 pts)

Team Participation

5 points

Team Presentation

10 points (including of quality of analysis conducted)

Design Journal

5 points

Total

20 points

 

 

The grade for the group will be based on the following:

 

 

What will be the critical links for team's success?

 

 

***Warning ! Procrastination can be hazardous to your grade.