CIS 480 - Lab

SE Lab and Project Overview

1. Review the information on process roles required in projects.

2. Team Leaders are recruited by the instructor. Each team leader is provided with a brief description of a project. From this description the team lead is to identify personnel from the class, by reviewing the resumes, needed to complete the project. The selection process is a round-robin, hence each project lead should have a prioritize list of personnel with reasons for needing that person on the team (skills).

3. Review effort tracking requirements.
4. Personnel selection process.
5. Teams meet to organize.
6. Team Leads email staff list to the instructor.

System Login

Usernames in all platforms are the same as CITS email usernames, but in all lower-case (only linux is case-sensitive, I think); the temporary password is the student id number; nts will require the user to change this, but I'm not sure linux forces this (yet). Please point out to students that real passwords should not be all numbers, but a mix of numbers, letters, punctuation, etc...

Problems should be directed to Paul Naylor (pnaylor@umassd.edu) in Dion 301.

Learning Portal

The majority of work submitted for this class, lecture and lab, will be to the Learning Portal, http://web.cis.umassd.edu. You should register as a user if you have not already done so. The Portal supports both individual work and sharing of documents for teamwork. You should become familiar with the workings of this software.

Username is first initial of first name followed by your last name. Your initial password is your student number. Passwords have been reset to SID.

Concept Map

We will be completing a number of assignments using the concept map softare, IHMC CMap. For a gentle introduction to concept maps and their creation, refer to the practice document we prepared.

For those wishing to install CMap software on their personal machines, we have downloadable archives available.

1. Team leads notify instructors of meeting location. Note you have two hours for organizaiton and planning, don't waste it! Instructors will make the rounds, checking on status and progress.

2. Teams should review the information in Portal to insure correctness: 1) insure the membership of each team is correct and 2) insure that the process roles are correct. We attempted to place each person in the group for a particular process role.

3. Effort data should be collected and summarized by Planning Managers. Problems with categorization should be discussed and clarified within the team.

4. Quality Managers should review material on quality assurance and configuration management pursuant to completing the team's Quality Assurance Plan.

5. Planning Managers have been given the expected completion date for requirements. Work accordingly.

6. QA should post the minutes of the team meetings in Portal. QA needs to have document standard for requirements ready, and process for requirements review. They also need the configuration management process in place so the support manager can implement.

7. The instructors would like to meet with each team for fifteen minutes to discuss any issues or concerns.

Project Guidance

1. Sample QA and Configuration plans were placed as resources in Portal for the QA group's review.

2. Teams meet to finalize approach to requirements and prepare requirements document.

3. Teams review the requirements review process prepared by QA.

1. Finalize requirements documents. Conduct internal review.

Requirements Review

Design Review

1. Navigation
2. B-Scan
3. Drive-by-wire
4. Basketball System

Teams meet. Continue to plan and work toward delivery on Nov. 5.

Teams meet. Continue to plan and work toward delivery on Nov. 5.

Teams meet with instructors.

1. Basketball Systemn
2. Drive-by-wire
3. Navigation
4. B-Scan

Project Demos

Design Task

1. Drive-by-wire
2. B-Scan

Project Demos by other teams.

Design Task

1. Basketball Systemn
2. Navigation

Project Demos by other teams.