4 ms·
The written requirement were written in C, C++, python, Verilog, Systems C. So they could be run. The runs were sent to the customer who would validate (approve
by f1shy 1y ago
The written requirement were written in C, C++, python, Verilog, Systems C. So they could be run. The runs were sent to the customer who would validate (approve) or reject.
- ttoinou 1y agoThat's pretty much how everyone is doing it, no ? It's a (Think a new improved model, Code the model, Study Results and compare with what we thought about the model) cycle. What's the alternative ?
- skydhash 1y agoI think the issue is how people goes about doing it. Often the model is clearly not improved, but it would mask problems some people wants under the rug. Sometimes, people are coding the wrong model or coding wrongly the correct model or coding wrongly the wrong model. Sometimes there's no study being done, only hope and prayers. And comparing is only ever done by the customer.
- f1shy 1y agoMmm bot really. First, it was HW and SW, and HW was simulated. Many go on to build something, then test Second, requirements are written in a formal language. I’ve never seen formal languages in DOORS (or similar) before Third we did not do the whole thing, just the bits and pieces in the requirements. After the requirements were done and approved, we move on to development, where the “normal” iterations happen. Subtle, but not the same