Our project is to design and implement (using Java programming language) a board game called Stratego.
By the end of this term, as in our last tutorial, we will be using our combined system (using at least one module from each team in our group) to play against the other group's system. It should be fun!
The name of the implementation class of GameInterface should be prefixed with team number, ie: Team1_GameInterface.
Added game rule: "PASS"(not move any pieces) is not allowed. i.e.: when MakeMove is called, a piece must move to another position.
Added game rule: Scouts can not jump over any pieces or lakes.
Deliverables & Deadlines
Deliverable
Due Date
Weight
D1: Software Requirement Specification
October 2nd, 2008
10%
D2: Architectural Design
October 23rd, 2008 Ext. October 27th, 2008
10%
D3: Detailed Design & System Implementation
November 13th, 2008 Ext. November 20th, 2008 League System Implementation - November 26th, By Midnight
10%
D4: Completed Documentation
November 27th, 2008 Ext. November 28th, By 4:30 pm
10%
Announcement
D2 should consist of both SRS and Architectural Design of the project. Architectural Design should at least include Analysis Class Diagram for all the scenarios, Interaction Diagram (Sequence Diagram) per scenario, and State Machine Diagram per controller class. You may also include other types of diagrams that you think is appropriate for the projects.
D3 should contain Detailed Design, both soft and hard copy of your code. For Detail Design, you need to specify attributes and methods for each class and the pre and post conditions along with the invariants for critical methods of your system. Read Chapter 4 of the textbook. For your code, please have your top level package named as teamX or leagueX (ie team1, league1, etc), and email me at jiangm5@mcmaster.ca on or by the due date. Please note following the Java coding style is essential. Here are some common Java code conventions from Sun.
League System Implementation is due November 26th, by Midngiht.
Deliverable 4 should contain all the up to date documentation of your project, including SRS, Architecture Design, Detail Design and any other documentation which is applicable, i.e. Testing Reports if you have done any testing for your system. You should also include a CD that contains the source code of your project.
Agenda
Tutorial 1: September 18th, 2008
Greeting & Introduction
Team Leader Selection
Team Picture Taking
Discussion on Software Requirement Specification
Tutorial 2: September 25th, 2008
Team 5 Picture Re-taking
Discussion on Business Events, View Points, and Modes
Discussion on Templates of Software Requirement Specification
Tutorial 3: October 2nd, 2008
Deliverable 1 Due Day
Discussion on Architectural Design, Class Diagram, etc.
Informal Requirements from Umpire System
Tutorial 4: October 9th, 2008
Release of Official Requirements from Umpire System
Discussion on Architectural Design, Class Diagram, etc.
Tutorial 5: October 16th, 2008
Deliverable 2 Due Date is Extended to October 27th, 2008
Deliverable 2 consists of SRS + Architectural Design
Discussion on Architectural Design, Sequential Diagram, etc.
Tutorial 6: October 23rd, 2008
Continue Working on Deliverable 2
Log Book Contents & Requirements
Details on Presentation for Next Week
Tutorial 7: October 30th, 2008
Presentation on Architectural Design (provide 5 copies of Analysis Class Diagram)
Discussion on the League System
Nov 6th, 2 Hour Lecture from Professor Khedri (2:30 - 4:30)