tag:blogger.com,1999:blog-7722108.post2648145100688247249..comments2024-03-28T12:11:07.539+05:30Comments on Thinking Tester: C-DLICE’ing in software TestingShrini Kulkarnihttp://www.blogger.com/profile/10782753752478547381noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7722108.post-5011974620325061592009-05-13T11:38:00.000+05:302009-05-13T11:38:00.000+05:30Hello Shrini,
Once again a good post ..
I have f...Hello Shrini,<br /><br />Once again a good post ..<br /><br />I have few questions on this DLICE process, would you please answer them. It would be helpful in understanding them better.<br /><br />As you said, some of the Task in D,L,I,C,E are very much overlapping in one way or the other. <br />For example When you discover(D) a product, you as well are learning(L) about it. I couldn't figure out the dominance of discovery over Learning. I feel if you learnt something successful which noboby has ever tried, it means you have discovered something. But intuitively learning is the process you would have followed. <br />Question:<br />So where would you draw a line between each of the tasks involved in DLICE ing. If DLICE is considered to be a process to be followed for Testing, it should have clear demarcations between the Tasks followed in it, right?<br /><br />The following lines are specific about the 'D' part of DLICE ing:<br />I personally feel some help has to be extended for the Tester to follow this 'D'(discovery) part of DLICE ing:<br />1. Without the functional architect's help, the developers cannot discover the characteristic of the Business process they are adding or enhancing. And it follows like a chain reaction; <br />2. Without the Developers documenting what change they have done in the codebase(for code maintenance) and what features are tuned in the application(by means of Specifications), the testers cannot collect the information about the change and discover the so called unknown area.. <br />I feel the 'C'(confirmation) process has to be carried out as sub-process in each of the stages i have enumerated. If the Architects, Developers don't confirm the correctness of the information they are letting out to the Developers, Testers respectively. Then it would cripple both Development and Testing Activity which is absolute waste of time and more importantly the cost.<br />Question:<br />How would this DLICE be used by a Tester if there are no co-operation from the Architects, and hence forward the Developers <br /><br />Thanks for your time!<br /><br />Regards,<br />VIJAYVIJAYhttps://www.blogger.com/profile/06341141676306726347noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-24518580918358550702009-03-07T05:40:00.000+05:302009-03-07T05:40:00.000+05:30Hi Shrini - was wondering when you'd blog again.I ...Hi Shrini - was wondering when you'd blog again.<BR/><BR/>I have no arguments with the premise, but do have two quick questions for you.<BR/><BR/>How do you pronounce C-DLICE - is it See-Dee-Lice, or is it sort of like "Slice" with a d shoved in there? I like pronouncing DLICE like DeLice - like I'm removing the Lice (the little bugs) from the software.<BR/><BR/>This is really more for Michael, but I'll ask you regarding his comment. I agree that testing is more than verification, validation, and confirmation, and have no problems with the cdlice part of it - BUT - I see verification, validation and confirmation more referring to the "what" of software testing, while C-DLICE refers to the "how". You can verify software (to an extent) by investigating, learning, and exploring the feature set.Anonymousnoreply@blogger.com