I would be interested in a case study where someone took a project that they worked on and explained the initial system requirements that they were given and then discussed how they broke that down into discreet classes/modules/actors. I find a lot of presentations tend to show one slide with requirements and then the next slide reveals their design. I'm more interested in hearing about how we got to that design as I often feel a bit stuck with blank block diagram syndrome.
Some specific things I would be interested in hearing about beyond how the presenter broke down the problem would be how their finial design may have deviated from the original design (what caused this change and how did they adapt)? Did any problems come up because of the design decisions? I'm not talking about problems like "it was difficult achieving the desired loop rates so we had to optimize" I'm thinking about higher level problems like "we designed this assuming X so when we needed to add Y it didn't fit into the rest of our design nicely". Based on that, if they were given a clean slate, what might they have done differently?
Matt J | National Instruments | CLA
