# data[].attributes.body
1. We can just say 'Maintain films' for use case name
3.2: The system itself can be the secondary actor.

# data[].attributes.body
4.1.1: LOGIN TO SYSTEM
The use case begins by staff logging in to the system before making any changes to the film.

4.1.4: PREVIEW CHANGES
The system will display the summary of the changes

4.1.5: SUBMIT CHANGES
The staff will then verify the changes made to the movie and submits the changes.

4.1.6: DISPLAY CONFIRMATION
The system saves the changes made to the selected movie and displays a confirmation message to the staff. The use case ends.

# data[].attributes.body
4.2.1: Must indicate "At MF 4.1.3 UPDATE DETAIL"
4.2.2: Do not have title.

# data[].attributes.body
For both:
Should not describe the UI design. Do not use words such as click on buttons and should resume at MF 4.1.4.

4.2.2: No flow name

# data[].attributes.body
5.1 - Staff has to log in to the system.
5.2 - NIL
5.3 - Film, Customer, Tickets, Movie details, Changes.

6. - NIL

7. Staff cannot change the movie timing again once a customer has booked the movie for that timing. The staff can only "Add movie" and "Modify Movie" when no customers have booked it and "Delete a movie" when the current date is after the last show of the movie"