Barak Agiv Itamar Ben-Zaken Barak Nahum Vladislav Smolensky Academic Advisor: Yuval Elovici Professional Advisor: Mira Balaban.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

An ASN.1 Profile Anders Ek
Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
Introduction to Visual Basic.NET Uploaded By: M.Sheraz anjum.
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Notes Dr. Alexander Apostolov.
Conversation Form l One path through a use case that emphasizes interactions between an actor and the system l Can show optional and repeated actions l.
Uml and Use Cases CS 414, Software Engineering I Mark Ardis Rose-Hulman Institute January 9, 2003.
Java Integrated Development Environments: ECLIPSE Part1 Installation.
NJIT Use Case Model Operation Contracts Prepared By: Sumit Sharma.
Academic Advisor: Prof. Ronen Brafman Team Members: Ran Isenberg Mirit Markovich Noa Aharon Alon Furman.
Barak Agiv Itamar Ben-Zaken Barak Nahum Vladislav Smolensky Academic Advisor: Yuval Elovici Professional Advisor: Mira Balaban.
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
Improving UML Class Diagrams using Design Patterns Semantics Shahar Maoz Work in Progress.
PROMPT: Algorithm and Tool for Automated Ontology Merging and Alignment Natalya F. Noy and Mark A. Musen.
© Copyright Eliyahu Brutman Programming Techniques Course.
Whole Platform Tesi di Dottorato di: RICCARDO SOLMI Università degli Studi di Bologna Facoltà di scienze matematiche, fisiche e naturali Corso di Dottorato.
Model Driven Integrated Development Environment Barak Agiv Itamar Ben-Zaken Vladislav Smolensky Academic Advisor: Yuval Elovici Professional Advisor: Mira.
Page 1 R Copyright © 1997 by Rational Software Corporation Analysis and Design with UML.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
An Approach and Tool for Synchronous Refactoring of UML Diagrams and Models Using Model-to-Model Transformations Hafsteinn Þór Einarsson Helmut Neukirchen.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
Faculty of Informatics and Information Technologies Slovak University of Technology Peter Kajsa and Ľubomír Majtás Design.
Ontology Development Kenneth Baclawski Northeastern University Harvard Medical School.
Page 1 What is the UML? UML stands for Unified Modeling Language The UML combines the best of the best from – Data Modeling concepts (Entity Relationship.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Introduction to the Unified Modeling Language “The act of drawing a diagram does not constitute analysis or design. … Still, having a well-defined and.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Integrated Development Environment for Policies Anjali B Shah Department of Computer Science and Electrical Engineering University of Maryland Baltimore.
Building Tools by Model Transformations in Eclipse Oskars Vilitis, Audris Kalnins, Edgars Celms, Elina Kalnina, Agris Sostaks, Janis Barzdins Institute.
1 MFI-5: Metamodel for Process models registration HE Keqing, WANG Chong State Key Lab. Of Software Engineering, Wuhan University
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Models for Language Engineering Bruno F. Barroca.
Page 1  Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling captures essential parts of.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Hyper/J and Concern Manipulation Environment. The need for AOSD tools and development environment AOSD requires a variety of tools Life cycle – support.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Lecture 3 Uses Cases Topics UML Use Cases pop quiz Readings: Chapter 3 January 24, 2008 CSCE 492 Software Engineering.
Composition of UML Described Refactoring Rules Presented by Chin-Yi Tsai.
ModelPedia Model Driven Engineering Graphical User Interfaces for Web 2.0 Sites Centro de Informática – CIn/UFPe ORCAS Group Eclipse GMF Fábio M. Pereira.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Phase 6 Start: Saturday14 April End: Saturday 21 April
LanguageLab A Meta-modelling Environment Terje Gjøsæter and Andreas Prinz, University of Agder, Norway SDL Forum 2015, Berlin, Germany.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Chapter 3: Introducing the UML
UML - Development Process 1 Software Development Process Using UML.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
Refining the Use Cases 1. How Use Cases Evolve  Early efforts typically define most of the major use cases.  The refining stages complete the process.
® IBM Software Group A Metamodeling Approach to Pattern Specification Maged Elaasar 1,2, Dr. Lionel Briand 1, Dr. Yvan Labiche 1 1 Carleton University,
Andrey Karaulov, Alexander Strabykin Institute for System Programming Russian Academy of Sciences SYRCoSE: Spring Young Researchers Colloquium on Software.
Requirement Engineering with URN: Integrating Goals and Scenarios Jean-François Roy Thesis Defense February 16, 2007.
Object-Oriented Software Engineering Practical Software Development using UML and Java Modelling with Classes.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
Module 9. Dealing with Generalization Course: Refactoring.
A UML-Based Pattern Specification Technique Presented by Chin-Yi Tsai IEEE TRANSACTION ON SOFTWARE ENGINEERING, VOL. 30, NO. 3, MARCH 2004 Robert B. France,
Evolution of UML.
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
Action Editor Storyboard
Business Models Modeling.
Daniel Amyot and Jun Biao Yan
Tools of Software Development
Informatics 43 Discussion, April 8, 2016
Chapter 20 Object-Oriented Analysis and Design
UML profiles.
MDT UML2Tools 0.8 Mini-deck
UML Design for an Automated Registration System
Presentation transcript:

Barak Agiv Itamar Ben-Zaken Barak Nahum Vladislav Smolensky Academic Advisor: Yuval Elovici Professional Advisor: Mira Balaban

To construct an Integrated Development Environment (IDE) for working with models  Providing feedback on the design  Providing modeling tools for the design process

 Modeling is an essential step in the design process of many systems  A common model is a structural model – depicts the structure of a system, rather than the behavior  A common notation is the Class Diagram in the Unified Modeling Language (UML)

 Class Diagrams allow significant expressive power, but also allow the creation of redundant, inconsistent and incorrect models  Designers are human – they make mistakes (e.g. lack of experience, complex models, merging several models)  Most UML Editors offer visualization of the model, and syntactic restrictions – but not semantic restrictions

 Deployed as an Eclipse plug-in  Feedback given in Problems View, graphical editor, dialogs

UML2Tools – graphical editors for UML diagrams UML2 – an EMF- implementation of the UML meta- model EMF (Eclipse Modeling Framework) – a meta-modeling framework Tools UML 2 Tools UML 2 (meta-model)EMF Framework

Rename Class After picking a new class in a wizard, a suggestion for renaming related: associations, fields and parameters is given Extract Interface Extract features from a class into a new interface, and update references to use the new interface In-line ClassMerge one class into the other Pull Up Field/Method Move a common field/method from several subclasses to their super-class.

 A class diagram before refactoring:

 In order to perform the Extract Interface refactoring we will need to:  Create the interface  Create the generalization between the class and the interface  Move the operations of the class to the interface  Update association ends that pointed to the class to now point to the interface

Defining Design- pattern templates Defining new templates and adding them to the tool-box Pasting Design- pattern templates into the model Picking a template from the tool-box and adding it to the model

Define Patterns Ability to add new pattern and registering it in the system Verifying a Model Against Registered Patterns Matching registered patterns against a model and warning when a match is found. For example: Contradictory generalization-set constraints Finite Satisfiability Pattern Patterns of Redundant and Incomplete Design Generalization – Sets Implementation Proposals We suggest to find the best alternative implementation for a generalization-set by the compiler constraints according to a heuristic search

 Hierarchy Cycle  Diamond Pattern

 Redundancy

 Verifying a model against an inconsistency pattern should take TBD seconds  The system will be able to handle a model with up to 2500 elements  Defining and registering a new template will be done visually  The system should be responsive at any time  Background processes can be aborted at any time

 Primary actors: Simple Modeler  Description: The modeler validates the model and looks for an inconsistency pattern. He can also choose to look for many/all the existing inconsistency patterns.  Trigger: The modeler wants to check the consistency of the model  Pre-conditions: none  Post-conditions: All the found patterns are shown to the modeler  Flow of events: 1. The modeler chooses the patterns he want to look for 2. The modeler starts the search 3. The system directs the modeler to the matched patterns  Alternative flows: None  Covered Requirements: Verifying a model against registered inconsistency-patterns