A-ESA General Discussions
9 responses to “A-ESA General Discussions”
-
Why do we need agile ESA?
-
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.
-
-
Will the A-ESA be supported by the tool?
-
See newly added “Model Tool” link, thanks.
-
-
Does agile architecture really need a modeling approach?
-
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.
-
-
Agile Enterprise Solution Architecture (A-ESA) Q&A
-
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.
-
Answers to reader questions posted here will be published in: enterprise-solution-architecture.com, which also includes past postings.
-
Leave a Reply