1. Develop a single overview use-case diagram. The diagram must have a minimum of 16 used cases (i.e. 16 functions of the DVD store from HW 1). On real projects you do not get to pick 16 activities. This decision is to reduce the size and complexity of the HW. I believe students can demonstrate their knowledge by using 16. I recommend picking the best 8 from the font end and best 8 from the back end that will provide as much detail as possible. The detail diagrams have includes and extends and the overview has none (see discussion in text book). This explains why the overview UC diagrams have less detail than the detail UC diagrams. It is the includes and extends that provide the details. When necessary, it is wise to improve/update the AD before creating the UC diagram. The book states that a system cannot have more than 9 use cases but you may violate the rule providing the diagram does not become cluttered and difficult to read. If that is the case, use two overview diagrams. 2. Develop one overview and two detail diagrams: 1. One detail for handling all back end related activities of the Store (backend) 2. One for handling all customer (front end) related activities of the Store /usr/src/docs-worker/temp/a39e0fae-9c42-440a-b421-1160d2f75d6e/9e558940770b37d0b7b2e3bedbf68a0d Note: if the back end and customer functions were not part of the original 16 , you have to add them. You may also identify additional back end and customer functions