3-player Chess

Cașu Cristinel (III – 2A)Hortolomei Irinel-Florin (III – 1A)

Requirements analysis Arhitectural design Detailed design Implementation Integration Validation & Verification Maintenance

Requirements analysis Arhitectural design Detailed design Implementation Integration Validation & Verification Maintenance

• Develop a Web-platform at client-side to offer support for playing real-time 3-player Chess matches. The game must have match history, player rankings and the graphics are to be made in SVG.

• Personas (demo) Vlad Mihalache (Primary) Delia Prisecaru (Secondary) Dorel Ciubotaru (Secondary) Ben Richards (Supplemental)

• QOCs (demo) How should the user login? What colors should the default theme use? How should players find informations about game? How will players try the game? What can a user do when he encounters a bug?

Requirements analysis

Arhitectural design Detailed design Implementation Integration Validation & Verification Maintenance

Requirements analysis Arhitectural design

Detailed design Implementation Integration Validation & Verification Maintenance

1. General design (demo)2. Custom matches (demo)

3. Leaderboard (demo)4. Learn 3-player Chess section & Play as Guest (demo)

Requirements analysis Arhitectural design Detailed design

Implementation Integration Validation & Verification Maintenance

• Client-Sideo HTML5 – latest html technologieso CSS3 – user graphic effects and animationso JavaScript – advanced animationso AJAX – asynchronous data transfer, for pulling data from server

• Server-Sideo PHP – server scriptso Comet – asynchronous data transfer, for pushing data to client

Requirements analysis Arhitectural design Detailed design Implementation

Integration Validation & Verification Maintenance

Each application module will be adjusted and integrated so as to meet sitemap structure.

Requirements analysis Arhitectural design Detailed design Implementation Integration

Validation & Verification Maintenance

Prior to release, the project will go through some series of testing. Because the project malfunctioning can lead to serious trust issues for our users there will be 4 types of testing:

1. Unit testing done by programmers

2. Overall testing done also by programmers

3. Group testing done by volunteers which were not involved in

development

4. Public testing done by users which are warned about possible

game changes

Requirements analysis Arhitectural design Detailed design Implementation Integration Validation & VerificationMaintenance

Maintenance will consist of 2 processes:

• Bug solving and code optimization

• Implementation of new features based on ideas from users

written on the forum

END