1. Check all choices that are not strengths of a UML class diagram. I chose B, but I was only half right A. highlighting dependencies between one class and another B. understanding the overall control flow of the system C. assessing whether you have too few/many classes in the anticipated system D. assessing the important entities in a system 2. Which of the following features are not represented in a UML structural representation of a software system? (only chose A and D is false) A. Operations with parameters and return values B. Visibility information C. Dependency relationships D. Events and actions E. Aggregation relationships F. Attributes with their types.