Measuring UML Conceptual Modeling Quality Samira SI-SAID CHERFI* Jacky AKOKA* Isabelle COMYN-WATTIAU* * CEDRIC - CNAM – Paris (France)

Slides:



Advertisements
Similar presentations
Software Engineering Key design concepts Design heuristics Design practices.
Advertisements

1 Software Architecture Completeness Analysis Christian LangeEindhoven, Software Architecture Completeness Analysis Interim Presentation Christian.
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Object-Oriented Software Development CS 3331 Fall 2009.
CS3773 Software Engineering Lecture 01 Introduction.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
© Copyright 2008, SoftWell Performance AB 1 Performance Testing Distributed Systems Concepts and Terminology v0.6.1.
The Vuel Concept: Towards a new way to manage Multiple Representations in Spatial Databases ISPRS / ICA Workshop Multi-Scale Representations of Spatial.
Object-Oriented Analysis and Design
Software Quality Metrics
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
Software Metrics II Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
1 A Framework for Measurement Valérie Paulus, Miguel Lopez, Gregory Seront, Simon Alexandre.
Software metrics Selected key concepts. Introduction Motivation:  Management:  Appraisal  Assurance  Control  Improvement  Research:  Cause-effect.
Validation of the Method Adoption Model for Functional Size Measurement of Web Applications Silvia Abrahão Valencia University of Technology, Spain
Ghent, July 6, Construction and Pre-test of a Semantic Expressiveness Measure for Conceptual Models Ann Maes Frederik Gailly Geert Poels Roland.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
1 Lecture 5 Introduction to Software Engineering Overview  What is Software Engineering  Software Engineering Issues  Waterfall Model  Waterfall Model.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
AOSE-2003, Melbourne July 15 th 1 Agent Oriented modeling by interleaving formal and informal analysis Anna Perini 1, Marco Pistore 2,1, Marco Roveri 1,
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Presenting and communicating statistics: principles, components, and their quality assessment. A proposal Filomena Maggino & Marco Trapani Università degli.
Software Engineering CS B Prof. George Heineman.
1 An Analytical Evaluation of BPMN Using a Semiotic Quality Framework Terje Wahl & Guttorm Sindre NTNU, Norway Terje Wahl, 14. June 2005.
Requirements Analysis
Quality Models and Quality Attributes. Outline  Process and product quality Improving the quality of the process can improve the quality of the product.
ITEC224 Database Programming
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Improving Design Workflow in Architectural Design Applications Presentation Doctoral Seminar 16/06/2006 Leuven (Belgium)
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Object-Oriented Analysis and Design An Introduction.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Validated Model Transformation Tihamér Levendovszky Budapest University of Technology and Economics Department of Automation and Applied Informatics Applied.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Software Quality Metrics
Temporal Modelling Project Johanna Drucker & Bethany Nowviskie University of Virginia.
Domain Model Classes and Objects Association Structure Requirement Specification Domain Model.
A Context Model based on Ontological Languages: a Proposal for Information Visualization School of Informatics Castilla-La Mancha University Ramón Hervás.
The Information School of the University of Washington LIS 570 Session 8.2 Notes on Presentations and Papers.
Software Prototyping. Introduction Builds an approximation to some system Builds an approximation to some system Easy to learn and understand different.
ICT EMMSAD’05 13/ Assessing Business Process Modeling Languages Using a Generic Quality Framework Anna Gunhild Nysetvold* John Krogstie *, § IDI,
A Metrics Program. Advantages of Collecting Software Quality Metrics Objective assessments as to whether quality requirements are being met can be made.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Understanding Data Intensive Systems Using Dynamic Analysis and Visualization Nesrine NOUGHI.
The Structure of the User Interface Lecture # 8 1 Gabriel Spitz.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
West Virginia University Sherif Yacoub, Hany H. Ammar, and Ali Mili A UML Model for Analyzing Software Quality Sherif Yacoub, Hany H. Ammar, and Ali Mili.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Software Measurement: A Necessary Scientific Basis By Norman Fenton Presented by Siv Hilde Houmb Friday 1 November.
 Introduction  Methodology  Case Study 1 : Event-B and RODN  Case Study 2 : B-Method and Atelier B  Observations and Analysis  Conclusion.
Be.wi-ol.de User-friendly ontology design Nikolai Dahlem Universität Oldenburg.
Chapter 5 – Software Tools. 5.1 Introduction Tools valuable for –Specification –Interface Building –Evaluation.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Aspect-oriented Code Generation Approaches Abid Mehmood & Dayang N. A. Jawawi Department of Software Engineering Faculty of Computer Science and Information.
A Hierarchical Model for Object-Oriented Design Quality Assessment
Rekayasa Perangkat Lunak Part-10
Rekayasa Perangkat Lunak
Object-Oriented Analysis and Design
Conceptual data modeling
Rekayasa Perangkat Lunak
Ada – 1983 History’s largest design effort
Measuring Data Quality and Compilation of Metadata
Object oriented analysis and design
Graphical Modeling of INFOD applications
Geographic Information Systems
Presentation transcript:

Measuring UML Conceptual Modeling Quality Samira SI-SAID CHERFI* Jacky AKOKA* Isabelle COMYN-WATTIAU* * CEDRIC - CNAM – Paris (France)

BDA 2002 october21th-25th 2 Outline Introduction Related literature Contribution Quality framework Quality metrics Quality assessment validation Conclusion Future work

BDA 2002 october21th-25th 3 Motivations Focus on early artifacts ( conceptual schemas ) Quality assessment approach Quality criteria Quality metrics Purpose-oriented quality assessment Weighted quality metrics Extensible quality metrics Genericity of metrics  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 4 Related literature Software products quality Fault prediction through program code quality assessment [Davis, 90],... Data quality Intuitive [Wang,95],... Theoretical [Wand,96],... Empirical [Wang,96],... Conceptual schemas quality [Batini,92],... Mainly qualitative criteria  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 5 Conceptual quality assessment A conceptual schema should: Provide a formal representation of the observed reality Meet the users requirements Be a basis for the future IS implementation and evolution  Motivations  Related literature  Contribution Quality framework Quality metrics Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 6 Quality assessment approach Quality criteria measured by quality metrics along each dimension  Motivations  Related literature  Contribution  Quality framework Quality metrics Quality assessment validation  Conclusion  Future work Quality Implementation Implementability Maintainability Specification Legibility Clarity Minimality Expressiveness Simplicity Correctness Usage Completeness Understandability

BDA 2002 october21th-25th 7 Quality assessment approach The specification dimension: efficiently use the notation provided by the model Easy to read (visual considerations) Simple (nature of concepts) Expressive enough (richness of models) Correct Legibility Simplicity Expressiveness Correctness  Motivations  Related literature  Contribution  Quality framework Quality metrics Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 8 The usage dimension: how close is the conceptual schema to the users perception Quality assessment approach Complete (requirements coverage) Easy to understand (how close are the modeling concepts to the users reality) Completeness Understandability  Motivations  Related literature  Contribution  Quality framework Quality metrics Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 9 Quality assessment approach The implementation dimension: ease of models implementation and evolution How far are the conceptual constructs from the implementation aspects? How easy is the evolution of the information system? Implementability Maintainability  Motivations  Related literature  Contribution  Quality framework Quality metrics Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 10 Metrics evaluation: Legibility ( Clarity )  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work 0.331

BDA 2002 october21th-25th 11 Metrics evaluation: Legibility ( Non- redundancy )  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work Administration_staff Medical_staff Service 1..* works_in 1..* works_in Administration_staffMedical_staff Service Staff 1..* works_in

BDA 2002 october21th-25th 12 Metrics evaluation: Legibility ( Aggregation degree) Where Level(Unnest(Ci)) counts the number of aggregation levels of an attribute Ci and NB(Ci) is the number of attributes in the schema  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 13 Where H is a hierarchy, Ci Є {attribute, association, operation}, DEF(Ci) counts the number of occurrences of Ci in H, USE(Ci) counts the number of inheritances of an element Ci+1, NB(H) is the number of hierarchies, and NB(Ci) the number concepts in H Metrics evaluation: Legibility ( Factorization degree)  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 14 Metrics evaluation: Expressiveness  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work Doctor Practitioner Researcher Independent_consultant Practitioner_researcher

BDA 2002 october21th-25th 15 Metrics evaluation: Simplicity  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work Doctor Practitioner Researcher Independent_consultant Practitioner_researcher

BDA 2002 october21th-25th 16 Quality assessment  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work Genericity of metrics Application to Entity-relationship formalism[ER2002] Application to a case study The quality of a schema depends on its purpose Constructing a « good » conceptual schema implies making a compromise between several quality criteria The difficulty of defining and interpreting a quality absolute value

BDA 2002 october21th-25th 17 Quality assessment

BDA 2002 october21th-25th 18 Quality assessment: prototype Adding quality measurement functionality to a CASE tool Construct an evolutive and modular solution

BDA 2002 october21th-25th 19 Quality assessment: prototype

BDA 2002 october21th-25th 20 Conclusion A quality evaluation framework Quality criteria and quality metrics Purpose-orientation of the metrics Genericity of metrics  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 21 Future work Enrich the framework (implementation and usage) Metrics for dynamic aspects in O. O. approaches Use the framework for quality approaches comparison  Motivations  Related literature  Contribution  Quality framework  Quality metrics  Quality assessment validation  Conclusion  Future work

BDA 2002 october21th-25th 22 Questions