So Ivar said to his friends “why don’t we actually ask users how they would use a system”.īut his friends were confused, “how would we do that?”, they asked. But when they built the systems they didn’t work too well because nobody had thought about how a user would actually use them. If you google him you will find out that he is still trying to get the IT industry to admit how simple things could be, while the rest of us are still trying make it all sound complicated so we can continue getting lots of cash for doing obvious things.Īccording to James King history (I haven’t checked my facts too carefully) people were building systems by asking the users what the system should do. I imagine he has his own groupies and he certainly has a big fan base, because he apparently invented sequence diagrams, he was one of the founding creators of UML and, if people had listened to him, he would have made the whole IT industry pretty simple and straightforward. Use cases were invented by a Swedish guy named Ivar Jacobson, who is really famous in geek circles. So I am going to recommend only using the good kind.īut what is a use case? It is simply an example of how a system (or business service) could be used by someone. I have encountered Use Cases on several occasions, sometimes they seem like a simple tool that can be used to better understand how a system behaves from a users perspective, while at other times people describe them as terrifying monsters that have murdered people and led to the destruction of entire projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |