Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Best methods for writing multi-dimensional business rules
Previous Previous
 
Next Next
New Post 3/21/2015 7:55 AM
User is offline EA_BA
1 posts
No Ranking


Best methods for writing multi-dimensional business rules 

Hello everyone,

I'm trying to find the best approach for writing business rules that cover multiple scenarios.

For example, i need to write a rule for rendering buttons on a particular page within the system. When the buttons are visible/ hidden.

Ideally the rule is a one stop shop for this one page. The visibility of the buttons are impacted by:

The workflow

The type of user

The user security rights

The users companies security rights

The Group the company is part of's security rights

Currently i am using a excel, with a row for each available buttons, a column for each workflow and each cell indicating Visible/Hidden

And i identify the rule as a comment within the cell... i.e a button only visible for X type of user with XYZ rights

It's not easy for the developers/ QA to interpret and a comment might get missed. Any suggestions for writing rules with so many factors?

 

 
New Post 3/23/2015 12:13 AM
User is offline BigPicGuy
16 posts
9th Level Poster


Re: Best methods for writing multi-dimensional business rules 

There could be several ways to write requirements of such kind. And I understand your quandary. In this case your end goal should be that your Dev/QA to understand and picture the requirement without much effort. 

Use Perspectives and flow charts. 

1. Title the requirement "Button(s) Visibility and State"

2. Choose one of the rule influencing factors, say, workflow since it is easier to draw as a series of steps. Your flow diagram will honor this as the perspective.

3. Start drawing and when you reach a point where you have to implement the rule, branch the possibilities out (this is the cumbersome part :)). 

4. If the possibilities are many and you cant fit it all in lucidly, combine more than one perspective (workflow+ user type) and start from there. The branching will be lesser, You can also have a separate chart for each branch to break it down better.

It is easier said than done but I assume the requirement is not too complicated and having views/perspectives as a part of requirements helps Dev/QA to appreciate the system better.  Let us know how it goes,

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Best methods for writing multi-dimensional business rules

Community Blog - Latest Posts

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Latest Articles

5 Trusted Tips to Move Your Business Analyst Career to a C-Suite Role
Sep 27, 2020
0 Comments
Business analysts who aspire to the topmost leadership positions and who are looking to expand their career horizons need to be multidimensional profe...
Copyright 2006-2020 by Modern Analyst Media LLC