In this interview, Michael Blaha discusses the relationship between use cases gathering and database modeling. His opinion is that it is fine to capture requirements with use cases, but they should be dependend of the class model, which defines the domain of knolwedge that can be referenced by use cases. For database applications it is much inferior to start with use cases and afterwards construct a class model, because they need a data approach and not a process approach. As object-oriented programming languages define a class structure to which logic is attached, it is odd that use cases put process first and defer attention to data structure.

Related Content:

• Primary and Secondary Use Case Actors
• Reuse of Use Cases Diagrams
• UML Use Cases in Agile Development