Incorporating Communication Outcomes into the Computer Science Curriculum

Lab - Domain Model using UML Class Diagram

Tue, 24 Jul 2012 20:38:56 -0400

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

Lab - Introduction to UML and Use Case Context Diagrams

Tue, 24 Jul 2012 17:44:08 -0400

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

Static and Dynamic Object Modeling Memo

Tue, 24 Jul 2012 17:11:22 -0400

Title

Static and Dynamic Object Modeling Memo

Course

Software Engineering

Abstract

Apply a contemporary analysis and design approach, such as object-oriented to a case study. Compare UML class and sequence diagrams.

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

Writing

Technical Skill

Design

Workplace Scenario

The purpose of this assignment is to further examine and compare two tools to support object design: Class diagrams and sequence (interaction) diagrams. When designing the classes (objects) we need to answer the following key questions:
• What software classes should we implement to produce the product?
• What are the responsibilities of each class (what are the attributes and methods)?
• How do the classes interact with one another and the actors?

Class diagrams and sequence diagrams are visual tools that help us to explore possible answers to the above design questions, and to document our decisions. Class and sequence diagrams are very commonly used design tools, so knowledge of these tools should be helpful to you in your future studies or career. In addition, the two diagrams model different aspects of the software, so the two diagrams are complementary.

In this memo to your supervisor you will summarize the purpose of static and dynamic models and give your own opinion on which type of model is most challenging and useful aid to software design.

Team Size

N/A

HW_15.docx

Design Proposal and Rationale

Tue, 24 Jul 2012 16:33:20 -0400

Title

Design Proposal and Rationale

Course

CS2

Abstract

For any set of requirements, students generate a design proposal rationale that includes a UML class diagram. The rubric evaluates how the students model the requirements and how they justify their design decisions and how the design meets the requirements. The objectives of this assignment are (1) to articulate a class diagram for an object-oriented system and (2) justify the decisions as modeled by the class diagram.

Prereqs: Students are expected to know advanced OO concepts like composition and inheritance. Additionally, students should be able to model an OO system using UML and should be familiar with design patterns, such as state, strategy, singleton, MVC.

The team size is flexible.

Any set of requirements could be used with this assignment. For a CS 2 class, the requirements usually consist of 3-4 use cases and the class diagram is typically 3-7 classes with a minimum of one inheritance and composition relationship.

This assignment is has been used as a deliverable in a larger programming assignment that spans multiple iterations. Students turn in a design document or proposal as part of an Iteration 0 along with a black box test plan. For an example of how the assignment has been used, please see the Somewhat Simplified Solitaire project. Please note that the project uses an older version of this assignment.

Author

Sarah Heckman, Ed Gehringer

Genre

design proposal, UML diagram

Assignment Duration

One Week

Communication Skill

writing, teaming, reading

Technical Skill

design

Workplace Scenario

A customer has provided your management team with a set of requirements. Your manager has requested that you and your co-workers each propose a design for the static layout of the system by identifying the objects, their state and behavior, and the relationships between the objects in the system. Your manager will then choose a design that best describes the requirements for implementation.

Team Size

DesignProposal.pdf

DesignProposal.docx

DesignProposal_Template.doc