Hello,
My answer is it depends on other requirements that you did not state.
If you choose to refer to the "Customer identification" as a first step of every base use-case, that means the customer will have to identify each time he wants to withdraw, deposit, or transfer. They are sort of stand-alone operation: if customer wants to perform two instance of these use-cases in a raw, he will have to identify twice.
On the other hand, if you write "Customer identified" as a pre-condition, you leave room for specifying several use case instance without identifying each time (some ATM system allows you to perform several operations). Here you would have to specify clearly the post-conditions of base use-case and/or add a use-case for ending the operations. However, you may have only one use-case here which is "Perform Bank Operation" with different alternative flows (withdraw, deposit, transfer) that can combine several times in a use-case instance. It depends on how you specify the goal of the use-case.
Above all, everything depends on your reader's knowledge concerning the use-cases: if they aren't capable of understanding the same thing as you write, don't put too much effort in getting state-of-the-art use-cases. Write what you think they will understand, get them explain to you what they understood, possibly rewrite what they didn't get in a manner that suit them, and get (or give) them training on "state of the art" use-cases.
Regards,
Gilles.
-----Message d'origine-----
De: Minimole Liz Thomas (Systems)
A: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Date: 15/07/02 14:19
Objet: (RUP) Doubt on the Include relation in the Use Case Specification
Let me explain my doubt with an example.
For an ATM system, I have 3 use cases Withdraw Cash, Deposit Cash,
Transfer Funds
The Customer Identification becomes a first step for each of the above
mentioned use cases. So the Identify Customer is yet another use case
which can be included in the base use cases.
Should this include use case be referred to as the first step of each of
the base use cases or referred to in the Pre-Condition of each of the
base Use Cases. Which is the most appropriate way of
representing/including this abstract use case in the Use Case
Specification of the base use cases?
Please give me a feedback on this.
Thanking you in advance,
Minimole Liz Thomas
Project Manager.
************************************************************************
*********
* RUP Forum is a public venue for discussions about the
* Rational Unified Process (RUP).
*
* For RUP support materials, process Plug-Ins, tutorials, whitepapers,
* a biweekly column, Rational University training courses, and more,
* please visit the Rational Developer Network (available to Rational
* customers) at: http://www.rational.net.
*
* For technical support of RUP, RPW, Rose or any other Rational
* product, please visit: http://www.rational.com/support
*
* For other discussion groups, such as Rose and UML, please
* sign up at: http://www.rational.com/support/usergroups/index.jsp
*
* To reply to a posting, please "Reply to all" or send
* To: [EMAIL PROTECTED]
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
*
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send an email:
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rup_forum
*
************************************************************************
****
=========================================================================
Ce message et toutes les pi�ces jointes sont propri�t� de VALTECH et
susceptibles de contenir des informations confidentielles � l'intention
exclusive de ses destinataires. Si vous avez re�u ce message par erreur
ou si celui ci vous est parvenu incomplet ou alt�r�, merci d'en avertir
l'exp�diteur par retour.Toute utilisation, diffusion ou publication non
express�ment autoris�e par nous par �crit est strictement interdite.
--------------------------------------------------------------------------
This message and any attachments are Valtech property and may contain
iconfidential information intended solely for the addressees. If your are
not the intended recipient of this message or if you have received it
uncomplete or altered, please notify the author by replying to his e-mail
immediately. Any unauthorised use, diffusion or dissemination not
expressly authorised by us in writing is strictly prohibited.
=========================================================================
Copyright Valtech 2002
