We need to document our company's system development life cycle (SDLC) process.
So we going down the V-Model levels, and for each level, drawing a process diagram showing the flow of human processes along the way, e.g., the Requirements department does a 'gather requirements' activity, then an 'evaluate requirements' activity, then structures them, and so on (just examples, of course). So we have come up with a diagram for many of each of the V-Model levels.
But .. challenge: Then some bright spark pointed out that different projects have different scopes/sizes (call it the Size Category -- e.g., it could be just a tweak (relative to an existing project) up to a whole new platform). So… for each project as it traverses the V-Model level, depending on the project size, not all the SDLC activities (e.g., full evaluate requirements) would actually need to be performed…
So. ... ok, one way would to, for each diagram, just add notes like "if you don't need to do 'Evaluate Requirements' then don't do it…
The challenge would be to find a visual way that is complete, correct and elegant (both correct and elegant …) to show this.
As usual, I assume that my company is not the first company to run into this.
I could think up a seqeunce of mathematical set assertions defining a 'graph', but that would not be a visual diagram.