Client Sector
 Criminal Prosecution
 Civil litigation
 Arbitration & Mediation
 Corporate / Financial
 Training / Seminars
    Services

      computer evidence
     e-document discovery
     mobile phone evidence
     expert evidence review
     demonstrative evidence
     case management
     document management
    
data recovery

   

    
    

          Report a cybercrime
          Laboratory Protocol
       Computer Case Law -UK
          Computer Case Law -US
          Some Sample Docs
          Relevant Legislations
          Globallegal framework           

          Forensic Software
          Forensic Books
          Forensic Hardware
          File Extensions
          Forensic Careers
         
Partners

      Subscribe to our Free
              News letter
 
 

               Bookmark and Share

 


 
 
 
Computers and  digital devices run on some form of software or code. Software is the intangible part of the computer that actually contains the instruction for how and when the computer or digital device will execute  a particular request from the user.

Software is written by specialist known as programmers. Given the complexity of most computer programmes, it is becoming an unacceptable constant that software must contain some form of bug (corruption that affects its smooth functioning ).



These bugs have been known to wreck havoc  on an entire computer network causing loss running into millions of pounds and dollars.

It is not acceptable that software should contain bugs that is capable of affecting its merchantability  as a product. There are acceptable testing standards that ought to be carried out before a given software is confirmed acceptable for use in a production environment.

Sadly, most programmers do not subject their code or software programmes to these tests and yet pass it to the end user as finished products.                                                                        
The obvious result is an epileptic product that works in a perfunctory manner . Software like every other product must be fit for purpose.    
 

 

How do you investigate compliance testing with respect to software failure resulting in lost time, money and human resources ?. How do you incorporate this component into your case strategy ?

How can we prove on a balance of probability, that a particular software is not fit for purpose. How do we establish the cause and effect relationship occasioned by software failure.

How do we ensure a business is not held to ransom by a failed or failing software company; by using escrow agreements.
 

                


 Contact us for further info.

                  

 
 
 
 
                                        
 

Copyright 2009   iTevidence   All rights reserved