peer review: <Mitchell Weingust Team 22> 8.1 Product Boundary - Use Case Diagram should be expanded on

[mitcholll]

artifact under review.

SRS Document

team number (for the team doing the review).

Team 22

description of issue.

Section 8. The Scope of the Product's use cases are a bit empty. The diagram contains 3 use cases, which can be broken down further into precise use cases amongst multiple users.

For example,
PUC-01: Receive user writings: I can see the interaction is between the user and the system, but what happens with the writings once they've been received? Are they stored somewhere?
Stating "Writing artifacts with customization settings" on the arrow could be broken down into use cases itself. Typically, arrows on Use-Case diagrams are labelled exclusively with <<includes>> or <<extends>>, not with additional instructions. Perhaps you could consider changing these additional labels into use cases themselves!

Following up on "Receive user writing", the LLM also has an arrow to it labelled "User Writing" from 'Generate suggestions and planning steps'. Logically, the flow could be improved by connecting an additional arrow from 'Receive user writing' to the 'LLM' user.

As well, you indicate that LLM is a user with the system, but it is depicted by a square instead of a stick figure. It would make it more apparent that it is another user if you change the icon.

@CSchank