THE GEORGE WASHINGTON UNIVERSITY SCHOOL OF ENGINEERING AND APPLIED SCIENCE DEPARTMENT OF COMPUTER SCIENCE

1. THE GEORGE WASHINGTON UNIVERSITYSCHOOL OF ENGINEERING AND APPLIED SCIENCEDEPARTMENT OF COMPUTER SCIENCE CSCI 195 SLIDE PRESENTATION TECHNIQUES Prof. John L. Sibert Prof. Kristin Heckman Course developed by: PROF. ARNOLD C. MELTZER Modifications by: PROF. ROBERT W. LINDEMAN

2. Things You Should Do • Face the audience • Do not crowd slides • Make eye contact • Keep diagrams simple • Use appropriate font sizes • Use color sparingly Kristin E. Heckman

3. Face the Audience • Image will be projected behind you • Periodically check that image is okay • Speak towards audience • Use laptop as "teleprompter" • Do not mumble • Keep hands out of pockets Kristin E. Heckman

4. Do not Crowd Slides • Do not try to pack everything onto one slide • It will start to look too busy • People will not be able to keep up • You will not be able to keep up • Break long lists into several slides Kristin E. Heckman

5. Make Eye Contact • Look for audience reaction • Do not rush • Make it clear how questions should be handled • Think of your audience as your peers Kristin E. Heckman

6. Keep Diagrams Simple • Limit the number of bubbles • Limit the number of arrows/arcs • Be consistent in objects • Boxes/bubbles are nouns • Arcs are verbs GenerateCode Parse Source File Symbol Tables Executable Code Kristin E. Heckman

7. Use Appropriate Font Sizes • 32 Point • 28 Point • 24 Point • 20 Point • 18 Point • 16 Point • 14 Point • 12 Point • 10 Point Kristin E. Heckman

8. Use Color Sparingly • Use high-contrast colors • For this course, you should only use black on white Yellow on Black Yellow on Blue Cyan on Blue Yellow on Red Red on Black White on Black Black on White Yellow on Red Black on Black Kristin E. Heckman

9. Use the “Power” of PowerPoint GenerateCode • Align slide components Executable Code Source File Symbol Tables Parse • Use the nudge • Adjust • line • spacing appropriately • Adjust • line • spacing appropriately Kristin E. Heckman

10. Things You Should NOT Do • (Don't) Keep your hands in your pockets • (Don't) Mumble • Um, uh, … • Basically, … • Like, … • You know, … Kristin E. Heckman

11. Things You Should NOT Do (cont.) • (Don’t) Read your slides • (Don't) Use the striptease method • (Don't) Use cool transitions Kristin E. Heckman

12. Final Thoughts • Practice your presentation • Have someone proff-read your slides • Have your files accessible • Floppy • CD • Net Kristin E. Heckman

13. Final Thoughts (cont.) • Load files before class begins • Verify file functionality • Give your audience something to take away Kristin E. Heckman

14. EXAMPLES Kristin E. Heckman

15. Types of Temporal Tasks • Past • What happened? • Replay events, After Action Reporting • Present • Who’s talking/collaborating now? • What’s changed? • Future • Planning, Exploring alternatives, What Ifs?

16. Future Combat System (FCS) C4ISR Current Trends • Future Army war fighting capability leveraging future C4ISR technologies ( 2008 - 2015) • Employment of networked sensors, C2, communications and weapon systems to defeat threats at standoff ranges • Extensive employment of robotics (air, ground, and unattended) for ISR, direct and indirect fire support, and logistics • M&S based acquisition • Extensive use of geographically distributed virtual simulation

17. Potential Scenarios Mission: Unit X is tasked with conducting snap checkpoints around Region Y. There have been reports of the trafficking of contraband within the Region, which is helping insurgent forces in the disruption of Peace and Stability Operations. • Unit X breaks its mission into two sub-missions. Team A will conduct route reconnaissance in the area to observe suspicious activity, and Team B will conduct snap check-points in order to inspect random and suspicious vehicles. • While moving along its route, Team A captures as much information as possible through its ASSIST systems. As they see suspicious activity their ASSIST system captures images, voice intelligence reports, and charts accurate locations. This information is collected into a central database in the rear for future planning and analysis. • Team B conducts snap checkpoints, and stops random and suspicious vehicles, while documenting the entire mission. As suspicious personnel are seen, their pictures are being taken, transmitted to the rear for cross-reference against black-list personnel. If personnel are identified by the rear as blacklisted, they are detained and brought-in for questioning Force Protection – Route and Area Recon

18. PEO C3T Integration COL(P) Joe Toughguy Deputy Commanding General Deputy Program Executive Officer Program Executive Office Command, Control and Communications Tactical Kristin E. Heckman

19. Strategic Thrusts • Objective Force - • Future Combat System • Objective Force Warrior • Digitization (Legacy & Interim Force) • Army Knowledge Management • Army Joint Intersections • Distributed Common Ground System - Army • Time Critical Targeting (see Joe Schmoe’s Briefing)

20. Initial OIF Systems Delivered by PEO C3T • Blue Force Tracking (BFT) • At Bde and below, OIF commanders used its Common Tactical Picture and messaging for situational awareness and tactical communications • Battle Command On The Move (BCOTM) • C2Vs, LDOCs, A2C2S, & Bradley BCVs integrated and deployed to theatreto act as OTM Corps to Bde command platforms • ABCS Upgrades • All ABCS systems were upgraded or expeditedto OIF units through an ASPB approved Operational & Urgency Need Statement • Global Command Control System - Army (GCCS-A) • At Div and above, OIF commanders used the GCCS-A Common Operational Picture as a baseline for situational awareness • Defense Collaborative Tool Suite (DCTS) • Enhanced collaborative capabilities (secure voice, whiteboard, chat, file storage, FTP) provided to all OIF units from Theatre-to-Division Accomplished effective OIF1 force upgrades in 120 Days

21. Summary of technical approach • Elements • Gloss-chasing • Semantic primitives • Common properties • Identifying and extracting events • More depth: higher performance on tailored events • More breadth: greater ability to identify events in the large • More smarts: fewer training data requirements

22. Team Monmouth The Nation’s Science and Technology Epicenter Internationally Recognized as Predominant Industrial Research Facility Winner of DoD Network Centric Most Innovative Program Home to 2 of Top 5 National Research Universities • Diverse Private R&D Sector Bell Labs - Top Commercial Lab Telecordia (formerly Bellcore) Home to 476 Electronic MFG Facilities • Strategic Location New York City Philadelphia Greater Metro Area Tri-State National Leader in R&D • Strong University Research SystemPrinceton University NJ Institute of Technology Stevens Institute of Technology Rutgers, The State University Monmouth University University of Pennsylvania Columbia University Cornell University Drexel University New York University • Federal and State Lab's US Army CERDEC (Fort Monmouth) Princeton Plasma NJ Nanotechnology Consortium NJ Science and Technology Commission Weldon Congressional Initiatives William Hughes FAA Tech Center Naval Air Warfare Center RDEC (Army) • COMMUNITY SYNERGY Facilities/Capabilities Educational Alliances Workforce Pool Consortiums Professional Associations Technology Collaboration PhD Panels > $35 Billion/Yr in R&D Investments DoD Leverages the R&D Infrastructure Kristin E. Heckman

23. break (51 senses) break(1): to separateinto pieces break(2): to damageso as to be inoperative … break(10): to fracture a bone Chasing glosses withverbs and events • Glosses define complex events in terms of basic events • Send: to cause to go, to cause to happen • Smash: to break into pieces • How to recognize a basic event • Chased by glosses of many other words • Has many metaphoric senses

24. Summary • The ways of implementing ASSIST technologies are virtually boundless. • Almost any soldier and planning / fusion cell could benefit from these technologies if implemented properly. • Scenarios help hone developmental spirals, but should not be the only driver for full system integration. A vetting process must be followed in conjunction with a user community. • Most implementations must adhere to the concept of “simple to use, easy wear.”

25. Briefing Guidelines • A briefing should be . . . brief • Allow 4 minutes per page • Use the slides to convey high-level information in bulleted, short phrases • If sentences are necessary, make them short • Make it easy – to deliver, read, and understand • Think impact . . . and keep it simple • Avoid densely packed text, complicated graphics, and gimmicks • Complement high-level text with clean graphics, pictures, or tables • Resist the temptation to make your briefing a detailed report