Question: 1. How we know that we are over modeling a domain model? (1 Point) Adding things to the diagram that has no value to the




1. How we know that we are over modeling a domain model? (1 Point) Adding things to the diagram that has no value to the stakeholders Designing something inside the software Adding things that are part of the technology of the user interface Making a complex diagram 1. When should we use a foreign key?* (1 Point) Always Only in data models (Database Design) Only in domain models Only in design class diagram Never 1. I'm confused about conceptual classes (Domain Model) and software classes (Class Diagram). whats the difference and why cant they be shown in a domain model?* (1 Point) Domain models are about the solution and Class Diagram are about the problem. It is wise to show your solution muddled up with the problem! Domain models are about the problem and Class Diagram are about the solution. It is not wise to show your solution muddled up with the problem! Domain models are about the problem and Class Diagram are about the solution. It is wise to show your solution muddled up with the problem! 1. I'm confused about conceptual classes (Domain Model) and software classes (Class Diagram). whats the difference and why cant they be shown in a domain model?* (1 Point) Domain models are about the solution and Class Diagram are about the problem. It is wise to show your solution muddled up with the problem! Domain models are about the problem and Class Diagram are about the solution. It is not wise to show your solution muddled up with the problem! Domain models are about the problem and Class Diagram are about the solution. It is wise to show your solution muddled up with the
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
