Data Semantics Requirements
A
data semantics requirement is a
data requirement that
specifies the semantic meaning of a mandatory data type of an
application,
component, or
business
object.
The typical objectives of a data semantics requirement are
to:
- Ensure that the stakeholders’ understand the
meaning of the data specified within the requirements.
The following are typical examples of data semantics
requirements:
- “An auction shall be identified as a Dutch auction
if and only if it has the following characteristics:
- Sellers list a minimum starting bid and number of
identical items for auction.
- There is no automatic proxy bidding.
- Bidders specify a bid price and desired quantity of
items.
- Once bidding closes, winning bidders are chosen based
(in order) on:
- Price. The highest bidders to bid become winning
bidders for the desired quantity of items as long as a
sufficient quantity of items remains. The bid price must
meet or exceed the reserve price.
- Desired Quantity. For bidders bidding the same price,
bidders that request a larger desired quantity of items
become winning bidders for their desired quantity as long
as a sufficient quantity of items remains.
- Time. For bidders bidding the same price and desired
quantity of items, bidders who place their bids first
become winning bidders for their desired quantity as long
as a sufficient quantity of items remains.
- All winning bidders pay the same lowest bid price that
meets or exceeds the reserve price, regardless of their
individual bid prices. (Note that Dutch auctions are
designed for sellers with multiple identical items to
auction, who are more interested in selling all items than
in maximizing the price per item.)”
The following guidelines have been found to be useful when
producing data semantics requirements:
- Every required data type should have a clear and concise
definition.
- Data semantic requirements may well overlap with the
definitions within the: