use-case

For a school assignment, we have to make a Usecase diagram. But the documentation that we have, is not very extended. It just describes what components a usecase consists of, and one example. We have to make a usecase about a library system. We have found 11 usecases, but I won't bother you with all of them. IIRC, a usecase describes a typical usage of a system, right? But what things belong on a usecase diagram, and how do they connect together? What we have now are four actors (member, employee, manager and accountant). The ones we have most problems with are member and employee. The

I have been reading documentation and watching screencasts specific to Mongo DB over the past few days and I am at a loss for when a solution like this would be better than a typical pg or mysql environment. Specifically, my question is under what circumstance (w/ use case would be nice) would you want to go the nosql route? Thanks! Many disparate writers. Especially when the writers can get segmented due to disconnections in the network, and will later need to resync data that has been written to on both sides of the bifurcation. This breaks ACID, and while you can solve the problem with

In a use case diagram what is the difference between <<includes>> , <<extends>> and <<uses>> ? Are <<includes>> and <<uses>> are the same thing? includes and uses are the same. From http://www.agilemodeling.com/essays/useCaseReuse.htm above An include dependency, formerly known as a uses relationship in UML v1.2 and earlier Nice writeup here: http://www.agilemodeling.com/essays/useCaseReuse.htm Summary from that article: An extending use case continues the behavior of a base use case. An include dependency is a generalization relationship denoting the inclusion of the behavior described by

I'm interested in using ZeroMQ in a project, but I'd like to hear about other's experience with it. I did some searching but found only mongrel2 project. Have you heard about other projects where it is used? What companies use ZeroMQ in production? We replaced usage of Unix named pipes with ZeroMQ. The communication overhead is equally not noticeable. And we got additional benefits: No limit on the message size. Ability to send the messages to remote boxes. No need to write our own thread for non-blocking send. Ability to receive messages from multiple sources. The webserver Mongrel2 uses

Question 1: What is the correct way to build a Use Case (or more than one) with 2 ways to do the same action? For example: I have a 3 screens in an iOS app: 1. A map view, which can be "long pressed" and has a camera button. 2. A camera view, which is shown if the user taps the camera button in the map view. 3. A place/pin editing view, which is shown if the user "long presses" the map view, or after the user chooses a photo in the camera view. This editing view has a save button to actually create the place with a photo and the location (long press coordinate or current location in case the

I want to have a correct use case diagram for an online job portal system. Here is my attemp: I have some doubts: I can't see where making "Login" use case witch is an important use case for this system. This use case diagram is not showing the difference between a simple visitor and a registered one. The former could view vacancies, view advice without the obligation for having an account. The latter could view vacancies, view advice, upload CV (after be logged), apply for a job (after be logged) ... Is having two actors "Simple visitor" and "Registred Visitor" in my diagram will be correct?

The concept of a coroutine sounds very interesting, but I don't know, if it makes sense in a real productive environment? What are use-cases for coroutines, that can be solved more elegant, simpler or more efficient as with other methods? True coroutines require support from your tooling - they need to be implemented by the compiler and supported by the underlying framework. One real world example of Coroutines is found with the "yield return" keyword provided in C# 2.0, which allows you to write a method that returns multiple values for looping. The "yield return" does have limitations,