Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Diagramming Content on InfoQ


RSS Feed
  • Start Your Architecture Modernization with Domain-Driven Discovery

    Successful projects start with robust discovery. What if your project is modernizing your tangled old legacy system or migrating all your workloads to the cloud? This article presents a guided approach to starting your next architecture modernization project with a Domain-Driven Discovery (DDD), illustrated with a medical supply company that is migrating its core systems to the cloud.

  • Why Do We Need Architectural Diagrams?

    Software architecture diagrams, when created well, and sparingly, can greatly improve communication within the development team and with external stakeholders. They require an understanding of the intended audience, and thoughtful restraint on what to include. Resist the temptation to think that diagrams are unnecessary or unhelpful, simply because there have been plenty of cases of bad diagrams.

  • The C4 Model for Software Architecture

    Software architecture diagrams can be a very useful communication tool, but many teams have scaled back on the creation of diagrams, and when diagrams are created, they are often confusing and unclear. The C4 model consists of a hierarchical set of software architecture diagrams for context, containers, components, and code.

  • The Art of Crafting Architectural Diagrams

    Architectural diagrams can be useful tools for documenting and communicating the design of a system. They must be self descriptive, consistent, accurate enough and connected to the code. Applying some guidelines can ensure the diagrams are useful to a variety of stakeholders.

  • Tracking Schedule Progress in Agile

    The challenge of knowing whether we are on track to deliver haunts projectmanagers and developmentmanagers at various levels as their organizations take on agile approaches to product and project development. Driving towards smaller work items and lower work in process brings the benefits of both better project risk management as well as more effective agile execution and learning.