4

I was wondering which symbol should be used for representing a user event (i.e. button click).

enter image description here seems like it should suffice, but isn't a user click technically enter image description here?

  • 1
    Why do you need to represent an event at all? Maybe a concrete example of what you are trying to represent would help me, but I've never had to represent button or key presses on a flowchart. – Thomas Owens Mar 6 '17 at 18:45
  • I need to chart out existing functionality so I have a basis to start documenting some new features. It's a file transfer piece, where users are displayed a grid of remote files that they can choose to download. It all starts with a click, right (heh I'm a bit sheltered). – samis Mar 6 '17 at 18:51
  • 1
    I'm probably need to zoom the abstraction level out a notch or two huh? – samis Mar 6 '17 at 19:06
  • 1
    I think when you're flow charting, the UI doesn't matter. So ignore the UI. Think about the inputs, outputs, data, processes, and decisions that you have. Inputs could be locations of file. Data would be the file metadata and/or the actual file contents. Processes could be authentication, authorization, and so on. – Thomas Owens Mar 6 '17 at 19:07
  • I forgot that I brought up a related flowchart question recently that was answered extremely throughly softwareengineering.stackexchange.com/questions/337875/… Looks like I need UML (I remember taking that class, but that was about it). My coworker suggested Interaction Diagrams in particular. – samis Mar 7 '17 at 13:18
1

Since this question remains unanswered, I'd like to expand on my comments.

In a flow chart, you probably don't need to represent events at the level of detail that you are thinking. A flow chart is a representation of a workflow, process, or algorithm. At the most basic level, it contains terminals (a start condition or event and one or more stop conditions or events), processes that cause data to change, decisions that need to be made, and input and output. There are some other concepts, such as referring to other processes (which may be documented in other flow charts), representing documents rather than just data, or manual operations that exist outside of the workflow or algorithm.

If you are modeling software, a button click is a very detailed event. If anything, the button click is most likely to be a terminal - the act of clicking a button starts a process. However, I wouldn't refer to this as a button click in a flow chart. This button click represents something at the process level - submitting data or forms, perhaps. That would be the true starting terminal. Alternatively, the entire process of a user completing a form could be represented as input - this would include every keystroke needed to complete the form as well as a button click or keystroke to submit it.

When you are creating flow charts, abstract away the user interface. Even abstract away the software. Think in terms of the data and information that you need and what high level events start the process. Put those onto the flow chart.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.