CSE Design Lab Milestone IV Dennis O'Flaherty James Hopkins Dave Festa Karl Schwirz.

Slides:



Advertisements
Similar presentations
Whats next in your presentations?. Title Slide Background Problem Statement Solution System Diagram Electrical Circuits Mech. Drawings Code Sample(s)
Advertisements

University of Colorado at Boulder – ECE Capstone – CDR – October 16, 2007.
Indora Integration Plan Project 4 Jim Gedarovich, Phil Ho, Joe Dowden.
CSE Design Lab – Milestone 2 James Hopkins Dave Festa Dennis O’Flaherty Karl Schwirz.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
Preliminary Design Review
RPI NEES SITE 2D Shaker & 2D Laminar Box 4-D In-flight Robot Web-Based Data Acquisition Advanced Sensing Other Aspects –Data Management –Tele-observation.
6. & 7. Teams: Technical Specification / Schedule Project Title Team Member 1 Team Member 2 Team Member 3 Team Member 4 Department of Computer Science.
OHT 14.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality infrastructure components The need for procedures and.
MyBeats Michael Smith. Integration Plans Entry Criteria Integration and Testing Error Documentation and Resolution Exit Criteria.
EE 296 TEAM “DA KINE” MICROMOUSE PROJECT PROPOSAL Team members: Software Group - Henry, James Roles : tracking, mapping, guidance, interface Hardware Group.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Voice Controlled Helicopter Team Members: Jonathan Lam, Mian Zhu.
Team Members: Nahiyan Ali Shrabantee Chatterjee Vaibhav Kumar Alex Weigel Tao Zeng Advisor: Dr. Mani Mina Client: Senior Design Dr. Gregory Smith.
NVLAP Overview and Accreditation Process March 2006.
RUP Fundamentals - Instructor Notes
1 Software Construction Software Construction Chapter 1.
Golf Swing Robot EE 486 Project Presentation College of Engineering and Technology Presented by Nasser Almarri.
Emanuel Gonzalez Antonio G. Rodriguez Arnaldo A. Oliver Raul Y. Mora.
FotoGazmic Software (From left to right: Chad Zbinden, Josey Baker, Rob Mills, Myra Bergman, Tinate Dejtiranukul)
Module 7 Session 7.3 Visual 1 Module 7 Planning and Scheduling with the Critical Path Method Session 7.3 The computer and project management.
Software Costs Hardware Costs Total Costs % Figure 1.1 Software and hardware development costs in the industrial robots.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
Testing 1 © Minder Chen, Source: Developing Web Applications with Microsoft Visual Basic.NET and Microsoft Visual C#.NET Testing Test plan objectives.
CSI-MAXIMUS, Inc CSI Comprehensive Service & Support Implementing the CSI Way.
CAR PARK PAY SYSTEM. Car park pay system able to manage, on ground & multi storey park lots, access, vehicular flow, manual or automatic toll collection.
Deployment Diagrams Martin Orendáč. Deployment Diagrams A deployment diagram in the Unified Modeling Language models the physical deployment of artifacts.
DEVELOPMENT OF LABORATORY MODULE FOR SMALL WIND TURBINE CONTROL SYSTEM (Phase V) Advisor/Client: Dr. Venkataramana Ajjarapu Group MembersPosition on Team.
Module 1: Introducing Windows Server 2003 Network Infrastructure Planning, Tools, and Documentation.
Team #5 Nicholas Baker Alejandro Haller Matthew Hudson Cristobal Riojas Sep 08, 2011 Fully automated machine that proves the concept of automated construction.
Module 13: Monitoring Resources and Performance. Overview Using Task Manager to Monitor System Performance Using Performance and Maintenance Tools to.
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
1 © 2008 RoboRubik ECE 477 Final Presentation Team 11 – Spring 2008 Tyler Heck Dave Bukiet Erik Carron Casey Kloiber.
Team Foundation Server Petr Moravek Senior Premier Field Engineer Microsoft.
Team #5 Nicholas Baker Alejandro Haller Matthew Hudson Cristobal Riojas Sep 09, 2011 Fully automated machine that proves the concept of automating construction.
Chapter 1 Software Engineering Principles. Problem analysis Requirements elicitation Software specification High- and low-level design Implementation.
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M37 8/20/2001Slide 1 SMU CSE 8314 /
Physical Views Component: A component is a physical unit of implementation with well-defined interfaces that is intended to be used as a replaceable part.
CSE Design Lab Milestone III Karl SchwirzJames Hopkins Dennis O’FlahertyDave Festa.
Team Everest; From:
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
P ROJECT N OMAD Jay Stenmark Team Leader USB Design David Graham FM Receiver Software Webpage Documentation Aimee Imparato USB Design Hardware / Software.
Library Management System. Aim : To develop a project titled “LIBRARY MANAGEMENT” and is developed to maintain the operation done in a library. To develop.
Unit 2 Computer Systems. The aim of this unit is to enable learners to:  Understand the components of computer systems and  Develop the skills needed.
House Finding Management Supervisor: Mr. Trần Đình Trí & Avengers Team 1.
Software Construction
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
Software Project Management
ECE 4006 Mid-Term Presentation
Team 1: 32 responses Team 2: 55 responses Team 3: 29 responses
ECE 477 Final Review: Team #
CIS 210 Systems Analysis and Development
Control Award This award is given to the Team that demonstrates innovate thinking in the control system to solve game challenges such as autonomous operation,
Lecture 09: Software Architecture (Part I)
Big Picture for Lab 5 Lab 5 Review with TA Course Wrap-up
Project Title Group member names
ECE 477 Design Review Team ??  Fall 2012
CSE 498, Collaborative Design
Project Prototype Demo 1 Grading Rubric
Project Title Group member names – alphabetical order – with dep’t in ()s e.g., Gaetano Borriello (CSE), … Problem (use visuals to describe your problem.
Around the room Orders of operations.
<Project Title>
Computers.
Configuration Management
Similarities Differences
G14 Autonomous Rover Wall Avoiding Robot
CHIC: Possibilities of Supply
Senior Project Proposed Solution
Presentation transcript:

CSE Design Lab Milestone IV Dennis O'Flaherty James Hopkins Dave Festa Karl Schwirz

Outline Component Diagram Entry Criteria Stubs and Data Exit Criteria Problem Resolution

T h e Ro b o t

Module Integration Diagram

Entry Criteria Module objectives defined by group Component tested by developer Component has been tested by non-developer team member

Stubs and Test Data Program stubs for testing hardware Hardware for testing software – Configured robot – Test Rooms

Exit Criteria Similar criteria to entry criteria: – Expectations defined by group – Test integration individually – Test by another group member

Problem Resolution Hardware has been integrated Software components depend on hardware, not on each other Manual control and visual modules are related but dependent Reduced dependencies mean that problems have fewer ramifications

Module Integration Diagram