use cases
Advantages: Nice way to wak through use cases to test your design. Nice to use when talking and developing in a team. Once you have the design down the coding can be stubbed out so that testing and developing can be done by more than one person. Easy to write up simple ones on a white-board.
Disadvantage: they are usually not documents that are kept up to date so they don't work well as long-term documentation
Activity diagrams' disadvantages:
UML modeling language include that these diagrams have the potential to become overly complex because their user-friendly nature may lend itself to an all-inclusive description. In other words, since it is so simple to display the information related to the project, why not include all of it? When an analyst has a large project, creating a single, overly complex diagram can be a temptation.
However, as one author notes, "if you are using activity diagrams to define the structure of a work flow, you should not attempt to explore several levels of activity graphs down to their most 'atomic' level". Instead, an analyst should try to present a new diagram for each work flow, or if more applicable, to use swimlanes to present different actors within the same work flow.
Another aspect of these diagrams is that they may not be used in lieu of a state diagram or sequence diagram because "activity diagrams do not give detail about how objects behave or how objects collaborate." This is not a disadvantage per se, but it is important for an analyst to keep in mind when applying diagrams to their work.
In conclusion, activity diagrams are fairly easy to get the hang of, and will be useful for most projects because they plainly and moderately clearly demonstrate how things work." Unlike many diagramming techniques, these diagrams also enable the depiction of multiple choices and actors within a work flow, and they are easy for even non-technical users to fol
Activity diagrams' advantages:
* UML modeling language included that these diagrams are normally easily comprehensible for both analysts and stakeholders.
* In UML for the IT Business Analyst, "The activity diagram is the one most useful to the IT BA for depicting work flow [because] it is simple to understand-both for BAs and end-users."
* Since they are among the most user-friendly diagrams available, they are generally regarded as an essential tool in an analyst's repertoire.
* Additionally, as stated above, activity diagrams allow an analyst to display multiple conditions and actors within a work flow through the use of swimlanes. Swimlanes, however, are optional as a single condition or actor is normally displayed without them
Advantages: Nice way to wak through use cases to test your design. Nice to use when talking and developing in a team. Once you have the design down the coding can be stubbed out so that testing and developing can be done by more than one person. Easy to write up simple ones on a white-board.
Disadvantage: they are usually not documents that are kept up to date so they don't work well as long-term documentation
Activity diagrams' disadvantages:
UML modeling language include that these diagrams have the potential to become overly complex because their user-friendly nature may lend itself to an all-inclusive description. In other words, since it is so simple to display the information related to the project, why not include all of it? When an analyst has a large project, creating a single, overly complex diagram can be a temptation.
However, as one author notes, "if you are using activity diagrams to define the structure of a work flow, you should not attempt to explore several levels of activity graphs down to their most 'atomic' level". Instead, an analyst should try to present a new diagram for each work flow, or if more applicable, to use swimlanes to present different actors within the same work flow.
Another aspect of these diagrams is that they may not be used in lieu of a state diagram or sequence diagram because "activity diagrams do not give detail about how objects behave or how objects collaborate." This is not a disadvantage per se, but it is important for an analyst to keep in mind when applying diagrams to their work.
In conclusion, activity diagrams are fairly easy to get the hang of, and will be useful for most projects because they plainly and moderately clearly demonstrate how things work." Unlike many diagramming techniques, these diagrams also enable the depiction of multiple choices and actors within a work flow, and they are easy for even non-technical users to fol
Activity diagrams' advantages:
* UML modeling language included that these diagrams are normally easily comprehensible for both analysts and stakeholders.
* In UML for the IT Business Analyst, "The activity diagram is the one most useful to the IT BA for depicting work flow [because] it is simple to understand-both for BAs and end-users."
* Since they are among the most user-friendly diagrams available, they are generally regarded as an essential tool in an analyst's repertoire.
* Additionally, as stated above, activity diagrams allow an analyst to display multiple conditions and actors within a work flow through the use of swimlanes. Swimlanes, however, are optional as a single condition or actor is normally displayed without them
Comments
Post a Comment