Decide the route after the map
Technology roadmaps are useful for getting the "big picture," but they are too broad in terms of where to go next. Here, we will divide it into 5 paths depending on what we want to dig into right now and pin the next page.
Five paths to follow after the roadmap
| What I want to know next | Next page | What you can find out |
|---|---|---|
| I want to reduce the measurement limit | EEG 101 / Datasets | You can check what can be measured and what cannot be measured by itself, which is the premise of the M series. |
| I want to dig deeper into reconstruction and causal estimation | Verification / Perspective | You can see where the R series connects to evaluation and causal verification. |
| I want to get down to implementation and L0 work | Hands-on / Datasets | I You can specify the minimum loop before proceeding to the series and the selection of input data. |
| I want to focus on verification conditions | Verification / Four paths after Verification | You can check the assertion level of the V series and the following branches of practice, closed loop, and identity. |
| I would like to see the system and external collaboration | Collaborations / Issue | You can check the D series and external dependencies while separating them from the preparations you can make now. |
Why this division
| way | Reasons for going to that page after Roadmap |
|---|---|
| Measurement | Since the M series determines input limits, it is better to check the basics of measurement on a separate page to reduce misreading. |
| Reconfiguration | The R series is connected to evaluation and causal verification, so it needs to be supplemented with Verification and Perspective. |
| Implementation | This is because it is difficult to make progress in the I-series unless you organize it not only on paper, but also through Hands-on and Datasets. |
| Verification | Since it is necessary to look at the overall design and assertion level together in the V series, it is more natural to dig deeper into the Verification side. |
| Social implementation | D series has a large system and external dependence, so it is easier to put it into practice if it is concreted in issues and collaborations. |
Assistance wiki when you stop midway
| Place to stop | Go back to wiki |
|---|---|
| Stops at reading P/M/R/I/V/D itself | How to read the roadmap |
| I want to look at it from the assertion level | How to read each L0 to L5 |
| Stops in order of descending to the practical side | One straight path from EEG to L0 / Four paths to follow after Verification |
| Stops in order of returning to theory side | Four routes to get started with WBE and dig deeper into theory |
| Stops due to external dependence and participation path | In-house production and external dependencies |
Common ways to get lost
Mistake
- Just reading the Roadmap makes you feel like you've decided what to do next: Actually, you need to narrow it down to one route.
- Skip M and R and move on to I and V: This makes it easier to move on to stronger arguments while still remaining within the limitations of input and estimation.
- Leave the D series abstract: It is more practical to cut the preparations back to Issues and Collaborations.
- If you go to Verification, you will understand everything: After the V series, there are the following branches at L0, L3, and L4.
Where to return next
Roadmap Please use Technology Roadmap to return to the text, Verification Platform to return to the verification side, and 4 routes from WBE introduction to deep dive into theory to return to the theory side branch.