Having read about the 4+1 Kruchten, I am required to document a system architecture using this concept. Instead of the notations proposed by Philippe Kruchten, we decided to go with UML instead. I am particularly interested in the process view, as I don't understand how to map this to my processes. I know I can use sequence diagrams or activity diagrams as suggested by Wikipedia and a paper by Sparx Systems. But they do not provide examples or details about the diagrams themselves. I have identified 8 processes in the application I am developing an architecture for. Does this imply that I would need to develop 8 sequence or activity diagrams? I don't feel it would be logical to compress all those different processes into just one of those diagrams.Example of some of the processes:Account registrationAccount authenticationAccount lookupChattingHow should the implementation of the Process View be performed, using either of the two diagrams proposed? Are the identified processes sensible, or are they too abstract? Is it sensible and clear to make, for example, 8 separate diagrams, or one diagram covering all the processes?
What does the Kruchten 4+1 Process View implementation look like using sequence or activity diagrams?
architecture;development process;uml