Search the whole librarySearch and tags
Advanced AI Library. Three Ways to Use It.
Plug it in as a prompt to get an answer. Set it as a goal to complete a complex task. Turn it into a reusable skill for your library.
Each resource is structured for all three.
Category counts cover all available entries.
Choosing a category or subcategory updates the results. Search and tag filters stay selected.
Quality Expectations
Entries tagged Quality Expectations across the library, including matching entries from the original collection.
Explore entries
Define Non-Functional Requirements for Quality Assurance
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt is designed to help teams articulate non-functional requirements that define quality expectations. It provides templates to ensure these requirements are clear, relevant, and aligned with user needs and business goals. Non-functional requirements are crucial for establishing the performance, reliability, and usability standards of a product. By clearly defining these requirements, teams can ensure that the product meets both internal quality standards and external user expectations, facilitating better alignment with business objectives.
{
"role": "You are a product development specialist with expertise in drafting non-functional requirements.",
"goal": "Create a set of non-functional requirements for [product] that meets [quality standards] and aligns with [user needs] and [business goals].",
"context": [
"Consider the product's intended use, target audience, and operational environment.",
"Include templates for documenting non-functional requirements such as performance, reliability, scalability, and usability.",
"Provide guidelines for aligning these requirements with user expectations and business objectives.",
"Factor in industry standards and best practices for non-functional requirements documentation."
],
"output": [
"A comprehensive list of non-functional requirements with clear definitions and success criteria.",
"Templates for documenting performance, reliability, and usability standards.",
"Guidelines for ensuring alignment with user needs and business goals.",
"Examples of industry-standard non-functional requirements for reference."
],
"toneStyle": "Professional, precise, and user-focused.",
"constraints": [
"Ensure the requirements are measurable and testable.",
"Avoid technical jargon that may confuse stakeholders."
],
"startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
"followUpQuestions": "After presenting the result, only if meaningful uncertainty remains or a useful refinement would improve it, ask up to [3] concise follow-up questions to refine a quality threshold or verification method. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Define relevant quality requirements with testable success conditions for the product's operating context.",
"Make performance, reliability, scalability, and usability documentation consistent with supplied user and business needs.",
"Use understandable language and distinguish verified industry standards from illustrative targets requiring confirmation.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}End of results.
Load more