Announcements Class is cancelled on Monday 11/22 The final exam will be take-home, two-three questions, optional for those who want to boost their mid-

Slides:



Advertisements
Similar presentations
CSE Senior Design II Final Project Presentation. 1  Monday, May 6 th 8:00 AM in ERB 103  Begins sharply at 8:00 AM in ERB minutes  Each team.
Advertisements

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
COMP4710 Senior Design Process Documentation and Deliverables.
Read Me (Delete this slide.) Required Template  Do not edit the Slide Masters.  Do edit the Handout Master (6 Slides Per Page) o In the lower left footer,
Read Me (Delete this slide.) (1 of 2) Presenting  The purpose of the alpha presentation is to demonstrate the alpha version of your software in order.
CS 197 Computers in Society Fall, Welcome, Freshmen!
Team READ THIS SLIDE CAREFULLY Beta Demonstrations will be given by each team at our all-hands meeting on the dates listed at All-Hands Meeting Agendas.All-Hands.
Team : READ THIS SLIDE CAREFULY Project Plan presentations will be given by each team at our all-hands meeting on the dates listed at All- Hands Meeting.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
CEP Welcome September 1, Matthew J. Koehler September 1, 2005CEP Cognition and Technology Who’s Who?  Team up with someone you don’t.
CSE 322: Software Reliability Engineering Topics covered: Course outline and schedule Introduction, Motivation and Basic Concepts.
International Management MSE-608A International Management Tal Ovadia Welcome to.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Team : CSE 498, Collaborative Design.
Introduction to SEG 5010 Hong Cheng 2009/10 Second Term.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
COMP4710 Senior Design Richard Chapman. Outline What is Senior Design? What is Senior Design? Course Structure Course Structure End of Cycle Binder End.
Read Me (Delete this slide.) (1 of 2) Presenting  The purpose of the beta presentation is to demonstrate that the software portion of the project is complete.
IACT303 – INTI 2005 World Wide Networking Welcome and Introduction to Subject. Penney McFarlane The University of Wollongong.
Preparing Technical Presentations CIVL 1101, Fall 2008 Project 1: Topographic Model.
Assignment 3: A Team-based and Integrated Term Paper and Project Semester 1, 2012.
Computer Network Fundamentals CNT4007C
BIT 115: Introduction To Programming1 Sit in front of a computer Log in –Username: 230class –password: –domain: student Bring up the course web.
Welcome to CS 3260 Dennis A. Fairclough. Overview Course Canvas Web Site Course Materials Lab Assignments Homework Grading Exams Withdrawing from Class.
COMP 523 DIANE POZEFSKY 20 August AGENDA Introductions Logistics Software Engineering Overview Selecting a project Working with a client.
COMP Introduction to Programming Yi Hong May 13, 2015.
Computer Networks CEN 5501C Spring, 2008 Ye Xia (Pronounced as “Yeh Siah”)
ECE450 - Software Engineering II1 ECE450 – Software Engineering II -the sequel- Winter Spring 2007 Instructor: Jorge Aranda.
CSE 436 Software Engineering Workshop Course Overview Christopher Gill CSE 436 January 2007 Department of Computer Science and Engineering.
COMP 523 DIANE POZEFSKY 19 August CHAOS REIGNS.
Welcome to CSIS10A Computer Science: Beginning Programming Please, take a syllabus.
Fall 2004FSU CIS 5930 Internet Protocols1 Welcome to CIS 5930 Internet Protocols Time: 5:15PM-6:30PM, TTh Location: Love 301 Fall 2004, 3 credits.
21 August Agenda  Introductions  Logistics  Selecting a project  Working with a client.
CSE Senior Design II Final Project Presentation. 1  This critical formal review serves as your Final Exam for SD2  Date: Friday, December 5 th, 2014.
Lecture 7: Requirements Engineering
Introduction to CS Senior Design Project I / II Prof. Dr. H. Altay Güvenir.
Fall 2o12 – August 27, CMPSC 202 First Day Handouts  Syllabus  Student Info  Fill out, include all classes and standard appointments  Return.
L8 - March 28, 2006copyright Thomas Pole , all rights reserved 1 Lecture 8: Software Asset Management and Text Ch. 5: Software Factories, (Review)
CSE Senior Design II Final Project Presentation. 1  This critical formal review serves as your Final Exam for SD2  Date: Friday, December 6 th, 2013.
Final Exam Review Session 14 LBSC 790 / INFM 718B Building the Human-Computer Interface.
CSE Senior Design II Day 1: Getting Organized Spring 2015 Instructor: Manfred Huber.
CS352 Software Engineering Project (Software Engineering in the Small) Michael Oudshoorn and Ray Babcock.
1 04/30/2003 ECE 554 COUNTDOWN DEMONSTRATION  Scheduling  Miscellaneous  Content FINAL REPORT  Check-In  Content FEEDBACK.
CSE Senior Design II Final Project Presentation. 1  Friday, May 3 rd 8:00 AM in ERB 103  Begins sharply at 8:00 AM in ERB minutes  Each team.
Introduction to Financial Management. Overview of Financial Management Introduction Keys to Success Recitations Class Structure - Syllabus Text – Financial.
COP4020 INTRODUCTION FALL COURSE DESCRIPTION Programming Languages introduces the fundamentals of the design and implementation of programming languages.
Computer Networks CNT5106C
Complete Design & Gate Review. Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard.
Course Overview Stephen M. Thebaut, Ph.D. University of Florida Software Engineering.
GEOMETRY MRS. GARIBALDI
CSE Senior Design II Final Project Presentation. 1  Friday, May 6 th 8:00 AM in GACB 105  Begins sharply at 8:00 AM in GACB minutes  Each team.
Computer Network Fundamentals CNT4007C
Welcome to CS 4390/CS5381: Introduction to Formal Methods
Computer Networks CNT5106C
Introduction to CS Senior Design Project I / II
Algebra II Fundamentals
Read Me (Delete this slide.) [1 of 2]
School of EE and Computer Science
Introduction to CS Senior Design Project I / II
Introduction to CS Senior Design Project I / II
Computer Networks CNT5106C
Read Me (Delete this slide.) [1 of 2]
Guidelines for Group Projects and Papers
Guidelines for Group Projects and Papers
Announcements Quiz 5: grades and solution posted
Introduction to CS Senior Design Project I / II
Computer Networks CNT5106C
Read Me (Delete this slide.)
Final Project Presentation
CSCI 203: Introduction to Computer Science I
Presentation transcript:

Announcements Class is cancelled on Monday 11/22 The final exam will be take-home, two-three questions, optional for those who want to boost their mid- term grade. Posted by 12/6, due 12/12.

Phase 5 and beyond Keys to earning your A

Team member contributions Teams may send me an , directing what percentage of the team grade is to be attributed to each team member Those who did not contribute, should be granted zero credits

The Peer Review Your rating is 10% of your grade. I’m serious. Do one for each team member and for yourself Your score: #you do - #bad Bring them to your demo Forms will be on the web site Hardcopy please

1. This team member was regularly available. 2. This team member regularly read and used in relation to the team project. 3. This team member was supportive of the activities of other members. 4. This team member started work with sufficient time to finish on time. 5. This team member tried hard regardless of the value of their contribution. 6. This team member was essential to our team's success. 7. This team member actively participated in Phase I. 8. This team member actively participated in Phase II. 9. This team member actively participated in Phase III. 10. This team member actively participated in Phase IV. 11. This team member HAD the background to significantly contribute to the team effort.

The Demo Your team is required to present your system design and to PROVE THAT YOUR PROJECT IS FEASIBLE You must distribute a “brochure” at the demonstration. The brochure should be an advertisement for your system’s capabilities and your hard work

The Demo System Architecture Feasibility Look-and-Feel Main Screens

Grading We fill out a form, and use subjective assessment of 11 categories (more later) Full participation by all team members Professionalism of the presentation Creativity and professionalism of the brochure Usefulness of the system in solving the problem Sensitivity to the customer and users Sound SW Engineering applied Creativity and usefulness of the user interface General attention to detail Fun & karma component

The Brochure Each group is required to hand it to the customer at the time of their presentation, so that we can remember your demo. This should include some critical screen snapshots and team identification information. This is critical so that we can distinguish you from the other teams. The brochure is similar to materials customers expect in real-world demonstrations.

The Brochure Tri-fold, color if possible (see me if this is an obstacle) Include Team # (letter?) and names One side commercial One side technical with demo agenda (this will focus the customer's attention so that the demonstration can be completed in a timely manner)

The Demo Prepare a 15-minute Customer Oriented Demonstration for your Project –We apologize in advance for giving you only 15 minutes to display all of your creativity and hard work –A timer will end your demo at 15 minutes, so plan your presentation well.

The Demo & presentation Everyone should participate Consider this a formal design review. Dress nice Consider it an attempt to get a contract from the customer

The Demo - presentation Present a “picture” of the final product Describe the computer architecture Show the user screens Identify problem areas Justify the cost as derived from Phase 4

Your software – usefulness in solving the problem State the problem explicitly State how you solve that problem in one sentence Why you discarded other solutions

Your software - Creativity and usefulness of the user interface Natural mapping Remember the good and bad examples Semantic use of color User - not CS - jargon

Your software – sensitivity to the customer and user It better not look like it was designed and meant to be run by CSE and CEN students. The language should be problem- space

Your software architecture - General attention to detail Consistency Misspellings are bad Seamless boundaries Context-sensitive help

Your software - Fun & karma component Please don’t stress out Attitude can overcome a meager baseline

Schedule Submissions by Sun 12/5 11:55pm Monday 12/6 - 9am: i/f c g 4pm: m j r Wed 12/8 - 9am: h b a 4pm: q k l Fri 12/10 - 9am: d e p 4pm: s n