READ THIS SLIDE CAREFULLY The intent of this presentation is to provide an “Executive Summary” of your project to Design Day attendees and judging panel.

Slides:



Advertisements
Similar presentations
A method for addressing any large problem. Carefully consider the problem. Define the problem. Ask yourself the following questions: What is it that I.
Advertisements

GE 121 – Engineering Design Engineering Design GE121 Oral Presentations Lecture 10.
Systems Analysis and Design in a Changing World
Chapter 8: Evaluating Alternatives for Requirements, Environment, and Implementation.
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.
Engineering H193 - Team Project Spring Quarter 2003 P. 1 Progress Reports Week 4 Day 1.
EPICS Design Review Template Notes:  Use the template as a guide to preparing your presentation….you may add, subtract, or rearrange as needed to tell.
Team READ THIS SLIDE CAREFULLY Alpha 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 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.
7. Team Project Schedules September 22, 2004 Wayne Dyksen Brian Loomis Department of Computer Science and Engineering Michigan State University Fall 2004.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
The Design Process. Analysis Think – what should the final design do? List customer requirements Consider constraints – balance tradeoffs Define specifications.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Team : CSE 498, Collaborative Design.
6. & 7. Teams: Technical Specification / Schedule Project Title Team Member 1 Team Member 2 Team Member 3 Team Member 4 Department of Computer Science.
6. & 7. Team Technical Specifications and Schedule Wayne Dyksen Brian Loomis Department of Computer Science and Engineering Michigan State University Spring.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter 2007 Progress Reports Week 4 Day 1.
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.
8 Systems Analysis and Design in a Changing World, Fifth Edition.
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.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
What is Business Analysis Planning & Monitoring?
2005/05/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Intro for SE’s (this slide to be deleted from your final deck!) This can be used as a template for an “intro” / executive summary The point of this deck.
10/10/2015 IENG 471 Facilities Planning 1 IENG Lecture END Project Report Requirements & Project Presentation Information.
Senior Design Experience Semester II Project Requirements and Timeline
COMP 208/214/215/216 – Lecture 8 Demonstrations and Portfolios.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
6/3/2016 IENG 471 Facilities Planning 1 IENG 465 – Final Design Project Report & Presentation Requirements.
Lab Course / Praktikum: S ummer Semester 2012 Project Management and Software Development for Medical Applications Computer Aided Medical Procedures (CAMP),
Computer Science and Engineering - University of Notre Dame Jimmy Neutron CSE 40827/60827 – Ubiquitous Computing December 9, 2009 Project Presentation.
4-2 CHAPTER 4 Engineering Communication © 2011 Cengage Learning Engineering. All Rights Reserved.
Research Methods Technical Writing Thesis Conference/Journal Papers
Computer/Human Interaction Spring 2013 Northeastern University1 Name of Interface Tagline if you have one (80 chars max, including spaces) Team member.
Read Me Carefully (Delete this slide.) Required Template  Do not edit the Slide Masters.  Do edit the Handout Master (6 Slides Per Page) o In the lower.
Project Management Requirements Prof. Ralph Locurcio, PE Dr. Troy Nguyen, PE.
Engineering H193 - Team Project Spring Quarter Gateway Engineering Education Coalition P. 1 Progress Reports Week 4 Day 1.
NOTE: To change the image on this slide, select the picture and delete it. Then click the Pictures icon in the placeholder to insert your own image. PBIS.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
 System Requirement Specification and System Planning.
Read Me (Delete this slide.) [1 of 2]
Read Me (Delete this slide.) [1 of 2]
Read Me (Delete this slide.) [1 of 2]
EPICS Design Review Template Notes:
Read Me (Delete this slide.) [1 of 2]
Read Me (Delete this slide.) [1 of 2]
Read Me (Delete this slide.) [1 of 2]
Team members: Project Manager: Facilitator: Customer Liason:
Read Me (Delete this slide.) [1 of 2]
Read Me (Delete this slide.) [1 of 2]
Team [Team Name] Alpha Presentation
ATS Architecture Design Solution Intent
Team [Team Name] Beta Presentation
Read Me (Delete this slide.) (1 of 2)
Read Me Carefully (Delete this slide.)
CSE 498, Collaborative Design
Employee engagement Delivery guide
Managing Work in the New Computing Environment March 14, 2003
Read Me (Delete this slide.) (1 of 2)
CIC BIM Competition Presentation Template & Content Guide
Team [Team Name] Alpha Presentation
Read Me (Delete this slide.)
04/18: Team Project Video Status Reports
Read Me (Delete this slide.) (1 of 2)
Team [Team Name] Beta Presentation
Read Me (Delete this slide.) (1 of 2)
Read Me (Delete this slide.) (1 of 2)
Instructions - Delete this first page
Presentation transcript:

READ THIS SLIDE CAREFULLY The intent of this presentation is to provide an “Executive Summary” of your project to Design Day attendees and judging panel. Design Day Presentations will be given by each team during scheduled timeslots during Design Day on Friday, April 30, The team presentation schedule can be found online at: Presenting teams are required to dress business professional. Teams should plan to present for approximately 5 minutes, with the remainder of any time during your timeslot reserved for questions from the judging panel. Significant deviations from the five minute mark may impact judging related to your presentation. The objective of your presentation is to provide a concise overview of your project, giving important information related to the project. Although the judging panel will have viewed your project video and technical specifications, your presentation should accomplish two goals: –Provide someone who may not have viewed your project materials with a high-level understanding of your project; and –Highlight particular items you feel are more important than others. The remainder of this presentation provides a template for information that may be highly relevant for a presentation of this nature. However, resist the urge to address every piece of information suggested. Pick and prioritize items that provide a good high-level overview. Miscellaneous wisdom for an Executive Summary presentation: Avoid the tendency to drive into the details before you have painted a very high level view of the information you need to present. With a short presentation, like this, do not feel obligated to have each team member participate in giving the presentation. If you can smoothly transition from member to member in the presentation, you can do so, but do not feel obligated. NOTE: The red notes on the subsequent slides are suggestions for content. Consider what information best presents your project, including what is offered in “red”. (And don’t forget to take the red notes out in your final presentation) Delete this slide from your presentation.

Project Executive Summary Department of Computer Science and Engineering Michigan State University Spring 2010 Team CSE 498, Collaborative Design

Team Project Overview Information to be considered on this slide should include: Client / client business Short project name Description of problem being solved and why it is a problem How was project “given” to you (not how you chose it, but how did client define the project for you?) Intended use of end product –Was project proof of concept – if yes what will project show and where will it be used downstream? –Was project actual product – if yes how/when will it be deployed? 3

Team Solution Overview Consider the following on this slide: Conceptual picture of deployed solution Interaction of solution with other systems or people/companies High-level view of solution, diagramming particular layers such as user interface, database engine, computational layer, communications layer, etc. 4

Team Technical Architecture Consider the following for inclusion on this slide: Discussion of technologies deployed in project Discussion of technology of interfacing points and connections to project sponsor data and/or systems Discussion of technology decisions made and why (including constraints you had to work around) Discussion of technology changes made during project Discussion of technology limitations of solution 5

Team Questions At this point, entertain questions.