After read some books suddenly a doubt grew up on my mind.
Is the included use case instanciable?
In "The reference manual":
On the page 277 we can read, after the question "Is the addition instanciable?": "Inclusion is not necessarily instanciable. It may be a fragment.". Reading this I�ve concluded that it can be instanciable.
On the page 297 we can read "The include relationship connects a base use case to inclusion use case. The inclusion use case in this relationship is not a separate instanciable classifier. Instead, it explicitly describes an additional behavior sequence that is inserted in to a use case instance that is executing the base use case". Here it looks like not instanciable.
In "Advanced Use Case Modeling":
On the page 166 we can read "Incuded use cases are simply use cases that are referenced within other use cases". If it is a normal use case it is instanciable and can be accessed straightly by an actor that want request a service.
What is the right approach? Is it instanciable? Can actors access it straighty without a base use case?
If I make for my application an "printer settings" window, that is a feature that can be accessed inside an use case or called by actor, can I call it a included use case?
Thanks
Vector
Busca Yahoo!
O melhor lugar para encontrar tudo o que voc� procura na Internet
