Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
*Could I translate user stories in UML diagrams to teach oriented object project? *Is it right?
*Is there someone with experience in it?
Your question is an interesting one, and using use case to model story is a debate and I am quite sure that there are a lot's of talk about UML usage in Scrum or Agile method.
I am not sure that Scrum experts would agree that a user story is a use case. For example, for me a use case is associated to a full description and for my understanding this is not the case of a user story.
Maybe this difference between use case and user story could help.
UML has "Use Case Diagrams" which are pretty much the UML version of a User Story.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
How to represent a system like google docs queuing system using UML class diagrams? I haven't used much UML and trying to design a system like Google docs.
I'm not a UML pro but I took a quick stab at it. There's probably some missing pieces here but I think it's a good start. It would be great if someone who knows how to correctly model this can provide their diagram.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I just drew an activity diagram, and I have 14 actors in my case. (I am making an activity diagram of online shopping site.)
Anyway... I am facing a problem with it, I am curious whether I must draw all actors in my diagram.
I have few system actors, so I am confusing how I place those actors between normal actors and system actors.
There are seller, non-seller who only buy products, and a manager who checks product posts. And finally I have to draw shipping system, certifying credit system, and more.
Thank you.
Well, I would say your use case is cut the wrong way. If it involves 14 actors then it looks like a pot of spaghetti and you did not sort out well. Look at the use case and try to find out what is wrong. There should not be more than 3 actors involved.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I'm learning about UML diagram and sequence diagram at the moment in one of my courses for my CS degree, and I wonder that if this is something that is common to use for developers or if this is just one of many approaches to analyse the design of the system.
I'm so used to the Waterfall model and wondering if there would be any benefits for switching my mindset.
Maybe the answer is obvious, but still think it would be interesting to hear from people that are more experienced in the area.
My first advice is not to mix concepts:
UML = modeling language.
Useful to describe/visualize the design of a system.
Waterfall model = design process.
Useful to describe in a linear-sequential manner the life cycle of a system.
This is a very short and non-deep description but ilustrates your question about the specific case of sequence diagrams, so in a real case scenario you probably will end using both like this:
-Requirement/Analysis: during this phase you will start creating some of the first UML Use case diagrams for your system.
-System Design: during this phase (or even earlier) you will start creating UML Sequence diagrams, UML Component diagrams and so on.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
It's been a really long time since I worked with UML Diagrams.
I started working with UML Use Cases again, for a real world project. I would like to ask some questions.
How should I approach writing use cases?
I believe the tasks that leads to a "Major/Bigger" task should not be considered as use cases by themselves. Am I right?
Okay, what if I have a task like View tutorial and it has Comment on Tutorial, Favourite Tutorial, etc. Should these be separate use case, Extending View Tutorial? If yes, but, aren't they small features, why we should include them?
I'm mixing some stuff here, I hope someone could enlighten me .
Thanks!
Read Alistair Cockburn's Effective Use Cases book (see it on Amazon: 1). He does an excellent job of explaining practical use of use cases in a structured and effective way.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
In Agile, should the 'user' in a user story always be the end-user or could it refer to different type of user? For example, is it acceptable to write something along the lines of, "As a developer I would like to have an interface to component B so that I can communicate with it from component A" or should it be restructured in terms of the benefit that such an interface would ultimately present to the end-user?
Chris,
The answer is "it depends on who the customer is". User stories need to be understandable and if possible written by your customer. If your customer is a developer of component A or B then it would make sense to you both.
However, if the customer doesn't immediately see the benefit of that I would ask "why" I was adding that interface and keep asking "why" until I get to an answer that the customer does understand. Then I'd write the user story so that the customer can understand what is being delivered.
Mike Cohen's book User Stories Applied is very good if you're looking for something more substantial to read.
http://www.amazon.co.uk/User-Stories-Applied-Development-Signature/dp/0321205685/ref=cm_rdp_product
Of course it is. If you are say writing a dll to develop with, then you are the end user of the dll...