On Page 125 of our text book, there is a table of Common Errors in using and modeling Activity Diagrams. There is also corresponding 'Rectifying the Errors' column along with corresponding examples. Please study this entire Table carefully. Then select any TWO of these common errors and describe how you would ensure you understand and sidestep those two errors when you model with Activity Diagrams. Your answers must contain an example - preferably from your Team Project domain.

Team project: Lucky insurance- insurance management system.

Thank you,

The table is below

Common Errors	Rectifying the Errors	Examples
Drawing activity diagram independent of use cases	Ensure a continuous cross-reference between activity diagrams and use case documentation.	Study Figures 7.2 through 7.5 and their corresponding use cases in Chapter 5. The mapping between the use cases and these activity diagrams is important.
Not having proper start and stop activities	Ensure one start activity and as many stop activities as needed.	Figure 7.5, like Figures 7.2 through 7.4, has one start activity but more than one stop activity.
Having a fork (sync point) but not having a join (sync point)	Ensure all forks have a join and vice versa.	Figure 7.2 on the right-hand side has a fork and a join. Every fork should ideally have a join.
Unsure of where to place activities that seem to belong to multiple actors	Place the activity in the partition belonging to the main actor who owns that activity.	In Figure 7.2, the activities belonging to the patient are AnnounceArrival and ProvideDetails; these are mainly within the patient partition, but the administrator is also involved in their execution.
Assuming system to be an actor	While a system is not an actor, there is usually a partition for the system.	Figure 7.2 has a partition corresponding to system. This partition contains all activities that are responses of the system to an action by an actor from the other partitions.
Confusing activity diagrams with use case diagrams	Activity diagrams have flow and decision points.	Study the examples in this chapter and compare them with the use case diagrams in Chapter 6.
Confusing activity diagrams and interaction overview diagrams	IOD are at a higher overview level	Figure 7.7, ConsultationDetails IOD, has references to ChecksCalendar and