UML, flowchart between pages
I remember seeing something similar in college, but because it's been too many years I forgot.
Which diagram should I use to represent the flow between pages?
Would be similar to represent the overall structure of the website. Example: on page X the user can have access to such other pages. As it is a web system, depending on the user profile it can have access to the page and I can differentiate in the diagram with a color relative to the profile that has access. It's more or less that, so I can document the pages and the flow.
3 answers
After your editing, it became clearer to understand what you need. In this case, I don't think a sequence diagram is the best choice. The sequence diagram models the communications (or transitions, in your case) over time between the entities involved. Thus, its great use is to represent the logical sequence in which actions, usually in a specific use case, are performed by all involved (users and components of a system).
For what I I get it, your interest is more in the sense of representing two Things:
- the logical structure of the website, i.e. which pages are linked to which other pages
- properties of certain transitions, such as if only one profile is able to make / allow a certain transition.
Thus, I agree more with colleague @rray's answer , about the use of the state diagram. In it you can represent each page as a state of your system, and in the transitions add information (even the color, which you yourself suggested) to indicate its properties.
Wireframes, which I mentioned in comments, would be more useful if you want to go into a higher (but not final - that is, very low-level) level of detail regarding which areas of each page should allow for transitions. This helps you not only plan transitions but also other aspects of user interaction. In this type from diagram, more informal, you can draw the transition arrows starting from specific areas of a draft of the screen, for example to indicate whether the user should always click on the same region to navigate, on side columns to have access to tools, etc.
It should be noted that although I think the sequence diagram is not the most appropriate, this does not mean that you can not use it. You will probably only have to do several of them, for each Scenario navigation. And, even though I answer this question of yours with the best I can infer based on my experience, I still think it's a bit opinion-based, as there really isn't a more correct answer.
Series or sequence diagram .
The sequence diagram is one of the UML tools used to represent interactions between objects in a scenario, performed through of operations or methods (procedures or functions). This diagram is constructed from the use case diagram. First, it is defined what is the role of the system (Use Cases), then, is defined as the software will perform its role (sequence of operations).
Source wikipedia
To display this information there are two candidates, they are the diagram of states or activities.
State diagram or state machine serves to display transitions of objects, systems, or protocols.
Activity diagram , serves to model workflows, processes algorithms, much like a flowchart the difference is that the latter does not support parallel activities.