JADE (Java Agent Development Framework) is a software framework to make easy the development of multi-agent applications in compliance with the FIPA specifications. JADE can then be considered a middle-ware that implements an efficient agent platform and supports the development of multi agent systems. JADE agent platform tries to keep high the performance of a distributed agent system implemented with the Java language. In particular, its communication architecture tries to offer flexible and efficient messaging, transparently choosing the best transport available and leveraging state-of-the-art distributed object technology embedded within Java runtime environment. JADE uses an agent model and Java implementation that allow good runtime efficiency, software reuse, agent mobility and the realization of different agent architectures.

Developing Multi-Agent Systems with JADE

DEAP is a novel evolutionary computation framework for rapid prototyping and testing of ideas. Its design departs from most other existing frameworks in that it seeks to make algorithms explicit and data structures transparent, as opposed to the more common black-box frameworks. Freely available with extensive documentation at http://deap.gel.ulaval.ca, DEAP is an open source project under an LGPL license.

/pdf/deap-evolutionary-algorithms-made-easy-2rwi6nvdhz.pdf

DEAP: evolutionary algorithms made easy

If patterns are good ideas that can be re-applied to new situations, AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis looks at what goes wrong in software development, time and time again. This entertaining and often enlightening text defines what seasoned developers have long suspected: despite advances in software engineering, most software projects still fail to meet expectations--and about a third are cancelled altogether. The authors of AntiPatterns draw on extensive industry experience, their own and others, to help define what's wrong with software development today. They outline reasons why problem patterns develop (such as sloth, avarice, and greed) and proceed to outline several dozen patterns that can give you headaches or worse. Their deadliest hit list begins with the Blob, where one object does most of the work in a project, and Continuous Obsolescence, where technology changes so quickly that developers can't keep up. Some of the more entertaining antipatterns include the Poltergeist (where do-nothing classes add unnecessary overhead), the Boat Anchor (a white elephant piece of hardware or software bought at great cost) and the Golden Hammer (a single technology that is used for every conceivable programming problem). The authors then proceed to define antipatterns oriented toward management problems with software (including Death by Planning and Project Mismanagement, along with several miniature antipatterns, that help define why so many software projects are late and overbudget). The authors use several big vendors' technologies as examples of today's antipatterns. Luckily, they suggest ways to overcome antipatterns and improve software productivity in "refactored solutions" that can overcome some of these obstacles. However, this is a realistic book, a mix of "Dilbert" and software engineering. A clever antidote to getting too optimistic about software development, AntiPatterns should be required reading for any manager facing a large-scale development project. --Richard Dragan

AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis

From the Publisher:
Eriksson and Magnus Penker now provide guidance on how to use UML to model your business systems. In this book, key business modeling concepts are presented, including how to define Business Rules with UML's Object Constraint Language (OCL) and how to use business models with use cases. The authors then provide 26 valuable Business Patterns along with an e-business case study that utilizes the techniques and patterns discussed in the book.

Business Modeling With UML: Business Patterns at Work

1. Impact Of Object-Oriented Software Development On Software Quality Software Quality Attributes Measures for Producing High-Quality Software Reduced Complexity Through Structure Potentials of Object-Orientation for Improving Software Reusability 2. Concepts Of Object-Oriented Software Development Basic Concepts Provided by Object-Oriented Programming Languages Enhancing Software Reusability by an Appropriate Combination of Object-Oriented Concepts 3. Survey Of Design Pattern Approaches The Role of Design Patterns Object-Oriented Patterns Coding Patterns Framework Adaptation Patterns-Cookbook Recipes Formal Contracts Design Pattern Catalog 4. Metapatterns Metapatterns and (Application) Frameworks Class/Objects Interfaces and Interaction Metapatterns Class/Object Composition Metapatterns Impact of Composition Metapatterns on Template Methods When to Choose a Certain Composition Metapattern Capturing Object-Oriented Design with Metapatterns 5. Sample Application Of The Metapattern Approach Overview of ER++'s Domain Capturing ER++'s Core Design with Metapatterns Resulting Sample Adaptation of ET++ Summarizing Remarks 6. Implications For Software Development > Framework-Centered Software Development Limits of State -of-Art OOAD Methodologies Vision of a Hot-Spot-Driven Approach

Design Patterns for Object-Oriented Software Development

Pattern languages of program design

Call for the Rational Use of Personality Indicators

A bias-voltage generator suitable for measuring a substrate leakage current is disclosed. The bias-voltage generator comprises of an oscillator, a charge-pumping circuit which is driven by the oscillator via a pumping capacitor, and a charge-pumping switch. The charge-pumping switch is connected in series with the charge-pumping circuit. The charge-pumping switch cooperates with an external electrode for controlling the ON or OFF condition of the charge pumping circuit. The charge-pumping switch is turned OFF by the external electrode becoming a floating state and a resistor employed to ensure the charge pumping switch is inoperable after the above-mentioned measurement is completed and the circuit is shipped from the factory.

Workshop on specification and design

During OOPSLA’91, there was a unique activity called “Parallel Universes” where several methodology experts were asked to demonstrate their problem solving approaches upon a problem they had never seen, in front of an audience. This paper presents a partial solution developed by this author as well as a brief tutorial of his methodology. Space limitations prohibit a complete discussion of this disciplined approach to object-oriented design. For further information about the approaches used, please contact the author.

A structured approach to object-oriented design

The key to making object technology work isn't technology. So what is it? This panel will cover a lot of the "soft" issues about dealing with people and teams. It's partly about managing software development, and mostly about doing it.

Norman L. Kerth

Papers

Pattern languages of program design

Call for the Rational Use of Personality Indicators

Workshop on specification and design

A structured approach to object-oriented design

Soft issues and hard problems in software development (panel)