UML,usecase
1.what's the difference b/w the UML and usecase?
2. if there is any common template / checklist is avaialable?
3.what is the baseline document for creating these diagrams?
Software/Hardware used:
Software/Hardware used:
ASKED:
October 26, 2007 3:47 AM
UPDATED:
March 30, 2011 7:17 AM
Answer Wiki:
UML is a modeling language that defines a standardized way to draw models of software systems. There are a number of different types of diagrams specified as part of the UML -
Class diagram
Object diagram
sequence diagram
Collaboration diagram
state diagrams
Activity diagram
Component diagram and
Deployment diagram
Selecting the diagram is based on the purpose and the requirement. use case diagram used to say how the software can be implemented and it will not stress how it can be implemented. and also UML stress on Object oriented design principles ,where designing software on OOD will be helpful. The full specification for the UML is available from the <a href="http://omg.org">Object Management Group</a> who design/revise/manage the specification. It is a pretty detailed document though. There are a number of simpler overviews. Here's <a href="http://www.agilemodeling.com/style/useCaseDiagram.htm">an example I found for use cases</a>.
To see all answers submitted to the Answer Wiki: View Answer History.
I’m not sure what you mean with the third point of your question — if you’re asking what context the use case diagrams should have, I’d say you should put them anywhere you need them. Usually I would expect to see them in a functional requirements document, for any particularly complicated or important interactions between users and the system. If that’s not what you meant, leave a comment and someone can revise the answer.
1) Use Cases are simply part of the UML tool set. One of the many means of communicating what the relevant functions are (things the business does)and how these functions relate to each other. There are in fact two levels of use cases – Business Use Cases and System Use Cases. Business Use Cases deal with interaction between the business and external systems / participants and System Use Cases describe interaction between an external system / user and the system function in focus.
2) There is no right and wrong in UML as the way it is adopted is quite unstructured with the exception of the symbology. That being the case, there are a stack of templates out there, each claiming to be better than the other. SO, in answer to your question, No, there are no ‘common’ templates and checklists. Look at it this way – if you are learning French, you are taught the formal / proper / purists’ version of the language. As your command of the language improves and your vocab increases, you start to bend a few ‘rules’ here and there (e.g. slang etc.). UML is no different.
3)UML can be adopted in all sorts of documents from initial scope documents right down to functional specs (as mentioned by LadyRatri). They are no restrictions as far as type of documents where you can include UML are concerned. As nutty as this may sound, you could even write a children’s story book in UML if you really wanted to!!! It really is that flexible.
If you’re looking for more resources or articles to help you better understand use cases and UML, SearchSoftwareQuality.com has several. Here are a few:
* Specifying IT: Key UML techniques in requirements
(http://searchsoftwarequality.techtarget.com/originalContent/0,289142,sid92_gci1273715,00.html)
* How to document use cases
(http://searchsoftwarequality.techtarget.com/originalContent/0,289142,sid92_gci1264767,00.html)
* The pros and cons of use case diagrams
(http://searchsoftwarequality.techtarget.com/originalContent/0,289142,sid92_gci1273406,00.html)