Comments on: Enterprise Decision Management and the Software Development Lifecycle http://jtonedm.com/2008/07/14/enterprise-decision-management-and-the-software-development-lifecycle/ James Taylor on Everything Decision Management Sun, 21 Mar 2010 19:03:55 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: James Taylor's Decision Management http://jtonedm.com/2008/07/14/enterprise-decision-management-and-the-software-development-lifecycle/comment-page-1/#comment-19338 James Taylor's Decision Management Wed, 10 Mar 2010 05:53:27 +0000 http://jtonedm.com/?p=500#comment-19338 <strong>Some thoughts on 'perfect' application development...</strong> John Reynolds had an interesting post a little while back where he shared some thoughts on Perfect development tools. His emphasis was on support for things like iterative and test-driven development but it seems to me that there is also...... Some thoughts on ‘perfect’ application development…

John Reynolds had an interesting post a little while back where he shared some thoughts on Perfect development tools. His emphasis was on support for things like iterative and test-driven development but it seems to me that there is also……

]]> By: Using business rules to close the SOA knowledge gap » JT on EDM http://jtonedm.com/2008/07/14/enterprise-decision-management-and-the-software-development-lifecycle/comment-page-1/#comment-13150 Using business rules to close the SOA knowledge gap » JT on EDM Thu, 12 Feb 2009 20:34:55 +0000 http://jtonedm.com/?p=500#comment-13150 [...] Now this is true but I don’t believe that better management of requirements is the answer. In fact what is needed is a way to turn what the SMEs know into something that can be managed in a repository and used to power systems directly. Working with SMEs to create sets of business rules to represent their know-how not only allows this knowledge to be stored in an executable format - reducing the likelihood of implementation error and speeding deployment and maintenance - it also allows each SME or SME group to manage their own rules. A modern Business Rules Management System (BRMS) will allow different users to have different access to rule sets, allowing each set of rules to be managed by those who know them best or those who “own” them. The BRMS can then be used to package up the relevant rules - typically many sets from many SMEs - into a decision service that can be deployed into a service-oriented architecture. Because the SME’s can edit the rules directly, business agility is increased because the time from the SME realizing that a change is needed to the time when that change is deployed can be cut dramatically using the rule management features of a typical BRMS. Dan’s comments about how to gather the know-how from SMEs are all good, but gathering their know how as requirements and not rules is going to limit the good it can do. I have blogged a lot on this topic but check out these two posts on the difference between requirements and Requirements and on how to fit business rules into a software development lifecycle. [...] [...] Now this is true but I don’t believe that better management of requirements is the answer. In fact what is needed is a way to turn what the SMEs know into something that can be managed in a repository and used to power systems directly. Working with SMEs to create sets of business rules to represent their know-how not only allows this knowledge to be stored in an executable format – reducing the likelihood of implementation error and speeding deployment and maintenance – it also allows each SME or SME group to manage their own rules. A modern Business Rules Management System (BRMS) will allow different users to have different access to rule sets, allowing each set of rules to be managed by those who know them best or those who “own” them. The BRMS can then be used to package up the relevant rules – typically many sets from many SMEs – into a decision service that can be deployed into a service-oriented architecture. Because the SME’s can edit the rules directly, business agility is increased because the time from the SME realizing that a change is needed to the time when that change is deployed can be cut dramatically using the rule management features of a typical BRMS. Dan’s comments about how to gather the know-how from SMEs are all good, but gathering their know how as requirements and not rules is going to limit the good it can do. I have blogged a lot on this topic but check out these two posts on the difference between requirements and Requirements and on how to fit business rules into a software development lifecycle. [...]

]]> By: Using business rules to close the SOA knowledge gap » JT on EDM http://jtonedm.com/2008/07/14/enterprise-decision-management-and-the-software-development-lifecycle/comment-page-1/#comment-12721 Using business rules to close the SOA knowledge gap » JT on EDM Thu, 08 Jan 2009 15:00:30 +0000 http://jtonedm.com/?p=500#comment-12721 [...] topic but check out these two posts on the difference between requirements and Requirements and on how to fit business rules into a software development lifecycle. This entry was posted on Thursday, January 8th, 2009 at 7:00 am and syndicated from James [...] [...] topic but check out these two posts on the difference between requirements and Requirements and on how to fit business rules into a software development lifecycle. This entry was posted on Thursday, January 8th, 2009 at 7:00 am and syndicated from James [...]

]]> By: Dave Wright http://jtonedm.com/2008/07/14/enterprise-decision-management-and-the-software-development-lifecycle/comment-page-1/#comment-10561 Dave Wright Thu, 17 Jul 2008 04:02:15 +0000 http://jtonedm.com/?p=500#comment-10561 Thanks for this, James... need to digest and think a bit... Thanks for this, James… need to digest and think a bit…

]]>