Winter Term, 2008
 Project Components |
Project Component Weightings |
Percentage Conversions |
| Instructor: Dr. Jonathan Mohr | |
| Office: N104 | Phone: 679-1514 |
| Office Hours: see instructor's home page | E-mail:
|
Detailed study of software development processes, life cycles, and tools, especially object-oriented methods. Team work is emphasized in the completion of a large software project, from problem definition through to maintenance.
Prerequisite — AUCSC 220.
On completion of this course, students should be able to:
This course focuses on a single semester-long software development project. The class will act as a software development team to implement a software system that solves a specified domain problem. The team may choose its own organization, process, and tools, subject to some constraints imposed by the instructor and others due to the academic context in which this software development process is situated. One fundamental constraint is that the project is to be completed using the object-oriented analysis and design principles studied in AUCSC 220.
The instructor will present background information to the class during some of the class sections, especially early in the term, about the selected problem and about some of the technical issues involved and how they can be solved in Java. Most of the class sessions, however, will be devoted to team meetings and team work on the project. The instructor will act as a domain expert (as far as possible) and a coach during these meetings.
During the last week of classes (April 9 and 14), the development team will present the results of their work to the instructor and each other, with an emphasis on the rationale behind the design and implementation decisions made, and will evaluate the process used with a view to identifying lessons learned and ways to improve future development processes.
There is no designated textbook for this course, but the textbook used for AUCSC 220, Craig Larman, Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3rd edition (Prentice Hall PTR, 2005), will be useful, and knowledge of its contents will be assumed.
In accordance with Augustana's policy on attendance and course work (Section 54.4 of the Calendar), an instructor is allowed to specify requirements with respect to attendance and class participation. This includes the right to suspend a student who has an inordinate number of absences in a course or who neglects his/her academic work. A suspended student may be refused permission to attend class sessions, submit assignments, and write examinations, except for the final examination.
In this course, any student missing more than two class sessions or failing to contribute in a substantial way to the team's software development effort may be suspended from the course.
A suspended student will be notified of the suspension by e-mail and by paper mail addressed to the student's assigned campus mailbox. It is the student's responsibility to arrange a meeting with the instructor to discuss the terms under which the suspension may be lifted.
The intended workoad for this class is 12 to 16 hours per week, including the (approximately) 4 hours of scheduled class and lab sessions. This assumes that software development teams will work together at times other than the scheduled class sessions and that individual members of the teams will work separately or in pairs to complete team-assigned tasks outside of regular class time.
Grades will be awarded using the Alberta-wide standard alpha four-point grading system. For assignments marked in percent, the percent/grade equivalents in this course will be approximately as indicated in the following table:
| Alpha Grade | Percentage Range |
|---|---|
| A+ | 94 - 100 |
| A | 87 - 93 |
| A- | 80 - 86 |
| B+ | 77 - 79 |
| B | 73 - 76 |
| B- | 70 - 72 |
| C+ | 67 - 69 |
| C | 63 - 66 |
| C- | 60 - 62 |
| D+ | 55 - 59 |
| D | 50 - 54 |
| F | 0 - 49 |
Your performance will be evaluated both as a member of a team and as an individual. One-half of your final grade will be determined by the instructor's assessment of the artifacts produced by the team as a whole; the other half of your grade will be the product of the score earned by the team on the project and your teammates' assessment of your contribution to the project.
For example, if the team project is evaluated at 70%, but your team reported that you contributed only three-quarters as much, in terms of both effort and quality, as the average team member, then your individual score would be 0.5 * 70% + 0.5 * ( 0.75 * 70% ) = 61%. Or, if your teammates concluded that you contributed 1.2 times as much to the project as the average team member, your overall score would be 0.5 * 70% + 0.5 * ( 1.2 * 70% ) = 77%.
Each team will be required to submit the following artifacts related to the software development project:
The weightings of the project components will be as follows:
| Software Architecture Document | 20% | |
| Architectural baseline | 20% | |
| Executable release | 40% | |
| User manual | 10% | |
| Other artifacts | 10% |
The University of Alberta is committed to the highest standards of academic integrity and honesty. Students are expected to be familiar with these standards regarding academic honesty and to uphold the policies of the University in this respect. Students are particularly urged to familiarize themselves with the provisions of the Code of Student Behaviour and avoid any behaviour which could potentially result in suspicions of cheating, plagiarism, misrepresentation of facts and/or participation in an offence. Academic dishonesty is a serious offence and can result in suspension or expulsion from the University.
Students who require accommodations in this course due to a
disability affecting
mobility, vision, hearing, learning, or mental or physical health are
advised
to discuss their needs with Specialized Support and Disability
Services, F214,
Faith and Life Centre, 679-1649, or
.
The structure of the semester can be summarized as follows:
| Jan. 9–Feb. 15 | First iteration of the elaboration phase |
| Feb. 16–24 | SPRING BREAK |
| Feb. 25–Apr. 7 | Second iteration of the elaboration phase |
| Apr. 9–Apr. 14 | Presentation and evaluation |
NOTE: Policy about course outlines can be found in §23.4(2) of the University Calendar.
| Course Materials Index |
Top of this Document |
Instructor
Contact Information |
