Business Requirements Modeling

How would you use Requirements Modeling and when?

Questions by sbice

Showing Answers 1 - 15 of 15 Answers

renuc

  • Jan 14th, 2009
 

When the application environment is complex and multidimensional and when many people are directly involved in using the system then we should use business modeling.
Example- We do not need busienss modeling if we are adding another feature in an existing telecom system but if we are making a new order entry system then we should use business modeling to take good advantage to support problem analysis

Arpit Mediratta

  • Mar 20th, 2009
 

I agree with the above answer but the Example been given is not absolutely correct.

Any time if you are adding some new module/application, you need to revise the Modeling Structure.

WHY TO REVISE:

Now this is an important question why to revise everytime when you add something new in to existing application.

See a very basic example is, lets suppose we have Requirment Management Tool, like RequisitePro.... if we have traceability between/among the requirements and we add new requiremnt then immediately it shows ERROR.

Why so? because it is afraid of that new requirement may change or conflict with any other requirement of the system.

Same here, if we don't add the new element in MODELING structure, no matters whatever modeling technique one is using, it might be Use Case diagram, flow, activity or any diagram, it may get stuck anywhere.

PURPOSE of MODELING-

1. Modeling is not so much used by BA but used extensively by Technical Programming Manager.

If any new element is not been added into the Modeling, how he will come to know that a new element has entered into the PROCESS.

2. Lets suppose BA is onsite for some time and new person or BA is overlooking the same process. Who will let him know that process has been changed due to some element.

So anytime if a single requirement/element is been adding/changing/deleting, revise into the MODELING.

Thanks and Regards,
arpit mediratta

  Was this answer useful?  Yes

jaskanwar

  • Jun 11th, 2009
 

I partially agree with arpit mediratta point...but i think everytime a small change which needs to be implemented you need not re-model the whole business process again.

Proper impact analysis should be done and all the impacted areas should be identified well in advance to remodel only that portion which is getting impacted.

srik_ba

  • Aug 16th, 2009
 

Each changes need mention in the modeling which is already developed.  Thus covering the change, no matter what level of change it is.  This will especially help in requirement tracibility matrix

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions