Regarding to identifying them in your code, IMHO, in an existing application, it is not easy to identify and extract the business rules out. therefore a BRMS solution should cover the whole lifecycle of business rules. When we are talking about BRMS, it is not only the execution (BRE) aspect of it but also other capabilities like, standard modeling language and authoring, debugging, testing, version control, deployment and hosting as a service (REST), security and permission control and so on.
One component of a BRMS is a Business Rule Engine (BRE) which allows you to execute the business rules that are modelled in different forms. If you want to extract them totally from your source code, and let them be managed out side of your source (JSP) you need a business rule management system (BRMS).
#CODE ON TIME WHAT ORDER ARE BUSINESS RULES EXECUTED IN UPDATE#
However structuring in a better way in your code, would be beneficial in long run of the project, so developers will be update them easier. So in your question, if you still keep the business rule in JSP codes, then there still is dependency to developers (and IT) so that's not much beneficial from what I just mentioned. For example, when a tax rate is changed, business can update the tax rule without need to ask IT team (developers). When you separate these from each other, then you allow business rules to be updated independently, with no application code change by business people.
Generally, your application should take care of different types of logic: Application Logic and Business Rule. There are many reasons that you should not implement business rules into your source code. What I see is most of the times, a confusion between different types of logic, and they all are called business rules by mistake. Business rule is a criterion used in business operations to guide behaviour, shape judgements and make decisions.