-
Notifications
You must be signed in to change notification settings - Fork 1
Requirements
2.1. Functional Requirements
2.2. Non-Functional Requirements
2.2.1. Security
2.2.1.1. Confidentiality, integrity, availability, accountability, privacy and authenticity shall be provided.
2.2.1.1.1. Privacy
2.2.1.1.1.1. The user’s information shall not be shared, copied or used without user’s permission.
2.2.1.1.2. Availability
2.2.1.1.2.1. Information shall be available to authorised users when they need them.
2.2.2. Usability
2.2.2.1. The system shall be user friendly.
2.2.2.1.1. Learnability
2.2.2.1.1.1. New users shall begin effective interaction.
2.2.2.1.1.2. Tutorial for the new users shall be provided.
2.2.2.1.1.3. Help document shall be provided.
2.2.2.1.2. Flexibility
2.2.2.1.2.1. Negotiable task allocation between the user and the system should be provided. (Task-Migratability)
2.2.2.1.2.2. The system shall be dialogue initiative.
2.2.2.1.3. Robustness
2.2.2.1.3.1. User shall be able to evaluate internal conditions of the system. (Observability)
2.2.2.1.3.2. The system shall provide support for undoing errors. (Recoverability)
2.2.2.1.3.3. The system functionality shall match common user tasks. (Task Conformance)
2.2.3. Portability
2.2.3.1. The system shall have Web and Mobile client.
2.2.3.1.1. The system shall be compatible with latest versions of Google Chrome, Mozilla Firefox and Safari available in 2016.
2.2.3.1.2. The system shall be compatible with Android.
2.2.4 Reliability
2.2.4.1. The system shall recover the last working state in case of crush.
2.2.5 Flexibility
2.2.5.1. The system shall be designed to add new features easily.
2.2.6. Accessibility
2.2.6.1. The interface shall be designed according to color-blindness.
2.2.6.1. The font size shall be changed for users who have eye discomforts.
2.2.7. Efficiency
2.2.7.1. The system shall be storage-friendly.
2.2.8. Maintainability
2.2.8.1. The system shall support previous version for 6 months.
2.2.9. Price
2.2.9.1. The system shall be free for all users.
2.2.10. Operability
2.2.10.1. The system shall be kept in safe and reliable functioning operation.
2.2.11. Performance
2.2.11.1. The maximum response time shall be 5 seconds for all tasks excluding problems regarding users such as network problems etc..
- Project Description
- Project Video
- Themes/Features
- User Stories & Acceptance Criteria
- Personas
- Domain Analysis
- Requirements
- Initial Plan
- Diagrams
- Use Cases
- Peer Reviews
- Mockups
- Test Plan
- User Tests
- Test Web Project
- Meeting 1 - 16.02.2016
- Meeting 2 - 18.02.2016
- Meeting 3 - 3.3.2016
- Meeting 4 - 7.3.2016
- Meeting 5 - 11.3.2016
- Customer Meeting 1 - 28.03.2016
- Meeting 6 - 8.4.2016
- Customer Meeting 1 - 29.9.2016
- Customer Meeting 2 - 06.10.2016
- Meeting 7 - 06.10.2016
- Meeting 8 - 13.10.2016
- Customer Meeting 3 - 27.10.2016
- Meeting 9 - 27.10.2016
- Customer Meeting 4 - 03.11.2016
- Meeting 10 - 03.11.2016
- Meeting 11 - 10.11.2016
- Meeting 12 - 01.12.2016
- Meeting 13 - 08.12.2016
- Customer Meeting 5 - 08.12.2016
- Meeting 14 - 08.12.2016