This discussion on the topic of Database Modeling with Dr. Michael Blaha try to answer the question “How good are UML use cases for Database Design“? His opinion is that use cases are rote work. The developer listens to business experts and slavishly write what they hear with little interpretation and no abstraction. There is little reconciliation of conflicting use cases. In a database project, the conceptual data model is a much more important software engineering contribution than UML use cases.
Database Modeling and Use Cases
Reviewing Requirements for Testability
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]
Read MoreUnderstanding System Analysis Models
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.
Read MoreFind Missing Requirements
This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read More