The VMEbus specifies features that are part of the VMEbus standard and features that are not part of the standard (e.., the choice of bus release algorithm). What are the strengths and weaknesses of this strategy (i.e., mandatory requirements vs. user options)?
What will be an ideal response?
This is an open?ended question. Essentially, a standard can be tight and all its aspects closely defined. Equally, it
can be loose and some of its aspects may be user?selectable options. The advantage of a tight standard with no
(or few) user options is that conformity and interoperability between systems is guaranteed. However, a very rigid
standard might alienate many potential users (because it is so restrictive). A loose standard can be more readily
adapted to suit circumstances; for example, the VMEbus standard does not define arbitration algorithms and
leaves the actual algorithm to the user.
You might also like to view...
In order for an object to be serialized, its class must implement the __________ interface.
a. Serial b. Serializable c. ObjectOutputStream d. Writeable
An agenda is a list of items you plan to discuss at a meeting.
Answer the following statement true (T) or false (F)