<![CDATA[Incorporating Communication Outcomes into the Computer Science Curriculum]]>

Abstract

This assignment allows presenters the opportunity to orally summarize the state of their team's project at the time of the presentation and the report should give the audience a low-level and technical look at the details of the team's design and implementation. Student team is required to give a copy of their team’s documentation to another team for review. Team will critique another team's project documentation/presentation. During the question and answer period of the formal oral presentation, each member of the critiquing team is expected to ask a probing question of the team that just presented their project.

Genre

Formal presentation/formal documentation; informal speaking (Q/A)

Assignment Duration

One Week

Communication Skill

reading, writing, speaking, teaming, listening

Technical Skill

Product Demonstration, Requirements, Design Expression, presentation of Implementation details, Continuous Quality Assurance (Testing)

Workplace Scenario

Managers will often review design and code of development team or individual. If team is using an iterative or agile process, this inspection will most likely focus on the details of the requirements, design, implementation & testing of the most recent iteration. For example, developers may be asked to demonstrate a crucial component of their system that is interesting or complex in terms of algorithms and/or code segments.

Team Size

4-6

Title

Course