Usually the model is business requirements-->user requirements-->functional requirememts.
What if you have to make and implement some system changes that do not involve the users at all, ie it is a change to data or sending new data.
Do you just skip the use case and skip the user requirements going straight to functional?
It is kind of hard to see how the data would change except ultimately meet some customer need, unless is is stricly implementation specific data.
That said, data flow diagrams can be used to model the internal behavior of a computer system.
Tony
Hi ,
How does it impact the whole application?
as you are aware use is with Biz rule & Functional Requirement & you are taking about system requirement where user is not involved.
Do you see any difference with AS-IS work flow & to be work flow. ?? if yes the same need to be documented. take sign off & the move forward.
txh Anil
Anil:
With DFD's you can model the behavior of the whole application, including behavior that the end user does not "experience".
A good as-is is typically a highly negociated document. Some say a good as-is is 98% of a to-be.
Quite often the business requirement is the same as the user requirement?!
For example:
BR 2 new reporting fields should be handle in the system,
UR The user must be able to see these in his management reports
FR Process the 2 new fields business rule validate, check, etc.
brought to you by enabling practitioners & organizations to achieve their goals using: