ERROR: relation "aaa130201_proceeding_action_tracker" does not exist LINE 1: INSERT INTO aaa130201_proceeding_action_tracker(action_track... ^There was an unexpected database error.ERROR: relation "aaa130201_proceeding_action_tracker" does not exist LINE 1: INSERT INTO aaa130201_proceeding_action_tracker(action_track... ^There was an unexpected database error.Information Systems Section Midyear meeting and 11th annual AIS New Scholar Consortium: Data Level Assurance and Software Quality
Individual Submission Summary
Share...

Direct link:

Data Level Assurance and Software Quality

Sat, January 12, 8:15 to 9:45am, TBA

Abstract

Providing information to stakeholders to assist them in making their evaluations of a firm’s performance is a topic that is generating renewed interest. Financial crises serve as major reasons for discussion of information availability and quality issues; additionally technological developments have also started to drive this discussion. Continuous reporting systems have received attention as an approach to providing stakeholders with information on a more current basis, and the technology makes these systems feasible. A major question that must be resolved is how to ensure that these systems will continue to provide data that is of sufficient quality for stakeholders to make value relevant decisions. Clearly the traditional model used to review data disclosed by the firm will not work when the lag between an event and data about the event is reduced and becomes continuously available. This paper looks at the concept of data level assurance; providing a continually updated quality measure which communicates the accuracy level for data made available with zero lag. Four factors which influence the ability of a continuous reporting system to provide quality data are presented and related to software product quality metrics.

Author