# Final Project ![Hint: You have already done the research on some of this.....](https://2507214486-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LpUPSf3tCxHePJxNjfg%2F-Lvg-LcrfRiCn7xpaIXR%2F-Lvg2n1Kw_fvpy3iAI4f%2Fimage.png?alt=media\&token=df5e1cf3-0cd1-40df-bd10-8811a82c3083) Step 1: Identify What is Great and Important about your topic Step 2: Identify some issues, problems, threats or concerns either to your topic's survivial OR that your topic is creating for other species Step 3: brainstorm things you can build and create using team micro:bits * [ ] 1 thing that shows the value, importance or functionality of your topic * [ ] 1 thing that shows a problem, issue, concern or threat surrounding your topic * [ ] identify the un global target that might be tied to this * [ ] 1 thing that illustrates a potential solution to a problem, issue, concern or threat to your topic * [ ] this can be different that the problem you have identified earlier #### Quickly Touch Base with Mrs. Wright before you move onto the next step As a group pick ONE of these and make some detailed plans about the physical design and then an input/process/output chart for the code --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://computational-thinking-in-room11.gitbook.io/room-112-dhs/software-development/final-project.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.