I would like to know the varrious software qualities(attributwes) identifying the functional and non-functional requirement qualities in nature.

Dani AI

Generated

As framed the question and following and , the practical challenge is not naming qualities but turning them into measurable, testable requirements that developers and testers can act on. Below is a concise approach to do that reliably.

Start with a short, repeatable scenario template: identify the quality (performance, security, usability, maintainability), the stimulus/source, the environment/load, the affected component, the expected response, and the measurable acceptance criterion. Make the metric explicit (percentile, throughput, error rate, MTBF), state the exact threshold, and name the test method and observation window. Example pattern: "Under X workload, Y percent of transactions shall complete within Z ms measured end-to-end over N minutes." This pattern follows common quality-attribute practice and maps easily to test automation and capacity planning (ISO/IEC 25010; Non-functional requirement).

Keep each non-functional requirement traceable: give it an ID, link it to an acceptance test, and record the architectural decisions that satisfy it. Prioritize NFRs so trade-offs are explicit (MoSCoW is a simple technique). Avoid vague words like "fast" or "user-friendly" without numbers and include how you will measure them. For prioritization guidance see MoSCoW method.

Recommended Answers

All 2 Replies

Your requirement, as stated, is non-functional.

commented: XD +4

Functional requirements normally deal with the functions that the software is supposed to offer. For eg. add/delete/modify inventory items.

Non-functional requirements deal with intangible items like stability, reliability, threshold, user-friendliness, etc.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.