On the Representation of Intangible Objects such as Software in a Measurement Context Miguel Lopez Valérie Paulus Grégory Seront Simon Alexandre.

Slides:



Advertisements
Similar presentations
1 OOR in the Classroom An Experience Report Ken Baclawski Northeastern University.
Advertisements

MAPPING DATA FLOW DIAGRAMS INTO STRUCTURE CHARTS
Kellan Hilscher. Definition Different perspectives on the components, behavioral specifications, and interactions that make up a software system Importance.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der.
Train Control Language Teaching Computers Interlocking By: J. Endresen, E. Carlson, T. Moen1, K. J. Alme, Haugen, G. K. Olsen & A. Svendsen Synthesizing.
A Review of Ontology Mapping, Merging, and Integration Presenter: Yihong Ding.
1 A Framework for Measurement Valérie Paulus, Miguel Lopez, Gregory Seront, Simon Alexandre.
1 On the Pertinence of the Notion of Etalon (Standard) for Software Measure Valérie Paulus, Miguel Lopez, Gregory Seront, Simon Alexandre.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Ghent, July 6, Evaluating a COSMIC-FFP Measurement Procedure for Multi-Layer Object-Oriented Conceptual Schemas Simon Claeys (Master student Ghent.
Statement of the Problem Goal Establishes Setting of the Problem hypothesis Additional information to comprehend fully the meaning of the problem scopedefinitionsassumptions.
Conceptual modelling. Overview - what is the aim of the article? ”We build conceptual models in our heads to solve problems in our everyday life”… ”By.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Course Instructor: Aisha Azeem
Meaningful Modeling: What’s the Semantics of “Semantics”? David Harel, Weizmann Institute of Science Bernhard Rumpe, Technische Universität Braunschweig.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
HL7 UK 2003 (c) Abies Ltd Modelling Clinical Information Using UML Tim Benson Abies Ltd
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Analysis and construction of software measures Jean-Marc Desharnais.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
OOPSLA 2003 DSM Workshop Diagram Definition Facilities Based on Metamodel Mappings Edgars Celms, Audris Kalnins, Lelde Lace University of Latvia, IMCS,
Selective and Authentic Third-Party distribution of XML Documents - Yashaswini Harsha Kumar - Netaji Mandava (Oct 16 th 2006)
1/19 Component Design On-demand Learning Series Software Engineering of Web Application - Principles of Good Component Design Hunan University, Software.
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
November 21, 2005 Center for Hybrid and Embedded Software Systems Tivadar Szemethy, Institute for Software Integrated Systems, Vanderbilt University A.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
COMP 354 Software Engineering I Section BB Summer 2009 Dr Greg Butler
SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler
5 June 2013 SDMX Technical Working Group Luxembourg 1 5 June 2013 SDMX Technical Working Group Luxembourg 1 WP Item 6 The Expressions Language of Banca.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Standards for Mathematical Practice
Software Design Deriving a solution which satisfies software requirements.
Modeling and simulation of systems Model building Slovak University of Technology Faculty of Material Science and Technology in Trnava.
Dimitrios Skoutas Alkis Simitsis
1 LiSyC ENSIETA/DTN 02/04/2008 AADL execution semantics transformation for formal verification Joel Champeau, Thomas Abdoul, Pierre Yves Pillain, Philippe.
Hybrid Transformation Modeling Integrating a Declarative with an Imperative Model Transformation Language Pieter Van Gorp
Verification of behavioural elements of UML models using B Truong, Ninh-Thuan and Souquieres, Jeanine In Proceedings of the 2005 ACM Symposium on.
Dr.Basem Alkazemi
SOFTWARE DESIGN. INTRODUCTION There are 3 distinct types of activities in design 1.External design 2.Architectural design 3.Detailed design Architectural.
Semantics for DSL Group Members: Ritu Arora, Diyang Chu, Zekai Demirezen, Jeff Gray, Jacob Gulotta, Luis Pedro, Arturo Sanchez, Greg Sullivan,Ximing Yu.
Software Design Process
Formal Methods.
COMP 6471 Software Design Methodologies Winter 2006 Dr Greg Butler
ESDI Workshop on Conceptual Schema Languages and Tools
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
9-Dec Dec-15  INTRODUCTION.  FEATURES OF OOP.  ORGANIZATION OF DATA & FUNCTION IN OOP.  OOP’S DESIGN.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
MDA & RM-ODP. Why? Warehouses, factories, and supply chains are examples of distributed systems that can be thought of in terms of objects They are all.
Sheet 1 MDAFA 2003 A Synthesis-based Approach to Transformations in an MDA Software Development Process Ivan Kurtev, Klaas van den Berg University of Twente.
Sheet 1 Forum on Specification and Design Languages (FDL), Frankfurt, September 2003 UML to XML-Schema Transformation: a Case Study in Managing Alternative.
Chapter 10 Software quality. This chapter discusses n Some important properties we want our system to have, specifically correctness and maintainability.
Aim: What is the function notation? Do Now: 1. y = x + 2, find y when x = 4 2. y = x 2 + 1, find y when x = 2 HW: p.129 # 3,4,7,10,12,14,15 p.126 # 17,19,21.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
Software Design. Introduction Designing engineering encompasses the set of principles concepts and practices that lead to the development of a high quality.
Accreditation of study programs at the Faculty of information technologies Tempus SMGR BE ESABIH EU standards for accreditation of study.
MDD-Kurs / MDA Cortex Brainware Consulting & Training GmbH Copyright © 2007 Cortex Brainware GmbH Bild 1Ver.: 1.0 How does intelligent functionality implemented.
Design Concepts ch-8
Chapter 2 Object-Oriented Paradigm Overview
Analysis Classes Unit 5.
A Hierarchical Model for Object-Oriented Design Quality Assessment
State Digrams in UML: A Formal Senmatics using Graph Transformations
Requirements Analysis and Specification
Software Design Methodology
Modelling Clinical Information Using UML
Software Architecture & Design
Presentation transcript:

On the Representation of Intangible Objects such as Software in a Measurement Context Miguel Lopez Valérie Paulus Grégory Seront Simon Alexandre

Questions  Are software so intangible that measurement of such abstract beings is impossible?  Is the nature of software so impalpable?  How can we formulate the software representation problem in order to allow measurement?

More Questions  Is it relevant to measure software representations in order to make decisions concerning this software?  Are the representations of software relevant and suitable for measurement?

Software Models  To measure, we need a representation of the software because of its intangible nature.  The representation of a software is called a model.

Different Software Models  In the literature, a lot of languages for representing software can be found.  UML  Graphs  Source Code  ….

Software Meta-Model  The concepts and their relations used for building a model are explained in a meta-model.  So, meta-models exist for UML, graphs, and so on.

Software Meta-Model Problem  How can we select a relevant and suitable meta-model in measurement context?  Is that always necessary to use meta- models in order to measure a software?  For an external measure, do we have to work with meta-models?

Meta-model for Measurement  Measure Definition:  Mapping between an empirical set onto a mathematical set.  A mapping between an empirical set of objects A and a mathematical set of objects B. Set A Set B

Set A Problem  Set A is a set of empirical objects.  By definition, tangible objects.  Are software tangible objects?  Is all the software intangible?  Or, just some parts, some attributes?  Some software attributes are intangible.  Coupling, cohesion, complexity,efficiency,…

Set A Problem  So, to perceive those attributes, they need representation or model.  Set A is replaced by a set A’ which contains representations of objects of set A.  The transformation A -> A’ transforms intangible objects into tangible objects.

Set A Problem  Does the transformation A -> A’ keeps the structure of Set A?  When measuring an element of A’, are we measuring the corresponding element of A? Set A Set A’ Set B

Build Set A’  To build the set of representations or models, we need to define the elements used for modeling.  These elements are formalized in a meta-model.

Meta-Model  So, the meta-model must be relevant and suitable in regard with:  Measurement Goal  Entity: products, projects, process  Attribute: properties of the entity: efficiency, coupling,…

Measurement Method  A measurement method must at least define:  Its goal  The considered entity  The attribute to be measured  In regard with these three elements, a suitable and relevant meta-model must be built or selected.

Entity & Meta-model  In this presentation, only the entity software product is considered.  The meta-modelisation aims at modeling the entity.  Several types of software product entities exist:  Requirements Document  Design Document  Source Code  Executable

Entity & Meta-model  The meta-model depends on the type of entity.  For example:  Design Document:  Meta-model of UML: class, relations,…  Meta-model of graphs: nodes, edges,…

Entity, Meta-model, & Attribute  But, the meta-model also depends on the type of attribute.  In regard with the attribute, some meta- models are more relevant and suitable than others.

Entity, Meta-model, & Attribute  For example, measuring the functional size of a software product with Cosmic- FFP:  Entity: Requirements Document  Attribute: Functional size

Entity, Meta-model, & Attribute  Meta-Model: Cosmic-FFP

How to verify the meta-model?  Two methods:  Expert-based: the relevance and the suitability of the meta-model is evaluated by a set of experts.  Empirical: the relevance and the suitability is of the meta-model is evaluated within a set of entities coming real projects.

How to verify the meta-model?  Problems with these two methods:  Expert-based:  Reliability of the experts judgment.  Representativity of the experts sample.  Empirical:  What does mean suitable and relevant in operational terms?  How can we make representative samples?

Advantages to explicit the meta-model  An explicit meta-model allows to better understand the entity and the attribute to be measured.  To meta-model an entity like design, source code in terms of a given attribute (coupling,…), it is important to understand and clearly define these terms.

Advantages to explicit the meta-model  An explicit meta-model allows to identify early in the measurement method, the limits of measurement:  Cosmic-FFP meta-model does not take into account the complexity of the data movement.  So, the software with complex algorithms are not sized by COSMIC-FFP

Meta-model for all types of measurement  Meta-model in external measures are often implicit.  It is not necessary to explicit the meta- model of the entity for external measures.  Response time: which is the meta- model of the entity?

Conclusion  Does the entity meta-model a critical activity in software measurement?  Must this activity be explored in details?

Questions ??