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

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC