req 2 Flashcards

1
Q

What is the outcome of requirements development?

A

A documented agreement among stakeholders about the product to be built.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What typically contains business requirements?

A

A business case or vision document.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How are user requirements captured?

A

In the form of use cases or user stories.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is a Software Requirements Specification (SRS)?

A

A document that includes the product’s functional and nonfunctional requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the most practical way to document requirements for software projects?

A

Structured natural language, augmented with visual models and other representation techniques.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the purpose of a unique persistent identifier for each requirement?

A

To track in change requests, modification histories, and requirements traceability matrices.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are some examples of unique persistent identifiers?

A

Unique sequence numbers, hierarchical numbering, or hierarchical text tags.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

True or False: UI designs in the SRS can replace written user and functional requirements.

A

False.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What does Section 1.1 of a Template SRS cover?

A

The purpose of the document.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is included in Section 2.1 of a Template SRS?

A

Product perspective, describing the product context and origin.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What should be identified in Section 2.2 of a Template SRS?

A

User classes and characteristics.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What does Section 5 of a Template SRS cover?

A

External interface requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

List the quality attributes mentioned in Section 6.

A
  • Usability
  • Performance
  • Security
  • Safety
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the characteristics that each requirement should have?

A
  • Complete
  • Correct
  • Feasible
  • Necessary
  • Prioritized
  • Unambiguous
  • Verifiable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the goal of writing good requirements?

A

To ensure consistent interpretation among readers and match the author’s intended meaning.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a generic template for a requirement from the system perspective?

A

[optional precondition] [optional trigger] the system shall [expected system response].

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Fill in the blank: The _______ shall be able to [do something] [to some object].

A

[user class or actor name]

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What writing style should be avoided to improve clarity in requirements?

A

Passive voice.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What should be avoided in requirements to prevent ambiguity?

A

Compound logical statements and negative requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What visual representation techniques can be used for system external interfaces?

A
  • Context Diagrams
  • Use Case Diagrams
  • Data Flow Diagrams
  • Ecosystem map
  • Swim lanes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is the generic syntax for writing requirements according to EARS?

A

<optional> <optional> the <system> shall <system>.
</system></system></optional></optional>

22
Q

What type of requirement is always active and has no preconditions or trigger?

A

Ubiquitous Requirements.

23
Q

What is the definition of usability according to ISO 9241, part 11?

A

The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.

24
Q

What is the role of requirements engineering in usability?

A

To define usability characteristics early in the development process and measure them throughout.

25
What does Requirements Engineering define in relation to usability?
The target usability level of an application in advance and ensures that the software developed reaches that level.
26
What is usability?
The extent to which a system, product, or service can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use.
27
List the five usability attributes outlined in the paper.
* Learnability * Efficiency * User retention over time * Error rate * Satisfaction
28
Define learnability in the context of usability.
How easy it is to learn the main system functionality and gain proficiency to complete the job.
29
What does efficiency measure in usability?
The number of tasks per unit of time that the user can perform using the system.
30
What is meant by user retention over time?
The ability for intermittent users to use the system without climbing the same learning curve from scratch each time.
31
What contributes negatively to usability?
Error rate from the number of errors the user makes while performing the task.
32
What does satisfaction quantify in usability?
A user's subjective impression of the system.
33
True or False: Learnability and efficiency can influence each other negatively.
True
34
What is the first phase of the usability process?
Usability Analysis
35
What is involved in user analysis?
Site visits, focus groups, surveys, derived data, and contextual inquiry.
36
What are usability benchmarks?
Quantitative usability goals defined before system design begins, based on the five usability attributes.
37
What is conceptual design in the usability design phase?
Defining the basic user-system interaction, its context, and the objects in the UI.
38
What is the purpose of prototyping in usability?
To help users understand tangible system prototypes much better than abstract specs.
39
What is formative assessment in usability evaluation?
Asking the test participant to reason aloud while using the system.
40
List three usability principles according to Nielsen.
* Simple and Natural Dialogue * Speak the User's Language * Minimize the User's Memory Load
41
What does the System Usability Scale (SUS) measure?
A quick and dirty survey method for assessing a system's usability.
42
How is the SUS score calculated?
Multiply the sum of scores by 2.5 for the overall value (between 0 and 100).
43
What is UMUX?
A four-question survey that serves as a proxy for the ten-question SUS.
44
What is accessibility?
The extent to which products, systems, services, environments, and facilities can be used by people from a wide range of characteristics and capabilities.
45
How does usability differ from accessibility?
Usability specifies a group, while accessibility targets the broadest range of users possible.
46
What is a key requirement for accessibility in web development?
Making a website or mobile application perceivable, operable, understandable, and robust.
47
List two cognitive accessibility tips.
* Deliver content in more than one way * Make content easily understood, using plain language standards
48
What is the role of semantic HTML in accessibility?
It helps screen readers understand the content more effectively.
49
What is WAI-ARIA?
A standard to provide additional semantics for screen readers where native semantic HTML cannot be relied upon.
50
What should be considered for mobile accessibility?
Ensure input is simple, the interface works on touch, and the design is responsive.