<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Design</title><link>https://sourceforge.net/p/rapidoaudit/home/Design/</link><description>Recent changes to Design</description><atom:link href="https://sourceforge.net/p/rapidoaudit/home/Design/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 24 Aug 2011 00:49:31 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/rapidoaudit/home/Design/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Design modified by Robert Mathison</title><link>https://sourceforge.net/p/rapidoaudit/home/Design/</link><description>Ideas about the design of the application
=========================================

When observing auditors doing their job, some key concepts arise to the mind: 

  * Reports are the most important thing of their job: it hold the results of their job and it is the "product" they sell
  * All the audit departments have a personal way to do their job. This personal way conforms with the standards and best practices, but there is always a customization and internal procedures added to this to customize or to adapt to the particularities of the organization they work in
  * For the internal auditors, to keep track of the status of the findings is not an easy task, so many give up doing this and changes it to a general check when doing the next work over the same department or scope. A bad idea because too much time could have passed since that and things may become worse
  * Auditors are a moving collective: they can move to do a report in a diferent place, return to his workplace in order to write the report, return again to another branch in order to recover additional information... a web application would be perfect. Having also an offline application would be desirable. 

So, when creating this project I have the following ideas in mind: 

  * Highly customizable environment, in order to allow users to adapt the application to their needs
  * Trackable findings: findings must be an identifiable element in the application, and must be possible to add other types of information that justify the follow up of these items
  * Reports will have a common look and feel
  * Application can be internetized (if such word exists)
  * An standalone application would be fine to work offline and then syncrhonize when reaching the office

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Mathison</dc:creator><pubDate>Wed, 24 Aug 2011 00:49:31 -0000</pubDate><guid>https://sourceforge.netf49bed473cded0440a351bd5f22e89a00c118de1</guid></item></channel></rss>