Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Sign Off
Previous Previous
 
Next Next
New Post 11/9/2009 5:39 PM
User is offline KJ
243 posts
6th Level Poster


Re: Requirements Sign Off 
Modified By KJ  on 11/9/2009 8:41:31 PM)

 

“A minimum of 100 forms shall be validated in a 24-hour period."
 
This is a Non-functional “performance” requirement (NFPR). And as these things go, they need to be viewed and responded to from a solution “Design/Build or Buy” perspective. The IT sign-off acknowledges receipt of the business needs only and IT will then pursue what is reasonable and feasible to satisfy the users’ requirement. The anxiety by IT indicates that they and the business do not have an agreed “delivery methodology” with the appropriate check-points. Furthermore, the business user needs to be educated that IT, as a partner, will design solutions within the resource constraints (time and money) as part of this delivery methodology.
 
For example, as part of the solution options IT may have to upgrade hardware. They will purchase extra disks and controllers if the 100 forms are IO intensive, or they may have to purchase extra RAM/Processors if the 100 forms are CPU intensive, to name a few solutions. The proposed hardware upgarde, which includes a hot-site, may be so costly that the initial NFPR is no longer economical and feasible as an in-house solution.  
 
Just a thought!
 
Warm regards,
K.
 
New Post 11/10/2009 4:24 AM
User is offline seaduspx
4 posts
No Ranking


Re: Requirements Sign Off 

Hello all!

The information provided is extremely beneficial and enlightening. 

Another question please.  With regard to the scope document, there are 2 schools  of thought here.  The first is that the scope document provides  a HIGH LEVEL overview of what is going to be achieved.  And that the detailed requirements are gathered, reviewed, and documented after the scope is established; thus providing a road map of sorts of what's in and  what's out of scope. The second school of thought is that the requirements should be written first and then included in the scope document. 

To me this is the proverbial "chicken of the egg" question. 

Any thoughts on this?  This may help me "explain" to others the solutions you all provided to me about the requirements.

Thanks!

 
New Post 11/10/2009 4:26 AM
User is offline seaduspx
4 posts
No Ranking


Re: Requirements Sign Off 

I'm sorry.  I may have been confusing in my last message. 

The first school of thought is that the scope is done first, which provides a roadmap to gathering the requirements.

Sorry about that. :-)

 
New Post 11/10/2009 10:26 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Requirements Sign Off 

Hi:

Great questions!   In the ideal, you would first create a context diagram.  A context diagram is a special type of data flow diagram in which the system is displayed as a single function/process - and also displayed is all the inputs to and outputs to/from the system.   As it displays the whole system as a single function/process, it is the highest level view of the system possible.  A context diagram is also an excellent scope statement, as it rigorously displays the extent of the system.

Notice that I bolded the words in the ideal.  One of the things you would be very wise to learn is that in the BA world, what is ideal is often not pratical.   In this case, especially for larger scale efforts, it is not possible to proceed in a pure top down manner as nobody - not even senior management - is knowledgeable enough to do such.  This is one of those dirty little truths that no one wants to discuss in books. 

So do the next best thing: proceed in as top-down a fashion as possible.  What I do is first create and verify some lower level data flow diagrams and then summarize them upwards into the top-level context diagram.   Key point:  Create lower level diagrams - but also create diagrams that may be very far from the lowest level diagrams - otherwise you very well risk drowning in an ocean of detail and never being able to identify scope.

Tony

 

 
New Post 11/10/2009 11:58 AM
User is offline Brian
2 posts
shadowfoot.com/footprints
No Ranking


Re: Requirements Sign Off 

Scope the project first. The context diagram will then allow you to see the scope of the work to be done, and you can document requirements within scope.

If you try documenting the requirements first you're likely to end up with a much bigger scope. With the scope defined you may still see scope creep, but this will have a better chance of being managed.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Requirements Sign Off

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