UML Diagram, Design Document, Peer Evaluation, self-evaluation,Team Presentation

One Week

writing UML diagrams, teaming

Design, Object Oriented Language Features

Your company has signed a contract to develop the class structure needed to implement a car's audio system's user interface.

Your team has been assigned to develop the design document which includes a UML diagram. You will be presenting this design document to your company's review committee which will review your work and evaluate it's completeness. Once completed your design document will be given to the programming department for implementation.

2

Memo

Less than a week

Writing

Project management

The purpose of this assignment is to help your team to plan the sprints for the Elaboration phase. In Elaboration we want to build the core software architecture, resolve high-risk elements (things we are unsure about), and define most of the requirements for our projects. In this memo to your supervisor you will recommend two use cases (or features) that you believe should be implemented in the Elaboration phase.

N/A

Coding, short-answer prose, mathematical reasoning

Two Weeks

reading, writing

Implementation, linear data structures, pointers and memory management

You have been hired by a major Casino chain to verify the Bayer-Diaconis theorem, which purports to prove how many times a 52-card playing deck must be riffle-shuffled in order to completely randomize it (that is, make sure that, when done, each card could be anywhere in the deck with equal probability – regardless of where it started.). It is extremely important to the Casino that, before each deal at the Black Jack table, a deck be shuffled enough to make the order random. Failure to do so could lead to potential biases that a player might exploit. But Bayer-Diaconis is an analytic proof – a logical deduction from first principles. Your employer wants empirical evidence that Bayer-Diaconis is correct. One possibility is to have you shuffle the desk for a few billion years and track where the cards end up, but that is impractical. What is practical is to run a simulation and apply a basic statistical tool to establish the actual bound.

Importance: Using simulation to study the behavior of complex systems is one of the primary functions of Computer Science, and this project will expose you to some of the basic principles of the area. At a lower level, it will also require you to work with linked lists – arguably one of the two most important data structures we use.

You will also be asked to read investigate the linked-list data structure and discuss aspects of the reading. In reality, you will often need to pick a data structure appropriate to your problem, frequently choosing between established structures you are unfamiliar with. This will involve a certain degree of research: reading and understanding papers or text on the options, and possibly defending your decision to a colleague, boss, or client. The questions in this assignment are intended both to test your understanding and to make sure you can coherently explain what you have learned to another party.

N/A

Critique, Oral Presentation

Short Activity

speaking, teaming, listening

varies

Frequently, throughout our careers we will be asked to give feedback to others to help them improve what they are doing. Being able to provide constructive, useful, and thorough critique improves the performance of your team, reflects positively upon you, and builds good rapport with your colleagues.

3

This assignment can be scaled to larger teams with a minimum of 3 per team.

The technical skill varies on this skill, because practically any technical skill can be demonstrated by the student lecturer. Keep in mind that that the student presentation is only 3 minutes long so the subject matter must be scaled so that it can be presented effectively in 3 minutes or less.

This assignment can also be used for other courses other than CS1.

CSC 225 – Introduction to Software Development PROJECT MANAGEMENT TOOLS REPORT The project manager has decided to continue development of the product begun but not completed by an acquired company. (This is the product your team evaluated in the Product Review Report, developed customer requirements for in the Customer Requirements Report, and developed a prioritized bug/enhancement list for in the Prioritized Bug/Enhancement Report.) The product manager has assigned your development team to select and implement project management tools. Specifically, the project manager wants your team’s recommendation on the following:  Process management tool (i.e., a tool to manage the development process)  Configuration management tool (i.e., a tool to manage the product code) Your team’s report needs to recommend tools that your team will use to effectively and efficiently manage product development. The project manager has asked your team to make a ten-minute presentation summarizing the report. Your team’s report and presentation provides the project manager with critical information to plan how to develop the product. YOUR DELIVERABLES 1. The project manager has asked your team to prepare a three-to-five-page project management tools report. 2. The project manager has asked your team to present significant findings from the project management tools report in a ten-to-fifteen-minute meeting. WHAT YOUR READER WILL DO WITH THE COMMUNICATIONS YOU PROVIDE The manager must develop a plan for completing the project. Therefore, the manager wants your team to answer the following technical questions: 1. What process management tool is best suited to manage the development process? 2. What configuration management tool is best suited to manage the development process? 3. What resources are needed to implement and maintain the recommended project management tools? You must provide answers to these questions in a manner that helps the manager develop a plan. The manager must evaluate your team to determine whether it is capable of completing the project. The manager will use your team’s report to answer the following questions: 1. Can your team evaluate and select project management tools? 2. Can your team implement and maintain project management tools? 3. Can your team document tool installation and maintenance for new team members? 4. Are you and the other team members able to work together effectively? You need to present your information in a way that persuades the manager that your team is technically proficient and effective at collaborating on a complex project. LEARNING OBJECTIVES FOR THIS ASSIGNMENT While working on this assignment, focus on developing your ability to perform these technical tasks: 1. Evaluate key features of process management tools for a development project. 1

CSC 225 – Introduction to Software Development 2. 3. 4. 5. 6. Evaluate the key features of configuration management tools for a development project. Estimate resources needed to install and maintain the project management tools. Install and test project management tools for a development project. Create a plan to train a new team member to use the project management tools. Identify the key technical information about a program that the project manger wants when deciding which project management tools to use.

Focus also on developing your ability to perform these communication tasks: 1. Write a report that helps managers make practical decisions efficiently. [Writing] 2. Write a report that builds a manager’s confidence in your team’s technical and communication abilities. [Writing] 3. Write a report that persuades mangers to accept your recommendation. [Writing] 4. Select key information from written report useful to the project manager. [Speaking] 5. Create an informative and useful presentation for the project manager. [Speaking] 6. Demonstrate trustworthy technical expertise and communication skills. [Speaking & Teaming] 7. Deliver your presentation in a professional manner that supports achievement of your goals. [Speaking & Teaming] 8. Collaborate effectively on a software development team. [Teaming] 9. Organize and execute a meeting with the project manager and the software development team. [Teaming] 10. Develop knowledge of individual team member skills and trust among team members. [Teaming] ASSIGNMENT SCHEDULE Monday (9/17): Introduction to project management and project management tools. Friday (9/21): Submit your report and make your presentation. Peer review of presentations. GRADING CRITERIA The grading criteria for your team’s written report and presentation are presented in the attached rubrics

2

CSC 225 – Introduction to Software Development Project Management Tools Report

Technical Rubric
TECHNICAL ABILITIES Ability
Evaluate key features of process management tools for a development project.

Details
Analyze the features of the process management tool

Report Section
Evaluation Section

EVIDENCE EXAMINED TO EVALUATE YOUR TECHNICAL ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Lists useful features with a brief, accurate description of each Useful features not listed, or missing or inaccurate description

Points

Evaluate the key features of configuration management tools for a development project.

Identify the key process management features for the development project Analyze the features of the configuration management tool

Lists features that support the project with persuasive justification Evaluation Section Lists useful features with a brief, accurate description of each

Project supporting features not listed or justification is not persuasive Useful features not listed, or missing or inaccurate description

Estimate resources needed to install and maintain the project management tools.

Identify the key configuration management features for the development project Identify the time needed to learn and maintain the project management tools

Lists features that support the project with persuasive justification

Project supporting features not listed or justification is not persuasive Project management task missing, missing time estimate, or missing supporting evidence. Team members not listed or relevant skills missing or inaccurate

Resource Section

Lists project management tasks with a time estimate with supporting evidence

Identify team member(s) needed to maintain the project management tool

Lists team members with description of relevant skills

3

CSC 225 – Introduction to Software Development
Install and test project management tools for a development project. Install the project management tools. Verify the installations has worked Identify in technical terms problems with the tool installation Installation Section Describes installation process accurately Focuses on the major steps taken Describes each major problem encountered precisely; summarizes the amount and kinds of minor problems encountered Lists tasks required to maintain project management tools; describe importance of each Plan describes specific steps for new team member Describes installation process inaccurately. Provides a narrative of every step taken Omits major problems encountered or describes them imprecisely; describes in detail each minor problem encountered Omits necessary project management tool tasks or inaccurately describes importance Plan description is disorganized, generic, or is not appropriate for a new team member Omits or describes inaccurately the key features of tools, or omits evidence to support their usefulness Omits or describes inaccurately costs of using each tool.

Create a plan to train a new team member to use the project management tools.

Identify the key information to maintain the project management tools

Training Section

Create a plan to train a new team member

Create a project management tool recommendati on.

Recommend a process management tool and a configuration management tool

Recommen dation Section

Describes accurately the key features of each tool that useful for the project supported with evidence

Describes accurately the cost (time and people) needed to successfully use the tool Provides enough detail to enable the manager to incorporate the tools

Describes recommendations vaguely so a manager

4

CSC 225 – Introduction to Software Development
recommendation into the project plan would not be able to incorporate it into a project plan

5

CSC 225 – Introduction to Software Development Project Management Tools Report

COMMUNICATION RUBRIC
COMMUNICATION ABILITIES Ability
Report helps project manager make practical decisions efficiently

Details
Provides critical information useful to the reader Critical information is easily accessible to the reader

Comm Skill
Writing

EVIDENCE EXAMINED TO EVALUATE YOUR COMMUNICATIONS ABILITIES (Note that your present your evidence in your report) Done Well Rating and Comments Needs Improvement
Contains all information useful to the reader and none that is not useful Uses text formatting, organization (e.g., headers), and graphic devices (e.g., lists and tables) that makes information easily accessible to the reader Uses style and tone appropriate for the workplace Useful information is missing or not useful information is included Fails to use formatting, organization, or graphics that makes information accessible to the reader

Points

Report builds project manager’s confidence in team’s technical and communicatio n abilities

Concise and appropriate writing style for project manager Uses precise terms appropriate for the reader

Writing

Uses terms and concepts familiar to the reader, or explains unfamiliar terms or concepts

Uses informal style and tone that is inappropriate for the workplace Misuses terms or concepts or uses terms or concepts unfamiliar to the reader without explanation Key findings are explained inaccurately or imprecisely Fails to used evidence from user training to support key findings

Provides accurate and precise explanations

Key findings are accurately and precisely explained Uses evidence from user training to support key findings

Uses credible evidence to support explanations

6

CSC 225 – Introduction to Software Development

Report persuades project manager to accept your recommendati on

Uses correct and appropriate spelling, grammar, etc. Integrates and interprets findings

Writing

Uses correct spelling, grammar, etc. throughout report Provides a summary that prioritizes and integrates individual findings and synthesizes an interpretation Provides a development plan that recommends actions that are supported by key findings Concisely and accurately demonstrates key features of user training Concisely and accurately demonstrates significant features of the user training sample

Several spelling, grammar, etc. errors in report Summary lists without prioritizations or fails to synthesize individual findings

Persuasively describes development plan

Select key information from written report useful to the project manager

Select information the demonstrates key features user training Select information that demonstrates significant features of the user training sample Select information that demonstrates significant factors affecting user experience Select information that recommends plans for program development Key information is presented

Speaking

Development plan that is does not recommend actions or is not supported by key findings Selected features are incomplete or redundant Significant features are missing, insignificant features are included, or irrelevant features

Concisely and accurately demonstrates significant factors affecting user experience

Significant factors are missing, insignificant factors are included, or irrelevant facctors

Create and informative and useful presentation

Speaking

Concise and accurate recommendations for program development Succinctly presents key information

Significant recommendations missing Omits or inaccurately presents key information

7

CSC 225 – Introduction to Software Development
for the project manager Handouts, visuals, demonstrations, etc. support and complement the presentation Uses concise, accurate, and useful support materials to support and complement the presentation Uses verbose, inaccurate, or extraneous support materials that detract from or confuse the presentation Order does not relate to the order of the written report or does not support report understanding Lacks focus or is disorganized; not useful for the project manager

Report order is clear from the presentation

Orders presentation to support the order and understanding of the written report Speaking and Teaming Demonstrates a clear understanding how to organize a presentation useful to the project manager Demonstrates careful planning, avoids firsttime problems, and anticipates potential problems Demonstrates a clearly defined role for each team member Attire for each team member is appropriate for the meeting Demonstrates a clear and accurate understanding of questions, and accurately and respectfully answers each

Demonstrate trustworthy technical expertise and communicatio n skills

Focused and organized presentation

Carefully planned and well-executed presentation

Demonstrations lack of preparation and inadequate planning

Each team member’s role is clearly defined

Team member roles are unclear

Each team member is properly attired for the meeting

Team members under dress or over dress for the meeting

Questions are accurately, authoritatively, and respectfully answered

Demonstrates lack of understanding or the lack of ability to explain answers to questions. Lack of respect for the

8

CSC 225 – Introduction to Software Development
questioner Tasks are not independent, are vague or unclear, or do not contribute to the software development task Some team assigned tasks that take too little or too much time, and teams are assigned tasks that fall short of or exceed the allotted time Individuals and small groups are unaware of the state of other individual or small group task Results of each task are not clear or are not easy to access No meeting announcement, missing information, or inadequate advanced notice One or more required attendees absent or late Omitted major topics, time not on task, not enough time to answer

Collaborate effectively on a software development team

Breakdown the software development project into small, independent task

Teaming

Each task is independent, clearly defined, and contributes to the overall software development task

Effectively and equitable assign tasks to individuals or small groups of developers that can be completed in the allotted time

Each team is assigned tasks that can be accomplished in the allotted time and tasks are evenly assigned

Effectively coordinate task among individuals or small groups

Each individual or small group is aware of the state of tasks assigned to other individuals or small groups Results of each tasks are collected in a uniform, easy to use document Meeting announcement is sent with date, time, and place in advance

Organize and execute a meeting with the project manager and the software development team

Effectively and efficiently coordinate results from each task Required attendees are notified of the meeting arrangement

Teaming

Required attendees are present on time

All required attendees present on time

Meeting is wellorganized and executed

All major topics are presented, no time is wasted, all questions are

9

CSC 225 – Introduction to Software Development
answered in the allotted time Team members are able to clearly state at least two strengths and weaknesses for each team member Team members complete assigned tasks and wait for others to complete assigned tasks all questions Team members cannot identify team member strengths or weaknesses

Develop knowledge of individual team member skills and trust among team members

Identify skills of each team member

Teaming

Develop trust among team members

Team members do not complete assigned tasks or do tasks assigned to others

10



Recommendation/Proposal

One Week

Writing, Speaking, Teaming

Tools

The project manager has decided to continue development of the product begun but not completed by an acquired company. The product manager has assigned your development team to select and implement project management tools. The project manager will use your selections to advise upper management on the resources required for the project.

4-6

The course (CSC 225 – Introduction to Software Development) is a sophomore-level, experiential introduction to software development that focuses on learning basic software development principles and communications skills by developing an ongoing project. The course project, Tank Wars, continues from the previous semester and is packaged for the next semester.

Over the course there are five set-up assignments
• Program Review Report
• Customer Requirements Report
• Prioritized Bug/Enhancement Report
• Project Management Tools Report
• Preliminary Test Plan Report
that provide background for four two-week Scrum Cycles included in the Scrum Process Management assignment.

Each assignment is a specific Technical Rubric.

The Communication Skills Rubric is the same for all six assignments. Communication skills are assessed cumulatively from the rubric. Communication skills that are to be assessed in this assignment are in red. Communication skills assessed on in earlier assignments and that will continue to be assess in this assignment are in green. Communication skills not assess are in black. All communication skills are assessed for the Scrum Process Management assignment.

brainstorming, discussion, design document, code, comments, pseudo-code, test results, documentation, peer evaluation, reflection, requirements, technical report, team meetings

Several Weeks

reading, writing, teaming, listening

team evaluation, implementation, tools, design, linear data structures, program design, comments, documentation, programming language basics, data types and variables, tools, research, problem solving

TEAM DESIGN DOCUMENT
Technical Task: Most real-world software development projects involve working as a team.
Professional Setting: Students work for a software company.
Professional Role: Students are members
Deliverable: Design document.
Real-world Audience: A project manager.
How the Audience will USE the students' communication: The project manager will use the students' design document to do the following: (1) Develop a plan for completing the project, and (2) Determine whether the team is capable of completing the project.
Additional Notes: Whether it is working with other developers, business people, managers, customers, or users, you must be able to adapt to different personalities and deliver a working product that meets the customer’s requirements.


ADDITIONAL SCENARIO:
Also, as a software developer in the work force, you may have to do some research to find a solution to a problem. In this assignment, you will be given a task (handling of the probability of a customer arriving) for which there is not a solution in your textbook. For example, this will require you to read other resources (such as the internet) to understand how to do random number generation.

4-6

Memo

Less than a week

Writing
Teaming

Requirements

The purpose of this assignment is to help your team to create your team’s initial product backlog (list of features). Creation of the backlog is the first step in the Scrum process. The product backlog will be used to plan the first Elaboration sprint. Each team member will help to create the initial backlog by more fully developing a use case for the class project. In this memo to your supervisor, you will write a more detailed use case for one of the features of your team’s project.

Learning to write use cases, and using the Scrum process, will help you in an internship or job since many organizations use these approaches.

Design Tradeoffs,White paper, Data Analysis

One Week

Writing, Teaming, Reading

Design Analysis, Security, Tradeoff Analysis

As a software engineer you will often be required to design information systems based on a client’s requirements. It is your responsibility to understand the needs behind the information system, develop a feature set based on the needs and produce a design for the information system. Once you have designed the information system, you will be often be responsible for analyzing the design to identify privacy issues, security vulnerabilities and identify and implement access control policies and mechanisms to prevent security breaches. You will also be required to enforce entity, referential and business rules to ensure that your information system provides a true representation of the real world data.

A critical ability while working within a team is to develop an ability to manage conflicts, accommodate different design decisions, and manage conflicting client requirements. This milestone helps you learn and apply these abilities in a real life situation.

3

coding, short-answer prose

Several Weeks

reading, writing

Implementation, pointer and memory management

You are a programmer for a tech. company who has been tasked with setting up a protocol for secure communications – allowing users to exchange emails without that cannot be read by outsiders. To do so you will implement RSA public-key encryption; because the speed of encryption/decryption is considered a priority, you will implement these in C (as opposed to C++ or Java).

From a pedagogical perspective, the point of this assignment is to give you exposure to C-style programming, helping you to understand memory manipulation. We will continue to use the C++ compiler (avoiding the hassle of installing a C compiler), but you will be restricted to using only C libraries. Hence you experience working with the C programming language, and have you think about issues that C++ frequently (and Java always) hides from the programmer. In the course of this project you will also look at both a common cipher algorithm and RSA, one of the core encryption algorithms. RSA was the first public-key encryption algorithm, and the mathematics on which it is built is similar to many more sophisticated encryption algorithms. You are not expected to understand the mathematical basis for RSA, but by the end of this project you should understand how public-private encryption key pairs are generated, how they are used, and why they are so useful in computer security.

N/A

Recommendation
Memo

Less than a week

Writing

Requirements

The primary tool at our disposal for defining requirements and identifying features is Use Case Modeling. Use cases are simply scenarios, or stories, that capture the functions that the system provides for the users. The use cases will help you to create your Product Backlog. In this memo to your supervisor, you will identify two use cases for your team’s part of the class project.

N/A