Efficient, Unified, and Intelligent User Requirement Collection and Analysis in Global Enterprises

Boukhari, Ilyès; Bellatreche, Ladjel; Khouri, Selma

doi:10.1145/2539150.2539263

Cited by 8 publications

(2 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Definition of the Pivot Model: in order to identify the different components of our pivot model, we deeply studied three important formalisms used in requirements-driven DW design : Goal-Oriented formalism, Process-Oriented language (we studied MCT model, a process model of MERISE, a french modeling methodology), and UML use case formalism. We proposed in [2] the proposed pivot model. Let's take the following requirement example to illustrate the model concepts: "the system should analyze attendance of students to courses".…”

Section: Requirements Definitionmentioning

confidence: 99%

See 1 more Smart Citation

Requirements Driven Data Warehouse Design: We Can Go Further

Khouri

Bellatreche

Jean

et al. 2014

Leveraging Applications of Formal Methods, Verification and Validation. Specialized Techniques and Applications

Self Cite

View full text Add to dashboard Cite

Data warehouses (DW) are defined as data integration systems constructed from a set of heterogeneous sources and user's requirements. Heterogeneity is due to syntactic and semantic conflicts occurring between used concepts. Existing DW design methods associate heterogeneity only to data sources. We claim in this paper that heterogeneity is also associated to users' requirements. Actually, requirements are collected from heterogeneous target users, which can cause semantic conflicts between concepts expressed. Besides, requirements can be analyzed by heterogeneous designers having different design skills, which can cause formalism heterogeneity. Integration is the process that manages heterogeneity in DW design. Ontologies are recognized as the key solution for ensuring an automatic integration process. We propose to extend the use of ontologies to resolve conflicts between requirements. A pivot model is proposed for integrating requirements schemas expressed in different formalisms. A DW design method is proposed for providing the target DW schema (star or snowflake schema) that meets a uniformed and consistent set of requirements.

show abstract

Section: Requirements Definitionmentioning

confidence: 99%

“…3. Pivot metamodel connected to the ontology metamodel [2] Note that each requirement can introduce new concepts to the ontology. For example, the requirement "the system should analyze attendance of students to courses" will be defined as a new concept in the ontology (having action, result, criteria and metric properties).…”

Section: Requirements Definitionmentioning

confidence: 99%