Software Development for Electrical Engineering
SFWR ENG 3M04, Term I 2002/03
Lectures and Tutorials
Monday, Wednesday, 8:30-9:20, Friday 10:30-11:20 in PC-155
- Thursday 10:30-11:20 in BSB-138
- Thursday 13:30-14:20 in ABB-136
- Friday 13:30-14:20 in ABB-136
Dr. J. Carette, ITC-129 , ext 26869,
Office Hours: Monday 1:30-3:30, Wednesday 10:30-11:30
3K04 Course Pack , Introduction to Software Engineering: A Collection of
Formal Software Specifications, by Dr. M. von Mohrenschildt
This course is for people who already know how to program and are
familiar with the use of programming languages. The topics of the
course are: Basic methods of specifying, designing and documenting
software systems; mathematical foundations of formal specifications;
modularity; module interface design; coding style; verification and
Course Information on Web, Project and Slides
The latest version of this outline and the most "up-to date"
information as well as hand-outs can be found on the course web page.
(Or go to my home page and then to the course page).
The slides and
assignments can be found there as well.
Mid-terms, Exams, and Grading
- There will be two mid-terms.
- The final examination will be
scheduled by the Registrars office in the usual way. It will be
three hours in duration and cover the material of the course,
handouts and assignments.
- The labs are conducted in form of lab assigments.
Each student has to do his/her own lab assigment. The lab-time spot
reserved on your time table is scheduled such that you have
sufficient time to complete each lab assigment.
There is no physical lab.
- There is a zero tolerance on academic dishonesty .
All assignments have to be solved by one person only,
any outside source, this includes asking other people,
or using any books or information found on the web has to
be documented. In complience with the senate regulations
on academic dishonesty I remind you that:
People who let other poeple copy are as
guilty as the ones who copy.
You are allowed to consult outside sources, meaning textbooks
or the web, but any use of an outside source
must be documented.
Students are refared to the statement on academic ethics:
which contain details on "Plagiarism" and "Improper Borrowing in Non-Verbal
Disciplines" such as "improper use of the computer files".
- It is essential that you fulfill the deadlines for the
assigments, there is no credit for documents handed
in after the deadline. This is manly due to the fact that
solutions will be avaiable after the due date.
- In the case the instructor or a TA
has the impression that an assignment is copied the instructor can
ask the corresponding students to explain exactly how the assignment
was prepared and take appropriate actions.
- Graded assignments and tests will
be returned during a tutorial session. The ones not picked up will
be placed in a pick up box at my office. No responsibility for loss
of assignments can be assumed by either instructor or the Teaching
- There is one marking scheme with two components A and B.
Sheme A gives a credit for the assignemtns while sheme B does not.
You have to pass component B else you fail the course.
If you pass component B then your final mark will be computed by
component A. This means that you can not pick
a marking scheme. The instructor will not change the marking
Mid-Term Test 1
Mid-Term Test 2
- The instructor does not accept
late doctor's notices, if you write a mid-term then the mark is
yours. If you do not write an exam or an assignment and do not provide
an acceptable doctors notice then it is marked with 0. The
instructor reserves the right to conduct any deferred exams orally.
Outline of the course lectures
The following outline is approximate and is likely to change.
- Introduction (1. Lect)
- Software Life Cycle (1. Lect)
- Specifications (4. Lect)
- Mathematics (4. Lect)
- Modularization (3. Lect)
- Module Interface Specification (4. Lect)
- Module Internal Design (4. Lect)
- Hierarchical Structures (2. Lect)
- Coding (1. Lect)
- Inspection (2. Lect)
- Testing (2. Lect)
- Requirements Specifications (4. Lect)
- Software Development Methods (4. Lect)
Slides will be made available online after the lectures.
"The Faculty of Engineering is concerned with ensuring an
environment that is free of all adverse discrimination. If there is a
problem that cannot be resolved by discussion among the persons
concerned individuals are reminded that they should contact there
Chair, the Sexual Harassment Office or the Human Rights Consultant,
as soon as possible."
"Students are reminded that they should read and comply with
the Statements on Academic Ethics and the Senate Resolutions on
Academic Dishonesty as found in the Senate Policy Statements
distributed at registrations and available in the Senate Office."
Students are referred to:
Adapted by JC, from pages by MvM and WM. Aug 2002