Non-Functional
Non-Functional
Category* |Priority |Non Functional
Requirement Name |Description |Applies to Use Case(s): |Exceptions | |
|Quality |1 |Persistence |The data should still exist in a database regardless of whether the |All | |
| | | |system is running or not. | | |
|Quality |2 |Reliability |Application should accurately capture student |All | |
| | | |preferences and generate an appropriate course | | |
| | | |offerings report. | | |
|Project Plan and |3 |Authentication |System should verify users to ensure that they are who they say they |All | |
|Development Methods | | |are. | | |
|Quality |4 |Security | Software should be developed with security in mind. (i.e. |All | |
| | | |prevention of SQL injection attacks.) | | |
|Project Plan and |5 |Traceability |System features and design must clearly trace back to requirements. |All | |
|Development | | | | | |
|Methods | | | | | |
|Quality |6 |Robustness |Software should be able to successfully handle error and boundary |All | |
| | | |conditions while running. | | |
|Environment and Technology|7 |Platform |The client software must be Internet Explorer and Firefox compliant. |All | |
|Constraints | | | | | |
|Quality |8 |Usability/Achievability |Application should be user friendly and easily navigable. |All | |
|Quality |9 |Availability |System should have a 95% uptime. |All |Uptime may decrease |
| | | | | |during registration. |
| | | | | |The functionality |
| | | | | |provided by CourseCast |
| | | | | |generally is not needed|
| | | | | |as much during this |
| | | | | |time frame. |
|Quality |10 |Performance |Application should be able to handle up to approximately 500 |All | |
| | | |simultaneous users and should be able to respond promptly to user | | |
| | | |input. | | |
|Project Plan and |11 |Delivery Date |The system and iterations must be completed by the end of April 2008.|All | |
|Development | | | | | |
|Methods | | | | | |
|Quality |12 |Maintainability |Amount of effort required to maintain and enhance application. |All | |
|Environment and Technology|13 |Installability |Ease of system installation on all necessary platforms. |All | |
|Constraints | | | | | |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- learning management system requirements
- functional requirements document checklist
- system requirements specification
- functional and non functional requirements
- non functional requirements in software
- gather non functional requirements task guidelines
- non functional
- using non functional requirements to structure design
- functional requirements document template
Related searches
- example of non functional requirements
- non functional requirement template
- non functional requirements list
- example non functional requirements
- non functional requirements software examples
- non functional requirement categories
- non functional requirements document
- writing non functional requirements examples
- technical non functional requirement examples
- functional and non functional requirements
- non functional requirements example
- data integrity non functional requirement