● DESCRIPTION Using the given base code which depicts a basic card game, form a group of 2 to 4 students from your section and review the base code provided.

You will find that it depicts the building blocks of a card game. There are classes that represent the Cards, the selection of a "hand" and the framework for the playing of the game. As we move through the term you will slowly extend this code base and refactor the code into a card game of your choosing. This means any game that is played with cards is eligible for the project. Some ideas are: ● ● Go Fish War Uno SYST 17796 Skip-Bo Spot It Blackjack Deliverable 1 You can also choose a game that is not on the list. More advanced students can choose a game with more difficult logic (e.g. Uno). There is no graphical user interface required. After you have chosen your group and decided upon a game, complete the Team Contract provided in a separate document and integrate it into your submission. Next, create a Git repository for your project group and store the base code in your repository. It can either be a public repository OR private. You must add your instructor as a contributor if you choose the private option. The information necessary to access the Git repository must be provided in the Design Document Template. Next, create the UML class diagram that correctly depicts the current code. Make sure you use a CASE tool such as Visual Paradigm. Finally, complete the Design Document Template for the current base code AND your chosen game and integrate it into your submission. SUBMISSION Please submit one PDF document per group. This means that the document should be professionally organized and have a uniform style throughout. It should look as though it came from one team, not 4 separate students. Please note that instructors may choose to run your submission through Turnitin or compare the submission with other students from other sections for academic integrity purposes. Please take the time to properly cite your sources. FINAL DOCUMENT LAYOUT One PDF with the following sections denoted using page numbers, headers and a table of contents: Team Contract UML Diagram Design Document Template (note that the work you complete in setting up the Git repository will be referenced here and you will provide information on how to access your Git repository here). ● ● RUBRIC Item Team Contract Git Repository Class Diagram Design Document Template 2022 Criteria Completed, signed by each team member and scanned as the first page in the PDF document Repository created, all group members have read/write access and instructor is able to view the repository. Repository should be complete (contain all base code) Proper syntax is used and the diagram is complete and is created using a Computer Assisted Software Engineering (CASE) tool such as Visual Paradigm. All sections of the template are complete. The Points 10 10 10 10 SYST 17796 Deliverable 1 Weight 1 4 3 2 Item 2022 Criteria design choices described represent the principles of 00 Design studied in class and are well articulated and presented. Points SYST 17796 Deliverable 1 Weight 2/n SYST 17796 PROJECT 2023 OVERVIEW 1. Project Background and Description The project in this course is designed to allow students to extend a given code base and incorporate the learning outcomes of the course by applying them to a larger project of interest. Students can self-select groups of 1-4 students with the understanding that the project is written to be enough work for 4 students. Students working alone will not be given less work, regardless of the circumstances. All students in a given group will receive the same grade on each deliverable and all students in the group are responsible for the academic integrity of each part of each deliverable. Students are expected to sign a group contract at the beginning of the project and submit it with Deliverable 1. The act of working in a group and the challenges that come with it are an expected part of the project completion and should be anticipated as part of student workload management. 2. Project Scope The project is meant to be fun! Beginning with the code given in Deliverable 1, each group will create its own extension to the basic card game code this is given as the base. This means any game played with cards is eligible, so pick something interesting to your group and that will be challenging for you to work on but allow you to fulfill the project requirements. Examples of possible projects are: ● ● ● ● Go Fish Blackjack War Spot It Uno Skip-Bo Any Card Trick 3. High-Level Requirements The team will finish the code to completion where the game can be played to some desired level. The group will also be responsible for creating and managing a project repository using Git and creating, running and managing tests for the project code. Written sections of the Deliverables are meant to be submitted via PDF and should follow APA citation guidelines with a professional writing tone. These are an important part of being able to articulate and justify your design choices along the way. 4. Deliverable Breakdown Each deliverable is worth 10% of the overall grade Individual Rubrics are included on each deliverable description. 5. High-Level Timeline/Schedule Note that the weeks given are based upon a 13-week term and will change for classes affected by holidays/closures/cancellations. 2 Week 6 10 13 Deliverable 1 2 3