UAV for Search & Rescue - Group 6

Mission and Scope

What problem does this project address?: This project addresses the problem of autonomous vehicles. In this regard, Unmanned Aerial Vehicle (UAV) has been chosen to fulfill the requirements of this project. We have proposed a novel UAV for search and rescue operations in a challenging urban areas populated with buildings and road structures.

What is the goal of this project?: This project aims to design UAV that has the capability of search and rescue operations. In this regard:

The goal for this project is to have an unmanned area vehicle where it can be operated unpiloted based on pre-programmed flight plans (mission plans) or more complex dynamic automation systems. The main purpose is rescue where our UAV can be used to help in identifying an area map or current situation in the area where it is unsafe for human to intervene without any information or complete information about that area.
Our UAV can help rescue work locate survivors in challenging urban areas and detect structural damage in hard to reach areas.
Our UAV is capable of flown in a challenging urban areas populated with buildings and road structures.
This is very useful for any rescue organization all around the world which it will minimize search and analysis time thus enable the operation to run smoothly without any unwanted errors.

What is the scope of this project?

Unmanned Aerial Vehicle (UAV) will be analyzed and implemented.
Our UAV has been chosen for search and rescue operation.
The scope of this project includes object-oriented analysis which emphasizes the description of the objects or concepts of the problem domain. On the other hand, object-oriented design, in which software development collaborate to fulfill the requirements, is out of our scope.
This project includes defining requirements (functional and non-functional requirements) and inception phase.
During the inception phase, we are willing to define: Use Cases, Domain Models, System Sequence Diagrams, UML Interaction Diagrams and UML Class Diagrams.
This project includes seven main components:

1	Mission Planning	to set and plan new mission(s) in case of disasters such as hurricanes, tornados, earthquakes ...etc
2	Navigation	to define the location and navigate successfully to search and locate survivors.
3	Motion/Path Planning	to define the path and plan trajectory movement of the UAV
4	*Perception and Capture Control*	to capture information area map and detect survivor

What development methodology is being used?: Our methodology includes object-oriented analysis which has the inception and its elaboration shown below in the blocks diagram. As can be seen and mentioned before: the last two phases (Construction and Testing) are out of our scope in this project.

Where should a new team member start?: New team members should start coding and programming which is the Design/Construction phase and Testing phase shown in the above blocks diagram. A new team member could start probably after we finish the Inception and its Elaboration phases.

Status

We have completed defining functional and non-functional requirements and are currently working on adding more of the functionality to implement UAV for search and rescue purposes successfully. We have also finished designing the main Use Case and another seven Use Cases for seven subsystems. The next major milestone is to design Domain Models. After that we can continue our work on System Sequence Diagrams, UML Interaction Diagrams and UML Class Diagrams.

To keep track of the flow of our project work, please see status report (1) and status report (2).

Project Documents

Vision:	Project Vision Supplementary Specification Glossary (Data Dictionary) Bibliography
Inception:	Project overview Project proposal Target audience and benefits Statement of user needs
Elaboration:	Project plan Software requirements specification Feature set Use case suite Domain Model System Sequence Diagrams (SSD)& Operation Contracts (OC) Design Class Diagram Interaction Diagrams : Sequence Diagrams & Collaboration Diagrams System Context Diagram Activity Diagrams State Machine Diagram Logical Layered Architecture QA Plan Test suite
Construction:	Review meeting notes Implementation notes User guide FAQ / Troubleshooting guide
Transition:	Install / Quick start Demo script Release notes Release checklist
Continuous:	Status report

For Everyone:	Project overview Project proposal Target audience and benefits Statement of user needs Software requirements specification Project plan Release checklist
For Management:	Project resource needs Status report
For Developers:	Design Review meeting notes
For QA:	QA Plan
For End Users:	Install / Quick start User guide Release notes
For Support and Ops:	Implementation notes FAQ / Troubleshooting guide
For Sales/Legal:	Demo script Legal issues

Project Overview

Mission and Scope

Status

Project Documents