http://cs-comm.lib.muohio.edu/items/browse/tag/Code+Review?output=atom <![CDATA[Incorporating Communication Outcomes into the Computer Science Curriculum]]> The dissemination of the project's research will come with the creation of a repository that allows CSE faculty members to access a web-based set of assignments. The goal of these assignments is to aid CSE faculty in redesigning their assignments, courses, and curricula in order to incorporate and enhance their students abilities to communicate and collaborate with a wide variety of audiences. The repository will be populated with assignments written and designed by both CSE and CAC faculty with the premise of integrating communication abilities while also enhancing the learning of the technical content being taught in their course and/or curriculum.

]]> 2020-05-18T19:20:54-04:00 Omeka http://cs-comm.lib.muohio.edu/items/show/107 <![CDATA[Project Review]]>

2012-07-26T12:01:37-04:00

Title

Project Review

Course

Capstone

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.

Author

Margaret Heil

Source

NA

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
]]>