Free uml 2.1 standard software for linux

Dreamlinux distribution is a modern and modular Linux system that can be run directly from the CD and optionally be easily installed onto your HD.

Dreamlinux comes with a selection of the best applications designed to meet mostly of your daily needs.

Dreamlinux is based on Debian and Morphix, which means it takes advantages of their best features and adds its own modern development tools.

Being a modular system Dreamlinux allows you to add new modules comprising your preferred applications and build a new Distro that meet your requirements by means of its revolutionary MKDistro tool.

uml2svg is an XSLT-based tool for converting XMI-compliant UML Diagrams into SVG.
We started the developing uml2svg with six main goals in mind:
- Standard conformance
- Good Documentation
- Modularity
- Extensibility
- Comprehensible SVG
- Multiple diagrams per XMI-file
SVG is a standard language for describing two-dimensional vector graphics in XML. As the open SVG standard gains in popularity and gradually replaces proprietary formats for vectorial graphics, the support provided by the Web browsers is getting better.
Plugins to display SVG exist for most browsers and it is most likely that the next generation of Web browser will provide built-in support for SVG. When that happens there will be no better way to distribute vector graphics on the web. Furthermore, not only web browsers can process SVG in a meaningful way; in fact that is just the tip of the iceberg. SVG can be easily read in, processed, and then transformed into many other formats, being well suited for both text and graphic tools as well as for web agents and screen readers.
UML diagrams are composed of lines, polygons, ellipses and text labels, so they are inherently vectorial. However, the SVG is not very well suited for direct use by UML tools. While some of them can in fact export UML diagrams directly to SVG, they do that by discarding all the information about structure, and converting everything into a shape. Moreover, some tools use the screen-capture function provided by their environment (such as java2d) and then they apply a filter to generate SVG out of the "screenshot".
What comes out of that is a pile of meaningless information, which by accident happens to draw a gorgeous diagram. How will a screen reader interpret such a file? How will a web crawler be able to index it? How will a web agent process it in a meaningful way? A program needs the semantic information that the humans can extract just by looking at a picture. For a machine, an obfuscated SVG file is not easier to process than a PNG file or any other image.
Although for humans it is better to be able to scale the image, for a program this is irrelevant. Programs need a way to "understand" the semantics of the UML models to be able to process and interchange them in a meaningfull way. This was the main idea behind the XML Metadata Interchange (XMI), an OMG specification for model interchange. And probably the best use that XMI has found so far is the exchange of UML models between different modeling tools. And while the XMI provides a standard way for tools to represent models as XML documents, it is still limited to the model elements only.
With the introduction of the UML 2.0 Diagram Interchange Specification as part of the upcoming UML 2.0 standard, it will become possible for tools to exchange the models together with the layout of the diagrams. We think that, once this specification appears, XMI will be used averywhere. Not only will the tools be able to exchange diagrams, but could even represent them internaly as DOM trees. Have you ever considered drawing your UML diagrams online, using only a web browser? This could be done even now by using a custom SVG syntax for the DOM tree, but a solution based on XMI could do even better and be a standard at the same time.
Therefore, we believe that with the advent of UML 2.0 and the increase in the use of SVG, the need for transformations between XMI and SVG will be great. Nevertheless when the uml2svg project was started, there was hardly any good open-source solution to convert XMI diagams into SVG.
The UML 2.0 Diagram Interchange Adopted Specification in its current incipient form references a set of XSL transformations. Although the standard draft covers them to a large extent, the link is actually broken (you can try for yourself). It has been broken for more than a year and most likely it will stay like that forever.
The personal webpage of Professor Mario Jeckle provides an online transformation service capable of dynamically generating SVG from XMI-compliant XML files. The XSL files accomplishing the transformations are also available on that website. These transformations are monolithic and not well documented (the only documentation is in the code, and it is generally written in German). With the tragic accident that took the life of Professor Jeckle, the transformations have no longer been maintained.
Finally, the STZ-IDA research center in Karlsruhe had to convert UML diagrams to SVG, as part of one of their projects. The XSLT stylesheet they created for this purpose was named xmi2svg and is available under the terms of the MIT license. At the time we started work on uml2svg the only type of diagrams supported was class diagrams.
Recently the package reached version 0.2 and it supports more diagram types, without major changes in the code (the opposite of what we were expecting). Andreas Junghans, the author of xmi2svg, provided us with a lot of insightful hints which helped us eliminate many glitches in uml2svg. It looks that the development of uml2svg and xmi2svg will continue in parallel, at least for a while. The good thing about this is that the two (quite different) implementations prove each others validity and the features tend to propagate freely from one side to the other. However, this comes with the prize of having to maintain two different code-trees and possibly confusing some users.
We did not like the two existing solutions because they were:
incomplete - just prototypes, not well suited for production environment
monolithic - hard to maintain and extend
not documented - hard to understand
At first sight, we thought we could find a way to improve one of the existing solutions and just add the features we needed. However, we slowly came to the conclusion that it would be better if we started anew. There are things one can fix in a project, but that does not include what we thought is was bad design. The fact that the two implementations presented above are open source helped us get quickly on the way with our own project.
Enhancements:
- Two annoying bugs were fixed.
- The site and documentation were updated.

UMLSpeed project is a compiler for a simple, C-style language that allows declaration of UML entities and diagrams. Diagrams can be compiled into SVG and the entities to XMI for use with other tools.
Why?
- Graphical UML tools in general suck - why should we, as programmers have to drag and drop stupid graphical things and use a mouse when we could express what we want 10 times faster with a text editor and a simple notation? - More importantly, why should we have to lay everything out when the computer could do it for us?
- Graphical UML tools are bloated, huge, memory and disk-hogging monsters.
- Graphical UML tools use either a binary data format or XML, which is not particularly friendly to source code control systems.
Main features:
- Written in GCJ-portable java and compiled natively. Its extremely fast even when dealing with thousands of entities and diagrams.
- Purely command-line driven and takes miniscule resources.
- Flexible enough with file imports that large UML projects can be broken up into separate files and only individual bits built at a time as required.
- C-style syntax means that the source language integrates well with source code control and diff tools.
- Standards compliant - produces interoperable SVG and XMI, as well as clean source code.
- Can integrate with automated build tools for regular diagram/xmi compilation.
Status
This is still alpha software. Dont hold me responsible if it kills your pets and blows your house up.
Implemented so far:
- Compiler/parser
- Namespaces, Class diagrams and related entities
- Use case diagrams and related entities
- Auto-link pathfinding
- XMI 1.3 output
- VIM syntax highlighting
- Code generation (Java and Python)
Still to do:
- Documentation output
- Code generation (Ruby, PHP, Perl, C++, C#)
- Diagram packages
- Diagram notes
- Alternative diagram layout managers
- Deployment diagrams
- Sequence diagrams
- Activity diagrams
Enhancements:
- Added facilities to store HTML of reports in a buffer for use by plugins and turn off file generation. Maven plugin now uses this when using Doxia for generation.
- Added $PROJECTNAME and $PROJECTVERSION HTML tokens, with CLI parameters to set them. Maven plugin will automatically set them.
- Added $PUBLISHDATE token
- Added $TOC key for generating links to bookmarks on the same page.

1060 NetKernel is a resource oriented microkernel and application server that provides a coherent execution abstraction that radically reduces software complexity. Its self-consistent design is based on the convergence and unification of powerful fundamental concepts found in the World Wide Web and Unix.
Resource Oriented Microkernel
The heart of NetKernel is a high-performance, carefully designed, and tightly crafted microkernel. Services and resources within NetKernel are located by URI addresses, just as resources are located on the World Wide Web. NetKernel implements and extends REST 1 into a general-purpose processing abstraction and allows it to be applied to the finest granularity of software systems to achieve phenominal performance; just as the REST Web-architecture achieves global scaling and high performance.
Coherent Abstraction
NetKernel unifies code execution and resource identification into a single addressing and processing abstraction. With this, software development becomes a process of construction (coding services), composition (linking and issuing service and resource requests), and constraint (restricting data values and honoring boundaries).
The simplicity of URI identified resources means that the results of service calls can be cached just as other resources, resulting in self-optimizing software where computation cost is a guaranteed minima.
Reduce Software Complexity
The unification of resources and services with URI addressing radically reduces sofware complexity. Because resources are addressed by URI and each request is a Web-like REST request dispatched to the microkernel, binding between clients and services occurs dynamically for each request. This late binding and the indirection of logical URI addressing results in a loosely coupled system which may be easily adapted. In fact, NetKernel supports dynamic upgrading of software and can support multiple versions of the same components simultaneously.
Complexity brought about by system growth is also managed through the URI address space which may be remodelled and extended indefinitely. A complex aggregation of services may always be abstracted into one or more higher-level services surfaced through URI interfaces.
Main features:
Manage Complexity
- NetKernels unification of resource and service addressing through the active URI scheme combined with late binding and loose typing means that complex systems can be partitioned not just into smaller coorperating systems, you can now create micro-services that hide complexity.
- With NetKernel, design and build larger and more ambitious systems while maintaining control of complexity.
Process XML with ease!
- Processing XML is often just too difficult. But the potential of XML is communication with almost no limit. How to harness and leverage the potential of XML? NetKernel provides hundreds of XML technologies as simple services (no APIs). Simply compose XML services into powerful message processes...
Integrate diverse technologies, apply business logic
- NetKernels uniform URI addressing of resources and service allow you to encapsulate and hide the complexities of any technology, whether it is a Java API, legacy code, or remote corporate systems. Once encapsulated, develop new coordination logic in one of NetKernels scripting languages.
Transport technology independence
- Write a service or application and deploy it to service requests from multiple transports concurrently. NetKernel makes it easy to utilize SOAP 1.1, SOAP 1.2, HTTP, JMS, Email, and Cron.
Extreme performance from intra-application caching
- NetKernels fine-grained dependency cache transparently and opportunistically caches the results of all micro-service requests. NetKernel processes are self-optimizing with guaranteed minimal processing required for a given transaction.
Team Player
- NetKernel has several deployment options that allow it to play well with other technologies and systems. Deploy NetKernel as an advanced standalone application server, as an embedded "co-processor" within existing J2EE applications, as a JMS message processor, as a SOAP client or server, or as an embedded component within any application.
Enhancements:
- New features include support for Berkeley DBXML and PiNKY, a community developed module providing Yahoo! Pipes features.
- Updates include Groovy language support at release 1.0, Ruby (JRuby) support at 0.9.9, and XML library updates.
- There are also documentation updates and UI refinements.

Open Blue Lab project is a modular ERP, built on a plugin architecture. Each business domain (such as Groupware, Financial, HCM, PLM, or SCM) is separated into subdomains which are implemented through plugins.
This form permits you to create all the information related to a contact you are in relation with, during, for example, a phone call. Once totally expanded, this form looks like the image on your right. A click on orange borders will open or close the corresponding section.
This form is directly generated from the UML model that describes CRM informations system. Layout like multicomuln is specified in a very easy way.
Enhancements:
- The CSS style was corrected by deleting the footer, changing skins, improving the search button, and adding PNG transparency.
- The action portlet was fixed up.
- Some messages have been translated.
- You can now drag and drop portlets.
- The search bar has been improved, so you can search by contact, city, company, or any other fields.
- You can now set prority on tasks.