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

Mock Q31: Improvement of the phrasing as well as clarification of answers #46

Open
rhoadesre opened this issue Feb 18, 2021 · 0 comments

Comments

@rhoadesre
Copy link
Contributor

Original question and answers:
Software architecture documentation could contain descriptions of cross-cutting concerns. Pick the TWO best reasons why documentation of cross-cutting concerns is useful.
a) Cross-cutting concepts should focus on the domain and be free of technical information.
b) Aspects or concepts that are used in multiple parts of your software architecture should be described in a non-redundant way.
c) Cross-cutting concepts can be reused in more products within the same organization.
d) Cross-cutting concepts should be implemented by specialists. Therefore, separate documentation is useful.

Problems:
Question: The first sentence in the question is not necessary and doesn't lead to clarification.
b) I don't understand what this means. I will try to interpret and rephrase.
c) needs clearer phrasing
d) not necessarily true or false. Cross-cutting concerns are often documented by different people based on their skills (internationalization, security, etc.)

Recommended changes:
Pick the TWO best reasons why documentation of cross-cutting concerns is useful.
a) Cross-cutting concerns should focus on the domain and be free of technical information.
b - option 1 as correct answer) The general implementation approach for specific cross-cutting concerns should be documented centrally and uniformly.
b - option 2 as wrong answer) The implementation approach for cross-cutting concerns should be documented in each part of the system that they occur.
c) The same implementation approach for cross-cutting concerns could be reused for multipole products within the same organization.
[Note: depending on the intent, either use "The same implementation ..." or "The same implementation approach ..:"]
d) Cross-cutting concerns require a specialized skillset (e.g. security); therefore, they should be documented separately from the software architecture.

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

1 participant