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

<![CDATA[Incorporating Communication Outcomes into the Computer Science Curriculum]]> http://cs-comm.lib.muohio.edu/items/browse/page/4?output=rss2 Mon, 18 May 2020 18:54:19 -0400 millarj@muohio.edu (Incorporating Communication Outcomes into the Computer Science Curriculum) Zend_Feed http://blogs.law.harvard.edu/tech/rss <![CDATA[Lab - Product Test Results]]> http://cs-comm.lib.muohio.edu/items/show/89

Title

Lab - Product Test Results

Course

Software Engineering

Abstract

Execute a system test for another team's product.

Author

Douglas Troy

Genre

Report

Assignment Duration

Class Period

Communication Skill

Writing
Teaming
Reading

Technical Skill

Testing

Workplace Scenario

The goal of this assignment is to analyze the test plans that we created in Lab#5, and suggest improvements to the plans, and to test our product. This assignment will give you experience testing another team’s product. You will complete a test report that will be given to the team responsible for the module that you tested. The report should help them to improve the quality of their product.

Team Size

4-6

Lab#6 Test Results.docx

]]> Tue, 24 Jul 2012 20:54:39 -0400 <![CDATA[Lab - Product Test Plan]]> http://cs-comm.lib.muohio.edu/items/show/88

Title

Lab - Product Test Plan

Course

Software Engineering

Abstract

Develop a system test plan.

Author

Douglas Troy

Source

www.developsense.com/testing/TestPlanOutline.doc

Genre

Report

Assignment Duration

Class Period

Communication Skill

Writing
Teaming

Technical Skill

Implementation
Testing

Workplace Scenario

In this lab you will create a test plan for your integrated product. Follow the outline below, which is adapted from IEEE Standard 829 and www.developsense.com/testing/TestPlanOutline.doc. This test plan will be used by another team to test your team’s project. In addition, this assignment will give you a general template that you can use for testing other code that you might write at school or on the job.

Team Size

4-6

Lab#5 Test Plan.docx

]]> Tue, 24 Jul 2012 20:49:11 -0400 <![CDATA[Lab - System Sequence Diagram]]> http://cs-comm.lib.muohio.edu/items/show/87

Title

Lab - System Sequence Diagram

Course

Software Engineering

Abstract

Create UML sequence diagrams to express class behavior.

Author

Douglas Troy

Genre

Design diagram

Assignment Duration

Class Period

Communication Skill

Writing

Technical Skill

Design

Workplace Scenario

In this lab you will our UML diagramming tool to create a system sequence diagram (SSD) for a use case in your project. The SSD is created using sequence diagram notation. You can use the SSD as an aid to help you team to design the interface with the end-user. As with the other UML labs, experience with modeling will be applicable to potential internships or careers.

Team Size

N/A

Lab#4 UML SystemSeqDiagram.docx

]]> Tue, 24 Jul 2012 20:43:39 -0400 <![CDATA[Lab - Domain Model using UML Class Diagram]]> http://cs-comm.lib.muohio.edu/items/show/86

Title

Lab - Domain Model using UML Class Diagram

Course

Software Engineering

Abstract

Create UML class diagrams that represent a problem domain from a requirement specification.

Author

Douglas Troy

Genre

Design diagram

Assignment Duration

Class Period

Communication Skill

Writing

Technical Skill

Design

Workplace Scenario

In this lab you will use our UML diagramming tool to create a domain model for your project. The domain model is created using class diagram notation, although we do not model methods in a domain model. The domain model is a design tool to help bridge the gap from the real-world object to software objects in your code. Your team can use the domain model to help guide the software design process.

Experience with UML modeling will be applicable to potential internships or careers.

Team Size

N/A

Lab#3 UML DomainModel.docx

]]> Tue, 24 Jul 2012 20:38:56 -0400 <![CDATA[Lab - Introduction to UML and Use Case Context Diagrams]]> http://cs-comm.lib.muohio.edu/items/show/85

Title

Lab - Introduction to UML and Use Case Context Diagrams

Course

Software Engineering

Abstract

Use UML class diagrams to create a context diagram for a case study.

Author

Douglas Troy

Genre

Design diagram

Assignment Duration

Class Period

Communication Skill

Writing

Technical Skill

Design

Workplace Scenario

In this lab you will use a UML diagramming tool to create the use case diagram for your project. Software design tools like this are common in industry, so becoming familiar with some tools will give you an understanding of similar software engineering of design tools. In this lab you will create a UML use case context diagram that you can use with the client to help to assure that you have a good understanding on the primary use cases in the project.

Team Size

N/A

Lab#2 UML Context Diagram.docx

]]> Tue, 24 Jul 2012 17:44:08 -0400 <![CDATA[Programming Concept Iterative White Paper]]> http://cs-comm.lib.muohio.edu/items/show/84

Title

Programming Concept Iterative White Paper

Course

CS1

Abstract

This assignment will give students a better understanding of fundamental software development concepts. It will allow them to discuss these concepts with others to refine their understanding. It will also give them practice documenting knowledge in a written form.

There are 4 stages to this assignment. In the first, the students research and create a report about one of a group of related programming concepts. In the second, the bring their research into the classroom and share it with the other students that have researched the same topic.

This assignment is a four step process. The first step is the homework assignment given in class and to be completed by each student individually. At the instructor discretion the concept topics available to the students can be either over material already presented in class or new material not yet covered in class. The second step is an in-class collaborative lab. The third step is a follow-up homework assignment. Again, individually undertaken by each student. The fourth step is a quiz to evaluate student concept learning. An optional step is an interactive, in-class session to discuss effective format, writing styles, research and writing techniques.

Author

Eric Luczaj

Genre

white paper

Assignment Duration

One Week

Communication Skill

reading, writing, teaming, speaking, listening

Technical Skill

control structures, iteration, sequence, function, varies

Workplace Scenario

Since we have chosen a fast-paced career where technology, development environments, and device platforms frequently change, we must develop our skills to learn new material effectively. We are not alone as we tackle these challenges. We can rely upon knowledge that we already have and we can collaborate to assist one another to gain more expertise. It is through the connections we make both to knowledge we have and to the people we know that will effective, productive, and valued in our careers.

In the workplace, we will often be asked to learn something new and bring that knowledge back to our team. How we give this knowledge back to our teams varies from informal conversation, to multi-recipient e-mails, to a very polished, published document sometimes called a white paper.

Team Size

N/A

Additional Information

This assignment can be modfied to incorporate any major course concept. The example provided within used control stuctures as an an example.

NSF CPATH Concept Writing Assignment.docx

]]> Tue, 24 Jul 2012 17:41:07 -0400 <![CDATA[Testing Techniques Memo]]> http://cs-comm.lib.muohio.edu/items/show/83

Title

Testing Techniques Memo

Course

Software Engineering

Abstract

Compare static and dynamic testing approaches.

Author

Douglas Troy

Source

Chapters 4 and 5, Software Testing Foundations: A Study Guide for the Certified Tester Exam

Genre

Memo

Assignment Duration

Less than a week

Communication Skill

Reading
Writing

Technical Skill

Continuous quality assurance

Workplace Scenario

Two general approaches to testing are static testing and dynamic testing. Static testing involves examination of design artifacts or code to look for problems. Static analysis can be done by humans or by software tools. Dynamic testing involves actually executing the code, supplying inputs, and examining outputs. Recall that testing can consume up to 50% of product development effort, so a knowledge of good software testing techniques can be very valuable.

In this memo to your supervisor, you will recommend how reviews (static testing) and how equivalence classes (dynamic testing) could be applied to your team project.

Team Size

N/A

HW_23.docx

]]> Tue, 24 Jul 2012 17:39:21 -0400 <![CDATA[The Basics of Software Testing Memo]]> http://cs-comm.lib.muohio.edu/items/show/82

Title

The Basics of Software Testing Memo

Course

Software Engineering

Abstract

Describe general principles that guide software testing.

Author

Douglas Troy

Source

Chapter 2, Software Testing Foundations: A Study Guide for the Certified Tester Exam

Genre

Memo

Assignment Duration

Less than a week

Communication Skill

Reading
Writing

Technical Skill

Continuous Quality Assurance

Workplace Scenario

In the Mythical Man Month, Fred Brooks observed that testing can often consume 50% of the time and effort in software development. Thus, learning how to design an effective testing process could contribute significantly to the timely and cost-effective delivery of software products. An understanding of the basics of effective software testing will help you with future projects and when you are involved with implementing new systems in your career.

In this memo to your supervisor you will summarize the general principles of testing and summarize how you have used two of them in your past programming experience.

Team Size

N/A

HW_22.docx

]]> Tue, 24 Jul 2012 17:36:00 -0400 <![CDATA[Using the Java API documentation to solve a problem]]> http://cs-comm.lib.muohio.edu/items/show/81

Title

Using the Java API documentation to solve a problem

Course

CS1

Abstract

This is an assignment focused on using Java API documentation to find methods that aid in solving a problem. In it, students must write a program that parses text and "cleans it up" (in particular: a name, address, and phone number, entered in a sloppy way by a user).

This is best suited to students who have only a basic knowledge of Strings and their methods, as it then forces them to dig around in the API documentation for Strings in order to find methods that accomplish their goals.

Author

Norm Krumpe

Genre

API documentation

Assignment Duration

One Week

Communication Skill

reading, writing

Technical Skill

Programming language basics

Workplace Scenario

The software you will write almost always depends on making use of packages, classes, and methods that were developed by other programmers. In order to use software written by others, it is necessary to be able to navigate and understand the documentation for that software.

In this assignment, you will need to solve a programming problem that requires you to use methods you have not seen or used before. You will produce a program that performs some fairly sophisticated parsing of Strings...parsing that is difficult to perform without first navigating the available methods in the String class.

When you are finished, you will report to your instructor on the methods that you used to solve the problem.

Team Size

N/A

Using the Java API documentation to solve a problem.docx

]]> Tue, 24 Jul 2012 17:35:24 -0400 <![CDATA[Class Implementation from API Description]]> http://cs-comm.lib.muohio.edu/items/show/80

Title

Class Implementation from API Description

Course

Data Structures

Abstract

Software specifications are often written in the form of API documentation. In this assignment, students are asked to write software by using an API as the specification.

Author

Gerald Gannod

Genre

api documentation

Assignment Duration

One Week

Communication Skill

reading

Technical Skill

implementation

Workplace Scenario

In the workplace, it is often the case that you will be asked to implement classes and programs based on an API specification. At those times, you are expected to spend a significant time understanding the requirements prior to starting the programming task.

Team Size

N/A

ClassImplementationFromAPI.doc

]]> Tue, 24 Jul 2012 17:33:54 -0400