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

ARCH-005: Modularity #22

Closed
jimsch opened this issue Apr 11, 2015 · 3 comments
Closed

ARCH-005: Modularity #22

jimsch opened this issue Apr 11, 2015 · 3 comments

Comments

@jimsch
Copy link
Contributor

jimsch commented Apr 11, 2015

Version -04

This requirement appears to be a duplicate of requirement G-005 and G-008. What is the reason for having this be distinct?

@ncamwing
Copy link
Contributor

ncamwing commented May 4, 2015

Hi Jim,
I view versioning and back compabilitibility as being somewhat different than extensibility.
The extensibility is to allow for other (especially vendor specific) attributes to be allowed (but not mandatory to SACM)....

Nancy.

@llorenzin
Copy link

Nancy, I read what Jim is saying as - extensibility (G-005) and versioning / backward compatibility (G-008) are already defined as general requirements, so why have the same requirement again in the architecture section? Jim - i think the answer is: ARCH-005 is specific to how the components are expected to interact with each other, which is defined in the architecture.

@jimsch
Copy link
Contributor Author

jimsch commented May 8, 2015

No change needed. Lisa is correct in terms of what I was asking.

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

No branches or pull requests

3 participants