C vs C++

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Train

Lifer
Jun 22, 2000
13,587
82
91
www.bing.com
Well lets start with the first one
usually 1.5wks development, 1wk QC & UAT, .5wk document & release
Which, to be honest, looks like you mean consecutively, not concurrently. And I don't think any reasonable person who would make the same interpretation as me would do so in malice. I'm not mad you weren't clear, but a simple clarification would have ended that right there, maybe something like "No, I was only providing a breakdown of what all goes into it, they ARE done concurrently, and the amounts of time aren't exact either, just estimates."

But you responded:
Possibly within your ignorance these statements contradict. Where did I specify they aren't done at the same time or in what order, or any information as to what your statements could possibly apply to? I simply provided a generalization to the time assigned per iteration for these tasks. If you take the times as exact as well, that's another faulty assumption.
 

Tweak155

Lifer
Sep 23, 2003
11,449
264
126
Well lets start with the first one Which, to be honest, looks like you mean consecutively, not concurrently. And I don't think any reasonable person who would make the same interpretation as me would do so in malice. I'm not mad you weren't clear, but a simple clarification would have ended that right there, maybe something like "No, I was only providing a breakdown of what all goes into it, they ARE done concurrently, and the amounts of time aren't exact either, just estimates."

But you responded:

Ok, I would argue the root of the problem was your assumption, thus our miscommunication. If you knew in your mind it didn't make sense, I would suspect you'd ask how it was possible, rather than make statements. But I can see how it could go both ways, thus I apologize for my miscommunication on my end.

The times provided were for the next release. Our QC team works full time, so during that 3 week span they are still working either on the same project or on other projects. Also the documentation differs throughout the 3 weeks, sometimes you're still trying to get the code just right, and rather than re-write documentation, you wait until the end (in general we don't have a single document that encompasses all functionality, rather documents that support specific areas or even a specific UI). Also sometimes peer reviews cause a re-write of both code and documentation, but in general it is done throughout the development process. The README is the only documentation written just before release. And in rare cases, documentation for your unit is written during the next iteration (someone has questions you didn't think to address in the original document).

The 1 week of QA is split between unit tests (this is the majority, done throughout iteration), merged code tests, and then final regression just before UAT. If any UAT issues arise and changes are made, regression testing is redone.

I don't think I'm speaking of anything outside the norm, although I've heard of teams who have no dedicated QC testers.