CS223 Introduction to Software Engineering 2005/06

Submission of Part B

For part B, in addition to the report (to be posted in the usual place), please submit your code and any other files you wish to submit, via BOSS, as an archive (.tgz or .zip). Only one team member should perform the online submission.

Note about "Description of how the Project was managed"

The second bullet point under section 6.2 of the ISE Software Development Team Project document (page 6) requires the ISE Part B report to include "a description of how the team Project was managed, ..." . This part of the report should address at least the following important issues of Project Management:

• Source Code Control (Build, Update, Version Control, Library, Repository, Change Control,...)
• Allocation of Responsibilities (Who did what , when and why (Roles? Any Dynamic Changes,...)
• Installing, Compiling and Executing (Configuration, Compile, Build (Make or Ant), Run,...)
• Planning and Scheduling Control (Critical Paths, Subsets, Effort Estimation, Change Control,...)

Notice about Exam

The exam format has changed - please read exam information.

The aim of this module is to teach the concepts and principles underlying the best practice in software development.

There are 20 lectures during terms 1 and 2, and the module is assessed by coursework (a group project counting for 70% of the module), and by a one and a half hour examination in term 3 (which is worth 30% of the module).

The module will be taught by Doron Peled (Module Leader), Ananda Amatya and Roger Packwood

The following information is available on-line

• List of Groups
. Now final!
• Timetable of Lectures and Surgeries (includes links to material presented in the lectures)
• Generating Test Cases from Use Cases
• Reading List
• Information about the Project
• How to write minutes for meetings