Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  How to organize Features and Business Rules for further discussions?
Previous Previous
Next Next
New Post 12/1/2015 6:05 AM
User is offline opposer
1 posts
No Ranking

How to organize Features and Business Rules for further discussions? 
Hi everybody. 
Here is my task.
The company, where yesterday was my first day, is developing a software, and it's partially complete. I'm first analyst here, and before hiring me theydiscussed all the requirements orally and didn't store them, so there is no any project documentation. So they gave me a task to organize all the features that are already released - into knowledge base, so they could discuss and add new functionality being able to see all that is done before. They want to prevent features conflicts also. 
So we had a workshop with teamlead and project manager, I extracted tons of facts about the software - about its features and business rules, which they conform to. I've organized user features into hierarchy and business rules among them  My idea is to organize the user features and business rules into one mindmap, so they could see them all when discussing new features.

Are there any better ways to organize this knowledge base? I wanted to organize features into a fishbone diagram, but how can I add business rules into it? Mark business rules somehow? Or are there any better ways to organize business rules and features?
New Post 12/10/2015 10:10 AM
User is offline Chris Adams
307 posts
5th Level Poster

Re: How to organize Features and Business Rules for further discussions? 

It sounds like you have pretty good handle on the features and business rules given where you started.  My main piece of advice is to map the features and business rules back to a requirement.  All features originate from a need.  Feature conflicts arise when a feature conflicts with a requirement or when it isn't the best way to satisfy that requirement.  

This process doesn't have to be too fancy or complex. I would take a somewhat agile approach to start. Create 1-3 sentence user stories representing each requirement.  Then map each feature to one or more user stories. And of course features can also have sub-features (your fishbone diagram).  I've written about a common method for creating user stories in our interview questions.

Using this technique, you capture the requirement in 1-3 sentences and then you document the acceptance tests on the back of the "card".  The back of the card is also a great place to capture specific business rules too!  Of course, here I'm discussing physical index cards for the sake of an example, but you can represent all of this in a database with fields for each or in a word document. 

The main to requirements.  Hope this helps.

Chris Adams
Core Member –
LinkedIn Profile
Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to organize Features and Business Rules for further discussions?

Community Blog - Latest Posts

What is Data Analytics? To understand the meaning of Predictive Analytics, let’s describe what Data is first. Data is a collection of facts, information, and observations related to a context. The data can be either structured or unstructured, stored in databases, spreadsheets, files, etc. Data analytics is the science of examining the data ...
1 Responses
There are many definition of business rules and the one that I really like is that business rules are: Criterion used to: Guide conduct or actions. Shape judgments of behavior. Make decisions. Ronald Ross   Having this definition in mind, let’s see what challenges a traditional rules management system w...
0 Responses
Goli Tajadod
Goli Tajadod
Patient diagnosis using Predictive Analytics In previous post we discussed different levels of Analytics, here we show a practical example of Predictive Analytics. What if Doctors and Patients could not just get a second opinion, but a third and fourth, and fifth, and so on? We believe that our doctors are all medical experts but patient diag...
0 Responses

Latest Articles

General Data Protection Regulation (GDPR)
Mar 21, 2018
It your responsibility to make sure that you understand what the impact of GDPR are going to be for the data that you work with. There is no doubt tha...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC