Podcast Beta
Questions and Answers
Which of the following phrases is considered vague and indefinable?
What is a potential problem of using the word 'or' in a requirement?
Why should long sentences with complex language be avoided?
Which of the following is NOT a recommended practice in writing requirements?
Signup and view all the answers
What should be done to avoid ambiguity in writing requirements?
Signup and view all the answers
What is the minimum frame rate required for the game?
Signup and view all the answers
Which of the following measures is not typically included in performance measures?
Signup and view all the answers
What is the minimal transaction rate during peak load according to the performance measures?
Signup and view all the answers
How is availability defined in the context of system performance?
Signup and view all the answers
What is the role of Mean-Time to Repair (MTTR) in calculating availability?
Signup and view all the answers
Which of the following best describes the measure of reliability?
Signup and view all the answers
When calculating availability, what does the formula Availability = MTTF/(MTTF + MTTR) rely on?
Signup and view all the answers
What is one of the examples of an availability measure?
Signup and view all the answers
What is the form of a ubiquitous requirement?
Signup and view all the answers
Which of the following requirements is an example of an event-driven requirement?
Signup and view all the answers
In the context of quality measurements, what should non-functional requirements avoid?
Signup and view all the answers
What is essential for stakeholders regarding non-functional requirement values?
Signup and view all the answers
Which requirement form specifies a response to an unwanted external event?
Signup and view all the answers
What should be known about the desirable direction of values in requirements?
Signup and view all the answers
Which type of requirement is expressed as 'WHERE the shall'?
Signup and view all the answers
What is a key consideration during the initial process of gathering requirements?
Signup and view all the answers
What type of text is considered 'noise' in writing requirements?
Signup and view all the answers
Which phrase exemplifies wishful thinking in writing requirements?
Signup and view all the answers
What is the maximum allowable downtime for a system with 99.99% availability?
Signup and view all the answers
Which of the following is NOT a security measure mentioned?
Signup and view all the answers
What does 'over-specification' refer to in writing requirements?
Signup and view all the answers
What does ambiguity in writing requirements imply?
Signup and view all the answers
Which metric measures the success of an authentication process?
Signup and view all the answers
What is the primary focus of usability measures?
Signup and view all the answers
Which of the following phrases indicates a suggestion rather than a requirement?
Signup and view all the answers
Contradiction in requirement writing can lead to what problem?
Signup and view all the answers
For a system to be compliant with privacy measures, what approach is advised?
Signup and view all the answers
What is a danger sign that indicates possibility rather than certainty in writing requirements?
Signup and view all the answers
What is the acceptable time frame for a system to detect at least 99% of known intrusions?
Signup and view all the answers
Which level of system availability corresponds to only 5 minutes of downtime per year?
Signup and view all the answers
Forward reference in writing requirements leads to which issue?
Signup and view all the answers
What is one of the architectural requirements that may result from security measures?
Signup and view all the answers
Study Notes
Writing Pitfalls to Avoid
- Clarity is essential; avoid ambiguity in writing requirements.
- Common sources of ambiguity include the use of "or" in compound requirements and vague terminology like "etc."
- Indefinable terms such as "user-friendly" and "flexible" lack measurable quality.
- Single requirements should be expressed clearly in individual sentences, avoiding conjunctions like "and" or "or."
- Avoid verbosity; concise writing is preferred over long, convoluted sentences.
Speculation and Wishful Thinking
- Avoid speculative language, such as "may" or "could," as it leads to unclear expectations.
- Wishful thinking involves unrealistic demands, e.g., "100% reliable" or "fully upgradeable," and should be avoided.
- Providing too many vague generalizations can lead to misinterpretation of requirements.
Typical Mistakes
- Noise refers to unnecessary information that doesn't aid in understanding requirements.
- Silence means omitting features that should be described clearly.
- Over-specification describes solutions rather than the problem at hand.
- Inconsistent terminology leads to confusion; ensure uniform language throughout documents.
- Ambiguity arises when text can be interpreted in multiple ways; strive for clarity.
Patterns for Functional Requirements
- Understand different requirements syntax: Ubiquitous, State-driven, Event-driven, Option, and Unwanted Behavior.
- Framework includes formats such as "The system shall..." for clear articulation of requirements.
Quality Measurements
- Non-functional requirements should be quantifiable; avoid subjective terms like "optimal."
- Stakeholders must comprehend the rationale behind requirement values.
- Early stages of requirement gathering can remain flexible; specific metrics can be defined later.
Performance Measures
- Key performance indicators include response time, throughput, and system capacity.
- Examples include requirements for transaction rates and processing times under specific workloads.
Reliability Measures
- Reliability signifies the system's ability to perform under stated conditions over a designated timeline.
- Measurable elements of reliability include defect rate and precision of calculations.
Availability Measures
- Availability indicates the proportion of operational time; calculated using Mean-Time to Failure (MTTF) and Mean-Time to Repair (MTTR).
- High availability standards illustrate desired uptime percentages and allowable downtime durations in operational contexts.
Security Measures
- Security can be evaluated by resistance to unauthorized access and the ability to maintain services during attacks.
- Architectural requirements may address authentication, detection mechanisms, and secure channels.
Privacy Measures
- Privacy requirements should encompass relevant laws and frameworks rather than generic clauses, ensuring specificity in compliance needs.
Usability Measures
- Focus on user ease and the requirement for minimal training, promoting intuitive design and functionality.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Related Documents
Description
This quiz covers common writing pitfalls to avoid, focusing on the importance of clarity and precision in language. Explore issues related to ambiguity and vague terms that can hinder effective communication. Learn how to eliminate confusing language to enhance your writing skills.
