<![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-18T18:55:27-04:00 Omeka http://cs-comm.lib.muohio.edu/items/show/79 <![CDATA[Memo to Project Client]]>

This can be used with projects other than the capstone.]]>

2012-07-26T11:58:09-04:00

Title

Memo to Project Client

Course

Capstone

Abstract

In this project, a team of students writes an e-mail memo to request a meeting with the client for their project.

This can be used with projects other than the capstone.

Author

Janet Burge

Genre

memo, e-mail

Assignment Duration

One Week

Communication Skill

reading, writing, teaming

Technical Skill

project summarization

Workplace Scenario

On your team project, you will be working with a client. Your first contact with the client will be through an e-mail memo introducing yourself and requesting an initial meeting with them and/or their project team to talk about the project. This e-mail should give the client all the information they need to schedule and prepare for the meeting.

Team Size

4-6

]]> http://cs-comm.lib.muohio.edu/items/show/78 <![CDATA[Physical Architecture and Deployment Diagrams]]>

2012-07-25T15:39:14-04:00

Title

Physical Architecture and Deployment Diagrams

Course

Software Engineering

Abstract

Sketch a deployment diagram describing the implementation of a system.

Author

Douglas Troy

Genre

Design diagram

Assignment Duration

Less than a week

Communication Skill

Writing

Technical Skill

Implementation

Workplace Scenario

An architecture is the set of significant decisions about the organization of a software system (section 13.4). The physical architecture is the assignment of concrete software components, such as programs, databases, webservers, and communication paths to machines like servers and desktop workstations (Chap 38). The physical architecture is the realization of the logical architecture. The purpose of this homework is to introduce deployment diagrams as a useful way to communicate the physical or deployment architecture.

For this assignment your supervisor will review a sketch of the layered architecture and deployment diagram for your team’s project.

Team Size

N/A

]]> http://cs-comm.lib.muohio.edu/items/show/77 <![CDATA[Logical Architecture and Layer Pattern Memo]]>

2012-07-25T22:08:56-04:00

Title

Logical Architecture and Layer Pattern Memo

Course

Software Engineering

Abstract

Describe logical architecture and the layers pattern.

Author

Douglas Troy

Source

Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.

Genre

Memo

Assignment Duration

Less than a week

Communication Skill

Reading
Writing

Technical Skill

Design

Workplace Scenario

An architecture is the set of significant decisions about the organization of a software system (section 13.4). The logical architecture is the large-scale organization of the software classes into packages, subsystems, and layers (section 13.2). A layer is a grouping of classes, packages or subsystems that has cohesive responsibility for a major aspect of the system. Also, layers are organized such that higher layers call upon services of lower layers. If you have taken the networking course or the operating systems course, you have seen examples of layered architectures such as the layers of the TCP/IP protocol stack, or the concept of operating system layers. The purpose of this homework is to introduce the general approach to software architecture design and to explore examples of the layer pattern. These concepts will help you in future projects where you need to create the overall design (architecture) of software systems.

In this memo to your supervisor you will summarize the three-layer pattern and recommend how the architecture for our project could be modified to add a feature that tracks the user’s progress through your project.

Team Size

N/A

]]> http://cs-comm.lib.muohio.edu/items/show/76 <![CDATA[Current Events]]>

This assignment requires student preparation outside the classroom as well as participation within the classroom. This assignment is most effective when used as a regularly scheduled event (for example, in the first class of the week, every week during the semester). ]]>

2012-07-25T14:47:00-04:00

Title

Current Events

Course

CS1

Abstract

Prior to class, students will find at least one current news article that relates to computer science. They will be expected to have read the article and be able to summarize the contents verbally. The article can be from any popular press or academic venue.

This assignment requires student preparation outside the classroom as well as participation within the classroom. This assignment is most effective when used as a regularly scheduled event (for example, in the first class of the week, every week during the semester).

Author

Eric Luczaj

Genre

informal verbal report, listening to presentations

Assignment Duration

Short Activity

Communication Skill

reading, listening, speaking

Technical Skill

varies

Workplace Scenario

Computer science connects to and integrates with other disciplines to solve problems. As professionals in our discipline we want to be able to intelligently discuss these concepts with others and to refine our understanding. In order to maximize the use of our time we need to improve their ability to read with purpose and to understand and summarize new material as well as to disseminate knowledge verbally to a group of our peers.

Team Size

N/A

Additional Information

Could be used in any course.

]]> http://cs-comm.lib.muohio.edu/items/show/75 <![CDATA[GRASP Patterns and Principles Memo II]]>

2012-07-25T22:07:38-04:00

Title

GRASP Patterns and Principles Memo II

Course

Software Engineering

Abstract

Describe seveal design patterns.

Author

Douglas Troy

Source

Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.

Genre

Memo

Assignment Duration

Less than a week

Communication Skill

Reading
Writing

Technical Skill

Design

Workplace Scenario

The purpose of this assignment is to introduce four additional GRASP patterns: Polymorphism, Indirection, Pure Fabrication and Protected Variations. GRASP stands for General Responsibility Assignment Software Patterns or Principles. Recall that a pattern is a named and well-known problem/solution pair that can be applied in new contexts, with advice on how to apply it in novel situations and discussion of its trade-offs, implementations, and variations. So a pattern is not a new idea. Rather, it is a tried-and-true principle. A knowledge of patterns can help you in your future software design endeavors. To quote the author, “The critical design tool for software development is a mind well educated in design principles.”

In this memo to your supervisor you will summarize several design principles and patterns and you will explain an example of a time that you employed polymorphism and the concept behind the protected variations pattern.

Team Size

N/A

]]> http://cs-comm.lib.muohio.edu/items/show/74 <![CDATA[Continuing to Think Recursively Using a Maze]]>

This assignment is typically given later in the semester, as students should understand classes and objects, I/O, and recursion.]]>

2012-07-25T14:45:35-04:00

Title

Continuing to Think Recursively Using a Maze

Course

Data Structures

Abstract

In this assignment, you will have to use everything you have learned to choose an appropriate algorithm and data structure for traversing a maze to find an object and get out - using a recursive solution! The objectives of this assignment are to (1) continue gaining experience with recursion, (2) improve the implementation of proper coding styles and documentation, and (3) effectively present a design in written and speaking (bonus) form.

This assignment is typically given later in the semester, as students should understand classes and objects, I/O, and recursion.

Author

Bill Eberle

Genre

design document, code, comments, pseudo-code, test results, documentation, individual presentations, oral presentations, reflection, tech report, video

Assignment Duration

Two Weeks

Communication Skill

reading, writing, speaking

Technical Skill

implementation, tools, design, recursion, linear data structures, program design, selection of algorithm and data structures, comments, documentation, problem solving

Workplace Scenario

DESIGN DOCUMENT AND PRESENTATION
Technical Task: The ability to speak in front of your peers, management, or more importantly a customer, will greatly influence your success in the real-world. If you cannot convey your ideas to your peers, you will have difficulty convincing others of your solutions.
Professional Setting: Students work for a software company.
Professional Role: Students are members of a project team.
Deliverable: Design document and associated presentation.
Real-world Audience: Management and peers.
How the Audience will USE the students' communication: The project manager and leaders will use the student's design and discussion to do the following: (1) Determine whether the team is capable of completing the project. (2) Develop a plan for completing the project.
Notes to Student: If you cannot present your ideas to management, you will lose their confidence in your abilities. If you cannot effectively present your product and ideas to a customer, you will probably lose their business.

ADDITIONAL SCENARIO
Recursion is a design concept that is critical to becoming a solid software engineer. In the real-world, the ability to recognize design patterns, and potential repetition, is necessary when performance of a system is critical. Doing this just takes practice!

Team Size

N/A

]]> http://cs-comm.lib.muohio.edu/items/show/73 <![CDATA[Auto Music System Part 3 - Simulator construction]]>

http://cs-comm.lib.muohio.edu/admin/items/show/65 to see previous assignment]]>

2012-07-30T16:26:19-04:00

Title

Auto Music System Part 3 - Simulator construction

Course

CS2

Abstract

The student will design and code an application that uses the Auto Music System classes designed and coded in previous assignments to simulate an actual car audio system. Refer to http://cs-comm.lib.muohio.edu/admin/items/show/65 to see previous assignment

Author

Paul Cantonwine

Genre

Pseudo Code, Test Plan, comments, code,Problems encountered report

Assignment Duration

One Week

Communication Skill

writing

Technical Skill

Programming Language Basics, Graphical Interface, OO Language Features

Workplace Scenario

You have been given all the classes for the Auto Music System and you need to develop an application that uses these classes to simulate a Car Audio System.

]]> http://cs-comm.lib.muohio.edu/items/show/72 <![CDATA[GRASP Patterns and Principles Memo]]>

2012-07-25T22:07:12-04:00

Title

GRASP Patterns and Principles Memo

Course

Software Engineering

Abstract

Describe the purpose of design principles and patterns. Describe some principles and patterns.

Author

Douglas Troy

Source

Larman, Craig. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition), 2004.

Genre

Memo

Assignment Duration

Less than a week

Communication Skill

Reading,
Writing

Technical Skill

Design

Workplace Scenario

The purpose of this assignment is to introduce the five GRASP patterns or principles: Creator, Information Expert, Controller, Low Coupling, and High Cohesion. GRASP stands for General Responsibility Assignment Software Patterns or Principles.

The author of or text book states that a pattern is a named and well-known problem/solution pair that can be applied in new contexts, with advice on how to apply it in novel situations and discussion of its trade-offs, implementations, and variations. So a pattern is not a new idea. Rather, it is a tried-and-true principle. A knowledge of patterns can help you in your future software design endeavors. To quote the author, “The critical design tool for software development is a mind well educated in design principles.”

In this memo to your supervisor you will summarize several design principles and patterns and you will explain an example of a time that you employed one of the patterns.

Team Size

N/A

]]> http://cs-comm.lib.muohio.edu/items/show/71 <![CDATA[Implementing and documenting a class]]>

2012-07-25T11:17:26-04:00

Title

Implementing and documenting a class

Course

Data Structures

Abstract

In this assignment, the student will implement a class and use the doxygen documentation facility to document it. Javadocs can also be used if java is the preferred language. The assignment is written for a specific class to be implemented in the context of a larger project and should be modified to account for using other classes or project.

Author

Gerald Gannod

Genre

comments, documentation, code

Assignment Duration

One Week

Communication Skill

writing

Technical Skill

implementation, coding

Workplace Scenario

Scenario: You have been assigned the task of both writing and documenting the behavior of a class.

Communication Audience: Other developers and potential maintainers

Deliverables: Source code with embedded comments plus generated html documentation of the source

How it will be used: The documentation will be used to understand how to use the code

Team Size

N/A

]]> http://cs-comm.lib.muohio.edu/items/show/70 <![CDATA[Software Architecture Document – Architectural Decisions Memo]]>

2012-07-25T17:13:43-04:00

Title

Software Architecture Document – Architectural Decisions Memo

Course

Software Engineering

Abstract

Document a project's software architecture and implementation using multiple views.

Author

Douglas Troy

Genre

Memo

Assignment Duration

Less than a week

Technical Skill

Install and deploy

Workplace Scenario

The purpose of this assignment is to introduce the Software Architecture Document (SAD). The audience for this document is other software engineers (not the client). The Software Architecture Document describes the big ideas of the design and implementation of your software. It is written for future software engineers who need to understand the how the system is implemented. For example, next semester a new team might take over your project and will need to understand the rationale behind your design and how the software is organized. Information like this is especially important for products like ours which we hope will be used for many years to come. The SAD is a compilation of “technical” design documents. These can include:
• Text descriptions, such as technical memos, that summarize important design decisions or characteristics
• Design diagrams, such as UML class and sequence diagrams, that describe static and dynamic design of your software

In this memo to your supervisor please document an important architectural decision made in for implementation of your team project. Your supervisor will use this to monitor the quality of the product’s implementation.

Team Size

N/A

]]>