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

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
Jason White
Jason White
New technology is in trend every day and striving to make its mark to be the best. It is not optional to stay exceptional, technology has made lives easy and uncluttered in so many ways that cannot be comprehended. With the latest technologies in the headlines every day, it is Artificial intelligence that is leading the race and being incorporated ...
0 Responses
Digvijaybook
Digvijaybook
The role of a business analyst is to manufacture a piece of art; the piece of art varies depending upon the methodology and techniques being used. Business analyst serves the project all through the beginning until the end and comes up with different pieces of art. It all depends on the case, the business analyst gets involved from the beginning of...
0 Responses






Latest Articles

Requirements Life Cycle Management with Azure DevOps
Jul 05, 2020
0 Comments
Requirements management is a critical function for business analysis. Requirements management is focused on ensuring that the business users and stake...
Copyright 2006-2020 by Modern Analyst Media LLC