Messages

1

Suggestions and Requests / Re: Element List improvements

« on: November 14, 2007, 07:11:43 am »

yes, me too

2

General Board / customizing the requirement fields

« on: November 19, 2007, 04:57:11 am »

Hi,
is there any way to change the possible values for the priority and difficulty fields of the requirement 'class'?

3

General Board / [help] changing properties of multiple elements

« on: November 14, 2007, 06:28:30 am »

Is it possible to change selected property of multiple elements at once ??
e.g. I have 100 Requirements in a package and I would like to change their status to "Implemented". Do I have to point-and-click each of them separately or is there a more effective way of doing it?

4

Uml Process / Re: how to model include relationship in uc scenar

« on: January 11, 2008, 07:06:38 am »

These stereotypes denote the structure of a text document, not the structure of an application system.

Well I can't really agree with you. Why can't those stereotypes be used while modelling an application system? The system use-cases idea states that the use cases document the iteractions between the actors and the system. And, therefore, one can use the 'extend' relationship when from a level of one interaction with the system (e.g. use case "browse invoices") he/she may invoke another iteraction (e.g. use case "download invoice documents")

Also note that you don't 'call' a use case in the same sense as you do a subroutine. Nor does the use case take parameters or return a result, at least not in the sense of a subroutine hierarchy.

You mean the function decomposition? Because, AFAIK, the use cases DO act "similar to calling a function or invoking an operation within source code" (Scott W. Ambler's article on reuse in use case model: http://www.agilemodeling.com/essays/useCaseReuse.htm).

As far as the preconditions are concerned, I agree it is a brilliant solution to most of the authorisation/login problems.  Though, in my application there will be various authorisation levels and the application will have to check user's authorisation level every time a "protected" operation would be accessed by him. Unluckily, this check often takes place in the middle of a use-case logic and according to our project methodology (maybe not the best one) we want to describe the use cases at such a detail level that we want to know when the authorisation level checking takes place (e.g. because very often we display a higher-level-authorisation-form then).

And thanks for your replies .

5

Uml Process / Re: how to model include relationship in uc scenar

« on: December 19, 2007, 06:48:04 am »

Of course! I have misunderstood the definition of Include relationship on wikipedia. Read only "There are no parameters or return values." but missed "The first use case often depends on the outcome of the included use case."

6

Uml Process / Re: how to model include relationship in uc scenar

« on: December 19, 2007, 06:19:04 am »

Thank you for your answers, the purpose I want to achieve is to factor out common logic from several use cases.

More specifically, I want to include an authorisation logic in a separate use case. According to UML specification, will the invoking (including) use case be aware of the included (authorisation) use case result (successful/failed)?

And one more question, BTW: Is there any difference between the "include" and "uses" relationship?

7

Uml Process / how to model include relationship in uc scenario

« on: December 05, 2007, 04:53:18 am »

Hi,
how do you model the include relationship in the use case scenario? Do you create a separate step e.g. 5. Include UC XXX or is there a better solution?