Changed lines 5-8 from:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they need to be about how people do activities together either when '''co-located''' (face-to-face) or '''distributed''' (over distance). You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, enhancing co-located group cooking, playing an outdoor location-based game with a group of friends, etc. There are LOTS of possibilities. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
to:
'''Theme:''' There is no specific theme this term. You should, in general, focus on technologies that allow for collaboration, communication (e.g., sending messages back and forth, talking with one another, etc.), or shared experiences in real time.
Changed lines 16-17 from:
'''Ethics:''' If you are conducting a study that involves people, normally we would need to get approval to run the study from the [[Office of Research Ethics at SFU | http://www.sfu.ca/vpresearch/ethics/]]. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
to:
'''Ethics:''' If you are conducting a study that involves people, normally we would need to get approval to run the study from the [[http://www.sfu.ca/vpresearch/ethics | Office of Research Ethics at SFU]]. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
Deleted line 26:
Changed lines 16-17 from:
'''Ethics:''' If you are conducting a study that involves people, normally we would need to get approval to run the study from the Office of Research Ethics at SFU. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
to:
'''Ethics:''' If you are conducting a study that involves people, normally we would need to get approval to run the study from the [[Office of Research Ethics at SFU | http://www.sfu.ca/vpresearch/ethics/]]. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
Deleted line 27:
Changed lines 24-25 from:
'''Submission deadline:''' Due in the final lecture of the term. Please submit your final papers in a Word document format to me, in addition to a PDF, both sent via email. I want to embed some comments within the Word doc that will help you revise the paper for submission to a conference venue.
to:
'''Submission instructions:''' Please submit your final papers in a Word document format to me, in addition to a PDF, both sent via email. I want to embed some comments within the Word doc that will help you revise the paper for submission to a conference venue. For deadlines, please see the course calendar.
Changed lines 18-19 from:
'''Length and Format:''' The final paper should be between 8 and 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. See [[Paper Format | this page]] for details on what sections to include in the final paper. For those who create systems for their projects, you can optionally submit a paper that is 4 pages long if you also submit an accompanying video demonstrating your system. The video should be between 2 and 4 minutes in length and adhere to [[http://cscw.acm.org/participation_video.html | these guidelines]].
to:
'''Length and Format:''' The final paper should be between 8 and 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. See [[Paper Format | this page]] for details on what sections to include in the final paper. For those who create systems for their projects, you can optionally submit a paper that is 4 pages long if you also submit an accompanying video demonstrating your system. The video should be between 2 and 4 minutes in length and adhere to [[http://cscw.acm.org/participation_video.html | these guidelines]].
I expect to see at least eight papers cited and discussed within a Related Work section of the paper. If you want to publish the work outside of the course, you'd likely need around twenty or more. So keep this in mind.
Changed lines 5-8 from:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they need to be about how people do things together either collocated''' (face-to-face) or '''distributed''' (over distance). You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, enhancing co-located cooking, playing an outdoor location-based game with a group of friends, etc. There are LOTS of possibilities. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
to:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they need to be about how people do things together either when '''co-located''' (face-to-face) or '''distributed''' (over distance). You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, enhancing co-located group cooking, playing an outdoor location-based game with a group of friends, etc. There are LOTS of possibilities. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
Added lines 5-8:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they need to be about how people do things together either '''collocated''' (face-to-face) or '''distributed''' (over distance). You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, enhancing co-located cooking, playing an outdoor location-based game with a group of friends, etc. There are LOTS of possibilities. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
Changed lines 14-17 from:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they need to be about how people do things together whether it be in person and face-to-face, or separated-by distance. You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, enhancing co-located cooking, playing an outdoor location-based game with a group of friends, etc. There are LOTS of possibilities. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
to:
Changed lines 12-13 from:
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, etc. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
to:
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, enhancing co-located cooking, playing an outdoor location-based game with a group of friends, etc. There are LOTS of possibilities. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
Changed lines 10-11 from:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they ned to be about how people do things together whether it be face-to-face and in person, or separated-by distance. You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
to:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they need to be about how people do things together whether it be in person and face-to-face, or separated-by distance. You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Changed lines 6-7 from:
# Study the use of existing mobile video chat systems by families: interview 8-10 people about how they use FaceTime as a part of their normal routines for video calling.
# Design a new system to better support family messaging (e.g., a futuristic text messaging service).
to:
# Study the use of existing mobile video chat systems by families for doing activities together over distance: interview 8-10 people about how they use FaceTime as a part of their normal routines for video calling.
# Design a new system to support the sharing of dinner over distance between remotely-located partners
Changed lines 10-11 from:
If you are conducting a study that involves people, normally we would need to get approval to run the study from the Office of Research Ethics at SFU. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
to:
'''Theme:''' All projects need to fit the theme of '''shared experiences'''. That is, they ned to be about how people do things together whether it be face-to-face and in person, or separated-by distance. You can study shared experiences that are already occurring or you can design a system or technology to support people's participation in shared experiences.
Shared experiences may include things such as sharing meals together over distance, watching television together over distance, attending a remote graduation, playing board games with a group of friends all in the same location, etc. The emphasis is on doing stuff together, whatever that stuff might be. This moves away from a lot of CSCW technologies that focus on communication, e.g., sending messages back and forth, talking with one another, etc.
'''Ethics:''' If you are conducting a study that involves people, normally we would need to get approval to run the study from the Office of Research Ethics at SFU. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
Changed lines 10-11 from:
If you are conducting a study that involves people, normally we would need to get approval to run the study from the Office of Research Ethics at SFU. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval.
to:
If you are conducting a study that involves people, normally we would need to get approval to run the study from the Office of Research Ethics at SFU. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval. That said, if you want to try and publish your work after the course, it is best to get external participants and go through the ethics process.
Changed lines 20-79 from:
!!!1. '''Study Project''':
If you did a study for your project, your final paper should include the following sections (and your presentation should similarly mirror them):
(:table border=1 cellpadding=0 cellspacing=0 width=100%:)
(:cellnr:)'''Introduction''': (~1 page in length)
Summarize the research space that you are looking at and illustrate why it is important. Describe the goal of the work. You can and should take the introduction from your Literature Review paper and rework it for this paper.
(:cellnr:)'''Related Work''': (~1 page in length)
Describe the related work in the area of your project. You need to include at least 8 papers as references.
(:cellnr:)'''Method''': (~1 page in length)
Describe the method you used as part of your project. Include: descriptions of participants, study stages and method details, sample questions, and analysis method.
(:cellnr:)'''Results''': (~3-5 pages in length)
Document the results of your project. Detail your main findings.
(:cellnr:)'''Discussion''': (~1 page in length)
Discuss your work. Include between a half-page and one page of thoughts about your work now that it is complete. Answer the question: "so what?" Now that your work is done, what does it mean? Why is it important? What is still left to be done? Discuss how your work generalizes to other demographics, settings, or design areas.
(:cellnr:)'''Conclusion:''' (~1/4 page in length)
Summarize your project and your overall findings.
(:cellnr:)'''Reference List:''' (~1/2 - 1 page in length)
Include a list of the papers you read for your related work. These should be cited in the document according to their number in the list. The list should be organized alphabetically by the last name of the first author on each paper. The format of the references should follow the samples in the ACM CHI Conference format document.
(:tableend:)
For projects that are systems, take a look at these short papers (that were submitted along with videos to a conference): [[http://carmster.com/clab/uploads/Main/LINCVideoExtendedAbstract.pdf | LINC Video]], [[http://carmster.com/clab/uploads/Main/LINCUbicompDemoAbstract.pdf | LINC Demo]], [[http://carmster.com/clab/uploads/Main/PeekABooAbstract.pdf | Peek-A-Boo Video]]. Notice how the systems are described using images, usage scenarios, etc and how the rationale is shown for the design. This is what I'd expect to see for your papers, but only in a longer format with even more detail. Note that these papers also don't really have a related work section, but yours should.
!!!2. '''Design Project''':
If you did a design for your project (e.g., you built a system), your final paper should include the following sections (and your presentation should similarly mirror them):
(:table border=1 cellpadding=0 cellspacing=0 width=100%:)
(:cellnr:)'''Introduction''': (~1 page in length)
Summarize the research space that you are looking at and illustrate why it is important. Describe the goal of the work. You can and should take the introduction from your Literature Review paper and rework it for this paper.
(:cellnr:)'''Related Work''': (~1 page in length)
Describe the related work in the area of your project. You need to include at least 8 papers as references.
(:cellnr:)'''Design Principles''': (~1/2 to 1 page in length)
Describe what principles your design is based on. What did you know you needed to include and why? (e.g., it needed to be flexible to use, it needed to support feature X). Use related literature to back up your principles as needed.
(:cellnr:)'''Design Evolution''': (~3-5 pages in length)
Document the design and its evolution. Use text and visuals. Explain why you designed it as you did (e.g., motivation, rationale). Show how the design started, what stages it evolved through, and what the final design looks like. Also describe how the design would be used by someone (e.g., provide a usage scenario: Sally walks up and touches the tablet to begin the application. She selects...)
(:cellnr:)'''Discussion''': (~1 page in length)
Discuss your work. Include between a half-page and one page of thoughts about your work now that it is complete. Critique the design: do you think it is good/bad? Does it match your original design principles? Answer the question: "so what?" Now that your work is done, what does it mean? Why is it important? What is still left to be done?
(:cellnr:)'''Conclusion:''' (~1/4 page in length)
Summarize your project and your overall findings.
(:cellnr:)'''Reference List:''' (~1/2 - 1 page in length)
Include a list of the papers you read for your related work. These should be cited in the document according to their number in the list. The list should be organized alphabetically by the last name of the first author on each paper. The format of the references should follow the samples in the ACM CHI Conference format document.
(:tableend:)
For projects that are studies, take a look at [[http://carmster.com/clab/uploads/Main/IntimacyCHI2012.pdf | this paper]]. Note the structure, style, and use of raw data (quotes) to illustrate the findings. The methodology of the study is also well documented. For the results, each section heading is one of the main themes that we found when doing our coding.
to:
Changed line 24 from:
(:cellnr:)'''Introduction''':
to:
(:cellnr:)'''Introduction''': (~1 page in length)
Changed line 27 from:
(:cellnr:)'''Related Work''':
to:
(:cellnr:)'''Related Work''': (~1 page in length)
Changed line 30 from:
to:
(:cellnr:)'''Method''': (~1 page in length)
Changed line 33 from:
to:
(:cellnr:)'''Results''': (~3-5 pages in length)
Changed line 36 from:
(:cellnr:)'''Discussion''':
to:
(:cellnr:)'''Discussion''': (~1 page in length)
Changed line 39 from:
(:cellnr:)'''Conclusion:'''
to:
(:cellnr:)'''Conclusion:''' (~1/4 page in length)
Changed line 42 from:
(:cellnr:)'''Reference List:'''
to:
(:cellnr:)'''Reference List:''' (~1/2 - 1 page in length)
Changed line 54 from:
(:cellnr:)'''Introduction''':
to:
(:cellnr:)'''Introduction''': (~1 page in length)
Changed line 60 from:
(:cellnr:)'''Design Principles''':
to:
(:cellnr:)'''Design Principles''': (~1/2 to 1 page in length)
Changed line 63 from:
(:cellnr:)'''Design Evolution''':
to:
(:cellnr:)'''Design Evolution''': (~3-5 pages in length)
Changed line 66 from:
(:cellnr:)'''Discussion''':
to:
(:cellnr:)'''Discussion''': (~1 page in length)
Changed line 69 from:
(:cellnr:)'''Conclusion:'''
to:
(:cellnr:)'''Conclusion:''' (~1/4 page in length)
Changed line 72 from:
(:cellnr:)'''Reference List:'''
to:
(:cellnr:)'''Reference List:''' (~1/2 - 1 page in length)
Deleted line 79:
Changed lines 28-29 from:
Describe the related work in the area of your project. You should take your literature review and condense it down to approximately one page in length.
to:
Describe the related work in the area of your project. You need to include at least 8 papers as references.
Changed lines 57-59 from:
(:cellnr:)'''Related Work''':
Describe the related work in the area of your project. You should take your literature review and condense it down to approximately one page in length.
to:
(:cellnr:)'''Related Work''': (~1 page in length)
Describe the related work in the area of your project. You need to include at least 8 papers as references.
Deleted line 80:
Added lines 12-17:
'''Length and Format:''' The final paper should be between 7 and 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. You will present the work to the class as part of a 20-25 minute presentation followed by questions.
'''Submission deadline:''' Due in the final lecture of the term. Please submit your final papers in a Word document format to me, in addition to a PDF, both sent via email. I want to embed some comments within the Word doc that will help you revise the paper for submission to a conference venue.
'''Evaluation:''' You will be evaluated on your ability to concisely document your project, method, and results. You will also be graded on your writing ability. Your presentation will be graded on your ability to present the project in an engaging and entertaining fashion. You will be critiqued on both the content of the presentation and your delivery.
Changed lines 79-84 from:
'''Length and Format:''' The final paper should be between 7 and 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. You will present the work to the class as part of a 20-25 minute presentation followed by questions.
'''Submission deadline:''' Due in the final lecture of the term. Please submit your final papers in a Word document format to me, in addition to a PDF, both sent via email. I want to embed some comments within the Word doc that will help you revise the paper for submission to a conference venue.
'''Evaluation:''' You will be evaluated on your ability to concisely document your project, method, and results. You will also be graded on your writing ability. Your presentation will be graded on your ability to present the project in an engaging and entertaining fashion. You will be critiqued on both the content of the presentation and your delivery.
to:
Changed lines 39-44 from:
For projects that are systems, take a look at these short papers (that were submitted along with videos to a conference). Notice how the systems are described using images, usage scenarios, etc and how the rationale is shown for the design. This is what I'd expect to see for your papers, but only in a longer format with even more detail. Note that these papers also don't really have a related work section, but yours should.
http://carmster.com/clab/uploads/Main/LINCVideoExtendedAbstract.pdf [[<<]]
http://carmster.com/clab/uploads/Main/LINCUbicompDemoAbstract.pdf [[<<]]
http://carmster.com/clab/uploads/Main/PeekABooAbstract.pdf [[<<]]
to:
For projects that are systems, take a look at these short papers (that were submitted along with videos to a conference): [[http://carmster.com/clab/uploads/Main/LINCVideoExtendedAbstract.pdf | LINC Video]], [[http://carmster.com/clab/uploads/Main/LINCUbicompDemoAbstract.pdf | LINC Demo]], [[http://carmster.com/clab/uploads/Main/PeekABooAbstract.pdf | Peek-A-Boo Video]]. Notice how the systems are described using images, usage scenarios, etc and how the rationale is shown for the design. This is what I'd expect to see for your papers, but only in a longer format with even more detail. Note that these papers also don't really have a related work section, but yours should.
Changed lines 69-72 from:
For projects that are studies, take a look at this paper.Note the structure, style, and use of raw data (quotes) to illustrate the findings. The methodology of the study is also well documented. For the results, each section heading is one of the main themes that we found when doing our coding.
http://carmster.com/clab/uploads/Main/IntimacyCHI2012.pdf
to:
For projects that are studies, take a look at [[http://carmster.com/clab/uploads/Main/IntimacyCHI2012.pdf | this paper]]. Note the structure, style, and use of raw data (quotes) to illustrate the findings. The methodology of the study is also well documented. For the results, each section heading is one of the main themes that we found when doing our coding.
Changed lines 12-13 from:
!!!1. '''Study Project''': If you did a study for your project, your final paper should include the following sections (and your presentation should similarly mirror them):
to:
!!!1. '''Study Project''':
If you did a study for your project, your final paper should include the following sections (and your presentation should similarly mirror them):
Changed lines 41-46 from:
http://carmster.com/clab/uploads/Main/LINCVideoExtendedAbstract.pdf
http://carmster.com/clab/uploads/Main/LINCUbicompDemoAbstract.pdf
http://carmster.com/clab/uploads/Main/PeekABooAbstract.pdf
!!!2.
to:
http://carmster.com/clab/uploads/Main/LINCVideoExtendedAbstract.pdf [[<<]]
http://carmster.com/clab/uploads/Main/LINCUbicompDemoAbstract.pdf [[<<]]
http://carmster.com/clab/uploads/Main/PeekABooAbstract.pdf [[<<]]
!!!2. '''Design Project''':
If you did a design for your project (e.g., you built a system), your final paper should include the following sections (and your presentation should similarly mirror them):
Changed lines 73-76 from:
to:
For projects that are studies, take a look at this paper. Note the structure, style, and use of raw data (quotes) to illustrate the findings. The methodology of the study is also well documented. For the results, each section heading is one of the main themes that we found when doing our coding.
http://carmster.com/clab/uploads/Main/IntimacyCHI2012.pdf
Changed lines 12-13 from:
1. '''Study Project''': If you did a study for your project, your final paper should include the following sections (and your presentation should similarly mirror them):
to:
!!!1. '''Study Project''': If you did a study for your project, your final paper should include the following sections (and your presentation should similarly mirror them):
Changed lines 36-39 from:
(:tableend:)
2.
to:
(:tableend:)
For projects that are systems, take a look at these short papers (that were submitted along with videos to a conference). Notice how the systems are described using images, usage scenarios, etc and how the rationale is shown for the design. This is what I'd expect to see for your papers, but only in a longer format with even more detail. Note that these papers also don't really have a related work section, but yours should.
http://carmster.com/clab/uploads/Main/LINCVideoExtendedAbstract.pdf
http://carmster.com/clab/uploads/Main/LINCUbicompDemoAbstract.pdf
http://carmster.com/clab/uploads/Main/PeekABooAbstract.pdf
!!!2. '''Design Project''': If you did a design for your project (e.g., you built a system), your final paper should include the following sections (and your presentation should similarly mirror them):
Changed lines 73-74 from:
'''Submission deadline:''' Due in the final lecture of the term. Email the document to Carman as a PDF file and also bring a printed copy to class.
to:
'''Submission deadline:''' Due in the final lecture of the term. Please submit your final papers in a Word document format to me, in addition to a PDF, both sent via email. I want to embed some comments within the Word doc that will help you revise the paper for submission to a conference venue.
Changed lines 51-52 from:
Document the design and its evolution. Use text and visuals. Show how the design started, what stages it evolved through, and what the final design looks like. Also describe how the design would be used by someone (e.g., provide a usage scenario: Sally walks up and touches the tablet to begin the application. She selects...)
to:
Document the design and its evolution. Use text and visuals. Explain why you designed it as you did (e.g., motivation, rationale). Show how the design started, what stages it evolved through, and what the final design looks like. Also describe how the design would be used by someone (e.g., provide a usage scenario: Sally walks up and touches the tablet to begin the application. She selects...)
Changed lines 12-13 from:
Your final paper should include the following sections (and your presentation should similarly mirror them) if you are writing about a '''study''':
to:
1. '''Study Project''': If you did a study for your project, your final paper should include the following sections (and your presentation should similarly mirror them):
Changed lines 22-23 from:
Describe the method you used as part of your project. If you conducted a study, include: descriptions of participants, study stages and method details, sample questions, and analysis method. If you created a design, include: descriptions of your design stages, methods for critique, and iteration.
to:
Describe the method you used as part of your project. Include: descriptions of participants, study stages and method details, sample questions, and analysis method.
Changed lines 25-26 from:
Document the results of your project. If you conducted a study, detail your main findings. If you created a design, document your final design through text and visuals.
to:
Document the results of your project. Detail your main findings.
Changed lines 38-40 from:
Your final paper should include the following sections (and your presentation should similarly mirror them) if you are writing about a '''design''' you have created:
to:
2. '''Design Project''': If you did a design for your project (e.g., you built a system), your final paper should include the following sections (and your presentation should similarly mirror them):
Changed lines 47-52 from:
(:cellnr:)'''Method''':
Describe the method you used as part of your project. If you conducted a study, include: descriptions of participants, study stages and method details, sample questions, and analysis method. If you created a design, include: descriptions of your design stages, methods for critique, and iteration.
(:cellnr:)'''Results''':
Document the results of your project. If you conducted a study, detail your main findings. If you created a design, document your final design through text and visuals.
to:
(:cellnr:)'''Design Principles''':
Describe what principles your design is based on. What did you know you needed to include and why? (e.g., it needed to be flexible to use, it needed to support feature X). Use related literature to back up your principles as needed.
(:cellnr:)'''Design Evolution''':
Document the design and its evolution. Use text and visuals. Show how the design started, what stages it evolved through, and what the final design looks like. Also describe how the design would be used by someone (e.g., provide a usage scenario: Sally walks up and touches the tablet to begin the application. She selects...)
Changed lines 54-55 from:
Discuss your work. Include between a half-page and one page of thoughts about your work now that it is complete. Answer the question: "so what?" Now that your work is done, what does it mean? Why is it important? What is still left to be done? Discuss how your work generalizes to other demographics, settings, or design areas.
to:
Discuss your work. Include between a half-page and one page of thoughts about your work now that it is complete. Critique the design: do you think it is good/bad? Does it match your original design principles? Answer the question: "so what?" Now that your work is done, what does it mean? Why is it important? What is still left to be done?
Changed lines 62-63 from:
'''Length and Format:''' The final paper should be 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. You will present the work to the class as part of a 20-25 minute presentation followed by questions.
to:
'''Length and Format:''' The final paper should be between 7 and 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. You will present the work to the class as part of a 20-25 minute presentation followed by questions.
Changed lines 12-13 from:
Your final paper should include the following sections (and your presentation should similarly mirror them):
to:
Your final paper should include the following sections (and your presentation should similarly mirror them) if you are writing about a '''study''':
Added lines 38-62:
Your final paper should include the following sections (and your presentation should similarly mirror them) if you are writing about a '''design''' you have created:
(:table border=1 cellpadding=0 cellspacing=0 width=100%:)
(:cellnr:)'''Introduction''':
Summarize the research space that you are looking at and illustrate why it is important. Describe the goal of the work. You can and should take the introduction from your Literature Review paper and rework it for this paper.
(:cellnr:)'''Related Work''':
Describe the related work in the area of your project. You should take your literature review and condense it down to approximately one page in length.
(:cellnr:)'''Method''':
Describe the method you used as part of your project. If you conducted a study, include: descriptions of participants, study stages and method details, sample questions, and analysis method. If you created a design, include: descriptions of your design stages, methods for critique, and iteration.
(:cellnr:)'''Results''':
Document the results of your project. If you conducted a study, detail your main findings. If you created a design, document your final design through text and visuals.
(:cellnr:)'''Discussion''':
Discuss your work. Include between a half-page and one page of thoughts about your work now that it is complete. Answer the question: "so what?" Now that your work is done, what does it mean? Why is it important? What is still left to be done? Discuss how your work generalizes to other demographics, settings, or design areas.
(:cellnr:)'''Conclusion:'''
Summarize your project and your overall findings.
(:cellnr:)'''Reference List:'''
Include a list of the papers you read for your related work. These should be cited in the document according to their number in the list. The list should be organized alphabetically by the last name of the first author on each paper. The format of the references should follow the samples in the ACM CHI Conference format document.
Changed lines 10-11 from:
Your final paper should include the following sections:
to:
If you are conducting a study that involves people, normally we would need to get approval to run the study from the Office of Research Ethics at SFU. However, as part of a course, you can conduct a study with people you know (e.g., family, friends) without having to get ethics approval.
Your final paper should include the following sections (and your presentation should similarly mirror them):
Changed line 18 from:
(:cellar:)'''Related Work''':
to:
(:cellnr:)'''Related Work''':
Changed lines 8-9 from:
to:
Changed lines 16-27 from:
to:
(:cellar:)'''Related Work''':
Describe the related work in the area of your project. You should take your literature review and condense it down to approximately one page in length.
(:cellnr:)'''Method''':
Describe the method you used as part of your project. If you conducted a study, include: descriptions of participants, study stages and method details, sample questions, and analysis method. If you created a design, include: descriptions of your design stages, methods for critique, and iteration.
(:cellnr:)'''Results''':
Document the results of your project. If you conducted a study, detail your main findings. If you created a design, document your final design through text and visuals.
(:cellnr:)'''Discussion''':
Discuss your work. Include between a half-page and one page of thoughts about your work now that it is complete. Answer the question: "so what?" Now that your work is done, what does it mean? Why is it important? What is still left to be done? Discuss how your work generalizes to other demographics, settings, or design areas.
Changed lines 24-25 from:
'''Length and Format:''' The final paper should be 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. You will present the work to the class as part of 20-25 minute presentation followed by questions.
to:
'''Length and Format:''' The final paper should be 10 pages long in [[http://chi2012.acm.org/chi2012archivalformat_final.doc | ACM CHI Conference format]]. You will present the work to the class as part of a 20-25 minute presentation followed by questions.
Changed lines 28-30 from:
'''Evaluation:''' You will be evaluated on your ability to concisely document your project, method, and results. You will also be graded on your writing ability.
'''Submission deadline:'''
to:
'''Evaluation:''' You will be evaluated on your ability to concisely document your project, method, and results. You will also be graded on your writing ability. Your presentation will be graded on your ability to present the project in an engaging and entertaining fashion. You will be critiqued on both the content of the presentation and your delivery.
