The “DQ_Requirement” metaclass represents a specific use case, necessary to model the DQ requirements (DQ dimensions) that will be relat to the “InformationCase” (IC) use cases.
The “InformationCase” metaclass represents the information cases (IC) of the Web application. Unlike normal use cases, the main function of the IC is to manage and store the data involv with the “WebProcess” type functionalities. This data will be relat to the specific DQ requirements (DQ_Requirement).
The Add_DQ_Metadata metaclass represents
a specific activity relat to the different “UserTransaction” activities. This metaclass is in charge of adding and/or verifying the DQ information (DQ metadata) associat with each of the instances of the DQ_Metadata and DQ_Validator metaclasses.
The “DQ_Metadata” metaclass represents a structural element of the belgium phone number library Web application. DQ metadata will be manag and stor here. This metadata will be associat with the “Content” type elements. In this sense, it will be possible to specify different DQ requirements directly how to take criticism? can you benefit from it? link to the data stor by the “Content” type elements.
Application using Eclipse plugin
The DQ_WebRE metamodel was implement in the Eclipse platform, making use of the Eclipse Modeling Framework (EMF). The “DQ_Validator” metaclass represents a structural australia aatabase airectory element of the Web system. This metaclass will be responsible for implementing specific DQ functions, with the aim of validating or restricting the user interface elements (WebUI) that the Web application will provide.