Hans van Wezep, software architect at Philips Healthcare, talked about model-based migration at the Bits&Chips Software Engineering conference. InfoQ did an interview with van Wezep about the challenges in maintaining legacy software, why manual refactoring is error prone, using models to refactor and migrate a codebase, and the benefits of using models when maintaining legacy software.
Computer-checked models can be used to prove that core communications and state management in a software program are 100% logically correct. Such models can also be used to generate 100% correct source code. The usage of formal methods can reduce costs and time to market and help to deliver highly reliable software products.
By using Model Driven Development component tests could be skipped and integration and system testing went a lot smoother, said Bryan Bakker in the presentation Model Driven Development (MDD) and its impact on testing. Main results from the MDD approach are a reduction of the amount of testing and increased reliability of the code that was generated from a mathematical model.
InterState is a new programming language and environment aimed at addressing the challenges of writing and reusing user interface code. InterState's creators Stephen Oney, Brad Myers, and Joel Brandt claim in their paper that InterState can help programmers to better understand, navigate, and reuse their GUI components even with complex interfaces involving thousands of objects.
This article includes advice for doing enough up-front architectural design to provide the needed structure to start a project, aligning the team with the architect’s vision and assessing the possible risks.
This article contains an interview on GenMyModel’s architecture, technology used and future.
Sparx Systems, an Austrian based vendor of UML tools, has recently published version 9.2 of Enterprise Architect. The new version adds features like enhanced simulation capability and support for describing ontologies.
On October 26th, The Jolt Judges announced the awards for 2011 in the category “Design, Planning, and Architecture Tools”. In detail, the Jolt hall of fame now includes the products Paradigm for UML, Restructure 101, and Requirements Center 2010.
Business-IT alignment, now part of mainstream EA, is increasingly viewed as an unnecessary overhead in a world where IT is a core business entity in the enterprise. Anirban Ray proposes a model driven approach to creating a SOE which makes a core assumption that IT is an integral part of the business which leads to business focused service offerings.
Keeping up-to-date with software architecture can be a tough endeavor. Information is normally available within thick books or somewhere hidden in the Web. Another more entertaining way can be to watch clips available at video sites such as YouTube and Vimeo.
The Special Interest Group on Software Engineering (SIGSOFT) of the Association for Computing Machinery (ACM) have awarded Mary Shaw and Dave Garlan the Outstanding Research Award 2011. Both computer scientists have pioneered the work on Software Architecture at the Software Engineering Institute of the Carnegie Mellon University in Pittsburgh.
Spec Explorer 2010 version 3.5 is an extension for Visual Studio 2010 that allows users to generate reusable test code and create, analyze and reproduce graphical models of software behavior. In addition to several bug fixes and improved documentation, this release of Spec Explorer includes enhancements to model change detection, multiple machine processing and the Cord editor.
Evolve is a lightweight tool for creating, wiring up and executing Java components. Developers can use Evolve to graphically describe JavaBeans and also optionally generate Java code for setters and getters. InfoQ spoke with Andrew McVeigh about the tool.
Jon Whittle presented last week at the SPLC 2010 keynote, some findings on experiences from using model-based development. He reported that 83% of respondents to his survey "consider MDE a good thing". Yet, the industry is still looking for how to create successful Model-Driven approaches.
A key decision for software architects involves where and how to introduce change into a system in order to effect a desired change. Leverage points are those places where micro changes can result in macro results. Twelve categories of leverage point are identified along with concerns about the changes.