The Risk Game Practicum

1
The Risk Game Practicum

• Team Risketeers

2
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

3
Project Overview

• Team
• Derek DSouza
• Xiang Shen
• Mentor
• Dave Root
• Client
• Gil Taran
• Other Stakeholders
• MSIT Distance Team

4
Project Overview

• Web-based game using concepts of Risk Board Game
• Multi-player gaming environment
• J2EE backbone
• MSIT Distance team focusing on User Interface
• Our team working independently to develop back
  end

5
Project Overview
6
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

7
Our approach

• This semester focus on architecture design
• Adapted ACDM process
• Overlapped roles
• Began on Stage 3
• Helped identify risks early
• Helped refine requirements

8
Our approach

• Coordinating with distance team
• Weekly teleconference meetings
• Decouple tasks
• Predefined protocol for interface
• Achievements
• Created and reviewed architecture documents
• Performed experiments
• On Schedule

9
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

10
Architecture High Level CC View
11
Database Design
12
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

13
Top Risks

• Using the technologies we selected does not
  support the required quality attributes might
  have to modify the architecture or change the
  technology.
• Team is unfamiliar with the technologies used to
  develop the game resources spent on training
  might take up too much time.
• The User Interface does not get completed on
  time might not be able to completely test out
  the product.

14
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

15
Experiments

• Incentive Technical Risks
• Web-based server push
• Flash Java communication
• Java Message Service (JMS)
• Plan / Process
• Research (Cutting-edge web techniques)
• Prototype function design
• Live chatting
• Flash-based
• JMS
• Basic database
• Implementation
• Client evaluation

16
Experiments cont.

• Result
• AJAX / Comet for server-push implementation
• Flash JavaScript JSP JavaBean for Flash
  Java communication
• OpenJMS Tomcat for web server
• MySQL / JDBC for database usage

17
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

18
Lessons Used

• Management
• Process guidance
• Methods
• Context Diagram
• Architecture
• Architecture design
• Analysis
• QA plan

19
Lessons Learned

• Process is important, even for a two-person team
• Architecture reviews are very useful to identify
  potential problems
• Well established communication process is
  important for cooperation between distance teams

20
Agenda

• Project Overview
• Approach this semester
• HL Architecture
• Risks
• Experiments
• Lessons
• Looking Ahead
• Questions

21
Looking Ahead

• Summer semester
• Incremental development
• AUP process framework
• Construction and Transition Phases
• Relatively lightweight
• Focus on whats important

22
High Level Timeline
23
Questions?
24
BACKUP SLIDES
25
Spring Schedule
26
Detailed Timeline
27
Detailed Timeline
28
Detailed Timeline