http://grandpaham.com/2008/06/29/bpr-and-requirements-development-process-definition/ A Mentor for Software Process, Business Process Re-engineering, Software Architecture, XML Schema Design, etc. Fri, 12 Nov 2010 15:56:41 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://grandpaham.com/2008/06/29/bpr-and-requirements-development-process-definition/#comment-156 grandpah Fri, 22 Aug 2008 16:32:47 +0000 http://grandpaham.com/?p=85#comment-156 Virginia DMV is using the ICONIX Process for Design. They have added a few twists that allow for collaborative design between DMV and its development vendor. This is actually exiting stuff. And yes, by using the Enterprise Architect tool we are able to identify relationships and sequencing of rules in the model. It will be interesting to see what the longer term implementation results are as well. As a contractor, I do not see any of the vendor proposals for the new system, but I expect that they all have something similar to ilog. It is going to be fun. Virginia DMV is using the ICONIX Process for Design. They have added a few twists that allow for collaborative design between DMV and its development vendor. This is actually exiting stuff. And yes, by using the Enterprise Architect tool we are able to identify relationships and sequencing of rules in the model. It will be interesting to see what the longer term implementation results are as well. As a contractor, I do not see any of the vendor proposals for the new system, but I expect that they all have something similar to ilog. It is going to be fun.

]]> http://grandpaham.com/2008/06/29/bpr-and-requirements-development-process-definition/#comment-155 grandpah Fri, 22 Aug 2008 16:22:40 +0000 http://grandpaham.com/?p=85#comment-155 Actually, you may be of tremendous help here. I will research your link. We do of course, find business rules. We also have a separate process reviewing/discovering the more detailed business rules that are embedded in legacy system code and tables. The difference in granularity between BPR level rules and code level rules can be an issue. Still, in the long run, a rule is just another form of requirement that needs to be traced to applicable business processes. Actually, you may be of tremendous help here. I will research your link. We do of course, find business rules. We also have a separate process reviewing/discovering the more detailed business rules that are embedded in legacy system code and tables. The difference in granularity between BPR level rules and code level rules can be an issue. Still, in the long run, a rule is just another form of requirement that needs to be traced to applicable business processes.

]]> http://grandpaham.com/2008/06/29/bpr-and-requirements-development-process-definition/#comment-150 Mel Wed, 20 Aug 2008 16:17:33 +0000 http://grandpaham.com/?p=85#comment-150 As you go through Business Process and requirements gathering and analysis you will also find business rules. Do you use any methodology to capture the rules? Do you use ICONIX too? Can you keep track of relationships and sequence between rules? I found the following Agile Business Rule Development could, http://www.ilog.com/brms/media/ABRD/ which could be helpful in your situation. As you go through Business Process and requirements gathering and analysis you will also find business rules. Do you use any methodology to capture the rules?
Do you use ICONIX too? Can you keep track of relationships and sequence between rules?
I found the following Agile Business Rule Development could, http://www.ilog.com/brms/media/ABRD/ which could be helpful in your situation.

]]>