0
CSE116 Scrabble Project TEAM WHY?
Stage 1 <ul><ul><li>Design a text-based game </li></ul></ul><ul><ul><ul><li>needed to respond to Place, Retract, Exit, and...
Stage 1 (cont) <ul><li>Used a Scanner to read the User Input </li></ul><ul><li>Wrote a Text-Based Input class to decouple ...
Stage 2  <ul><ul><li>We now used Team C's Stage 1 code </li></ul></ul><ul><ul><li>We now needed to implement GUI into this...
Stage 2 (cont) <ul><li>Once decoupling was finished, we tried using a drag and drop method for placing and retracting piec...
-Current Status / Stage 3 <ul><li>Working on implementing RMI. </li></ul><ul><li>2. Special Score Spaces </li></ul><ul><li...
-Current Status Trie Dictionary is Complete. -Constructed using BRStruct<String>. -Uses visitors for validating and loadin...
-What we Learned about Coding… -The importance of Decoupling code. -The usefulness of commenting code and having accurate ...
-What we Learned about Teams… -Dividing up responsibilities to increase efficiency. -Working with conflicting schedules to...
Upcoming SlideShare
Loading in...5
×

CSE116

180

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
180
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "CSE116"

  1. 1. CSE116 Scrabble Project TEAM WHY?
  2. 2. Stage 1 <ul><ul><li>Design a text-based game </li></ul></ul><ul><ul><ul><li>needed to respond to Place, Retract, Exit, and Redraw Board </li></ul></ul></ul><ul><ul><ul><li>Did not need to check a dictionary </li></ul></ul></ul>
  3. 3. Stage 1 (cont) <ul><li>Used a Scanner to read the User Input </li></ul><ul><li>Wrote a Text-Based Input class to decouple the functionality of game from the input </li></ul><ul><li>Unfortunately, we weren't allowed to use that code in Stage 2. </li></ul>
  4. 4. Stage 2 <ul><ul><li>We now used Team C's Stage 1 code </li></ul></ul><ul><ul><li>We now needed to implement GUI into this, as long as check the words in a dictionary </li></ul></ul><ul><ul><li>The most difficult part was decoupling this code into a TextViewer Class and a GUIViewer Class. </li></ul></ul>
  5. 5. Stage 2 (cont) <ul><li>Once decoupling was finished, we tried using a drag and drop method for placing and retracting pieces from the board. </li></ul><ul><li>This was overly complicated when dealing with LayoutManagers. </li></ul><ul><li>In the nick of time, success! </li></ul>
  6. 6. -Current Status / Stage 3 <ul><li>Working on implementing RMI. </li></ul><ul><li>2. Special Score Spaces </li></ul><ul><li>-We picked a Stage 2 codebase that would allow easy implementation </li></ul>
  7. 7. -Current Status Trie Dictionary is Complete. -Constructed using BRStruct<String>. -Uses visitors for validating and loading the words.
  8. 8. -What we Learned about Coding… -The importance of Decoupling code. -The usefulness of commenting code and having accurate documentation. -The benefit of running JUnit tests to verify code is working properly. -How to use consistency in our coding and following standards.
  9. 9. -What we Learned about Teams… -Dividing up responsibilities to increase efficiency. -Working with conflicting schedules to find time to work. -Effective communication and criticism. -Knowing everyone’s strengths and weaknesses and how to use them to the teams benefit.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×