Refine your Chat Application ticket

### Link to the coursework

https://github.com/CodeYourFuture/Module-Decomposition/issues/2

### Why are we doing this?

The "Write and Deploy Chat Application Frontend and Backend" ticket is too big to be useful.

We can't meaningfully plan a 16 hour ticket, we can't easily tell if we're struggling and need help, and it doesn't help us understand what is important and what we should skip if we run out of time.

Split it into smaller tickets which each won't take more than 3 hours to complete. Prioritise them:
* Which do you need to do first?
* Which are absolutely required?
* Which ones could you skip if you ran out of time?

Bear in mind you only have 16 hours to do this project. It's ok to decide not to do some of the requirements. But you should be intentional about which ones you skip. e.g. it would _not_ be ok to skip adding the ability to send messages. A chat application doesn't make sense without being able to send messages.

### Maximum time in hours

1

### How to submit

Create prioritised, estimated tickets on your planning board breaking down the big ticket into small tickets.

リンクされている coursework issue #2 を開いて大規模なチャットアプリケーションのチケットを理解し、その後、小さなチケットを作成する予定の計画ボードを確認してください。作業が優先順位付きのチケットに分割され、それぞれが3時間以内と見積もられ、16時間のプロジェクト上限内で必須作業とスキップ可能な作業が特定されていれば完了です。

索引モデルが issue の本文から書いたものです。