Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SA4D #9

Open
rdmueller opened this issue Dec 11, 2016 · 2 comments
Open

SA4D #9

rdmueller opened this issue Dec 11, 2016 · 2 comments

Comments

@rdmueller
Copy link
Member

I think we should write something about the difference between SA4D and arc42.

I see the main difference that arc42 need no code and can be used to describe a software architecture independent of code. SA4D builds on the assumption that the needed architecture diagrams can be extracted from the code - it does not plan the architecture, but documents it.

As a result, both approaches might be used together: arc42 for planning and SA4D in a later stage for checking that reality and plans are the same. From that point on, SA4D could generate the diagrams for arc42.

Please correct me if I got it wrong...

@gernotstarke
Copy link
Member

my thesis is that architecture models can NOT generally be generated from code, at least not without massive help by knowledgeable people...
Generation works for smaller systems (single-language, already good modularization)...

But: It'd be great to cover SA4D + arc42 in the FAQ (and in some articles in JavaMagazin...)

(my current prio is to add further questions to the faq-site - then add additional topics)

@rdmueller
Copy link
Member Author

yes, I agree with your thesis.
As I do understand Simons approach, he codes his solution with some architectural hints within the code. That lets him generate the diagrams from the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants