Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Detailed Requirements Document vs Use Case - whats the industry best practice
Previous Previous
 
Next Next
New Post 8/11/2011 3:26 PM
User is offline Hamiltonie
2 posts
No Ranking


Detailed Requirements Document vs Use Case - whats the industry best practice 

Hi all - First i know that many of you will say - "well that depends on the application" - lets say its a large scale build project that is *very* business rule and process intensive application and once completed the requirements needs to live on. The client already has numerous systems on site that use differing styles of requirements management - think detailed requirements documents (DRD's) on some and use cases on the other. I am now putting together an RMP that would be used for the new 'build' and the older systems to be assimilated into if possible.

I personally am a use case guy and always promote this style because i have seen many times a way to big gap between DRD's and development. The BA / SA never takes it low enough from that point on and the developer never logically models it / documents it from that point and 6 months down the line the developer and the BA are arguing about what should have been developed. With use cases that ambiguity is worked out before the package is delivered to the developer so there is a lot less margin for error.

Can anyone point me to a best practices document on what approach and when - is there such a thing ? Alot of it is fear of the unknown with some. Can anyone point me to some best practices or why one ios better than the other - or white papers ? I've read some of the threads on here like the case for use cases - good perspectives but i need more formal links (other than RUP / Agile who really sell there own methodology) independent links ?

Any help - input would be greatly appreciated - thanks,

Gary

 
New Post 8/12/2011 12:57 AM
User is offline Kimbo
450 posts
5th Level Poster


Re: Detailed Requirements Document vs Use Case - whats the industry best practice 
Modified By Kimbo  on 8/12/2011 3:09:07 AM)

 Hi Gary,

Interesting questions!

First of all, reading between the lines it sounds like you use Use Cases to model design. What everyone seems to call System Use Cases. We used to call that structured english or pseudocode back in the day, but no matter. Am I right? When I talk about use cases here I mean proper, solution agnostic business use cases not screen design.

Anyway I think a combination of textural requirements, process, functions (business use cases), business rules, non-functionals, business domain plus various other artefacts that you need from time to time, will define any system no matter how big or small. That is the business requirements. 

Systems analysis stuff, called functional requirements where I work but could be something else where you are, is about defining the screens, data, validations and other stuff needed to realise the business requirements and develop from.

I'm being simplistic but that's pretty much it in a nutshell.

Not sure there is anything like a best practice out there. Everyone will have a different opinion. I've been thinking of writing a paper about all this myself. No idea where to get in published though.

Anyway, when you find your "best practice", just remember that one man's best practice is the next man's belly laugh!

Kimbo

 
New Post 8/12/2011 12:11 PM
User is offline Hamiltonie
2 posts
No Ranking


Re: Detailed Requirements Document vs Use Case - whats the industry best practice 
Modified By Hamiltonie  on 8/12/2011 2:11:52 PM)

Thanks for the response - yes your very correct. To me a part of this problem has happened over the last 7-10 whereby (behind my back ) the role of business analyst got decomposed to being business analyst and system analyst. To me the business analyst has stepped alittle to out of the elaboration of requirements phase and the systems analyst has stepped out of the early construction phase and into it. But it is all based on your perception of correctness. But never the less both pieces to requirements analysts role / duties are still needed.

But even with all that said i still need some industry best practices as to best approaches and i'm having a problem finding good whitepapers on the subject. Any help would be appreciated.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Detailed Requirements Document vs Use Case - whats the industry best practice

Community Blog - Latest Posts

The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...
Elicitation involves bringing out or drawing out information. Elicitation is a key task in business analysis as without proper elicitation the requirements for the solution to the business needs cannot be identified. 1. Not understanding underlying business need Organization’s business environment keeps changing with respect to Customer...

 



 

Copyright 2006-2021 by Modern Analyst Media LLC