Difference between revisions of "COMP354 - fall 2005"

Latest revision as of 20:56, 15 November 2013

Course Description

COMP 354 Software Engineering I (4 credits)

Prerequisite: COMP 352; ENCS 282. Principles of software development and maintenance. Software lifecycle models and deliverables: requirements analysis and specification, architectural and detailed design, implementation, verification and validation. People, product, and process issues: team dynamics, communication, presentations, reviews. Lectures: three hours per week. Laboratory: two hours per week. Tutorial: one hour per week. NOTE: Students who have received credit for COEN 431 may not take this course for credit.

Course Schedule and Contacts

Examinations Schedule

Homework and Project Assignments Schedule

Lecture Schedule and Material

Tutorial and Laboratory Schedule

Course Material

• Course outline
• Unified Modeling Language [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
• Example for project deliverable 1
• Example for project deliverable 2
• Example for project deliverable 3
• Example using another template (3 phases in one document)

Project Description

You have to build a game that is an equivalent of the game "Conquest" [1], a clone of the popular board game "Risk". You have to extract all requirements by downloading and inspecting the free version of the game. All features of the game must be listed in your initial requirements document in deliverable 1. You also have to analyze these requirements by giving them relative importance and an evaluation of the difficulty of implementation. When setting up your project plan (also in deliverable #1), you have to specify in what order the requirements will be implemented, as well as restricting the scope of the project by eliminating some features if you find that some are too much time consuming or difficult to implement. However, there are some mandatory features that are to be implemented in all projects (some not being part of the original game) :

1. The game must be playable in text mode, using windows with fields showing the relevant information of the game, as well as buttons and menus to control the game execution.
2. The map must be customizable, i.e. one can define what countries are part of the map, give them names, and specify their neighbouring countries. For example, this could be done using a matrix. The engine of the game execution must be able to run a game with any valid map configuration without recompiling the game.
3. A computer player must be available. It does not need to act intelligently, but must be able to take a turn without user interaction, meaning that the game can execute with no user interaction by using only computer players without human players.
4. A save game feature (and the corresponding loag game counterpart) must be available.