Free modeling tool software for linux

PyReverse is a set of tools for reverse engineering Python code. So far, it features dependency analysis tools, documentation generation, and XMI generation for importation in a UML modeling tool. A special module can be used to generate files readable by Argo UML.
currently PyReverse build a representation of the source tree with:
- docstring for modules, classes, functions
- exceptions raised in functions
- modules attributes, functions, classes
- classs attributes defined in the class scope, inheritance links
- class instances attributes defined in the __init__ method. If possible, get the default value
- functions parameters name and optional default value
- detection of interface/abstract classes and visibility using regular expressions
- detection of links between classes using attributes default value
PyReverse provides modules which use this representation for:
- producing a XMI 1.0 UML 1.3 DOM representation
- creating PGML diagrams definitions according to the project representation, the XMI definition and a XML file which describes briefly the content of the diagrams (see ???). Those diagrams can be readen/edited with Argo UML
- generating UML diagrams readable by VCG (see ???).
- analyzing dependencies (see ???).
- generate skeleton for unit tests, using the unit testing framework for the standard library.

PyDBDesigner is a free relational database modeling tool that is planned to be able to design both logical and physical models similarly to Erwin(c) and PowerDesigner.

Its goal is to provide a useful toolset that allows developers analysts and database designers to design and develop databases from the verbal model to the schemas and SQL scripts.

There is no such a tool is available as a freeware. There is a project called DbDesigner, but it seems to be discontinued and its functionality is not enough for modeling (and the concept behind it seems to be weak).

The concept is to implement ER logical and physical modeling paradigm as correctly as possible, meanwhile creating a tool that is useful as soon as it is possible. So the development concept is that features are added rapidly, but carefully (trying to leave space to the features that come later).

For example, the "type" class is good enough to implement data domains, however, the code that actually creates domains using GUI is not implemented. The "type" attribute of the properties uses this object, so adding domains to attribute types is easy.

OCamlI18N is an OCaml library for programs internationalization.
OCamlI18N (will) provide an I18N module modeling locales, time zones, calendars and dates, numbers and collations for any language, provided enough locale information has been given to him.
The design is heavily inspired by Javas model of localization classes and its motivation was to have a completely thread-safe implementation of internationalization for OCaml fans. If you have any suggestions about the code, contact me (mattam AT mattam DOT org).
OCamlI18N is distributed under the terms of the LGPL.
Enhancements:
- Makefile (VERSION): Set to 0.3, for first release of LDML parsing code.
- src/ISO*.ml*, src/KeyTypes.ml*, src/Variants.ml*, src/ISO_types.ml*: Support for ISO and LDML types, with direct encoding of the enumerations as variant types.
- src/generate_parser.ml: Parser generator, using camlp4 for code construction and capable of producing class types, implementations and parsing code from DTDs.
- src/LDML_types.ml*, src/LDML_impl.ml*: generated code for parsing LDML documents using pxp.
- src/LDML_support.ml*: Support functions for parsing.
- src/LDML.ml*: main entry point to access LDML information.

DaVinci is a comprehensive framework for model-driven Web Engineering.

DaVinci is designed as a complete toolkit which consists of three parts: the DaVinci Modeling Framework, the DaVinci Architecture Layer and the DaVinci Runtime Library.

Characteristics:

A fundamental difference to existing Web Engineering frameworks is the architectural concept of DaVinci which is specified in the DaVinci Architectural Layer. The architecture is based on the assumption that, for a Web application (by contrast to a more document-centric Web site) the hypermedia paradigm is more circumstance than useful.

A classical Web site is based on URLs, hyperlinks, and various kinds of resources which is the basic concept of hypermedia systems like the Web.
In the scope of DaVinci, a Web application is more like a traditional application running in the browser. Thus the bahavioural (or functional) aspect is much more important than pages. Pages are generated and transient. Therefore, the basic idea of DaVinci was to eleminate the classical hypermedia paradigm and to inject an additional layer between the Servlet Container and the application (see figure showing the DaVinci Stack).

The DaVinci Architectural Layer provides concepts which are missing in the Servlet API but essential for Web applications. While other projects (e.g. Java Server Faces or Struts) do not re-define the interaction process, DaVinci defines a dedicated GUI model as well as an interaction process.

These four important aspects outline the main characteristics of the DaVinci Web Engineering Framework:

A Web application is not just a set of Web pages, its rather a piece of software with application logic and business state. Thus, the notion of a user session is fundamental.

The view state is part of the session. It is based on a hierarchical view tree model with switchable sub-trees. This allows to change the GUI during the session, but always keeps the GUI in a certain, deterministic state.

Instead of refering to documents, URLs are refering to actions that can be invoked. When modeling an application with DaVinci, the GUI including all interaction spots (buttons, forms, etc.) is well defined allowing the incorporation of CASE tools.
Application logic is modeled using traditional methods and indepenently of the views.

The DaVinci Architectural Layer

The figure below shows the DaVinci Stack. Between the Servlet Container and a DaVinci Web Application there is the DaVinci Architectural Layer.

The DaVinci Modeling Framework

The DaVinci Modeling Framework is a UML-based toolkit for modeling DaVinci applications. It defines the modeling process starting with use cases and storyboarding, then defining the GUI (user-experience model), the database design and finally the application logic which can be done using UML thoroughly. The DaVinci Modeling Framework will provide a rich set of CASE tools which will facilitate and automate the modeling process.

There is already a simple View Stubs Generator which takes a view tree configuration file and generates all views (JSP files) based on configurable skeleton templates. The generator can be found in the package at.davinci.casetools.

The DaVinci Runtime Library

This is the JAVA library containing all required classes for running DaVinci applications. In other words, this is the implementation of the DaVinci Architectural Layer. Currently it also includes all development libraries and CASE tools. But these will be extracted and become part of the DaVinci Modeling Framework in future.

Generic client/server applications

The framework is designed in such a way as to enable the development of any client/server applications. This means, the DaVinci Architectural Layer can be decoupled from the Servlet Context/Web Server-bundle and run on-top of an autonomous DaVinci kernel module. Different FrontController implementations enable the integration of different client/server communication protocols (e.g. FTP, POP3, plain socket communication, etc.).

Thus its possible to use a POP3-FrontController, which will react on incoming e-mails. This can seamlessly migrate different communication channels within a business application and enable business workflows, that are not only based on HTTP, but also on E-Mail, FTP, etc. The framework can also be used for writing arbitrary socket-based server applications (for example a socket-based configuration utility running on an embedded device, etc.)

Currently there is a SocketController, which can be connected with an arbitrary telnet client, and a ConsoleRenderer which will render the state of the view tree into plain text.

Molecular Workbench project is a piece of free, open-source modeling software specifically designed for use in education. Powered by a set of real-time molecular simulation engines that compute and visualize the motion of particles interacting through force fields, in both 2D and 3D, it provides a simulation platform for teaching and learning science.
Many abstract concepts in physics, chemistry and biology can be dynamically visualized, and virtual experiments based on molecular simulations can be designed, limited only to your imagination.
The MW software consists of:
- a set of model builders, simulators and their associated scripting environments.
- a word processor for creating hypertext.
- an authoring system for constructing your own graphical user interfaces for your own simulations.
- an embedded-assessment system that allows you to design your own questions and collects student data.
- a special browser for you to deliver and for the users to access stuff created using the above sub-systems.
- Web services for collaboration among authors, students and teachers.
All these sub-systems are seamlessly integrated behind an easy-to-use graphical user interface. The customizability of models through the authoring system allows you to design user interfaces appropriate to your audience, without having to get them involved in the complexity of the modeling engines.

QML (Quantity Modeling Language) is a "thing"-based language for scientific and mathematical data modeling.
Each "thing" is a quantity which may be associated with either a structure or physical phenomena.
Quantities, in turn, may hold other Quantities or values (numbers or strings). Higher-level data models, which associate or define meanings to various quantities (such as velocity or position), can be built from QML quantities.
The higher-level data model (XML) schema that inherits from QML may be understood, and its instance documents may be parsed into QML documents and objects by the QMLReader.
Enhancements:
- This release adds partial Xerces2 DOM support, and works with Java 1.4 and Java 1.5 (no JAXP DocumentBuilder/Factory support currently).
- The test procedure is a little less chatty.
- Support has been added for testing either/both Crimson/Xerces DOM support.
- (Note: Crimson support only works with Java 1.4, as Java 1.5 interfaces have DOM lvl 2 and 3, which crimson doesnt support).
- This release adds compilerargs, and better build support for different configurations to build.xml.

Nano-Hive is a modular simulator used for modeling the physical world at a nanometer scale.

The intended purpose of the simulator is to act as a tool for the study, experimentation, and development of nanotech entities.

Nano-Hive is a GPL/LGPL licensed open-source development - you can download and use it for free.

Nano-Hive can be run stand-alone, or easily integrated to support other applications such as CAD tools.