1 / 20

Integrated Development Environment for Working with Models ARD

Integrated Development Environment for Working with Models ARD. Barak Agiv Itamar Ben- Zaken Barak Nahum Vladislav Smolensky Academic Advisor: Yuval Elovici Professional Advisor: Mira Balaban. Vision. To construct an Integrated Development Environment (IDE) for working with models

gilda
Download Presentation

Integrated Development Environment for Working with Models ARD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Integrated Development Environment for Working with ModelsARD Barak Agiv Itamar Ben-Zaken Barak Nahum VladislavSmolensky Academic Advisor: Yuval Elovici Professional Advisor: Mira Balaban

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

  3. The Problem Domain • 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)

  4. The Problem Domain Cont. • 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

  5. Software Context • Deployed as an Eclipse plug-in • Feedback given in Problems View, graphical editor, dialogs

  6. Software Interfaces • UML2Tools – graphical editors for UML diagrams • UML2 – an EMF-implementation of the UML meta-model • EMF (Eclipse Modeling Framework) – a meta-modeling framework Framework Framework

  7. Functional Requirements – Class Diagram Refactoring

  8. Extract Interface – An Example • A class diagram before refactoring:

  9. Extract Interface • 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

  10. Functional Requirements – Templates Definition

  11. Templates – An Example

  12. Functional Requirements – Analyzing The Model

  13. Genset proposal – An Example

  14. Patterns Recognition - Examples • Hierarchy Cycle • Diamond Pattern

  15. Patterns Recognition - Examples • Redundancy

  16. Non-Functional Requirements • 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

  17. Use Case Diagram

  18. Model Verification Against Registered Patterns • 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

  19. Sequence Diagram

  20. Thank you!

More Related