CS411W Outline

Overview

This Module will serve as a review of CS 410 and an introduction to CS 411W. We will discuss the various, communication tools, hardware tools, and software tools for this semester. During the first week of the semester, your team will should update any and all materials as a result of lessons learned in CS 410.

Objectives

At the end of this module, students will be able to:

1. Recognize the general goals for the course.
2. Discern team member skills and identify team development needs.
3. Modify existing CS 410 documentation based on lessons learned.
4. Investigate and establish mechanisms of communication and collaboration.

Relevance

The business and research communities provide require online communication and collaboration using asynchronous and synchronous tools. Students will function as effective members of geographically separated team by contributing to the development of a Docker based prototype on a CS Department provided virtual machine (VM).

Overview

The work will begin on the prototype development environment. Teams must configure their virtual machines to support. Development milestones will be identified, along with a list of tasks for each milestone. A schedule will be created and resources applied. Lab 1 will be collaboratively outlined and individually written.

Objectives

At the end of this module, students will be able to:

1. Maintain a team website.
2. Identify and leverage domain appropriate collaboration & communication tools.
3. Identify high level tasks with prioritization of CS 410 user stories
4. Assign personnel resources to tasks
5. Identify and configure prototype development tools.
6. Prepare a Gantt chart of milestones for prototype development.
7. Write a descriptive paper (Lab 1) summarizing the real world product and planned prototype development.

Relevance

We will leverage Agile software development & design in prototype design. This is based around user stories that may change (usually do) along the way. The goal of this module is to confirm mentor acceptance of the development approach. Lab 1 is representative of the type of descriptive documents students will be required to create in the workforce.

Overview

The goal of Module 3 is to prepare a detailed list of tasks necessary to complete each prototype milestone. The tasks will have associated timelines and resources. This will allow for the creation of a weekly “to do” list for the team and each individual of the team. Lab 2 describes and defines the specifications and requirements. The mentors should be actively consulted during this design process.

Objectives

At the end of this module, students will be able to:

1. Identify sub-tasks for each milestone.
2. Record and track sub-tasks with a Gantt chart, task board, story board, or issue tracker.
3. Identify tasks that can begin immediately.
4. Create a list of design/coding elements to be completed each week.
5. Write in the style required for specification and requirement documents in the workforce.

Relevance

An absolutely critical component of software design is the writing of specifications and requirements. Also critical is the ability to provide software code based upon provided documents.

Overview

Testing is notoriously given the least amount of time and attention in software development. You should recall Test-Driven Development (TDD) from your previous coursework. We are currently implementing prototype functionality, yet need to simultaneously prepare test cases for our requirements. Significant progress should be made on software development over the next four weeks. Each team will collaborate on an outline of Lab 3 (i.e., the Test Plan).

Objectives

At the end of this module, students will be able to:

1. Maintain a Gantt chart, story board, or issue tracker of software development progress.
2. Prepare industry standard test cases that verify and validate the requirements from Lab 2:
   1. unit tests
   2. integrations tests
   3. system tests
   4. acceptance tests
3. Collaborate on the authoring of test cases and traceability matrices.

Relevance

Software development in industry is heavily dependent upon adherence to requirements. The only way to guarantee that the correct software solution to a problem has been achieved is through verification and validation via testing. If the test cases are not written to properly assess the development, time, money and credibility are lost. Possibly resulting in job loss and business failure. Students will experience the detailed process of this critical V & V element using their prototypes as the test bed.

Overview

The primary objective of this module is to practice agile (potentially scrum) development of the prototype with frequent instructor and mentor interaction. Weekly progress examinations will be conducted, and feedback will be provided. Adherence to requirements and development toward correct validation and verification is expected.

Objectives

At the end of this module, students will be able to:

1. Collaboratively continue successful prototype development employing all necessary software tools.
2. Collaboratively prepare a User Manual developed for the prototype.
3. Interpret the writing style necessary for user manuals.
4. Demonstrate correct adherence to user manual authoring standards.
5. Effectively demonstrate the prototype to the instructor and mentor.

Relevance

The ability to effectively communicate the purpose of user interfaces is a part of software engineering. The ability to take the reader of a user manual step-by-step through the usage of the screen is a skillset needed in industry. If a user cannot understand the interface, they may not utilize the product. The process of interim reviews of software development requires unique skillsets:

1. A developer must be able to professionally take criticism.
2. A developer must be able to ask questions of the customer to deliver a product that solves a problem correctly.

Overview

This module guides the student to successful completion of all written labs (re-writes). Demonstrations will be necessary to gain approval of their mentor, which is required by the end of the semester. The goal is to provide each student with an appreciation of industry’s expectations upon graduation with a degree in computer science.

Objectives

At the end of this module, students will be able to:

1. Summarize their journey through their professional preparation for employment.
2. Summarize the successes and challenges of developing professionally written technical documents typical of computer scientists.
3. Summarize their successes and challenges of working on a team to design, develop, and deliver a large scale software product.
4. Deliver a working product to their mentor.

Relevance

At the end of every software development process industry members must conduct Project Postmortem. The goal is to repeat the aspects that were great, and avoid those that cost them time and money. Keeping on top of customer expectations is critical in providing a useful product that correctly solves the prevalent problems that necessitated the need for a software solution.