COMPUTING SCIENCE 220
Software Engineering and Human-Computer Interfaces

COURSE DESCRIPTION AND REGULATIONS

Fall Term, 2007

Quick Links

Course Outline

Assignment Weightings

Percentage Conversions

Instructor: Dr. Jonathan Mohr
Office: N104	Phone: 679-1514
Office Hours: see instructor's home page	E-mail:

Calendar Description:

Software engineering paradigms, requirements specification, object-oriented design, visual modelling, software verification and maintenance. Software environments and software engineering tools. Introduction to human-computer communication and interfaces. Societal iimplications such as the cost of failure and professional responsibilities.

Requirements:

Corequisite: — CSC 210.
 

Objectives:

On completion of this course, students should be able to:

1. Identify and discuss the technical and engineering activities of producing a software product.
2. Describe issues, principles, methods and technology associated with software engineering theory and practices (e.g., planning, requirements engineering, design, coding, testing, quality assurance, and configuration management).
3. Model a system using a visual modelling tool and the Unified Modelling Language (UML).
4. Identify and discuss paradigms of interaction, principles to support usability, and evaluation techniques for interactive systems.

Method of instruction:

The lecture component of this course will present an introduction to software engineering with an emphasis on object-oriented analysis and design, including visual modeling using the Unified Modeling Language (UML), iterative development using the Unified Process, and design patterns. As time allows, we will also discuss principles of human-computer interaction, project management, the various stages of the software life cycle, and software configuration management.

The lab portion of the course will consist of selected activities from the development of a system, such as writing use cases, drawing various UML diagrams, developing a domain model and a design model, and mapping a design to Java code in an implementation model.

Textbook:

Craig Larman, Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3rd edition (Prentice Hall PTR, 2005).

Grading Policy:

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:

Your performance will be evaluated through a set of assignments, a mid-term exam, and a final exam.

Assignments are due by the start of the class or lab session on the due date stated in the course outline or on the assignment specification. Late submissions will be subject to a penalty of 1% per hour or portion thereof, except for a valid medical excuse or other reasonable cause approved by the instructor prior to the due date.

The weighting of exams and assignments will be as follows:

Academic Integrity:

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.

Guidelines for Academic Integrity in This Course

All work submitted for grading must be your own, unless a group of students have arranged with the instructor in advance to complete a given assignment as a group project. Programs that appear to be the same, to have been derived from a common source, or to have been fraudulently obtained or created by any means will be given a failing grade.

Some of the practices which are regarded as inappropriate academic behaviour (academic dishonesty) are:

• submitting someone else's work as your own;
• writing or creating a work in the knowledge that it will be fraudulently submitted by someone else as his or her own (whether or not you receive payment);
• altering someone else's work (e.g., by changing the variable names) to conceal the fact that it was fraudulently obtained and submitted;
• using portions of another person's work (including algorithms or code from textbooks, magazines, or other sources) without acknowledgment.

Students are encouraged to assist one another in completing assignments, especially by explaining concepts to each other, by helping one another to learn the use of system utilities and programming environments, and by assisting each other in locating bugs. However, in order to avoid inadvertently becoming involved in a case of academic dishonesty (for example, when another student submits a program which is suspiciously similar to yours), you are advised to:

• protect your computer account with a secure password, changed frequently;
• ensure that copies of your program or work-in-progress are securely recycled or shredded;
• discuss programming principles and techniques with other students, not particular lines of code.

Accommodation of Disability

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 .

Course Outline:

The approximate dates on which the various topics of the course will be presented, along with an indication of which pages of the textbook are to be read in connection with each topic, are given in the accompanying course outline.

NOTE: Policy about course outlines can be found in §23.4(2) of the University Calendar.

Links

Course Materials Index

Top of this Document

Instructor Contact Information