Skip to content

Commit 6ba99d6

Browse files
author
Matt Hansen
authored
Merge pull request #1 from mkhansen-intel/init_docs
Feedback requested - Initial design documents templates
2 parents 786eedf + ff3df8b commit 6ba99d6

File tree

4 files changed

+55
-2
lines changed

4 files changed

+55
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1-
# navigation2
1+
# Navigation2
22

3-
ROS2 navigation
3+
ROS2 Navigation
4+
5+
# Contributing
6+
Currently we are in the design phase, and are accepting input and requirements. To contribute, see the [design README.md](design/README.md)

design/README.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# ROS2 Navigation design documentation
2+
This is where the ROS2 Navigation design documentation is being collected and vetted
3+
4+
# Use Cases
5+
These are for defining how the user interacts with the system
6+
7+
See the [use case template](use_cases/_template_use_case.md)
8+
9+
# Requirements
10+
These are for defining the technical requirements
11+
12+
See the [requirement template](requirements/_template_requirement.md)
13+
14+
# Contributing
15+
To submit a request for a use case or requirement, copy and modify the template and submit a pull request for review
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
# Requirement Title
2+
The \<navigation system> should be able to \<shall> \<do something>
3+
4+
## More details
5+
- Why is this needed?
6+
- What is the expected user interaction?
7+
- What use case does this map to?
8+
- Are there any non-functional requirements (build system, tools, performance, etc)
9+
10+
11+
# Example:
12+
13+
# Warehouse Navigation
14+
The navigation system should include a modular collision avoidance algorithm that can be replaced with a new algorithm at run time
15+
16+
## More details
17+
- I want to be able to write or use my own collision avoidance algorithm without having to re-compile the entire stack from source
18+
- Ideally I can just change out a node using a custom launch file
19+
- This maps to the "Collision Avoidance" use case
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Use Case Title
2+
As a \<Developer, Researcher, Technician, etc.> I want the robot to \<action> so that \<I, the robot, etc.> can \<do something important>
3+
4+
## More details
5+
- Why is this needed?
6+
- What is the expected user interaction?
7+
- Are there any non-functional requirements? (build system, tools, performance, etc)
8+
9+
# Example:
10+
11+
# Warehouse Navigation
12+
As a warehouse robot operator, I want the robot to navigate without colliding into people or objects so that it doesn't hurt anyone or damage anything
13+
14+
## More details
15+
- I want this so that I know the robot won't damage itself, damage property or hurt anyone
16+
- I shouldn't have to interact with the robot to prevent it from crashing into people or things

0 commit comments

Comments
 (0)