Method for prior questionnaire content re-use utilizing a central project repository, with analytical action based change detection.
Publication Date: 2017-May-25
The IP.com Prior Art Database
Method for Prior Questionnaire Content Re-Use Utilizing a Central Project Repository, with Analytical Action Based Change Detection
Within a basic service delivery model where a client engages repeatedly within a short period of time for a service that requires details of that service as requested via questionnaire, often times details of those answers may change over time, yet many other things remain constant. As a result it is useful to re-use past information while allowing for changes. In addition, having a central document that retains descriptive information and key categorical attributes about the client/project is often desired. Finally there is a need to have item by item confirmation of agreement with any re-used content and related signoff/history for such action. This method leverages multiple concepts which results in dynamic updates and exchange of data to allow for the quick re-use of past questionnaire answers, while also providing a field level audit point with signoff/history, ability to update to more recent information, storing of key attributes in a central project core document for future reference and continued reuse. Prior to the service engagement, a questionnaire is sent to the client to request information required to prepare for and perform the service engagement. On the first engagement the questionnaire has no known information about the client or proposed engagement details. However, upon completion of the first questionnaire, the set of attributes that would be considered relatively static are stored within a core project document for that project/client. On subsequent engagement requests, the questionnaire is then able to present the option to utilize past answers or modify and update them. On completion of these subsequent questionnaires the results are analyzed and compared to the core project document to determine if it requires updating (only the most recently created questionnaire for the most recent engagement causes the update). Possible attributes which could be utilized in this method are customer name, unique identifiers, project/application name, contact information, other categorization content, other details relevant to the engagement (size of entry being worked), etc. The incorporation of a single project core document then results in a parent-child relationship between this entry and the many questionnaire entries related to it that serve as the engagement reference (most likely also related to a specific engagement record depending on test documentation system implementation). Because of this, it becomes possible to extract other statistics and relationships from this project core document which can be directly updated and stored as attribute values, rather than a performance hitting query against the many existing questionnaires. For example, the number of engagements performed in the past, the date of the most recent one and key values extracted from the most recent questionnaire (client nam...