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

Disambiguate command vs message requirements #525

Closed
skliper opened this issue Feb 20, 2020 · 0 comments · Fixed by #526 or #530
Closed

Disambiguate command vs message requirements #525

skliper opened this issue Feb 20, 2020 · 0 comments · Fixed by #526 or #530
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Feb 20, 2020

Is your feature request related to a problem? Please describe.
"Command" terminology has been used for both ground commands (that increment command counters) and inter-app commands (that typically do not increment command counters). So it's unclear in the requirement which sort of use case is intended.

Describe the solution you'd like
"Command" is ground command with additional associated behavior (increments command counters), "Message" is typical sb message that does not increment command counter.

Describe alternatives you've considered
None

Additional context
Discovered during requirements scrub, helps clarify what impacts command counter.

Requester Info
Jacob Hageman - NASA/GSFC

skliper added a commit to skliper/cFE that referenced this issue Feb 20, 2020
@skliper skliper added this to the 6.8.0 milestone Feb 25, 2020
astrogeco added a commit that referenced this issue Feb 26, 2020
@astrogeco astrogeco linked a pull request Feb 26, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants