I would suggest that it is graybox since you specifying and visually modeling and this is before any code is written. Without source code you have no white or glassbox. Blackbox is definitely out since you can see inside the box to an extent.
Graybox can generally mean that you have architectural knowledge of the product(s). This is what UML provides.
[This message has been edited by jpensyl (edited 11-12-2002).]
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by joe_dickason: It would seem that determining black vs. grey vs. white would depend on the UML diagram/notation you were using.
Use cases and use case diagrams are definitely black box.
Class or state diagrams more toward grey-black box.
I'll second Joe on this subject.
UML is "just" a notation. You can use it for different purposes. As an example, in our company we use it for use cases, high level system descriptions, process description, but we just plan to use it for design.
... Not even me.
Such a gray area! I think we are all in agreement here. The usage extent of UML and the associated detail make it easier to rather subjectively characterize the UML product as white, gray, or black. That said...
Generally speaking, a design is considered gray box when speaking systems.