Free contract approval workflow software for linux

Bio::Tools::Run::PiseWorkflow is a class to create a Pise workflow using Pise application objects as methods. A workflow is defined by a set of methods which all instanciate the class PiseApplication.

SYNOPSIS

# First, create a Bio::Tools::Run::AnalysisFactory::Pise object:
my $factory = new Bio::Tools::Run::AnalysisFactory::Pise();
# Then create the application objects (Pise::Run::Tools::PiseApplication):
my $clustalw = $factory->program(clustalw);
$clustalw->infile($my_alignment_file);
my $protpars = $factory->program(protpars);

# You can specify different servers for different applications :
my $protdist = $factory->program(protpars
-remote => http://kun.homelinux.com/cgi-bin/Pise/5.a//protpars.pl,
-email => your_email);

# Create a new workflow object :
my $workflow = Bio::Tools::Run::PiseWorkflow->new();

# Define the workflows methods using the application objects:
# the application method $protpars will receive the output of
# type readseq_ok_alig from the application method $clustalw.
$workflow->addpipe(-method => $clustalw,
-tomethod => $protpars,
-pipetype => readseq_ok_alig);

# The application method $clustalw will be piped to a second
# application method ($protdist) using the output of type readseq_ok_alig.
$workflow->addpipe(-method => $clustalw,
-tomethod => $protdist,
-pipetype => readseq_ok_alig);

# The application method $protpars will be piped to the application
# method $consense using the output of type phylip_tree.
my $consense = $factory->program(consense);
$workflow->addpipe(-method => $protpars,
-tomethod => $consense,
-pipetype => phylip_tree);

# Run the workflow.
$workflow->run();

Class::Contract - Design-by-Contract OO in Perl.

SYNOPSIS

package ClassName
use Class::Contract;

contract {
inherits BaseClass;

invar { ... };

attr data1;
attr data2 => HASH;

class attr shared => SCALAR;

ctor new;

method methodname;
pre { ... };
failmsg Error message;

post { ... };
failmsg Error message;

impl { ... };

method nextmethod;
impl { ... };

class method sharedmeth;
impl { ... };

# etc.
};

Background

Design-by-contract is a software engineering technique in which each module of a software system specifies explicitly what input (or data or arguments) it requires, and what output (or information or results) it guarantees to produce in response.

These specifications form the "clauses" of a contract between a module and the client software that uses it. If the client software abides by the input requirements, the module guarantees to produce the correct output. Hence by verifying these clauses at each interaction with a module, the overall behaviour of the system can be confidently predicted.
Design-by-contract reinforces the benefits of modular design techniques by inserting explicit compile-time or run-time checks on a contract. These checks are most often found in object-oriented languages and are typically implemented as pre-conditions and post-conditions on methods, and invariants on classes.

Note that these features differ from simple verification statements such as the C assert statement. Conditions and invariants are properties of a class, and are inherited by derived classes.

An additional capacity that is often provided in design-by-contract systems is the ability to selectively disable checking in production code. This allows the contractual testing to be carried out during implementation, without impinging on the performance of the final system.

Adding design-by-contract to Perl

The Class::Contract module provides a framework for specifying methods and attributes for a class (much like the existing class definition modules Class::Struct, Class::MethodMaker, and Class::Generate). Class::Contract allows both per-object and per-class methods and attributes to be defined. Attributes may be scalar-, array-, hash-, or object-based.

Class::Contract differs from other class-specification modules (except Class::Generate) in that it also provides the ability to specify invariant conditions on classes, and pre- and post-conditions on methods and attributes. All of these clauses are fully inheritable, and may be selectively disabled. It differs from all other modules in that it has a cleaner, simpler specification syntax, and -- more importantly -- it enforces encapsulation of object attributes, thereby ensuring that the class contract cannot be subverted.

Defining classes

Class::Contract provides an explicit syntax for defining the attributes, methods, and constructors of a class. The class itself is defined using the contract subroutine. contract takes a single argument -- a subroutine reference or a block. That block is executed once and the results used to construct and install the various components of the class in the current package:

package Queue;
contract {
# specification of class Queue attributes and methods here
};

DwWorkflow is a datawarehouse process workflow server and generator of datawarehouse mappings.
It allows the user to define dependencies between tables or files and processes and it runs processes in parallel according to these metadata.
DwWorkflow can run with or without an SQL database server. A process can be any program, not just a database statement.
Enhancements:
- This release includes a graphical plugin for the Eclipse platform for the dwworkflow server, and also includes needed changes in the server for the plugin to work.

mrtg-ntap-probe can probe for Network Appliance NetCache caching appliance and NetApp Filer.

mrtg-ntap-probe retrieves the disk and file (inode) utilization by volume or quota tree name, so you do not need to find the right OID, which might change over time as you add and/or remove volumes and quota trees.

You need a recent release of mrtg 2.x, perl 5.003 or better, a NetApp NetCache appliance with NetCache release 5.1 or better and/or a Network Appliance Filer running Data Ontap 6.0 or better.

If you have a Network Appliance service contract and access to their software tools library on now.netapp.com, you should also take a look at their mrtg-filer and mrtg-netcache packages!

Workflow::Factory is a Perl module that generates new workflow and supporting objects.

SYNOPSIS

# Import the singleton for easy access
use Workflow::Factory qw( FACTORY );

# Add XML configurations to the factory
FACTORY->add_config_from_file( workflow => workflow.xml,
action => [ myactions.xml, otheractions.xml ],
validator => [ validator.xml, myvalidators.xml ],
condition => condition.xml,
persister => persister.xml );

# Create a new workflow of type MyWorkflow
my $wf = FACTORY->create_workflow( MyWorkflow );

# Fetch an existing workflow with ID 25
my $wf = FACTORY->fetch_workflow( MyWorkflow, 25 );

Public

The Workflow Factory is your primary interface to the workflow system. You give it the configuration files and/or data structures for the Workflow, Workflow::Action, Workflow::Condition, Workflow::Persister, and Workflow::Validator objects and then you ask it for new and existing Workflow objects.

Internal

Developers using the workflow system should be familiar with how the factory processes configurations and how it makes the various components of the system are instantiated and stored in the factory.

Apache Graffito provides a framework used to build content-based applications.

Graffito is a framework used to build content-based applications like CMSs, document management systems, forums, blogs, etc. It offers a complete platform for creating, managing, and publishing content in your portal or in any other kind of Java application.

It integrates content repositories, workflow, collaboration, and personalization via existing open source projects and standards like WEBDAV.

JawFlow is a Workflow Engine partially conformal to WfMC (www.wfmc.org) directives, completely written in Java using JMX technology. It understands XML Process Definition Language (XPDL) and can be customized using activities written in Java or in any scripting language supported by BSF.

JawFlow is composed by many interacting modules. Many of these modules are JMX Mbeans and so they need a JMX Agent to run. To develop, test and run JawFlow we used Jboss AS but since there are no strict dependencies in the code related to Jboss it should be installed in any application server supporting the JMX technology.