Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Modeling Tool Content on InfoQ


RSS Feed
  • The Spotify System Model: Automated Architecture Visualization at Spotify

    Spotify engineers recently published how they standardized architecture diagrams at the company. They defined a standard system model named the Spotify Software Model and adapted the C4 model to visualize it. This combination created a shared language used across the organization, which helps communication, aids decision-making, and supports Spotify's software's evolution.

  • Model-based Migration Approach for Maintenance of Legacy Software

    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.

  • Developing Provably-Correct Software Using Formal Methods

    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.

  • InterState: A Language and Environment for Expressing Interface Behavior

    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.

  • Jolt Award 2011 for Design, Planning, and Architecture Tools

    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.

  • Evolve: Using Components to Improve on Dependency Injection

    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.

  • Microsoft Has Released “Oslo” May 2009 CTP

    Major features of “Oslo” May 2009 CTP are: “Quadrant”, a visual modeling tool, changes of the “M” language specification and the addition of predefined domain models to speed up development.

  • Article: RGen: Ruby Modeling and Code Generation Framework

    This article introduces RGen, a modeling framework inspired by openArchitectureWare and technologies like the Eclipse's EMF. RGen uses internal DSLs for defining metamodels and offers a full modeling stack for Ruby.

  • Presentation: Managing Variability in Product-Lines

    Managing commonality and variability is the core of product line engineering. In this presentation, Markus Völter illustrates how model-driven and aspect oriented software development help addressing the challenge of managing variability in product line engineering.

  • MindScape Has Released LightSpeed 2.0

    MindScape has released version 2.0 of their domain modeling and ORM tool. LightSpeed 2.0 includes a visual domain model designer integrated with Visual Studio 2008, support for LINQ and the ability to access multiple databases concurrently.

  • Are Business Analysts Ready to Become Programmers?

    Microsoft seems to think so as they prepare to deliver on the Oslo vision. Back in November 2007 Doug Purdy made a veiled reference to a new project in development calling it "Emacs.NET". This fueled rampant speculation far from the intended mark.

  • Interview: Markus Voelter about Software Architecture Documentation

    InfoQ interviewed Markus Voelter about the importance of writing software architecture documentation and the problems noticed by him when it comes to creation of useful software design documents.

  • Article: Process Component Models: The Next Generation In Workflow?

    Tom Baeyens wrote a summary of the state of Workflow & BPM standards and tools. After a detailed look at BPEL, BPMN, and other technologies such as choreography, XPDL, BPDM, jPDL, Tom takes the stance that it is time to abandon the idea that non-technical business analysts can draw production-ready software in diagrams and separate the analysis process models and executable process models.

  • Prefer Broad Design Skills over Platform Knowledge

    In his latest article Martin Fowler suggests that what matters most while building a team is not experience or thorough knowledge of the specific platform and business domain, but rather some broader skills that allow building quality software and delivering value.