1 / 35

The Role of Aviation in Urban Warfare

This project report evaluates the use of Vertical Takeoff and Landing (VTOL) aircraft in urban warfare scenarios, addressing challenges and technology gaps. It includes stakeholder analysis, requirements elicitation, system architecture design, and technology assessment.

teegarden
Download Presentation

The Role of Aviation in Urban Warfare

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Role of Aviation in Urban Warfare Capstone Project Report 18 December 2009 Team Sikorsky (#7): Michael Bovan, Bryan Driskell, Michael Ingram, Jay Stewart, Damian Watson http://mason.gmu.edu/~jstewarc syst-798@googlegroups.com

  2. Agenda • Project Introduction • Requirements & Elicitation • System Architecture • System Analysis • Business Plan & Technology Assessment • Conclusion & Road Ahead

  3. Background • 80% of worldwide population in urban environments by 2030 • Unified population of terrorists / enemy combatants and civilians alike • Example: 2008 Mumbai terrorist attacks on Taj Mahal Hotel • Urban Environment Vertical Takeoff & Landing (VTOL) Missions: • Search & Rescue (SAR) • Attack & Target Designation • Troop Transport • Reconnaissance • Logistical Resupply

  4. Problem Statement & Objective • Problem Statement • Increasingly Urban Battlefield • Unique Challenges for Aviation Assets • Red vs. Blue Warfare Model is Ineffective • Unknown / Undefined Roles • Project Objective • Analyze the role of VTOL aviation for future military missions in urban environments. • Evaluate current aviation platforms • Identify technology gaps • Develop mission and/or system requirements and conduct trade-off analysis

  5. Deliverables, Assumptions, & Scope • Deliverables • Quantitative Analysis • System Requirements • System Architecture • Assumptions & Scope • Focus on military operations and military vehicles • Focus on VTOL vehicles • Focus on SAR operations within the urban canyon (UC) • Stakeholders

  6. Supporting Documents (Developed) • Proposal & Problem Statement • Operational Concepts Definition • Objectives Hierarchy Analysis • Stakeholder Elicitation Plan • Requirements Elicitation Plan • System Requirements Traceability Matrix • System Requirements Specification • System Analysis & Scorecard • Physical Architecture • Business Plan & Technology Assessment

  7. Project Schedule • Networked Schedule • Shows Critical Path • Critical Path - Stakeholder Elicitation and Functional Architecture • Gantt Chart • Start and Finish of Tasks • Shows Progress on Tasks

  8. Agenda • Project Introduction • Requirements & Elicitation • System Architecture • System Analysis • Business Plan & Technology Assessment • Conclusion & Road Ahead 8

  9. Requirements Elicitation - General Approach • Understand the stakeholders and ‘capture’ their requirements Meet with Prime Stakeholders Weekly Use Conversational Methods (Interviews, Focus Groups) • Analyzing stakeholder selections Defined High Level System Attributes Use interviews and an Attribute Ranking System Repeat process for lower level system attributes • Communicating stakeholder ideas Share elicitation choices between stakeholders Reach agreement on top choices • Agreeing on selections/requirements Negotiate with stakeholders about requirements Ensure Traceability between requirements and system attributes

  10. Requirements Elicitation (Cont) Requirements For the VTOL Project, Requirements Elicitation was accomplished primarily through: • Weekly Meetings with Prime Stakeholder • Use of Current Event Discussions • Brain Storming Sessions • Attribute Ranking Elicitation • Scenario Discussions • Use Case /Activity Diagram Development • Requirements Document Reviews and Negotiations

  11. Requirements Management Requirements Damian’s Comment Revised Requirement Action Taken Requirement Type # Original Requirement More • MS Excel 2003 • 200+ Requirements • Easy to Set up, Difficult to Manage • Cumbersome Traceability • Not easily Linked to other Architecture Modules

  12. Requirements in Enterprise Architect Requirements • Improved “Nested” Structure • Configuration Management • Enhanced Requirements Traceability • Linkable to other Module Elements • Input • Operational Concept • External Interface • Functional • Technology • System Wide • Output

  13. Agenda • Project Introduction • Requirements & Elicitation • System Architecture • System Analysis • Business Plan & Technology Assessment • Conclusion & Road Ahead

  14. System Architecture Overview • Referenced Department of Defense Architecture Framework (DoDAF) v1.5 • Used non-DoDAF diagram to model Physical Architecture • Focus on applicable Systems and Services Views (SV-1 /4) • Diagrams developed using Unified Modeling Language (UML) • Tool: Enterprise Architect (EA) v7.1

  15. System Architecture Process

  16. SV-1 System Interface Description

  17. SV-4 Example (Use Case) (Activity Diagram)

  18. Functional Decomposition

  19. Function To Form Map (Communicating) (Top Level)

  20. Agenda • Project Introduction • Requirements & Elicitation • System Architecture • System Analysis • Business Plan & Technology Assessment • Conclusion & Road Ahead

  21. Analysis [1] • Data: Market Research & Sponsor Input • Scenario Development via Use Cases

  22. Analysis [2]

  23. Analysis [1] • Data: Market Research & Sponsor Input • Scenario Development via Use Cases

  24. Analysis [2]

  25. Agenda • Project Introduction • Requirements & Elicitation • System Architecture • System Analysis • Business Plan & Technology Assessment • Conclusion & Road Ahead

  26. Business Plan • Use • Investment • Partnerships • S-curve • Marketability • Consumer Use – Point-to-Point travel • Alleviate City street congestion • Policy & Law • Protect Noise Pollution • Safety

  27. Technology Assessment [1] In Function to Form Mapping, certain functionality depends on “Critical Technologies”

  28. Technology Assessment [2] • Used Morphological Box to generate solutions for each critical technology • Assessed feasibility and generated design combinations 28

  29. Conclusions & Road Ahead • No one vehicle currently suitable for SAR mission • VTOL Maneuverability Technology and Safety limit SAR Mission Effectiveness • Communications Technology can support SAR Missions within the UC • Identified capability gaps • Conduct Analysis of Alternatives on Future Technologies • Develop Design Solutions

  30. Acknowledgement • Thank You Sikorsky for the Opportunity to Support Your Projects • Mr. Chris VanBuiten • Mr. John Burton • Mr. David Kingsbury • Thanks to GMU Faculty 30

  31. Backup Slides Igor Sikorsky & Orville Wright with Sikorsky XR-4 in 1942 Comdr. Frank A. Erickson, USCG & Dr. Igor Sikorsky, Sikorsky Helicopter HNS-1 C.G. #39040.

  32. Schedule

  33. Schedule (Network Diagram 1 of 2)

  34. Schedule (Network Diagram 2 of 2)

  35. System Boundaries • External: Humans (Operators, Maintenance), SAR Sensors. • Internal:platform,sensors forvehicle health & navigation,mounts &rails

More Related