Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
Cases Page
Project Description
Our term project was to design and create a slide show of images that also includes an editor. Basically, we coded a program that mimics some of the functionality in PowerPoint and Photo Shop. Here we will pressent the last 3 Milestones of the term project (Milestones 3-5) which were group deliverables. Here is a list of the specifications for all 5 Milestones:
Also, we will present advice on having a successful group experience, things to look out for in squeak, and general good advice.
Keys to Group Success
- Meet Often!!! Our group met twice a week and 3-4 times a week during the week leading up to the due date of a Milestone.
- Group Coding Sessions We highly recommend having these for these main reasons:
- Information Sharing - good to have others around so you can get help from them
- Motivation - it keeps people on track and thinking about the project, and with the rest of the groups members working, one tends to work too
- Status - group coding sessions allow everyone to know what each other is working on and how far along that person is. This prevents the "90% done" phenomenon.
- Planning - going along with status, group coding sessions allow for easier planning of future meetings because everybody is on the same page. Also, if a part of the design needs to be changed everybody can discuss and implement the changes together.
- Bonding - It is very important to spend time with your group members in order to establish friendly relations beyond the "give me your code so I can integrate it" scenario. You will be working together for half of a semester, and as friends you will be more able to cope with inevitable setbacks that may cause tension in the stressful last hours before it's due.
- Integrate Often!!! Relying on one huge last minute integration is a recipe for disaster. USE CHANGE SETS! Learn value of 'code' button while filing them in. The 'version' button for messages is very helpful incase something goes wrong and you want to revert to an older version.
- Designate an Administrative Liason This person will be responsible for all of the administrative tasks that need to be taken care of like group correspondance, setting meeting times with the TA, turning in the assignments, following up on questions the group may have for the TA or Professor, etc.
- Stick to Schedule For the design Milestone you will have to come up with a schedule of meeting times and group member responsibilities along with their due dates. Adhering to this schedule will keep you on track. Don't cancel meetings ever! They will be more help to you than you think, even if quick.
General Advice
- Read and Re-read Specifications Milestone requirements are layed out for you very well, pay attention to them at all times. This will keep the members of your group from getting mixed ideas on what needs to be accomplished.
- Adhere to Design Your Design Milestone lays a good foundation for the rest of your project, stick to it as much as possible but don't be affraid to change it as your project grows. When your design does change, keep your design updated for everybody to see. Remember that fewer classes is not better.
- Ask Questions Don't be affraid to go to either the TA or Proffessor with any questions you might have. Keep in mind that TA's are very lonely durring their office hours and are often anxious to dish out extra points if you go see them .
- Required Functionality First! Finish what you have to do before you go the extra mile to clean up the code/UI. When you are finished, do go back for both degheto-ization and unghettification =).
Common Problems with Squeak
- Random Crashes Be weary, Squeak has a tendancy to become corrupted and lock up.
- Save Image Constantly!! We've all lost important code, and know how annoying it can be. Also, make sure to file out your category often so you can file it back in to a new image if your current image becomes corrupted.
- Keep a Spare Clean Image Not only do you need a clean Squeak image for testing your final Project, but your image may become corrupted along the way, and hence you will need a backup.
- Comments are Lacking The majority of Squeak is not commented well, be prepared to dig through many layers of uninterpretable code to find the answers you need.
Milestones
- Milestone 3: Design Everything Plan, Analyze, and Design the Entire System.
- M3.zip (Descriptions of contents below)
- Scenarios.doc Includes scenarios that account for all major functionality, and that touch on every class in our design.
- CRCcards.doc Graphical representation of our CRC cards, not including GUI classes.
- ClassDiagram.gif and ClassDiagram.vsd UML Class diagram of all of our M3 classes, including GUI classes.
- ClassDescriptions.doc Detailed and understandable descriptions and names of all classes, including GUI classes.
- Timeline.doc Schedule of group events, including meetings, and deadlines for the semester.
- Responsibilities.doc List of which group member is accountable/responsible for each functionality.
- Milestone 4: Ordered Slide Shows and Advanced Photo Manipulation
- M4.zip (Descriptions of contents below)
- Scenarios.doc Includes scenarios that account for all major functionality, and that touch on every class in our design.
- CRCcards.doc Graphical representation of our CRC cards, not including GUI classes.
- ClassDiagram.gif and ClassDiagram.vsd UML Class diagram of all of our M4 classes, including GUI classes.
- ClassDescriptions.doc Detailed and understandable descriptions and names of all classes, including GUI classes.
- README.txt Contains directions and useful tip for operating the program. Tries to clarify any confusing behavior.
- cs2340.st Category that contains our Squeak code. Implements red-eye removal, pixel filtering, cropping, scaling, rotating of the images, ordering of the image thumbnails, along with save and save as functionality for the images.
- Milestone 5: Slide Shows with Sound and Text Annotations
- M5.zip (Descriptions of contents below)
- Scenarios.doc Includes scenarios that account for all major functionality, and that touch on every class in our design.
- CRCcards.doc Graphical representation of our CRC cards, not including GUI classes.
- ClassDiagram.gif and ClassDiagram.vsd UML Class diagram of all of our M5 classes, including GUI classes.
- ClassDescriptions.doc Detailed and understandable descriptions and names of all classes, including GUI classes.
- README.txt Contains directions and useful tip for operating the program. Tries to clarify any confusing behavior.
- cs2340.st Category that contains our Squeak code. Implements the above M4 functionality in addition to allowing background music, textual annotations which are saved and spoken with the Slide Show, sound annotations with both specified sound file, and user recorded sound files, converting of a slide show with background music, sound and text annotations into HTML pages.
- buttonNext.jpg and buttonPrevious.jpg Used on HTML pages for navigating through the slide show. Place these files in the 'z' drive.
Links to this Page
- Case last edited on 29 July 2009 at 11:50 pm by c-76-97-208-233.hsd1.ga.comcast.net
- Michael Helman-Darley last edited on 29 July 2003 at 1:04 am by aep28.eastnet.gatech.edu
- Mandy Zielonka last edited on 25 July 2003 at 7:43 pm by conway-w2k.cc.gatech.edu
- Captain Kirk and the Crew last edited on 29 July 2003 at 12:50 am by aep28.eastnet.gatech.edu