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

Feedback on the Product Backlog #2

Closed
scharffc opened this issue Mar 21, 2018 · 0 comments
Closed

Feedback on the Product Backlog #2

scharffc opened this issue Mar 21, 2018 · 0 comments
Assignees

Comments

@scharffc
Copy link

Add a link on the wiki called Feedback from Dr. Scharff with link https://github.com/paceuniversity/cs3892018team1/issues/new.

We need the link to your req validation on the wiki, the one that was done by the other team.
#1

Keep the req validation you did too.

Put functional and non-functional req in different colors. How many functional and non-functional req do you have?

Did I draw your app? If yes, this needs to be in the req discovery document.

I put some comments. Please leave them but answer them.

US are well-written. We get a good idea of the app when reading the reqs.

I would not put login as a high priority. People who install apps will not like to have to create an account the first time they use the app. We could use the app for a while without registering.

In terms of priority think about the core features of the app. What the app relies on.

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

5 participants