Hello here
November 2009View which web pages I came across today on faves.com - http://bit.ly/1x4DyK
RT @numerikbook: Une image prise sur le vif, en fin de journée, dans le métro, vaut mille mots numériques ! bit.ly
Smarter Work on a Smarter Planet (IBM Movie) bit.ly
My anti-virus doesn't let me work...grr
LOL ! Lawyer: "Have you lived in this town all your life?" Witness: "Not yet." bit.ly
Les cons, ça ose tout. C'est même à ça qu'on les reconnaît.
bit.ly
twitdraw.com Le ciel (par Thomas) #twitdraw
@roulive processus endothermique ? bon rétablissement à tous.
"Le Digital Native déborde d'idées, il est ambitieux, imaginatif et multitâches. Il aime travailler en équipe, tout en ressentant un fort besoin d'autonomie et d'indépendance. Il a tendance à rejeter l'autorité, mais accepte la compétition." Ouille, ca me fait penser a quelqu'un... Source : Brainsfeed : (réflexion) > Les Digital natives: une nouvelle génération d'employés Bruno Rives: Eblouissant... "Magnetic Movie from Semiconductor on Vimeo." bit.ly
Camel Market in Pushkar Mela - bit.ly
RT @Stiliweb: twitpic.com - Google Streetview car visits Overijse (Belgium)
IBM OmniFind has a well-defined Java API for ease of deployment into existing enterprise applications. bit.ly
AC Milan-Real Madrid. Mireille says 2-4 I say 2-2
Having fun with the 100 Ridiculously Questionable T-Shirts bit.ly
October 2009Beau travail ! RT @mulkers: We're ready for Halloween... bit.ly
Today we visited the Van Gogh Museum in Amsterdam. There we saw many elephants : bit.ly
This morning (Oct 28, 2009) I attended a iLog Business Rules Management System (BRMS) Demo and it gave me an idea. iLog has a great tool for testing rules. It allows to design test cases using MS Excell that are sent to the Rules Engine in order to determine if a rule set provides the expected decision. In the past I ave been involved with the difficult exercice of generating test data for Business Processes. Using the iLog testing tool, this could be realized like this : 1. Before the process is designed, use the BRMS to design the process vocabulary. 2. Create some basic rules which from process inputs produce process outputs. In fact these rules simulate the process. 3. Create the rules test cases such that the rule responds the right process output from a given process input. In fact the rules set must simulates the process for the foreseen test cases. 4. Communicate the rules and their test cases to the Process developpers so they can design and build the process using the test cases. 5. For automating the tests, at the end of the process (or at intervals if the process is composed of serveral parts), send the process inputs to the business rules and ask the rules engine to compare process results with the expected process results (this requires a comparison rule which allows to determine of two result sets are considered equivalent). To illustrate this, I used the opportunity to test gliffy to make a diagram: http://www.gliffy.com/publish/1872505/ Last twit was to test the del.icio.us / Twitter integration...
Testing Business Processes with iLog Business Rules (Illustrated with Gliffy) bit.ly
|