Learning Outcomes

The School of Computing is undergoing a major curriculum review aimed at recasting the entire set of degree programs in terms of learning outcomes: brief statements of competencies successful students will acquire by the end of a course or a degree program. This page describes the current state of the learning outcomes related to CISC 322.

Program Learning Outcomes

A program learning outcome (PLO) is one that describes a competency of graduates of a particular degree plan; typically each PLO is achieved by learning outcomes from several required courses. Some of the course learning outcomes described below support aspects of program-level learning outcomes, particularly:

Course Learning Outcomes

To complete this course successful students will demonstrate their ability to:
  1. design architectures based on natural language requirements (PLO 3.2)
  2. recognize and describe the various architecture styles and design patterns
  3. work effectively in a group setting (PLO 6.1)
  4. communicate effectively verbally and in writing (PLO 4.1)
These high-level learning outcomes may be supported by more detailed ones described in lectures and term work.

Pedagogical Approach

This course is organized around a mix of reading assignments, traditional lectures, and active in-class learning.

Reading assignments have deadlines by which you must answer a series of simple questions about the reading and propose topics for further discussion. Some material is covered only in the readings; basic information is not covered in the lectures. Some lectures (typically scheduled 1-2 days after the deadline) will be based on your answers and suggested topics, and may answer a subset of the detailed questions you ask on the questionnaires.

In-class exercises involve working on a problem individually for a part of the class period, followed by group discussion, creation, and presentation of a joint solution, facilitated by the instructor. Some individual assignments and test questions will be similar to those of the group exercises.

Traditional lectures will present topics not covered in suitable readings. This means that if you do not attend these lectures, you won't be able to make it up, since there are no readings, the class slides don't spell out in detail everything I say in class, and there is no guarantee when, if ever, I will be able to record the lectures.

Group Work

Working in teams is an explicit learning outcome of this course. There are several reasons why this is worthwhile, but the main pedagogical reason is that group work exposes you to multiple points of view. At this level of University learning, there can be multiple answers to a question, each with different strengths and weaknesses. Different people will think of different answers, and you need to develop the skills and attitudes that let you come up with multiple answers and criteria for evaluating them. The loudest person's answer, or that of the one with the most dominant personality, is not necessarily the best. Even a "bad" idea may have aspects worth considering and incorporating into whatever alternative you choose.

If you continue on to a job in the Computing industry you will almost always be working in a group, and experience with group work is an advantage when applying for jobs.


Questions? Contact the instructor.
This page last modified