Petals ESB v3.0 is finally out (two years after the v2.0 release), there are many changes in this version but here are the main ones :

Petals ESB 3.0, includes a lot of improvements for users, as well as optimisations, and nice new features :
- Dynamic configuration, and hot-deployment of new nodes
- Redesigned webconsole for administration, and deleted statistics monitoring (based on OW2-OpenSUIT)
- SCA support: SCA engine (OW2-FraSCAti), and SCA designer (Eclipse)
- BPEL support: BPEL engine, and BPEL designer (Eclipse), with validation (based on a new BPEL engine!)
- WS Notification and WS-BorkeredNotification support (EDA)
- more and more things…

Integration with new Petals Camelia softwares :
- Petals Studio: Complete Eclipse development environment, for Petals ESB
- Petals Master: SOA Governance (OW2-Dragon)
- Petals View: Business flow monitoring based on Petals EDA feature (based on OW2-OpenSUIT)

We gave this release a name : Camelia.

Жили у нас кот а также ежик. В едином, была у их общественная чашка, из-за которой они непрерывно вели войны. Кот был более, потому он просто отодвигал ежика от чашечки. Потом ежик выдумал последующее: он подлезал перед кота и выпускал иглы. Кот шипел а также удирал. Потом кот выучился выздоравливать на цыпочки и стал пренебрегать ежа.

В следующий раз смотрим данную картину: ежик тихо ест, подходит кот, отодвигает его, ежик подлезает перед кота, издаёт иглы, кот становится на цыпочки а также продолжает быть. Затем еж готовит необычный ход: он идет к коту сзаду а также, делая упор на задние лапы жрущего кота, кусает его за самое важное. Такого клика кота я более никак не слышал.

Асечное

Только будто приключилось. Разговариваю со Свердловском… Человек на том конце кое-что навечно умолкнул. Ну, а также я тружусь покуда. Вдруг появляется:

- Ух ты! Думала с тобой 20 мин. разговаривала, а оказывается – с другим!!

- Как так?

- Да окошко перепутала!

- Ну ты, мама, отчуждаешь! И будто наговорила?!

- Да ничё! Никто в том числе и а также никак не заметил!

Представляете, какие мы ведем дискуссии, ежели из-за 20 минут даже никак не осознаем, с кем говорим…

On November 19, JVA Consulting and friends celebrated the graduation of the Fall 2009 Executive Director Academy (EDA). Students from a variety of backgrounds in the nonprofit world—all desiring to reach their potential as nonprofit leaders—were recognized for completing the fifth installment of the 13-session, intensive course.

Throughout the ceremony, graduates reflected on their EDA experiences. Some marveled at the amount of information they had absorbed, while others were amazed that through EDA, they had been able to transform areas of weakness into areas of strength. “Whatever your challenges are,” said Julissa Soto, “in here you’re going to find some answers.”

Samantha Johnston has 10 years of experience working in the nonprofit sector. After developing her own idea for a nonprofit organization, Samantha decided to learn more about the leadership role of an executive director. “EDA helped me hone in on the skills that I needed to grow in as well as the skills that I already have,” said Samantha. “It was an excellent time to get together with my peers who are in similar situations, get input from them, as well as understand what the executive director position is and what is needed to make an organization run well.”

EDA graduates developed a unique bond over the course of their seven weeks together. Following the ceremony, graduates exchanged business cards and promised to turn to each other as resources in the future. The safe, candid environment that EDA creates helps foster close networks of peers in the nonprofit community. Although some graduates were sad that they would not be back next week to see each other, others were excited to implement the knowledge and skills they had gained.

“I’m going to take away a lot from this experience, “ said Julie Gutman. “Armed with that knowledge, I feel like I can do what I want to do and grow in my career.”

The sixth EDA begins April 13, 2010, and runs through May 27. Classes will be from 3-6 p.m. at JVA. Students who register and pay in full before January 1, 2010, will receive $100 off the price of the course. To learn more about EDA or to register, click here.

Tim Edwards has tagged version 3.6 to stable, and version 3.7 is the new development version.

The stable release will only be updated with bug fixes, while all new development and experimental stuff will go into the development release.

Users will experience fast UI responses with the new stable release 3.6.163, which has just been pushed to Fedora updates. This release also unleashes extra capabilities for managing big IC projects, which was lacking in the 3.4 series.

Karen Bartleson reports some interesting facts from the 22nd EDA Interoperability forum in her blog.

Richard Paw represented the EDA Consortium’s OS Roadmap Committee. This group produces guidelines for operating system and hardware platforms that help unify EDA tool support around common platforms. (It drives customers crazy when the tools they purchase don’t support the same platforms.) The guidelines will be updated in September 2010. Added will be SLES 11 (SuSe Linux) and Windows 7. Dropped will be SLES 10. In 6 months, the committee will review Windows XP, Vista, and the upcoming RHEL 6 (RedHat Enterprise Linux).

Dave Graubart represented the EDA Consortium’s Anti-Piracy Committee. He said it’s hard to feel the love when you’re getting ripped off. The committee estimates that 1/3 of all EDA software use worldwide is pirated or overused beyond the license agreements. Not scientific data, but troubling nevertheless for the EDA industry. It’s easy to find the stolen binaries so most of the 1/3 estimate comes from this, not misuse/overuse which is harder to find. There are potential techniques to help prevent this piracy and the committee will continue its work to solve the problem.

İyidi yaa

No need to call – just show up

Eden Prairie @ 5:00 on Sundays

Wooddale Church room 133 (downstairs)                                                            6630 Shady Oak Road, Eden Prairie

eda.minnesota@hotmail.com or call Kelly at 651.246.5935

Minneapolis @ 5:45 on Fridays

Grace University Lutheran Church

324 Harvard Street SE, Minneapolis, MN 55414 

Park in Lot AA across the street, even in “reserved” space. Church is on University of Minnesota East Bank Campus

 EDAstpaul@gmail.com or call Britt: 651-587-0711

Excelsior @ 7:30 PM on Saturdays

 640 Virginia Shore Circle, Excelsior, MN 55331

Call Sydney for more information at 952-237-9112

Little Falls@ 6:00 on the 2nd and 4th Mondays of the Month

St Gabtriel Hospital in the Rose Room. Please use the 3rd Street entrance

edalittlefalls@hotmail.com or call JoAnn at 320-232-9576

Owatonna @ 6:00 on Thursdays

South Central Human Relations Center

610 Florence Avenue

EDA.owatonnamn@yahoo.com or call Kim at 507-390-0447 

O Esquadrão de Demonstração Aérea (EDA), popularmente conhecido por Esquadrilha da Fumaça, fará uma apresentação em Natal no domingo (15), às 15h30, entre as praias dos Artistas e do Meio. O show aéreo faz parte das comemorações da Semana da Asa, na qual a Esquadrilha está fazendo um circuito por todo o Brasil.

Durante a demonstração, que dura em média 35 minutos, onde são executadas 55 acrobacias, os pilotos da Fumaça irão fazer uma surpresa ao público presente na exibição.

Além do show de acrobacias, na segunda-feira (16) pela manhã, a equipe do EDA que vem a Natal, composta por 36 militares (pilotos, mecânicos e pessoal de apoio), irá visitar duas entidades filantrópicas em Parnamirim: o Lar de Assistência a Criança (LAC), que atende cerca de 70 crianças carentes, e o Lar Espírita Alvorada Nova (LEAN), onde moram cerca de 40 idosos.

Formado pelos mais experientes pilotos da FAB, o trabalho da Esquadrilha ultrapassa o voo. Eles realizam um trabalho social, por isso visitam entidades carentes para levar uma mensagem positiva. Na ocasião, a BANT e a ASFAN (Ação Social da Família Aeronáutica de Natal) estão realizando uma campanha interna para arrecadar donativos para o LEAN.

A Esquadrilha da Fumaça realizou sua primeira exibição oficial em 14 de maio de 1952. Desde então, milhares de pessoas têm travado contato com os pilotos e mecânicos que os assessora. Atualmente, com mais de 3300 demonstrações realizadas no Brasil e no Exterior, os integrantes da Esquadrilha são considerados “os embaixadores do Brasil no céu”.

Fonte: Tribuna do Norte

At the October 2009 ALT.NET Northeast Wisconsin user group, Scott Felder put together a great demonstration of NServiceBus and how it actually works. He has since followed up with a well written article on his new blog that talks about Domain Driven Design and when/where NServiceBus, or some other message bus/EDA, might fit in. It’s definitely worth a read.

2009-10-29 Ansoft_ePhysics 3.1
2009-10-26 Agilent.IC-CAP.v2009 for WIN&Linux
2009-10-26 Mentor.Graphics.HDL.Designer.v2008.1
2009-10-25 Mentor_Graphics_FlothermPCB_ v5.3
2009-10-24 AWR_Design_Environment_9_0_4818
2009-10-23 FLoTHERM_V8.2
2009-10-20 LayoutEditor.v2009.10.14
2009-10-17 BluePrint-PCB.v2.1.0.463.with.CAM350.v10.1.0.363
2009-10-15 Agilent_RF_Design_Environment_(RFDE)_ 2009_ Linux
2009-10-15 Agilent_ IC-CAP 2009 Win &Linux
2009-10-14 Mentor_Graphics_Olympus-SoC_v2009.04.R3
2009-10-13 Sigrity_SpeedXP_Suite_V8.0
2009-10-12 EMA TimingDesigner v9.2
2009-10-11 Mician_uWave_Wizard_ v7.0
2009-10-11 Magma_FineSim Pro_ v2008.09 Linux
2009-10-10 XHDL_v4.0.40_Windows
2009-10-09 Magma_SiliconSmart_v2009.02
2009-10-08 Mentor_Graphics_FormalPro_ v2007
2009-10-07 Mentor.Graphics.PADS.Flow.9.0.1
2009-10-06 Synopsys Hspice vC-2009.09 Linux
2009-10-04 Cadence_IFV8.2
2009-10-03 Ansoft_HFSS_ V12
2009-10-02 Cadence_RC9.2

2009-09-26 Cadence MMSIM v7.11.071 Update
2009-09-25 Cadence SOC8.10.002
2009-09-24 xilinx ISE 11.3
2009-09-23 Cadence_IC6.13.541
2009-09-22 Simetrix 5.6
2009-09-21 Cadence Assura v4.10.002
2009-09-18 Synplify FPGA_vC-2009.06
2009-09-16 SpyGlass 4.2
2009-09-15 IAR Embedded Workbench for MSP430 v4.20.1
2009-09-14 IAR Embedded Workbench for ARM v5.40
2009-09-13 Mathworks.Matlab.R2009b
2009-09-12 Proteus V7.6_SP0
2009-09-11 Synopsys_saber_vC-2009.06-SP1
2009-09-10 Cadence IFV 8.1 Linux
2009-09-09 Altera.Quartus.II.v9.0.SP2
2009-09-08 Feko Suite 5.5
2009-09-08 Synopsys Tcad_Taurus_md_vC-2009.06
2009-09-07 Fintronic.Super.FinSim.v10.0.03
2009-09-06 Impulse.CoDeveloper.Universal.v3.60.a.2
2009-09-05 SynaptiCAD.Product.Suite.v14.07d
2009-09-04 Ansoft Maxwell v12.2
2009-09-03 NI.LabVIEW.2009.v9.0.Touch.Panel.Module
2009-09-03 NI.LabVIEW.2009.v9.0.System.Identification.Toolkit
2009-09-03 NI.LabVIEW.2009.v9.0.SoftMotion.Module
2009-09-03 NI.LabVIEW.2009.v9.0.Mobile.Module
2009-09-03 NI.LabVIEW.2009.v9.0.Real.Time.Module
2009-09-03 NI.LabVIEW.2009.v9.0.Microprocessor.SDK
2009-09-03 NI.LabVIEW.2009.v9.0.DSC.Module
2009-09-03 NI.LabVIEW.2009.v9.0
2009-09-03 NI.LabVIEW.2009.v9.0.Control.Design.and.Simulation.Module
2009-09-03 NI.LabVIEW.2009.v9.0.Desktop.Execution.Trace.Toolkit
2009-09-02 Synopsys Cadabra vB-2008.09 Linux
2009-09-02 Synopsys Customdesigner vC-2009.06 Linux
2009-09-02 Synopsys ESP vC-2009.06 Linux
2009-09-02 Cadence.Allegro.SPB.v16.20.014 Update Only
2009-09-02 Synopsys NS vC-2009.06 Linux
2009-09-01 Mentor Graphics FloEFD pro 9.1
2009-09-01 Mentor.Graphics.Expedition.Enterprise.Flow.v2007.6
2009-09-01 Pulsonix 6.0 build 3818

Big Ball of Mud

Let’s start with my original example business, Acme Enterprise.  Acme wishes to build an ecommerce system to sell its products to its customers.  The developers at Acme start out by building a web application that customers can come to for placing orders, employees in the pricing department can update product prices, and employees in the inventory management department can maintain product SKUs and product levels.  As time goes on the pricing department wants to add new functionality to the system to maintain promotional pricing on products, discount pricing on products, etc.  The inventory department wants to add new functionality to the system to provide auto-replenishment on products, warehouse location of products, etc.  As the application grows into one monolithic system it can quickly become unmanageable in its current form, or as some call it, BBOM – Big Ball of Mud.  More importantly, the different departments within Acme define the term “Product” differently.  The sales department defines a “Product” as an item ordered by a customer and added to a shopping cart with a price and quantity ordered information attached to it.  The pricing department defines the “product” in terms of not only unit price, but promotional pricing, and marketing campaign pricing that is valid for a particular time period. Meanwhile the folks in inventory management define a “Product” in terms of Quantity on Hand, Warehouse Location, and Reorder Threshold Trigger.  As the system grows, so does the complexity and the size of our BBOM.

Bounded Contexts

This is where Domain Driven Design (DDD) can help with the design of our ecommerce system.  When we start to define the term “Product” with the people responsible for products in each of the departments within the company, we realize that they all care about this thing called a “Product” but they each talk about it in a different context.  This is where DDD introduces the idea of a Bounded Context.  Our system can be split into separate contexts each with its own explicit boundary.  So what we end up with in our system is a bunch of Bounded Contexts for each of the different contexts within the system: an inventory context, a pricing context, sales context, etc.  Each Bounded Context has its own model and ubiquitous language that defines the domain and entities like “Product” uniquely to its own definition.  The key phrase to our bounded context here is “explicit boundary”.  Each context provides a contract to the outside world to interact with and can be viewed as its own application within an application.  This can provide modularity to our overall system design.  One Bounded Context shares data with another Bounded Context via a Context Map.  A Context Map exposes a well defined contract interface that can be consumed.

Bounded Context as a Service

Now let’s take our DDD ecommerce system and apply SOA principles to it. Remember when I stated that a Bounded Context provides an explicit boundary?  One of the core tenets of SOA states that “Boundaries are explicit”.  I also stated that a Bounded Context can provide modularity within our system and that a context can be viewed as an application within an application.  Well another core tenet of SOA states that “Services are autonomous.” Hmm, so what else do bounded contexts and SOAs share in common?  A Bounded Context within our system communicates with another Bounded Context within our system via a context map that provides a contract interface to the outside world.  SOA; “Services share Schema and Contract, not Class”.  So when we compare the Bounded Context of our DDD and the Services of our SOA, there really isn’t a whole lot of difference between the two.  Maybe in an SOA we should call them “Bounded Services”?  SOA is about the separation of Bounded Contexts in our application into their own services so looser coupling can be achieved while providing a certain degree of service reuse within our enterprise.  Our context map or interface to the SOA service can be done via a web service, restful service, or WCF.  For example, in our DDD ecommerce application, if we wanted to replace the inventory context with a third party inventory management or ERP system like SAP, there may be a bit more work involved to decouple it from the old system and integrate the new SAP system.  With SOA, we have a lesser degree of coupling to deal with so integrating to the new inventory system will be easier.  Notice, I said “easier” not seamless.

EDA with NServiceBus

This brings me to Event-Driven Architecture (EDA), more specifically, EDA with NServiceBus.  As we’ve taken our initial BBOM ecommerce application and we introduced DDD principles to it and refactored our system, we began to decouple the system into different functional modules, or Bounded Context, within one application running on our web server.  Each department (inventory, pricing, sales), would access the same system to update their various domains of information.  As we moved to SOA, we took this one step farther by making these contexts autonomous services that can be distributed on different servers running within our enterprise, providing user access to a particular service to only the people in the department that need to update data within that service.  The problem with traditional SOA is it still gives us a certain level of coupling with our enterprise applications between services.  If the inventory service needs to inform the pricing service that a new SKU has been entered into the system, the inventory service must know that the pricing service exists within our enterprise.  Meaning, the inventory service must be programmed to make a service call to a service interface (web service, WCF, socket call, etc.) on the pricing service.  If we decide to use a different system in the future to do pricing, we need to update the inventory service to call the new service interfaces on the new pricing system.  This is where event messages and NServiceBus can help.  If we define a series of business events that describe important transactions within our enterprise, we can publish their event messages to a message bus.  Now instead of our services interacting directly and having to be aware of one another in the enterprise, each service only needs to know to publish event messages to the message bus, and only subscribe to event messages on the message bus that it cares about.  So in the case of our inventory service, and our pricing service, the inventory service can publish“New SKU” events and the pricing service and subscribe to “New SKU” events.  At no point does the inventory service need to know about the pricing service and conversely, the pricing service doesn’t need to know about the inventory service; now what “links” the two systems together are the “New SKU” events, and more importantly the data contained within.  In essence, the event messages and the service bus, in this case NServiceBus (but we could use others) become the “Context Map” defined back in our DDD application.  The event messages are our contracts and NServiceBus becomes our service transport layer to communicate between Bounded Contexts/Services with a higher level of decoupling between our services than we had with our traditional SOA.

In conclusion

            NServiceBus provides an easy to use API to the framework to work with so we can create an event message driven architecture.  Publishing event messages via NServiceBus will allow for a much more loose coupling design between the different Bounded Contexts or Services running in our enterprise.  While applications or services will always have a higher degree of coupling between their application layers, (UI, Business Layer, DAL, etc.), Event-Driven Architecture with NServiceBus can provide for a much lesser degree of coupling between the explicit boundaries of the services.

Last week, New York Times technology reporter, Steve Lohr, wrote about a Booz&Company annual survey of the 1,000 largest corporate spenders on research and development. In an economic environment laced with cost cutting measures across capital investments, marketing and payroll, the obvious premise for a survey on this topic would be that R&D spending would also take a hit.

Not so, according to the results. Respondents indicated that R&D budgets actually increased 5.7 percent in 2008 and 70% planned to maintain or increase their spend in 2009. Surprising? Not really given the survey also revealed more than 90% of the participating executives said innovation was critical to their companies’ success. More than 90%! With 14 pages of summary, testimonials, pie charts and graphs, this report gives a clear picture of just how integral innovation is to the corporate strategies behind the world’s most important industries.

The report uses an arms-race analogy to describe how the 1,000 largest corporate R&D spenders consider innovation so important, they don’t want to disarm despite the short-term economics. Innovation is the foundation they are betting on to hold their market positions and gain a competitive edge. In their minds, everything can be cut…but not R&D.

For me personally, the release of the Booz&Company results couldn’t have been better timed – today happens to be the fourth annual Innovation Day. But with the added reinforcement of the survey conclusions, a big question came to mind. How does an “arms merchant” like Cadence take advantage of the innovation arms race? The answer is simple. We INNOVATE!

The survey reached 1,000 of the largest corporate spenders on R&D. These companies are the leaders in their respective industries – all well-known for innovation. They are also EDA customers. So when I say the answer for Cadence is to innovate…I’m talking about creating technology that is not just tightly aligned with but intrinsic to the innovation our customers bet their companies on.

EDA customers use the innovation we create to change the world – literally, their products change the world for consumers and businesses. If we enable them to bring products to market faster, more cost effectively and with better quality, our innovation becomes invaluable to their success. We become the competitive weapon they won’t go to battle without.

Innovation is the heart and soul of Cadence – it’s in our DNA and it’s what makes us different. We’ve made powerful advances possible and now have over 800 U.S. patents – that’s more than any other EDA company.  We’re very proud of our history and the Cadence employees who’ve spent many dedicated hours making their complex ideas a reality for our customers.

Being that today is Innovation Day, it’s an important annual milestone for Cadence. In honor of the occasion, we’re taking this opportunity to recognize some of the company’s amazing technology leaders and highlight their contributions to the EDA industry this year. We have a big day planned and since we go big or go home – the celebration will come with all the bells and whistles worthy of their achievements.

No matter what your plans are today to ring in Innovation day, on a larger scale, there’s no doubt innovation continues to thrive in Silicon Valley thanks to the great minds and dedication of our technology leaders/entrepreneurs. I look forward to being a part of future developments and strongly believe if we continue to focus on solving hard problems, we can foster a positive influence throughout the world.

-JB

Estructura de Datos y Algoritmos

TEMA 4

Representación enlazada

Transparencias (PDF)

TEMA 3

Genericidad

Transparencias (PDF)

Ejercicios resueltos (PDF)

Ejercicio adicional resuelto (PDF)

TEMA 2

Fallos de ejecución: clasificación, representación y tratamiento

Transparencias (PDF)

Ejercicios resueltos (PDF)

Ejercicio adicional resuelto (PDF)

TEMA 1

Herencia y polimorfismo

Transparencias (PDF)

Ejercicios resueltos (PDF)