Free uml 2.0 specification software for linux

libFoundation is an Objective-C library that provides an almost complete implementation of the OpenStep specification. libFoundation also has many other extensions that can be found in the Apples Mac OS X Foundation library.
Enhancements:
- This release works with the libobjc provided by GCC (3.0 and up), and has been ported to 64-bit platforms.
- A few minor bugs have been fixed, and support for OpenBSD has been improved.

Pathan is an XPath processing library. Pathan library is written in C++, and uses the Xerces-C DOM XML Parser by the Apache Foundation.

The Pathan project incorporates Pathan 1, implementing the W3C XPath 1 recommendation, and Pathan 2, implementing the W3C XPath 2 draft specification.

Pathan has been developed jointly by DecisionSoft, Sleepycat Software , Stylus Studio and Parthenon Computing .

Pathan 2 aims for XPath 2 compliance.

The beta release is conformant to the the November 2003 release of the specification. It conforms to the February 2004 publication of the W3C DOM Level 3 XPath working note.

XLObject is a clone of basic services offered by the Qt object model, redesigned around modern features of the C++ language. Signals and slots are used for communication between objects. There are instances when we want some objects to know the changes of a particular object without having to write code for each interested object.
This design is common in GUI programming, where another widget needs to be notified implicitly of the change of one widget. Since the widget needs to be usable everywhere, the design should be as generic as possible. The event-generating widget should not need to know how or which widgets are informed of the event.
In older C-based toolkits, this functionality is achieved by using "callbacks" - registering pointers to functions to a processing function. The problem with callbacks is that they are not type safe, prone to crashes, and are strongly tied to the processing function.
Signal and Slots is an implementation of the Observer design pattern made popular by the Qt toolkit. It provides a much safer alternative to callbacks in addition to being built on the principles of object-oriented programming. Qt implemented this feature by dynamically adding extra information to classes during compile time with the help of an external meta object compiler.
XL Signal and Slots achieves the same functionality without the meta compiler by taking advantage of C++ templates. This direct approach is very fast compared to Qts string-based approach with the added benefit of:
Allowing all member functions to be treated as slots.
No longer needing specification of non-standard macros during class definitions.
At the same time, the library tries to follow the design of Qt as closely as possible where it:
Automatically severs the connection if either receiver or sender is destroyed so your program does not crash during the process of emitting a signal.
Lets receiver objects know which sender Object emitted the signal
Lets the compiler catch type mismatches.
Allows a slot to have a shorter signature than the signal without having to rebind types.
Optionally allows objects to be organized as object trees and achieving a concept that is more or less similar to garbage-collection.
The library aims to achieve the core signal and slots functionality very well and at the same time be as less complicated as possible. In around a thousand lines of code, the library is capable of being embedded into the application in a very tiny amount of space.
Enhancements:
- This release fixes a severe memory leak in the thread class.
- The documentation was improved in some of the utility classes.
- Options are provided to specify an optional address in server sockets.
- Some additional fixes were made in the core socket classes.

The MZL & Novatech Traffic Statistics Linux Server is intended to run in servers in intranet or on a gateway and allows to view the Linux servers network usage information on Windows workstations as HTML reports.
It reads IP packet from libpcap and allows users of the free Windows client to see the amount of bandwidth consumed as an icon in the system tray.
The user is able to see which hosts, services or ports were the top traffic consumers. MZL & Novatech TrafficStatistic works on IP packet level, therefore the user gets reports on all the traffic, regardless wether this traffic was made by a browser, a filesharing software or a secure connection. It contains an editor for specification of local addresses and ports to be captured or not captured. This allows to capture traffic to a proxy or VPN but exclude the rest of local traffic.
MZL & Novatech TrafficStatistic can be useful for many diffrent people:
- broadband (like DSL or cable) users with a volume metered (bandwidth limited) charge plan have always an eye on the currently accumulated consumed traffic.
- internet users with a flatrate can see whether a cheaper metered charge plan might be appropriate for their consumption habbits
- internet users are able to see, which services cause the most traffic
- internet users are able to see, how much traffic was consumed with their top target hosts
- operators of dedicated servers in a bandwidth metered charge plan get up-to-date statistics
- network operators can see bandwidth consumption cut by host and service of all machines in the local net
MZL & Novatech TrafficStatistic contains an IP detail record (IPDR) generator developed on basis of ACE. MZL & Novatech TrafficStatistic has be installed with administrator privilegues.
It is distributed as binaries for Linux with lib_c like Redhat 9, Suse 9 or Debian Sarge. The Traffic Statistics Windows client is needed to configure the Linux Server.

UML::Sequence is a Perl module to render UML sequence diagrams, often by running the code.

SYNOPSIS

use UML::Sequence;

my $tree = UML::Sequence->new(@methods, @outline, &parse_method);
print $tree->build_xml_sequence(Title);

To use this package, or see how to use it, see genericseq.pl and seq2svg.pl.
This class helps produce UML sequence diagrams. build_xml_sequence returns a string (suitable for printing to a file) which the seq2svg.pl script converts into svg.

To control the appearance of the sequence diagram, pass to the constructor:
1 a reference to an array containing the signatures you want to hear about or a reference to a hash whose keys are the signatures you want 2 a reference to an array containing the lines in the outline of calls 3 a reference to a sub which takes signatures and returns class and method names

To build the array references and supply the code reference consult UML::Sequence::SimpleSeq, UML::Sequence::JavaSeq, or UML::Sequence::PerlSeq. To see one way to call these look in the supplied genericseq script.

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.