1. 3-player Chess Cașu Cristinel (III – 2A) Hortolomei Irinel-Florin (III – 1A)

2.  Requirements analysis  Arhitectural design  Detailed design  Implementation  Integration  Validation & Verification  Maintenance

3.  Requirements analysis  Arhitectural design  Detailed design  Implementation  Integration  Validation & Verification  Maintenance

4. 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.

5. 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?

6. Requirements analysis  Arhitectural design  Detailed design  Implementation  Integration  Validation & Verification  Maintenance

8. Requirements analysis Arhitectural design  Detailed design  Implementation  Integration  Validation & Verification  Maintenance

9. 1.General design ( demo ) 2.Custom matches (demo) 3.Leaderboard ( demo ) 4.Learn 3-player Chess section & Play as Guest (demo)

10. Requirements analysis Arhitectural design Detailed design  Implementation  Integration  Validation & Verification  Maintenance

11. Client-Side o HTML5 – latest html technologies o CSS3 – user graphic effects and animations o JavaScript – advanced animations o AJAX – asynchronous data transfer, for pulling data from server Server-Side o PHP – server scripts o Comet – asynchronous data transfer, for pushing data to client

12. Requirements analysis Arhitectural design Detailed design Implementation  Integration  Validation & Verification  Maintenance

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

14. Requirements analysis Arhitectural design Detailed design Implementation Integration  Validation & Verification  Maintenance

15.  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

16. Requirements analysis Arhitectural design Detailed design Implementation Integration Validation & Verification  Maintenance

17.  Maintenance will consist of 2 processes: Bug solving and code optimization Implementation of new features based on ideas from users written on the forum

18. END