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.

Sign up for GitHub

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

Jump to bottom

How is communicated? #33

Open
Kr0nox opened this issue Jan 29, 2024 · 0 comments
Open

How is communicated? #33

Kr0nox opened this issue Jan 29, 2024 · 0 comments
Labels
accepted Uncertainty was manually verified and entered into the archive

Comments

@Kr0nox
Copy link
Collaborator

Kr0nox commented Jan 29, 2024 •
edited
Loading

How is communicated?

Description

The uncertainty regarding communication methods and channels employed within a software development project.

Literature Reference

Classifications

Category Option
Location Behavior
Architectural Element Type Connector
Type Scenario Uncertainty
Manageability Fully Reducible
Resolution Time Design Time
Reducible by ADD Yes
Impact on Confidentiality Indirect
Severity of the Impact High

Keywords

Communication

Example

Communication over a public network like the internet raises different concerns regarding security as a private connection, e.g., using a VPN.

Related Uncertainties

Children:

#39, #41

Related Uncertainties:

#62
@Kr0nox Kr0nox added the proposal A proposed uncertainty that was not yet verified and added to the archive label Jan 29, 2024
This was referenced Jan 29, 2024
Open
Open
Open
Open
Open
@sebinside sebinside added accepted Uncertainty was manually verified and entered into the archive and removed proposal A proposed uncertainty that was not yet verified and added to the archive labels Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted Uncertainty was manually verified and entered into the archive
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sebinside @Kr0nox