In: Computer Science
1. The system failure rate shall be less than 1 failure per 1000 hours of operation.
This is a non-functional requirement as the system failure and success rate is something that is inherent to the developer and not specifically needs to be mentioned by the client. Any good software or system should have a low failure rate even without being needed to be mentioned separately. This attribute of the system is known as reliability.
2. The system shall return for a search run by a user in less than 3 seconds.
This is a non-functional requirement as the time taken to return a search result is inherently an attribute of a good system known as performance. The performance of any system is a non-functional requirement as no client needs to specifically mention that the system required should have excellent performance ability.
3. The system shall be available 99.99% of the time.
This is a non-functional requirement as the availability of the system is expected at all times. This is a combination of attributes like reusability, robustness, and performance. The onus of providing a system which is at disposal of the client at all times is expected from the developer without the client being required to mention it separately.
4. The system shall allow the human resource manager to view attendance reports and check-in/ check-out times for hourly employees.
This is a functional requirement as this relates to the attribute of a system known as accessibility. Accessibility to the system is specifically provided by the client to provide a different level of authentication to the people with differing responsibilities.
5. The system will require less than 10 Mbps internet speed to handle 100 concurrent users.
This is a non-functional requirement as this relates to capacity, bandwidth, and internet speed. These qualities are expected from any good system from the side of the developer. The client expects a system having minimal resource utilisation and maximum output.