Is this a problem in software development ?

Are some areas of computing infested by phonies ?


If it’s not true, there’s no harm done, we can simply state it is not true.


"When you know a thing, to hold that you know it; and when you do not know a thing, to allow that you do not know it - this is knowledge." -- Confucius ...


But I noticed this loophole:





5.


We want to make sure that “agreed” software is released. So we’ll stack a meeting with people who know possibly little about the matter and the meeting will “agree” on the software.


Why did we stack the meeting with unknowledgeable people. ?


Well we couldn’t spare any other staff to attend the meeting.





Why didn’t we leave the original programmer alone to do his job. He would have done much better by himself ?


Well, looking back we should have, but we thought it was important to release “agreed” software.

Is this a problem in software development ?
What U have mentioned is unprofessional conduct, which is self-defeating.





"agreed" software, is the application that meets


a) the requirements finalised with the client


b) the Quality certifcation committed by the Vendor


c) the contractual obligations
Reply:If I write a program or computer system I am usually following a written requirement or specification.





But who is to say that my work meets the requirement or specification?





This does not even take into consideration coding standards!





Several methods are in place to ensure that my work meets all requirements.





1) Code walkthroughs


2) Testing - Program, System and Integration


3) User testing.





After all of these steps the code can be signed off and accepted by the users.





Even after all this the code may still not work. This is an acceptable level of failure and in the computing world we are prepared to accept that this can happen.





By "agreeing" the software you should be in effect reviewing all of the testing results and agreeing that the risk involved in implementing the program is acceptable.