Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Context Diagram: Bank ATM Example
Previous Previous
Next Next
New Post 5/14/2008 7:01 AM
User is offline James-STL
10 posts
10th Level Poster

Re: Context Diagram: Bank ATM Example 

This is a great experience for a newbie such as myself. Thanks for pointing me in the direction of DIA.


I'm looking @ the context diagram and im wondering why there is no mention of how non-cash instruments/cheques will be extracted from the ATM? Would that not be a part of the context diagram or am i wrong?

Thanks again,

James - St. Louis Mo

New Post 5/14/2008 7:21 AM
User is offline sonavi
37 posts
9th Level Poster

Re: Context Diagram: Bank ATM Example 

Hi James,

When i read the Bank ATM requirements it didnt mention extracting cheques/ non cash instruments except Cash. What i have understood that we can only deposit cheques/non-cash instruments to the ATM but can't extract. I may be wrong but this is what i have understood.



New Post 5/14/2008 8:55 AM
User is offline James-STL
10 posts
10th Level Poster

Re: Context Diagram: Bank ATM Example 
Modified By James-STL  on 5/14/2008 10:56:51 AM)



I'm referring to the process for physically removing those negotiable instruments from the ATM. Would it be performed by XYZ?

Thanks for the quick turnaround...

New Post 5/14/2008 1:51 PM
User is offline roxy999
5 posts
10th Level Poster

Re: Context Diagram: Bank ATM Example 
Modified By roxy999  on 5/14/2008 3:52:31 PM)

Hi there.

As i worked for one of the bank the process of  picking up of physical instruments deposited was done by Teller manager Front Office, and after the checks are picked up they are entered in a saperate register and handed over to the Manager  ITem Processing Center, Operations Service Delivery for further processing  ...


New Post 5/14/2008 2:04 PM
User is offline Adrian M.
764 posts
3rd Level Poster

Re: Context Diagram: Bank ATM Example 
Modified By Modern Analyst  on 5/14/2008 4:22:48 PM)

Hi Guys,

It's awesome to see your enthusiasm! 

First of all, let's make sure we are all working off the same requirements (the last attachment in the previous thread).  I'll re-attach it here for easy reference.

Let me try to answer some of your questions and provide some feedback:

  • I'm not an expert on Context Diagrams and DFDs but I think we should clarify what is a Context Diagram. 
    • There are many folks who will use a context diagram to show all kinds of different things. 
    • From my perspective, a Context Diagram is the Level 0 of a set of Data Flow Diagrams.  Therefore, the Context Diagram itself is a data flow diagram.  What this means is that the relationships among processes and entities in a Context Diagram show Data Flow and not actions.  Therefore the relationships should not be named as "Verb Noun" but just  "Noun".
    • In both context diagram versions, the relationships seem to show actions and not data.  If you are going to create the next level of data flow diagrams  (decomposing what is supported by the "Use CyberBank ATM" ") then you will see that the verb labels, such as "Withdraw Cash", "Deposit Cash", etc. are actually sub-processes in lower level DFDs.
    • Any other Senior BAs care to comment on this one?
  • At the Level 0 of the Context Diagram, the main thing you need to identify correctly are all the external entities that will interact with our main process "Use Cyberbank ATM" process.  So you should take a look at the requirements document for such requirements.
    • The Customer is an external entity and you got that
    • If you take a look at Requirement # 2 you will see that the ATM must interact with the Cyberbank's main on-line banking system (OBS).  This should be in your context diagram as an external entity.
    • Are there others?  Take a look at the requirements doc?
    • Also - make sure that you don't have external entities which are not supported by the existing requirements or else we get "Scope Creep".  In one of the context diagrams I noticed an external entity called "Admin/Maintenance System".  Based on the requirements, I'm not sure what this is.

Lessons Learned - for ANY Business Analyst:

  • Make sure you understand your tools and their purpose.  In this case the Context Diagram: what is it, what are the rules, etc.  No understanding your tool leads to misuse which leads to the perception that that tool does not work or is not effective. 
  • Beware of Scope Creep! The business analyst must ensure he/she has a solid understanding of the requirements and when new ones come up the requirements document/repository should be update.  There are many instances where once a requirement has been identified, documented, and agreed upon, another stakeholder comes along who had a different experience at a different company/job and "assumes" on how the system should work without checking the requirements.

Best regards,

- Adrian

Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 Login to download attachment
Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Context Diagram: Bank ATM Example

Community Blog - Latest Posts

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 in Agora Insights' Blueprints for Success I'm thrilled to have Susan Moore join us for episode 9 in our Blueprints for Success. In this session, Susan shares her rich tapestry of experiences that have shaped her career. Her journey into business analysis (ba) is a compelling narrative of exploration and disco...
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...



Copyright 2006-2024 by Modern Analyst Media LLC