Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 1

a tool to roll over futures contracts

5.0
 
  0 reviews  |  2 users  |  4,063 lines of code  |  2 current contributors  |  Analyzed 1 day ago
 
 

Lokad Message Contracts DSL Sample (aka Mercenary) is a reference implementation that shows how to streamline .NET contract generation with Visual Studio. This is useful for reducing development friction on projects that use CQRS, DDD, Event sourcing or rely on any other repetitive code that changes frequently.

5.0
 
  0 reviews  |  1 user  |  16,054 lines of code  |  4 current contributors  |  Analyzed 7 days ago
 
 

There are so many DBC libraries for Java out there, yet none of them that I've looked at met the following criteria: * easy to use with little overhead (i.e. no extra class-hierarchies for contracts) * complete code-integration (no comment-parsing stuff that needs adjustment as soon ... [More] as you change a method- or parameter-name) in pure Java * being able to not only throw an assertion when a contract fails, but also to silently log the contract violation and leave the application running (e.g. in production systems) * easily extensible with own contracts or checks * assign contracts to foreign classes (e.g. preventing to call "new Integer") * lots of more ideas, e.g. profiling or logging method calls, customizable behavior for each contract definition, etc. [Less]

0
 
  0 reviews  |  1 user  |  10,295 lines of code  |  0 current contributors  |  Analyzed 7 days ago
 
 

Tool to rebalance portfolios (of financial securities) based on (banded) constraints (levers).

0
 
  0 reviews  |  1 user  |  1,884 lines of code  |  0 current contributors  |  Analyzed 5 days ago
 
 

ContractFoundry aims to manage contracts made with customers, vendors, partners, or employees. It includes negotiating, ensuring compliance with the terms and conditions, documenting and agreeing during implementation or execution of contracts.

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

A social networking app for social contracts. See the wiki pages, the mailing list, and Central Desktop. Currently deployed on App Engine at http://ignatz-app.appspot.com/ .

0
 
  0 reviews  |  0 users  |  15,852 lines of code  |  0 current contributors  |  Analyzed over 1 year ago
 
 

Master thesis. If you are interested in details what is going here please contact me. adamsonicatgmail.com

0
 
  0 reviews  |  0 users  |  20,507 lines of code  |  0 current contributors  |  Analyzed 7 days ago
 
 

Latest News2 Jan 2010: Treaty for Eclipse 2.1.1 released. Treaty is now dynamic, i.e. a contract registry is maintained when new bundles are installed/uninstalled. Treaty contains a new contract vizualisation framework (see snapshot below), and some example contracts for standard Eclipse extension ... [More] points (some of which fail !). Contracts can now have triggers and actions (=they are based on ECA rules). This means that component lifecycle events can trigger contract verification. To try it, install the respective Eclipse plugins from the following update site: http://treaty.googlecode.com/svn/tags/release2.1.1/treaty-eclipse-updatesite/site.xml. 30 November 2009: We have submitted a proposal to talk about Treaty at EclipseCon. 26 March 2009: We have finished an experiment where we formalised existing contracts documented in Eclipse extension points, and then verified Eclipse against these contracts. There are some surprising results. IntroductionTreaty is a contract framework for arbitrary component models. It supports the precise specification of relationships between collaborating components and verification with respect to these contracts. To explain this, consider a simple clock application in Eclipse (this application can be installed from the following update site: http://treaty.googlecode.com/svn/tags/release2.0.0/treaty-eclipse-updatesite/site.xml). The clock view provided by the plugin displays date and time, but the actual date formatting services are provided by additional plugin components. The relationship between these components is described by precise contracts that reference types defined in an ontology. The following contract types are used in the example: Java classes must implement Java interfaces (level 1 contracts) - used to provide date formatter classes implementing a given interface. XML instances must instantiate a given XMLSchema - used to provide date format strings, contracts are therefore "polymorphic" (like in Eclipse). Java classes have to pass JUnit functional tests (level 2 contracts) - used to make sure that data formatter implementation classes render at least date, month and the last two digits of the year. Java classes have to pass JUnit performance tests (level 4 contracts) - used to make sure dates can be rendered in complex contracts: a plugin can either provide the class or the XML format definition, but not both (exclusive disjunction). The prototype uses a verification service to check the system for integrity as defined by these contracts. This is useful in complex dynamic systems that change often as new services (components) are discovered and integrated. Treaty is not invasive: contracts are just text files added to the plugin meta data (example). Treaty is open: the contract vocabulary consisting of types and relationships has an open modular design. In particular, the underlying component model itself can be used to make contributions to the contract vocabulary. Relevant publicationsJens Dietrich, Graham Jenson: Components, Contracts and Vocabularies - Making Dynamic Component Assemblies more Predictable. In Journal of Object Technology, vol. 8, no. 7, November - December 2009, pp. 131-148 http://www.jot.fm/issues/issue_2009_11/article4/ . This is an extended version of the WCOP workshop paper. Jens Dietrich, Graham Jenson: Treaty - A Modular Component Contract Language. Proceedings WCOP'2008. Jens Dietrich, John Hosking, Jonathan Giles: A Formal Contract Language for Plugin-based Software Engineering. Proceedings of the 12th IEEE International Conference on Engineering Complex Computer Systems (ICECCS 2007), pp. 175-184, 2007. DOI. Antoine Beugnard, Jean-Marc Jézéquel, Noël Plouzeau, Damien Watkins, "Making Components Contract Aware," Computer ,vol. 32, no. 7, pp. 38-45, July, 1999. DOI - contract levels are defined here. MiscellaneousTreaty for Eclipse contains a custom JUnit that allows constructor dependency injection. See also the discussion on the JUnit mailing list about unit testing and dependency injection. TodosAdd triggers and actions to the contract language. Apply this to other component models: document components, pure OSGi, .. [Less]

0
 
  0 reviews  |  0 users  |  56,005 lines of code  |  0 current contributors  |  Analyzed 9 days ago
 
 

Helping today's couples build the best possible tomorrow for themselves – and their children. That's the mission of WeDo Marriage® Limited, the world's first marital corporation. WeDo Marriage® offers offers both partners an in-depth, multi-step, holistic process in which they can ... [More] learn more about themselves and each other, and express and develop shared expectations of a married future together. If you and your partner want a marriage with greater mutual commitment and a more assured foundation for a happy, rewarding and well-lived life, then WeDo Marriage is for you. Because a WeDo Marriage is grounded the law of contracts, couples are empowered to design and implement their own marriage contracts that reflect their own values and aspirations. Our corporate vision is simple, ambitious and transformational: WeDo Marriage® Limited will be the defining marriage innovator of the 21st century. [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors  |  Analyzed 8 days ago
 
 

Create a library to support light-weight contracts validation

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.