Describe the method at the level of components and decisions

The method section explains how you will build or investigate the solution. It does not need code, but it should be specific enough that a reviewer can spot problems.

Cover, briefly:

• Architecture: the main components and how they talk to each other. A simple block diagram helps.
• Technology choices: the stack, with one line on why each fits (for example "PostgreSQL because stock data is relational").
• Data: where it comes from, how much you expect, and how you will clean and store it.
• Process: how the team will work, for example two-week iterations with a demo to the supervisor at the end of each.

For a research project, describe the approach you will test and what you will compare it against. Avoid choosing tools only because they are fashionable; examiners routinely ask why you chose them.