A use case describes an objective that a primary actor wants to accomplish and the sequence of interactions between the primary actor and a system such that the primary actor's objective is successfully achieved. Use cases are not functional requirements and do not define internal system processes that would not be visible to the user in their interaction with the system. Use cases are about describing system behavior from the perspective of the user and as such can be considered user requirements.
Use cases shift the perspective of requirements development to discussing what users need to accomplish, in contrast to the traditional elicitation approach of asking users what they want the system to do.
The World Wide Web is a vast, diverse, and dynamic ecosys- tem of content authored and consumed with innumerable frequency. Al- though content may have an original purpose, it can and will be repur- posed in new and unexpected ways.
As Open Data becomes commonplace, methods are needed to integrate disparate data from a variety of sources. Although Linked Data design has promise for integrating world wide data, integrators of- ten struggle to provide appropriate transparency for their sources and transformations.
Out-of-date or incomplete drug product labeling information may increase the risk of otherwise preventable adverse drug events. In recognition of these concerns, the United States Federal Drug Administration (FDA) requires drug product labels to include specific information.
Within the field of ocean science there is a long history of using controlled vocabularies and other Semantic Web techniques to provide a common and easily exchanged description of datasets.