Project Management

Please login or join to subscribe to this thread

Quality requirements VS Quality of services requirements

linkedin twitter facebook   Requirements Management  
avatar
Kevin Drake Perth, Western Australia, Australia
I need examples on each, please
Sort By:
avatar
Habib Alsaffar Jeddah, Saudi Arabia
Kevin,

Quality requirements are specifications of the quality of products, services, processes or environments. Quality is any element, tangible or intangible, that gives things value beyond their functionality and features.
Example, as QHSE
Environmentally,
office indoor - poor ventilation will give lack of air quality, controlling office temperature ( lack of or uncontrolled mentioned will effect to employee income of their daily work.

Quality of Service Requirements: Quality of service requirements are technical specifications that specify the system quality of features such as performance, availability, scalability, and serviceability.
in other hand, "The name 'Quality of Service Requirement' was suggested as alternative to 'nonfunctional requirement' or 'quality attribute' in MSF for Agile Software Development by Sam Guckenheimer.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
I will write but both have ambiguity. Quality of Services (QoS) requirements are often named Non Functional Requirements. Those must be considered as attributes of the product/service/result the project is creating. That is valid for software and non-software products (I am clarifying because some people tied non-functional to software). I am using Barry Bohem´s Clasification from years because that clasification is applied to lot of domains. I do not like wikipedia but the article inside it deserves to be read mainly because the clasification: https://en.wikipedia.org/wiki/Non-functional_requirement.
Quality Requirements is about quality itself. Basically is about to decide if you will use quality assurance and quality control in your project.. The important thing is Quality Requirement defines the expectations of the customer for quality, the internal processes as well as the attributes of products that indicate whether the quality factors are satisfied or not.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
The important thing is: all related to quality impacts on customer satisfaction. As project manager you will accountable to create the product/service/result exactly as defined. That only can be achieved through Quality. Project manager will contribute to customer satisfaction with that because project manager is not the role that help organization to define the product/service/result, that mean, to translate needs into requirements. The only requirements you are in charge of are project requirements. Projecr requirements are defined from product requirements. So, Quality is a component of project requirements project manager is in charge of definition.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Critics can't even make music by rubbing their back legs together."

- Mel Brooks

ADVERTISEMENT

Sponsors