1 / 14

A Design Metatool

This project aims to create a metatool that captures the characteristics of various design tools, facilitating interaction and improving user experience. By employing a UML-based tool description model, the metatool will enable users to visualize the design flow and automate tool interactions based on given requirements. The implementation will leverage Java for transportability and an AWT GUI for user-friendliness. Future work includes extending the tool description model and enhancing GUI features to improve scalability and usability.

marty
Télécharger la présentation

A Design Metatool

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. A Design Metatool Rong Chen Mentors: Roberto Passerone, BassamTabbara Supervised by Prof. ALBERTO SANGIOVANNI-VINCENTELLI

  2. The Problem • Current design tools • are powerful • can achieve different design goals • But, they • need users to help them interact with each other • hide inner design flow from users

  3. Project Objective • Design a metatool to • capture different tools’ characteristics • show the design flow to users • make tools interact by themselves • be user-friendly (GUI)

  4. Tool-Description Model • Describe tool characteristics • name • inputs and their formats • outputs and their formats • commands and options • etc.

  5. Tool-Description Model • Build a tool-description model • language: UML • tools: Together/J • current model: small (a couple of classes) • expected model: large (many classes and packages) • scalability: good

  6. Tool-Description Model Together/J PolisTool association visual design DataBase name command ... instance instance build-sg sg-to-c class dependence object

  7. Tool-Description Model Together/J Public class PolisTool { public string name; private string command; ... private DataBase database1; } automaticaly genarated codes Public class DataBase { } …

  8. Design Flow Navigation Internal model dependency o.s. sw build-sg c file esterel shift partition code size run time build-blif hw

  9. Design Flow Navigation • Given input, find out all possible outputs • start from input node, visit all following nodes, then show nodes • Given input and output, find out design flow • start from input node, search output node, then show the path • Given output, find out necessary input • start from output node, retrieve all preceding nodes, then show nodes

  10. Automated Tool Interaction • Objective • once given requirements, the whole design will be automatically carried out • Approach • the metatool interacts with O.S., gets run-time environment, launches different tools

  11. Automated Tool Interaction metatool call ... Ptolemy VCC Polis Unix command done not done yet

  12. Implementation • Language: Java • for good transportation • GUI design tool: AWT • for good transportation

  13. Remarks • The core of the whole work is to build a proper tool-description model • Formal specification method (UML) is highly recommended here to maintain good scalability

  14. Future Works • Future works • tool-description model needs to be further extended to include more tools • Inner data model needs to be developed to handle intermediate results • Enhanced GUI features are needed

More Related