The Sarbanes Effect on Software Development

One of the most pervasive, and often justified complaints coming from QA professionals is that senior corporate management seems unaware of their existence, let alone their value. All too often perceived as a necessary evil or discretionary expense, QA is often a target of budget and schedule cuts. But all that could change with the Sarbanes-Oxley Act. In this column, Linda Hayes explains what this new legislation could mean for your QA team.

One of the most pervasive, and often justified complaints coming from those of us toiling in QA is that senior corporate management seems unaware of our existence, let alone our value. All too often perceived as a necessary evil or discretionary expense, QA is often a target of budget and schedule cuts. When it comes to communicating up the organization, I am reminded of the joke where the testers declare the product as "crap," which the next level of management softens into "manure," which is then further interpreted as "fertilizer," which finally reaches the top levels as "rich and productive."

A large part of the problem is that if QA does a good job, no one hears about it. No one appreciates the complaints that weren't received and the problems that didn't happen. Another part is that if there are problems, QA gets the blame. But all that could change. For those of you still puzzled by the title, the Sarbanes-Oxley Act is the new legislation passed in reaction to Enron, WorldCom, and similar fiascos. As someone who is saddled with degrees in accounting as well as law, but whose career is in QA, this topic is of particular interest to me.

A cursory reading reveals that the SEC is now demanding that corporate officers and directors "certify" (read as take personal responsibility and potential liability for) the accuracy of financial reports. This includes the issuance of an "internal control report" that attests to the effectiveness of the controls and procedures for financial reporting. A more detailed reading of the fine print reveals that these provisions don't just cover areas such as corporate finance and independent auditors, they also cover systems that impact financial results such as information technology and other operational areas. Does it mean that if your ERP system has a bug that affects your financial statements, your chief executives are automatically defendants? Maybe, maybe not.

The violation must be "knowing and intentional" to give rise to liability. This means that the executives must have known that there either was a problem or, at least, a high probability that one might exist, and then intentionally disregarded it. Obviously, if the QA organization uncovers significant errors in the ERP system and management knows there is a potential impact on the financial results but proceeds with the implementation anyway, then there is probably liability.

But what if the ERP system wasn't tested at all? Arguably, in that case, management would have no notice of any issues and therefore could not intentionally disregard them. But this is where the internal control report kicks in. The company must maintain adequate controls to assure that these types of errors don't occur.

Sarbox, as it is fondly called by all the lawyers and accountants licking their chops, doesn't define internal controls directly; it is generally accepted that the definition will be the same one used by auditors and prescribed by the Codification of Statements on Auditing Standards Section 319 ("AU Section 319"). AU Section 319 describes internal controls as including five components:

About the author

Linda Hayes's picture Linda Hayes

Linda G. Hayes is a founder of Worksoft, Inc., developer of next-generation test automation solutions. Linda is a frequent industry speaker and award-winning author on software quality. She has been named as one of Fortune magazine's People to Watch and one of the Top 40 Under 40 by Dallas Business Journal. She is a regular columnist and contributor to and Better Software magazine, as well as a columnist for Computerworld and Datamation, author of the Automated Testing Handbook and co-editor Dare To Be Excellent with Alka Jarvis on best practices in the software industry. You can contact Linda at

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!