WIXLIB

Team 2: BoeingKML Urban Scene Builder 2008Technical Specification / ScheduleKML Urban Scene Builder 2008Team 02: BoeingCSE 498, Collaborative DesignJeff WinshipTom PytleskiDaniel BriggsMichael JefferyDepartment of Computer Science and EngineeringMichigan State UniversityFall 2008Team 02: BoeingProject Overview Boeing simulates urban warfare situations These simulations require complex 3Denvironments Having artists manually build theseenvironments is costly KMLUSB 08 will procedurally build 3D urbanenvironments using a combination of GoogleEarth User Interface, KML 2.2, and LUAscripting interface.2CSE 498, Collaborative Design, Fall 20081Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Functional SpecificationsTeam 02: Boeing Initial View of GEUIFCFunctional SpecificationsTeam 02: Boeing User Can Load Files4CSE 498, Collaborative Design, Fall 20082Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Functional SpecificationsTeam 02: Boeing User can draw the footprint and specify theproperties of a building.Functional SpecificationsTeam 02: Boeing To close the footprint the user has to click onthe first point.CSE 498, Collaborative Design, Fall 20083Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Functional SpecificationsTeam 02: Boeing Can move a footprintFunctional SpecificationsTeam 02: Boeing Can rotate a FootprintCSE 498, Collaborative Design, Fall 20084Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Functional SpecificationsTeam 02: Boeing Moving a nodeFunctional SpecificationsTeam 02: Boeing Saving a fileCSE 498, Collaborative Design, Fall 20085Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008System Components Hardware Platforms– Personal Computer Software Platforms / TechnologiesTeam 02: Boeing– C – XML KML COLLADA––––LUAWeb BrowserGoogle EarthJavaScript11Architecture IllustratedTeam 02: Boeing KMLUSB08 DFD12CSE 498, Collaborative Design, Fall 20086Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Architecture IllustratedTeam 02: Boeing 3DMC DFDRisks GUI– Designing solutions for Google Earth that complywith Google Terms of Service (ToS).– Time invested in studying ToS and creatingsolutions.Team 02: Boeing COLLADA– Complying completely with COLLADA standard sothe file created will be readable by the UI.– Time spent reading specification and DOM. Model Creation– Most important piece of functionality– People and time spent early in project schedule14CSE 498, Collaborative Design, Fall 20087Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Team 02: BoeingRisks DiagnosticGeometryRisksTeam 02: Boeing How to model interior of buildings. We are onlydealing with exterior nodes in our current design.CSE 498, Collaborative Design, Fall 20088Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Project Schedule1. Program Flowa) Program able to follow set up flow with simple objects.b) 9/252. GUI CreatedTeam 02: Boeinga) GUI able to make footprints to a limited extent.b) 9/253. Alpha Presentationa) Program able to follow flow with a few models withouttextures.b) 10/064. Displaying Dataa) GEUIFC should be able to show models as they areentered.b) 10/0917Project Schedule5. Texturesa) Textures and folder hierarchy should be mostly functional.b) 10/166. LUA DecisionsTeam 02: Boeinga) LUA should have most decision making complete.b) 10/237. Test Casesa) Test Cases should be set up for implementing beta.b) 10/308. Beta Demoa) Beta app should be up and running, benchmarks createdhere to be tested against later.b) 11/0318CSE 498, Collaborative Design, Fall 20089Michigan State University

Team 2: BoeingKML Urban Scene Builder 2008Project Schedule9. Refining Benchmarksa) Benchmarks should have refined logic and be createdaccurately.b) 11/13Team 02: Boeing10. Testinga) Test cases should all be working well and fully textured upto the benchmarks.b) 11/2011. Project Videoa) Project video completed.b) 12/0112. Design Daya) Everything done and delivered.b) 12/0519CSE 498, Collaborative Design, Fall 200810Michigan State University

Team 2: Boeing KML Urban Scene Builder 2008 CSE 498, Collaborative Design, Fall 2008 10 Michigan State University ing 19 Project Schedule 9. Refining Benchmarks a) Benchmarks should have refined logic and be created accurately. b) 11/13 10. Testing a) Test cases should all be working well and fully textured up to the benchmarks. b) 11/20 11 .