OOAD artifact for a third party utility....

[Merlin M Koppula]

During implementation, the development team decides to use a third party utility to provide some of the required functionality. What OOAD artifact would MOST likely reflect this change?
(choose one)
a)Activity diagram
b)Package diagram
c)State diagram
d)Interaction diagram
I think (b) - package diagram is correct.
Because all the other diagrams are more detailed.
Interaction diagram models a single use case and hence can not show the entire application with reference to the functionality that is replace by the utility.
State diagram models a single object states. So, it canot be the answer.
I have some doubts about the activity diagram. It models the behavior of several objects across several use cases to acomplish a functionality.
So, I think either (a) or (b) is correct.
Please tell me what your views are on these choices.
Thanks.

[Suresh Ray]

In my opinion, Package Diagram is the correct answer, since we can represent logically distinct component(s) or objects, external(having varying interfaces ) to the system by using Package Diagram notation.
Activity Diagrams usually cover behaviour of objects spanning one or more use cases, but not the entire subsystem, hence (a) is incorrect.
Just my 2cents..

[Merlin M Koppula]

Suresh,
Thank you. I think package diagram as the correct answer too.
However, when I took the mock test, I got 93% with four questions wrong. one in development process, one in requirements modeling, two in architecture). So, I posted all the questions that I had doubt please see other questions that I posted today and let me know your opinion on them too.
Thanks.