How do you map a system?

[parwalrahul (Rahul Parwal)]

System analysis is an essential skill for software testers. It helps us identify how different parts of a system connect and where potential risks or opportunities for testing might lie.

While system mapping may seem daunting at first, using the right technique can simplify even the most complex systems.

This activity is all about putting system analysis into practice! Let’s explore different ways to visualise and understand a system and share what we find!

Steps:

1. Pick a system: Choose one from the list below list of possible application(s):

   • Social media platform
   • E-commerce website
   • Video streaming service
   • Fitness tracking app
   • Food delivery application

2. Select a tool: Use one of these tools to represent the system or choose your own technique:

   • Use Case Diagram - Focus on user interactions and system boundaries.
   • Data Flow Diagram (DFD) -Show how data moves through the system
   • Mind Map - Capture key components and their relationships.

3. Create your diagram:

   • Map out the key components and workflows of your chosen system.
   • Focus on making the diagram simple and clear.

4. Reflect:

   • Write a few sentences on what you learned from visualising the system.
   • Try using a second tool to create another diagram, then compare the results.

5. Share your work

   • Share your reflections and comparison findings in reply to this thread to share and gain insights from others.

Why take part?
Sharing your work helps others see different ways of analysing systems.

Looking forward to seeing your system maps!

[kiwi_in_oz (Mara Brownlee)]

I used the e-commerce site example and applied use case/mind map.

It is easier to visualise rather than looking a document, mapping out the use case diagram may be able to help you find things you may have missed reading a document (pages of text is never fun)

Mind map - found this was more higher level to plan for functional/non functional/technical + key features. But also could see how they relate to each other, and more of “what do we need/what is required” questions started to pop up.

Use case diagram - more zoned in to the step by step process of “how” the process works, but then also gets into the detail of what’s involved at which process. Also found I was asking more “what will happen if” questions. And so many arrows, Figma skills are still basic

Definitely one to work on!