COURSE: CPSC 490-001 Tues. 1:40-4:20 EMCS 312
PREREQUISITES: CPSC 251 and 261 (350) with grades of C or better and senior standing in Computer Science.
|
Instructor: |
Dr. Stephanie Smullen |
|
Office: |
EMCS 313A |
|
Telephone: |
425-4395 |
|
E-mail: |
|
|
Office Hours: |
As posted or by appointment |
TEXTBOOK: Software Project Management for Small to Medium Sized Projects, Rakos
COURSE OUTLINE: Each student in this course will participate as a team member in the specification, design, coding, and release of a information technology product. Each team will consist of four team members selected by the instructor. See the Course Materials section for your team. This course is NOT a competition among the separate groups; it is an effort on the part of each group to perform the best that it possibly can. The performance (either success or failure) of one group is independent of the performance of the other groups in the course. Each group will have a different approach and will face different problems and different opportunities.
Some parts of the team's work will be graded as a team effort and some parts will be graded individually. Each team member will evaluate the efforts of the other team members and these evaluations will be included in the final grade for the course. Each individual in the course must maintain a notebook (journal), which will be graded at intervals during the course. You must record all of your work on the project in this notebook. You should make it a habit to record an entry in your journal each time you work on any aspect of the course, have a meeting, ask a question of the instructor or your team, perform any library or online research, or write any portion of the code or project milestones. You must record:
· the starting time
· the ending time
· the subject
· the activity
· the persons present
· notes to carefully document your work, describe the division of work, plans for written documents and presentations – everything about your work on the project
See the journal file for more information on the format required for the notebook. The team final report must document and analyze the time spent by category of effort and calculate the productivity of the team during each phase of the project.
All deliverables graded and returned items, and other documents relevant to the project will be dated and saved by the team. Notebook entries should refer to the appropriate items to document your work on the project.
The reuse of your own or others’ code is encouraged. However, you must have the legal right to use any such code and you must be able to demonstrate that you have this right when asked to do so. You must document where all reused code originated, who wrote it, and how you modified it. If you do not acknowledge the work of others, you will be in violation of the honor code and will be given an F for this course.
It is your responsibility to be aware of fixed due dates and your proposed due dates. Late work will receive a grade of 0. You may request changes in your proposed schedule by emailing the instructor at least 2 days in advance.
Notebooks and peer evaluations are due by 1:00 p.m. on the stated due date (see the calendar). Written reports not accompanied by oral presentations are due by 1:00 p.m. on the stated due date. Written reports accompanied by oral presentations are due at the end of the oral presentation.
Note: If you are a student with a disability (e.g. physical, psychiatric, vision, hearing, etc.) and think that you might need special assistance or a special accommodation(s) in this class or any other class, contact the Counseling and Career Planning Center, 338 University Center.
If you find that personal problems, career indecision, study and time management difficulties, etc. are adversely impacting your successful progress at UTC, please contact the Counseling and Career Planning Center, 338 University Center, phone: 425-4438.
Grading components:
You start with 0 points. Each of these deliverables adds points to your grade. Some of these points are earned individually and some are earned by the group. The calendar gives the due dates for notebooks, peer evaluations and fixed deliverables. If you are late turning in the notebook you will lose 1 point per day -- the notebook will not be accepted for grading after the Friday of the week it is due. If you are late turning in the peer evaluation forms, 2 points will be deducted from your peer evaluation score for each day they are late.
Notebook evaluations: 5 at 3 points each 15
Notebooks will be graded based on the accuracy, appropriateness, neatness, completeness, and professionalism of the entries. The notebooks must be bound, written in ink with numbered pages and without excessive blank spaces. Notebooks must follow all guidelines detailed in Research Journals listed in the Assignments section.
Peer evaluations: 4 at 5 points each 20
Peer evaluations will be graded on the overall team performance against the goals, and on the individual's contribution to the team effort and success as rated by the other team members and the instructor. Peer evaluation forms are available in Course Materials.
Oral presentations: 4 at 5 points each 20
Dates: final group presentation on the last day of class; other dates to be specified in your initial proposal.
Each person must participate in at least two oral presentations plus the user training session and the final class presentation. Oral presentations will be graded on professionalism, delivery, the use of visual aids, accuracy, completeness, and the ability to handle questions. Each student MUST participate in FOUR presentations. Oral presentation evaluation forms are available in Course Materials.
Group report parts: total for graded parts 35
Written reports will be graded on technical feasibility, presentation, professionalism, accuracy, completeness, and the use of appropriate tools. Cost report forms must be submitted with each written report. They are available in Course Materials.
Instructor evaluation: 10
Instructor evaluation will be based on your performance during the semester and the final examination.
Total points: 100
Grade: 100-90 A, 89.9-80 B, 79.9-70 C, less than 70 F. Honor code violation: F
Course Deliverables:
Preliminary Project Plan and Proposal Due no later than 9/3
Written; sample: R261-274 Reference: R1-55, 128-160, 190-254
The Request for Proposals is available in Course Material.
Submit two copies of your schedule (maximum of one page in length) that labels each part and specifies the days when each written part will be submitted and each oral presentation will be made. Failure to submit this schedule will result in a grade of 0.
Functional Specifications Document Due no later than 9/21
Written; sample: R275-282; Reference: R56-69
Design Specifications Document Due no later than 10/12
Written; sample: R283-291; Reference: R70-92
Acceptance Test Plan Document
Written; sample: R292-294; Reference: R93-98
Working user interface prototype
Written description with screen copies; Reference: R161-189
Coding and internal documentation completed
On CD – do not print the code; Reference R99-119. Installation and maintenance guide is required.
Demonstration of working product and user training All groups present on 11/23
Written training manual and oral presentation; Reference: R120-123
Presentation of product to the class All groups present on 11/30
Each group member presents five minutes; group has 30 minutes in all.
Written final report including written user manual and/or online help Due no later than 12/7
Includes analysis of results of acceptance testing, cost and productivity reports for the project. Reference: R124-128
Oral presentations: dates to be determined by each team. Presentations must be made on Tuesdays between 1:40 and 4:30. Each presentation should be approximately 20 minutes in length (5 minutes per member) plus 5-10 minutes for questions. Each person must participate in all four of his/her group's presentations. Suggestions for possible interim presentations include:
1. Walkthrough of functional specifications for correctness
2. Presentation of acceptance test plan and project status report
3. Demonstration of prototype user interface
For all oral presentations you should assume that the audience does not know who you are or what you are doing. Introduce each team member and the general topic of the presentation at every presentation.
Each team member needs to speak for 4-8 minutes. Points are deducted from the individual’s grade for presentations that are too short or too long. If the presentation is too long – it will be stopped after 25 minutes.
Within 24 hours after your presentation, you must email me your opinion of your individual performance on the oral presentation – include what you did well, as well as what you did poorly.