I don't think I'll be posting about every diagram I do--they're not great works of art the world must see, and if you really wanna see them they'll be in the Github repo. But I did want to post something project specific for each piece of theory here. Thus, please see below.
I think this is pretty self explanatory, even to the uninitiated. Black dot with no ring is the start point, black dot with a ring is the end of the use case. In this case, we can end the use case by just...stopping, or by going on to the "create course" use case. Which will be a diagram I can link to, hence that weird symbol after the Create Course block.
As an aside, I'm using a program called Violet to do my diagrams, and have been for about a year now. It may not be as fancy as Visio or several online subscription options, but I'm honestly more interested in being able to get something on paper (so to speak) quickly, so I can start messing with it. I need to understand what I'm looking at, not be wowed by how cool it looks. Plus, the damn thing is free, period, so it's perfect for personal or student use.
Activity diagrams are really simple stuff, and you'll note I pulled the "main" use case (create an account) and didn't dive into the secondary ones (set e-mail, for instance). I feel there's a law of diminishing returns when nesting diagrams like this...and seriously, "set password" is a single method use case (or damn near), as far as what I have to write. I'm not mapping out that flow--that level of detail is where the sequence diagram and the class diagrams come in.
Again, while I'm knee-deep in planning and this is all front of mind, I don't really need a visual reminder of what is going on...but later, with the last use case I work on? Or if I need to go back in and debug something? Might as well just lay this all out, document it, and have it on hand for reference.
Y'know, like blueprints to a skyscraper.
I think this is pretty self explanatory, even to the uninitiated. Black dot with no ring is the start point, black dot with a ring is the end of the use case. In this case, we can end the use case by just...stopping, or by going on to the "create course" use case. Which will be a diagram I can link to, hence that weird symbol after the Create Course block.
As an aside, I'm using a program called Violet to do my diagrams, and have been for about a year now. It may not be as fancy as Visio or several online subscription options, but I'm honestly more interested in being able to get something on paper (so to speak) quickly, so I can start messing with it. I need to understand what I'm looking at, not be wowed by how cool it looks. Plus, the damn thing is free, period, so it's perfect for personal or student use.
Activity diagrams are really simple stuff, and you'll note I pulled the "main" use case (create an account) and didn't dive into the secondary ones (set e-mail, for instance). I feel there's a law of diminishing returns when nesting diagrams like this...and seriously, "set password" is a single method use case (or damn near), as far as what I have to write. I'm not mapping out that flow--that level of detail is where the sequence diagram and the class diagrams come in.
Again, while I'm knee-deep in planning and this is all front of mind, I don't really need a visual reminder of what is going on...but later, with the last use case I work on? Or if I need to go back in and debug something? Might as well just lay this all out, document it, and have it on hand for reference.
Y'know, like blueprints to a skyscraper.
Comments
Post a Comment