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

Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Architecture and AI In our recent conversation with Joseph Edward, we explored the transformative power of business architecture (BA) and technology as tools for uplifting communities. Joseph, with his rich background spanning from education to IT leadership, shared...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - The AI Business Analyst I recently had an engaging discussion with Maria Becerra, a passionate advocate for AI and an accomplished business analyst, on the AI Business Analyst. Maria is a respected name in strategy, business analysis and AI. Her path from Colombia to Canada ...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Analysis. I'm happy to share insights from my recent conversation with Kingsley T. Ihejirika, PhD, an ICT Business Analyst at the Ministry of Justice in New Zealand. Kingsley's unique blend of academic theory and practical expertise sheds light on the path t...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC