use-case

At the moment, I have defined 3 different use cases that are really just 3 steps in a business process ... Say I have a list of people, and all these people are interested in obtaining one or more limited resources (say for example, they are seats at concerts). Ultimately, I want to automatically and fairly allocate these people to the available seats. I have a few different algorithms I use to do this. I am documenting a system that already exists (retrospectively), so even through the process is a little convoluted, I can't change it. The process I have to use is as follows: 1) Define a set

Let's take the example of logging in and add item as two use case of an items management system. the requirements of the client are : (he needs/wants to : ) Gain legitimate access to the resources of the system; Add Item (create one). we also know that no unauthenticated user should use the system ! My questions are : 1) Is " Gain Access " a use case ? A precondition to other use-cases ? Or Both ? (knowing that by naming the use-case " Gain Access " and not "Logging in" I wanted to highlight the need rather than the solution to that need. 2) if " Gain Access " is a use-case, does the " Add

I am currently refreshing/altering my knowledge in software development because I will work in this area soon. We have learned a lot about UML diagrams and coding at University, but I have never brought it all together in a real Project. Therefore, I started to create a test web-app in Grails, and I wanted to begin with a requirements analysis and use cases too keep it close to reality. My web-app should allow users to share recipes, find recipes and review recipes by other users. Every recipe has many ingredients, which are not just strings but rather entities so that calories, fat, protein

I do not understand well following topic since it is a bit ambiguous from what I read: Inlcude is like a reference to next part, the usecase is not completed without it. This part should be referenced from more places otherwise its use has no sense. But I have seen an example when there is "include" only in some IF statement is true, like: Add new product--->include--->Add new manufacturer . //Adds only when doesnt exist. Why there isnt "extend"? Is it because somewhere else could be "Add new manufacturer" used once again? Thanks Exactly. Once you extend another use case you've reached the end

I'm trying to model some requirements and I saw some examples in the web with use cases generalization, but the UML 2.5 standard review doesn't say anything about generalization in Use Case Diagrams, or I can't find it. So, is generalization supported by standards? Since a UseCase is a Classifier, they can be generalized. The UML 2.5 spec contains an example of this in Fig. 18.11 on p. 686 (the "ATM Services" example). Tricky. While the Generalization relationship is defined as going between two Classifiers , and a Use Case is itself a specialization of a Classifier , the semantics of the

experimenting with Cockburn use cases in code I was writing some complicated UI code. I decided to employ Cockburn use cases with fish,kite,and sea levels (discussed by Martin Fowler in his book 'UML Distilled'). I wrapped Cockburn use cases in static C# objects so that I could test logical conditions against static constants which represented steps in a UI workflow. The idea was that you could read the code and know what it was doing because the wrapped objects and their public contants gave you ENGLISH use cases via namespaces. Also, I was going to use reflection to pump out error messages