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

How to deal with gap analysis? Ned clear definition for "gap analysis #266

Closed
chachamimm opened this issue Jan 31, 2024 · 1 comment
Closed
Labels

Comments

@chachamimm
Copy link
Collaborator

McCool: we need a document on the current features.
... I agree we should not accept proposals which are already covered.
... Btw, I think user stories are good way to see the gaps also see issue 261 also
... #261
kaz: we need to define "gap analysis" a bit more
... user story is important but it's already required for the use case definition phase as the starting point
... my understanding on what Mizushima-san meant by "gap analysis" is evaluating if the requirements extracted from the use cases are already covered by the existing WoT standards or not
... but we still need to clarify what we mean by "gap analysis"

@egekorkan
Copy link
Contributor

Duplicate of #267, closing

@egekorkan egekorkan closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants