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

Non-functional requirements #5

Closed
timroesner opened this issue Feb 5, 2019 · 2 comments
Closed

Non-functional requirements #5

timroesner opened this issue Feb 5, 2019 · 2 comments
Assignees
Labels
2 Takes 2h to complete General Spike Doing research on the topic
Projects

Comments

@timroesner
Copy link
Owner

Compile a list of all non-functional requirements, divided into -Must, -Should, -Optional

@timroesner timroesner added Spike Doing research on the topic 2 Takes 2h to complete General labels Feb 5, 2019
@timroesner timroesner added this to To do in Sprint #1 Feb 5, 2019
@renjieye07 renjieye07 moved this from To do to In progress in Sprint #1 Feb 11, 2019
@renjieye07 renjieye07 moved this from In progress to To do in Sprint #1 Feb 11, 2019
@renjieye07
Copy link
Collaborator

Usability
It should take at most ten minutes for a user to completely understand how the website works.
It should take at most five steps for a user to complete a task.
Reliability
System crashes must not alter user data.
The web application must be able to handle incorrect inputs from the user and display correct error messages.
Performance
The system must be able to handle at least one hundred simultaneous connections at a time.
Availability
The system should be accessible 24/7.
The server should not be down for longer than ten minutes at a time.
Supportability
The system should allow new features to be easily implemented.
The code should be well documented to enhance readability.
Implementation
The web application should be supported on any platform and operating system.
Interface
The interface should be user-friendly and easy to use to avoid any confusion.
Colors used on the web application must not interfere with user readability.
Buttons and navigation links should be clear and easy to understand.
Form inputs should be appropriately labeled.
Packaging
The deployed web application should be accessible to users on any operating system as long as the user has internet access.

@renjieye07 renjieye07 moved this from To do to In progress in Sprint #1 Feb 11, 2019
@timroesner
Copy link
Owner Author

Put this into a google doc: https://docs.google.com/document/d/1YxsshVe6K2E9JdymZwx0F6RqYh8-Re33v8u4-ruePbQ/edit#

When you're ready move the ticket into "needs review"

@renjieye07 renjieye07 moved this from In progress to Needs review in Sprint #1 Feb 19, 2019
Sprint #1 automation moved this from Needs review to Done Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 Takes 2h to complete General Spike Doing research on the topic
Projects
No open projects
Sprint #1
  
Done
Development

No branches or pull requests

2 participants