Results for area 10.4 General concepts
a statement of what objective results are to be provided by the standard and how it is intended to achieve the vision
a statement summarising the overall concept and goals that the standard seeks to achieve
purposes for which personal data are collected
the exact equipment specification or manufacturers identification as installed in a deployment
a design in generic terms based on a requirement rather than an exact identification of equipment specification or manufacturers identification
data concept; structural relationship
ability of a device to perform its intended function under given conditions of use for a specified period of time (or number of cycles)
word denoting a description that is one level of abstraction above the concept being described
specialization/generalization relationship in which an object class of a specialized element (child) is substituted for a generalized element (parent)
taxonomic relationship between a more general element and a more specific element
NOTE 1 The more specific element is fully consistent with the more general element (it has all of its properties, members, and relationships) and may contain additional information.
NOTE 2 In the metamodel, a Generalization is a directed inheritance relationship, uniting a GeneralizableElement with a more general GeneralizableElement in a hierarchy. Generalization is a subtyping relationship; that is, an Instance of the more general GeneralizableElement may be substituted by an Instance of the more specific GeneralizableElement.
framework that may be used repeatedly to meet requirements that are similar to some extent
rigorous statement of policy, sometimes expressed in the format IF…THEN…ELSE…, that must be followed when the stated conditions are satisfied
structured proposal for business improvement that functions as a decision package for decision-makers The business case should explain why a project is required for the business and what the product or service is going to be. It should include an outline of the “Return on Investment” (ROI), or a cost/benefit analysis for the project, the project's product and performance characteristics, major project risks and the opportunities.
The business case addresses, at a high level, the business needs that the project seeks to meet. It includes the reasons for the project, the expected business benefits, the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a GAP analysis and the expected risks.
statement of user need, typically expressed in a single-sentence form to assist with later verification of compliance
representation of a series of interactions between an outside entity and the system, which ends by providing business value
NOTE A use case is a sequence of actions that an actor (usually a person, but perhaps an external entity, such as another system) performs within a system to achieve a particular goal.
state of an entity or a set of state variables; also the qualification of a contract or agreement
named value denoting a characteristic of an element; a property has semantic impact
NOTE Certain properties are predefined in the UML; others MAY be user defined. See: tagged value.
relationship nature of how two entities affect each other including dependencies
process based on data element transformation
ITS service actively requesting the data that is required for the service operation
ITS service operating on data delivered without request by an actor or its system