The End …but there’s still some work to do. What Remains 1.Final Project Submission (20% of final grade) 2.Take Home Final (10% of final grade) 3.In-Class.

Slides:



Advertisements
Similar presentations
COMP4710 Senior Design Process Documentation and Deliverables.
Advertisements

MAT 3751 Analysis II Winter 2014
MAT 3749 Introduction to Analysis Fall 2013
CSE 113 Introduction to Computer Programming Lecture slides for Week 10 Monday, October 31 th, 2011 Instructor: Scott Settembre.
Game Inception and Design Project 1 Due dates: –Wednesday, January 18th: First-draft –Monday, January 23rd: Peer Review due –Thursday, January 26th: Final.
Game Inception and Design Project 1 Due date: –Wednesday, May 24 th (in class)
SLIDE 1IS 202 – FALL 2003 Lecture 26: Final Review Prof. Ray Larson & Prof. Marc Davis UC Berkeley SIMS Tuesday and Thursday 10:30 am - 12:00.
Transitioning to XP or The Fanciful Opinions of Don Wells.
Complete and Present Prototype Project 6 Status report: Tuesday, October 5 th Due: Saturday, October 9 th Presentation: Tuesday, October 12 th.
COMP4710 Senior Design Richard Chapman. Outline What is Senior Design? What is Senior Design? Course Structure Course Structure End of Cycle Binder End.
Russell Taylor Lecturer in Computing & Business Studies.
A Technical Game Project 4 Due dates: Game Idea Friday, March 16 th Game Plan Friday, March 23 rd Web Page Sunday, April 9 th First Playable Wednesday,
Big Projects  Part of this class is about picking a cool software project and building it 1.
Welcome to CompSci 100! As You Arrive… Make sure you grab a syllabus packet. Read through it. I will be covering the most essential points in my talk,
GRADE 11 COMP-SCI ICS3U. COURSE DESCRIPTION Javascript & HTML5 Artwork- A bit of photoshop Coding skills, hardcore coding skills- We are using the basics.
CS 304 Project Kirk Scott 1. The specifications for this project will be subject to possible minor revision as the semester progresses depending on what.
Mark Nelson What are game engines? Fall 2013
EECE 310 Software Engineering Lecture 0: Course Orientation.
Z26 Project Management Introduction lecture 1 13 th January 2005
Use Case Modeling. Watch the video on use cases Review at minute 2:41-3:37.
Today’s class 1.Refamilizaring ourselves with the big picture. 2.Debriefing preliminary reflections and user research. 3.Characterizing the user/audience.
Software Specification and Design Sirisin Kongsilp & James Brucker.
Design Patterns in Java Chapter 1 Introduction Summary prepared by Kirk Scott 1.
TGP2281: Game Programming III also better known as Game AI.
Patterns and Reuse. Patterns Reuse of Analysis and Design.
Coursework Documentation INTRODUCTION TO INTERNET.
The content of these slides by John Galeotti, © Carnegie Mellon University (CMU), was made possible in part by NIH NLM contract# HHSN P,
Excellence is a Habit Feb Lecture 14 We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle.
1 Design and Integration: Part 2. 2 Plus Delta Feedback Reading and lecture repeat Ambiguous questions on quizzes Attendance quizzes Boring white lecture.
Documentation. Your documentation must fit the needs of your audience. It’s always better to say one thing that is useful, as opposed to many things that.
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
IST 210: Organization of Data
Format of the Final Project. Final Project The Final project is due 1 week from today. To complete the project students must prepare the following – A.
COMN Organizational Communication Lecture 1a
Final Major Project Feedback. How I got feedback: I showed my FMP to a focused audience group I created a questionnaire on Google docs which included.
Jin-Ning TiohComputer Engineering Tony RossComputer Engineering Dave ZajicekComputer Engineering Alex BurdsComputer Engineering Abstract In recent years,
Technical Description Project Project 2. Overview Write a technical description of a process related to e-waste streams for a lay audience – Work solo.
Project. Research Project Due: – Project report due Monday midnight Delayed a bit due to popular demand Can accept an even higher delay (Tuesday at noon)
Prepare a Game Treatment Project 3 Due dates: Tuesday, September 14 th, in class.
Version Control and SVN ECE 297. Why Do We Need Version Control?
BIT 142:Programming & Data Structures in C#. 2 Syllabus : Book info BIT 142 uses the book fairly extensively –I would recommend getting it The edition.
Jump to first page Craft & Design Final Project Folio.
Vision using Wavelets CIS 541 Team 6 Presentation 6 Megan Enns Tim Weninger Brett Wolfington CIS 541 Team 6 Presentation 6 Megan Enns Tim Weninger Brett.
E-Mission + Team of undergraduates = ??? Background and motivation.
What to do week 5! In preparation for the client meeting! Please see the schedule for everything else…
CS 241 Section Week #1 January 26, Topics This Section HW #1 SVN Review (…by the command line!) C Code Examples.
IST 210: ORGANIZATION OF DATA Introduction IST210 1.
1 CERN School of Computing CSC 2015 Feedback Nikos Kasioumis Giuseppe Lo Presti.
CSS 290: Video Games and Computer Programming. CSS 2902 Reading: Intro To C# & XNA PLAD Ch 1 GMA Ch 1, 2.
VIP: Design Notebooks Julie Sonnenberg-Klein Academic Program Manager Vertically Integrated Projects Program.
HPC audit One radiographers experience. Introduction So, how did I feel when I opened the letter saying I was being audited? Quite frankly, it sucked!!
FINAL PRESENTATION 25% of Your Total Grade. PRESENTATION INSTRUCTIONS Give a short presentation based on one of the main topics from the text (the topics.
HCS 451 Week 5 Learning Team Tools and Decision Making for Ongoing Performance Management Presentation To purchase this material click below link
Lesson 08.
421 Review Questions Does software engineering add documentation that slows down the project? Is there one software process that is better than the others.
Proposals and Progress Reports
J200/02 Music and News Annotated Sample Assessment Materials.
CMSC201 Computer Science I for Majors Lecture 11 – Program Design
CSE 5912 Student Presentations
Introduction to Programming 2
I494: Designing and Developing an Information System
Final Project Details Note: To print these slides in grayscale (e.g., on a laser printer), first change the Theme Background to “Style 1” (i.e., dark.
English 1301 Week 6, Day 1 February 20, 2018.
BIT 142:Programming & Data Structures in C#
[Solomon Westerman] [PM]
Studio day : Monday February 4
Finding and using code online
CS a-spring-midterm2-survey
Your Project Title (It is YOUR project, not the team's project, not CAM2) Your Name Date.
CS a-spring-midterm-survey
Presentation transcript:

The End …but there’s still some work to do

What Remains 1.Final Project Submission (20% of final grade) 2.Take Home Final (10% of final grade) 3.In-Class Final (5% of final grade)

Final Vooga Submission 1.Overall Group Functionality (25%) – Functional Game Framework, with many useful features – Functional Level Editor, with some useful features – Demo Game that Uses The Features – DEMO VIDEO 2.Overall Group Design (25%) 3.Individual Functionality (25%) 4.Individual Design (25%)

Final Vooga Submission 1.Overall Group Functionality (25%) 2.Overall Group Design (25%) – Team Design Doc. A explanatory documentation that explains how to use all the various features of the framework, including things like level editor integration. – Written for a game developer who wants to build a game with your framework – Use plenty of example code! (maybe cribbed from your demo game) – Don’t just explain the easy stuff. Include discussion of how to extend the framework if you need custom functionality. – NOT 8 design docs stapled together – Does NOT need to talk about design rationale 3.Individual Functionality (25%) 4.Individual Design (25%)

Final Vooga Submission 1.Overall Group Functionality (25%) 2.Overall Group Design (25%) 3.Individual Functionality (25%) – Write a short document that explains what features and classes you implemented – Obviously, you should have implemented quite a bit of stuff – Everything must be in the git repo, and integrated (NOT “oh well you just run this separate thing and you see…”) – If you break your team’s git repo on Thursday night, you will be penalized 4.Individual Design (25%)

Final Vooga Submission 1.Overall Group Functionality (25%) 2.Overall Group Design (25%) 3.Individual Functionality (25%) 4.Individual Design (25%) – Your design doc – From the Vooga website: “Your design exemplifies a strong command of the design concepts discussed in this course. You have chosen a good balance between useful default functionality and providing the ability for custom expansion. Your design is sophisticated, involving several different classes interacting in an interesting way that goes beyond a single pattern. Your explanation is clear and shows effort, including code samples and diagrams where appropriate. Your design document shows a detailed command of the terminology and discusses several design alternatives each of which is a viable design in its own right.”

Take Home Final You’ve got it Due 5/4 2pm (time the in-class final starts) Any questions?

In class final Similar to Midterm, covers 1 st half of semester too Patterns covered: 1.Memento 2.Iterator 3.Proxy 4.State 5.Intepreter 6.Visitor I will send out sample questions for these patterns…during finals week