> For the complete documentation index, see [llms.txt](https://gosford-high-school.gitbook.io/preliminary-software-engineering/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gosford-high-school.gitbook.io/preliminary-software-engineering/unit-1-programming-fundamentals/5-assessment-task-1/task-guide/design/structure-chart.md).

# Structure Chart

You need to create a structure chart which shows **the main routine (main() function) and all subroutines (other functions).** Likely you will not have many control variables or flags **except for the API request, which will control whether or not you can search the data.**

## Example

The following is an example of the rock collection system (not a real API by the way - but it serves for an example of what your system may look like). 

<figure><img src="https://115028830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhF2chp1dcxIJhlOQSKVq%2Fuploads%2F8We1MdrWGqmOLDboV4L9%2Fimage.png?alt=media&amp;token=5e2bfad2-93ac-412f-a144-891c8a4d8e52" alt=""><figcaption><p>Example of a Rock Collection System with all subroutines and API Request</p></figcaption></figure>

## Need More Information?

{% content-ref url="/pages/VfkFW10uc2bEWpQmjYPQ" %}
[Structure Charts](/preliminary-software-engineering/unit-1-programming-fundamentals/charts-and-algorithms/structure-charts.md)
{% endcontent-ref %}