FIDO GOV Discussion Forums

| lost password
home recent posts search register AspNetForum v.

Home » GSA - FACA Database » Business Rule: New System Business Rule: Consultations: Messages in this topic - RSS

2/13/2007 12:55:15 PM
Posts 29
When edits are made to consultations, all of the actions that are executed at the creation of a consultation, need to be re-executed. This includes resetting New Committee and Terminated Committee. Some committees are exempt from renewal and when they are exempt from renewal, the committee will normally have only a single establishment consultation, perhaps some amendment consultations if changes are made to the charter, and a single termination consultation. Committees are only a new committee in the year they are established, so if a consultation should be added or edited or deleted in later years, the New Committee Field should be set to “No” at the completion of the edit.
2/20/2007 3:10:38 PM
Posts 3
Ken, I'm not sure I understand the first concept in this post. Maggie
2/22/2007 11:05:20 AM
Posts 29
When considering a system, whether in development or production, Business rules can exist in at least two different conceptual perspectives, and sometime many more. On one hand, from a high level organization perspective, a rule can refer to a business process, like the consultation guidance that you are considering distributing to the CMOs. In a system, the business rules are the actions that are executed on a specific piece of data when it is entered into a field in a particular row in a particular table in a particular context. With each action being a separate rule, there can be dozens of rules for a single piece of data. Each rule must be tested and then executed when the data is being added, edited, updated, or deleted in a specific context. The rule states the data, the context, and the execution steps. Our current system has thousands of rules at the system level, and the new system will have even more. As we start looking at and discussing the rules, a lot will be mashed up together because we will try to say too much in too short a space with too few details. The first sentence "When edits are made to consultations, all of the actions that are executed at the creation of a consultation, need to be re-executed." was an example of mashing stuff up together. What I could/should have said was that all the rules that were considered, tested, and executed when a consultation was first created, also need to be considered, tested, and executed again against the current set of table relationships when an edit is made to any single data element in a consultation record. We do not currently do that now, with the care and completeness that we need to try to ensure exists in the new system in every instance. The rest of my statement was identifying a problem in the current system where the system level business rules do not seem to be properly applied.
edited by on 2/22/2007
3/15/2007 8:50:28 AM
Posts 4
Since renewal for non-discretionary committees is a little different than that for discretionary committees (no concurrance needed, for example), it might make sense to separate the two and include only those fields applicable to the specific committee types.
pages: 1