Urgent! Give the Answers pl.

[Avijeet Dash]

1) What are the system's actors in the diagram, Figure Use Case ?
a) Clerk, Manager, Bank network
b) Clerk, Manager, Bank network, Customer
c) Clerk, Manager, Customer
d) Clerk, Manager
I hope u remember the diagram, there were 4 stick actors.
-----------------------------------------------------------
2) What is wrong with the following analysis use case?
a) The actor's actions and system responses are not separated.
b) "Sell goods" is too broad to be a use case.
c) There is nothing wrong with this use case.
d) There are design details intermixed with the requirements.
I hope again that u remember the image.
----------------------------------------------------------------
3) Scheduling project activities such as functional increments and test case development, which one of the following OOAD artifacts is the MOST useful?
a) Interaction diagrams
b) Package diagrams
c) Activity diagrams
d) Class Diagrams
e) Use cases
-----------------------------------------------------
4) Which of the following are true about services resulting from use cases?
a) New requirements in use cases generally result in one or more public methods in a business domain class.
b) Private methods are required by the system's use cases.
c) Use cases drive the design of interaction diagrams, which in turn define public methods in model classes.
----------------------------------------------------------------
5) True or False? All public methods in business objects come directly or indirectly from USe Case requirements.
-----------------------------------------------------------
6)which 2 should be present while writing USe Cases?
a) development team
b) OO Expert
c) domain expert
d) requirements decision maker
-------------------------------------------------
7) To MOST effectively manage teams working on different packages within a large project, which one of the following should be true?
a) An architecture board of team leads should negotiate and coordinate changes to inter-package messages.
b) One technical lead should control the project details and communicate decisions to the different teams.
c) Communications between the teams should be minimized to reduce overhead burdens while they work on separate, independent use cases for their packages.
d) The team leads should focus on quality designs for the internals of their packages, mentoring their team members
-------------------------------------------------
anticipating a quick reply.
thanks
Avijeet

[Laojar Chuger]

1). The answer should be a). Because there is no any connection between the system and actor Customer, it should not be considered as the actor of the system.
2). I could not found anything wrong with the use case. So c)should be the answer.
3). e). Use case. It is the current industry practice.
4). Seems to me the answer options is not complete.
5). I am not sure as you can say every method is from use case requirement. What's the deal of designing? What does it mean by indirectly?
6). c). domain export is a must. a). developing team is absoultely not needed. d). requirements decision maker is more important than OO expert. b). OO expert is not absolutely necessary. I would choose c). and d). However I have a feeling that I may have made a wrong choice.
7). a).

[Michal Harezlak]

This look like questions from IBM's 486 mock?
1) If I remember correctly the Customer did not interact with the system:
a) Clerk, Manager, Bank network
2)
d) There are design details intermixed with the requirements.
3) the process is use case driven
e) Use cases
4)
a) New requirements in use cases generally result in one or more public methods in a business domain class.
c) Use cases drive the design of interaction diagrams, which in turn define public methods in model classes.
5) true
6) i' m not sure here
c) domain expert
d) requirements decision maker
7)
a) An architecture board of team leads should negotiate and coordinate changes to inter-package messages.

[John Wetherbie]

Can someone verify these are from a mock exam vs a real one? I am not familiar with the "IBM 486" exam that you are talking about.
Thanks,
John

[Avijeet Dash]

These are from the mock.
Avijeet

[Tony Chen]

My choices:
1) http://certify.torolab.ibm.com/figures/test486F1.gif
a) Clerk, Manager, Bank network
2) http://certify.torolab.ibm.com/figures/test486F3.gif
d) There are design details intermixed with the requirements.
3)
e) Use cases
4)
a) New requirements in use cases generally result in one or more public methods in a business domain class.
c) Use cases drive the design of interaction diagrams, which in turn define public methods in model classes.
5)
True
6)
b) OO Expert
c) domain expert
7)
a) An architecture board of team leads should negotiate and coordinate changes to inter-package messages.

[Michal Harezlak]

Tony,
It looks like we agree upon most of the answers, except for 6.
I am pretty sure that the use case is "useless" if there was no decision maker involved. In other words you need to ask the client what he wants. � and since use cases are not a OO methodology there is no need for OO expert.
Regards.

[Laojar Chuger]

I tend to agree that OO expert is a better choice than decision maker. Without the OO expert, the domain expert could not even know the format and requirements of use case writing assuming he has not be trained before. One of the uses of use case is used as a mean for development management. Therefore decision will not have to be made till development. In addition, a well designed model needs to understand all the detail of the business domain, which could include all the possible use cases even they will not be implemented later.

[Michal Harezlak]

Laojar:
IMHO OO Expert is not a specialist on use case. Use cases are used in all kinds of systems (real time assembler systems). All the decisions regarding app functionality are make when writing use case, so decision maker is pretty essential. Lets say we are considering �sale item� use case, we need someone to make the decision if we should allowed use of debit cards or not (some places still don�t).

Originally posted by Laojar Chuger:
... a well designed model needs to understand all the detail of the business domain, which could include all the possible use cases even they will not be implemented later.

If you are not going to use it, Why bother?

[This message has been edited by Michal Harezlak (edited January 30, 2001).]

[Avijeet Dash]

a simillar question was there in the real test.
the options were very clear stating that different (domain/technology) experts need to be present partly whenever they are required and the requirement decision maker need to be present always and negotiate through domain experts and technology expert.

[Laojar Chuger]

Resonable.
One of the uses of the use case is for business procedure development. It is seems that use case format issue is not important in this case. However, the use case is the driving force for the whole oo process. Without a clearly defined use case, the oo process may end with at least an incomplete object model. My concern is to get a well designed model that is extensible. In this case the completeness of the use case model may be more important. That's why I am thinking OO expert is more important than decision maker.

[Tony Chen]

Michal & Laojar:
I still believe that the two person should be domain expert and OO expert. Today, I read a great book SanFrancisco Design Patterns by three IBMers. In the Appendix B, History of project SanFrancisco, it reads:
"In March 1995, the SanFrancisco project was started at the IBM site in Rochester, Minnesota, by a group of object-oriented technologists and a consortium of business partners. The first phase focused on four key and well-defined domains (Distribution, Logistics, General Ledger, and Accounts Payable/Accounts Receivable). Together, domain experts and object-oriented technologists started to define the core business activities (processes) with each of these domains. This work was carried out at various business partner sites in Sweden, Norway, and England. A larger business partner community reviewed the results of this analysis at various points in the process. While the domain content was being defined, the overall SanFrancisco technical architecture was also being defined."
What do you guys think?
[This message has been edited by Tony Chen (edited February 03, 2001).]

[Michal Harezlak]

Tony:
I still fail to see how OO Expert is helpful in defining use cases. What's more I believe that his presence might be harmful, by imposing "system oriented point of view". He dose not have any knowledge useful at this point. Use cases do not contain any information concerning system implementation.

[Glen Tanner]

I agree, Use Cases can be created entirely by the business analysts. Developers, etc. don't need to be involved.
So, my answer is: domain expert, and requirements decision maker.
All you need is someone with business domain experience (domain expert) and someone to decide the scope of the system (requirements decision maker). Remember that Use Cases are in the analysis phase, not design.
[This message has been edited by Glen Tanner (edited February 20, 2001).]