A-ESA

Agile Enterprise Solution Architecture

A-ESA General Discussions

The blog comments received after August 15, 2024 have been responded to through email exchanges for more effective two-way communication. Answers to frequently asked questions can be found in various A-ESA FAQs and short articles.

13 responses to “A-ESA General Discussions”

  1. Josh Zhang Avatar
    Josh Zhang

    Why do we need agile ESA?

    1. Sean Gu Avatar
      Sean Gu

      The agile ESA (enterprise solution architecture) fills the missing specification in the solution architecture modeling space. A-ESA’s plan-while-modeling approach facilitates EA landing and solution improvement. In short, it emphasizes significant case scenarios and focuses on non-functional requirements and governing correlations. It uses less formal specifications for ease of learning and adoption, communicates better rather than more, and allows for some flexibility.

  2. Jason Avatar
    Jason

    Will the A-ESA be supported by the tool?

    1. Sean Gu Avatar
      Sean Gu

      See newly added “Model Tool” link, thanks.

  3. Dan Swish Avatar
    Dan Swish

    Does agile architecture really need a modeling approach?

    1. Sean Gu Avatar
      Sean Gu

      Agile architecture commonly requires agile and quick modeling. An agile modeling approach is a balance between agility and architectural compliance.

      An agile architecture without a modeling is either a small-scale architecture or a scratchable architecture or the like. Even a decent-sized solution or product hosted in a cloud environment needs agile modeling support. In a word, adapting to change becomes challenging without implementing agile modeling within the enterprise-wide architecture in some shape or form.

  4. Sean Gu Avatar
    Sean Gu

    Agile Enterprise Solution Architecture (A-ESA) Q&A

    1. Sean Gu Avatar
      Sean Gu

      Why does A-ESA prefer a relationship view over an interaction view?

      A-ESA is all about the big picture of enterprise solutions, not each individual use case. Don’t get caught up in the design mindset when you’re creating enterprise solutions. If you can, try to avoid using interaction or sequence diagrams unless you’re dealing with a pretty complex scenario. Use the interaction view only for analyzing critical cases or walkthrough validations.

    2. admin Avatar

      Answers to reader questions posted here will be published in: enterprise-solution-architecture.com, which also includes past postings.

  5. Hermelin Avatar
    Hermelin

    whoah this blog is excellent i really like studying your posts.
    Stay up the good work! You already know,
    lots of individuals are looking around for this info, you could aid them greatly.

  6. Lillaven Avatar
    Lillaven

    That is very interesting, You’re a very professional blogger.

    I’ve joined your feed and sit up for in search of extra
    of your excellent post. Additionally, I’ve shared your site in my social networks

  7. Keith Avatar
    Keith

    great issues altogether, you simply gained a new reader.
    What could you recommend about your publish that you just
    made a few days in the past? Any certain?

  8. Rosellar Avatar
    Rosellar

    Thanks for one’s marvelous posting! I definitely enjoyed reading it, you are a great
    author. I will always bookmark your blog and may come back in the
    future. I want to encourage you to continue your
    great writing, have a nice holiday weekend!

Leave a Reply

Your email address will not be published. Required fields are marked *