Requirements Engineering > RE Important > Flashcards

RE Important Flashcards

(110 cards)

Study These Flashcards
1
Q

What is the User Perspective Requirements?

A

Condition or capability needed by a user to solve a problem or achieve objective

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

What is the System Perspective Requirements?

A

Condition or Capability that must be met or possessed by a system or system component

To satisfy contract, standard, specification or other formally imposed documents

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

What is Industry Perspective Requirements?

A

A documented representation of condition or capability

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

List out 4 RE Process

A
  1. Elicitation
    • Optain requirements from stakeholders
  2. Documentation
    • Describe requirements properly
  3. Validation and Negotiation
    • Check requirements meet certain quality criteria to resolve conflict
  4. Requirements Management
    • Structure requirements to prepare for different roles, change and implement consistently
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the Fact Ear?

A

Concerns objective, matter-of-fact information, such as data or literal facts

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

What is the Self-Disclosure Ear?

A

Provides implicit information about the sender (which may be conscious or intended), revealing things like their motives, values, emotions, or likes/dislikes

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

What is the Relationship Ear?

A

Conveys information about the nature of the relationship between the sender and receiver, including how they get along and what they think of each other

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

What is the Appeal Ear?

A

Desire, advice, instruction, or command that the sender is seeking through the message

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

List out 6 reasons for RE

A
  1. Identify problems
  2. Understand the problems
  3. Provide details to the system to be built
  4. Basis for design and implementation
  5. Contract between stakeholder and developer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

List out 2 types of requirements

A
  1. User Requirements
  2. System Requirements

User Requirements are high-level, natural language statements detailing the expected system services and constraints for the client

System Requirements are more detailed descriptions of the software system’s functions, services, and operational constraints written specifically for the developer

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

List out 2 classification of System Requirements

A
  1. Functional Requirements
  2. Non-Functional Requirements

User Requirements -> System Requirements -> Functional / Non-Functional Requirements

Functional Requirements define the services the system must provide, detailing what the system should do

Non-functional Requirements are the constraints placed upon the system’s operation and services

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

List out 3 categories of Non-Functional Requirements

A
  1. Product Requirements
  2. Organizational Requirements
  3. External Requirements

Product Requirements: These requirements specify or constrain the behavior of the software itself, defining necessary characteristics like performance or usability.

Organizational Requirements: These are broad system requirements derived from policies and procedures in the** customer’s and developer’s organization**.

External Requirements: This broad category covers all requirements derived from factors external to the system and its development process, such as regulatory or legal constraints

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

List out categories for Product Requirements (6)

A
  1. Performance (Response time, Resource Utilization)
  2. Security (Data,Network)
  3. Reliability (Dependability, Fault Tolerance, Recoverability)
  4. Usability (Understandability, Learnability)
  5. Maintainability (Testability, Changeability)
  6. Portability (Installability, Adaptability)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is the primary purpose of the System Boundary?

A

Separates the planned system from its environment, delimiting the changeable/shape-able part of the reality from aspects that cannot be changed through development

Think of the System Boundary as the dividing line that separates your project from the rest of the world

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

Define the System Context.

A

The context is the part of a system’s environment that is relevant to understanding the system and its requirements

Think of it as everything outside your project fence (the environment) that still matters to your project

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

What is the System Scope?

A

The system scope is the range of things that can be shaped and designed when developing the system, and it is located within the system boundary

Like everything inside your project fence (inside the System Boundary) that you actually get to build, design, and control

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

What does Feasibility Study reveal?

A

Reveal whether a project/plan is feasible (workable)

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

List out 4 types of Feasibility Study

A
  1. Technical
  2. Operational
  3. Economic
  4. Schedule
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

List out 4 RE Process

A
  1. Elicitation
  2. Documentation
  3. Validation & Negotiation
  4. Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

List out 4 Requirements Elicitation Activities

A
  1. Requirements Discovery (With stakeholders)
  2. Requirements Classification and Organization (Groups related requirements to form coherent clusters)
  3. Prioritisation and Negotiation
  4. Requirements Specification (Document)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

List out 5 problems during Requirements Elicitation

A
  1. Stakeholders don’t know what they really want
  2. Stakeholders express requirements in their own terms (cause misinterpretation)
  3. Different stakeholders have conflicting requirements
  4. Requirements may change during later process
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What will errors in requirements document lead to?

A

Lead to extensive rework costs

The cost of fixing requirements is much greater than repairing design and coding errors

Change to requirements means that system design and implementation must change, and system must be re-tested

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

List out 5 Requirements Checking

A
  1. Validity Checks (Requirement fulfilled different stakeholder need)
  2. Consistency Checks (Requirement not confilict with each other)
  3. Completeness Checks (Include all functions and constraints from user)
  4. Realism Checks (Can be implemented using existing technology)
  5. Verifiability Check (Verifiable by writing a test set)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

List out 2 stability types Requirements

A
  1. Ensuring (Stable requirements from core activity)
  2. Volatile (Change during development or system is in use)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
List out 3 attributes for the Kano Model
1. Basic Attributes (Dissatisfiers) 2. Performanmce Attributes (Satisfiers) 3. Excitement Attributes (Delighters)
26
List out 2 benefits of Interview
1. New topic can be addresses immediately 2. Ideal to find out performance factors
27
List out 2 weakness of Interview
1. Result depends on the experience of the moderator 2. Time consuming
28
List out 3 strength of Questionnaire
1. A lot of information in short time with relative low costs 2. Researches a large and distributed target audience 3. Obtains feedback from stakeholders with difficulties to phrase their knowledge
29
List out 4 weakness of Questionnaire
1. Ask topic already know 2. Hard to developing good queationnaires 3. Futher enquiry often not possible 4. Few feedback on missing motivation
30
List out 2 strength on Brainstorming
1. Generate many ideas in short time 2. participants inspired each other
31
List out 2 weakness of Brainstorming
1. Influence of dominant participants, difficult group dymanic 2. Not applicable to elicit detailed requirements
32
List out 2 strength and 1 weakness in Brainstorming Paradox
Strength 1. Find risk and how to address it 2. Same as classical brainstorming Weakness 1. Same as classical brainstorming
33
How does participants take different viewpoints in Change of Perspective
Six Thinking Hats
34
What is the Strength of Analogy?
1. New inspiration and perspectives 2. Hidden : Useful for delicate topics ## Footnote Analogy involves analysing analogies in nature or elsewhere to generate new ideas and perspectives
35
List out 2 weakness on Analogy
1. Not effective when participants do not have deep domain knowledge 2. Difficult to find an analogy that fits well
36
When is Observation good?(4)
1. Stakeholder have no time 2. Stakeholder are not good in phrasing their knowledge 3. Identify detailed requirements and basic factors 4. Work is difficult to explain in words
37
When is Observation bad? (3)
1. Risk to reuse inefficient processes and solutions 2. Identify only performance factors, which already exist 3. Not applicable for all new processes
38
When is Field Apprenticing good? (3)
1. Challenging procedures and existing solutions 2. Identify basic factos 3. Inversion of 'guide-follower' relationship between RE and stakeholder ## Footnote Executing the work of the user under their guidance
39
When is Field Apprenticing bad? (3)
1. Same as Observation field 2. Time consuming for stakeholder 3. Hurdle of needed domain knowledge for requirements engineer
40
List out 4 strength of System Archeology
1. Independent of the Stakeholders 2. Existing know-how is conserved 3. Identify basic factors 4. Provides detailed requirements ## Footnote Explor existing system functionalities
41
List out 3 weakness of System Archeology
1. Existing improper solutions are kept 2. A lot of work 3. Familiarity of the requirements engineer with implementation language
42
When are Prototyping being used?
To understand the consequences of the new or modified requirements more easily
43
Which modal verb indicates "Duty"?
Shall
44
Which modal verb indicates "Wish"?
Should
45
Which modal verb indicates "Intention"? (Future Requirement)
Will
46
Which modal verb indicates "Recommendation"?
May
47
List out 3 types of System Activities
1. Autonomous System Activity (System executes function **without user interaction**) 2. User Interaction (**User interact** with the system) 3. Interface Requirements (Execute function depend on **third system**)
48
List out 5 elements should be included inside Requirements Templates
1. Legal Obligation (Shall, Should, Will, May) 2. Determine the core of requirements 3. Characterize the activitiy of the system (Autonomous system activity, User Interaction, Interface Requirements) 4. Insert Objects 5. Determine logical and temporal conditions
49
List out 3 common elements for Requirements Document
1. Overview, Context, Scope 2. Functional Requirements 3. Non-Functional Requirments
50
What is Norminalization? | Causes of errors using Natural Language
A process (normally long lasting) is transformed into a single event ## Footnote Transmission, input, booking, acceptance
51
What is Nouns without reference index? | Causes of errors using Natural Language
Nouns are incompletely specifiec ## Footnote The user, controller, system, message
52
What is Universal Quantifier? | Causes of errors using Natural Language
Not all objects defined by universal quantifier should be treated the same way ## Footnote very, never, always, each time, in the evening, all, some, nothing
53
What is Imcompletely specified conditions? | Causes of errors using Natural Language
In a description of a conditions that is often missing | if...then, in case, whether
54
What does Representation Property maps?
Models map reality
55
What does Reduction Property maps?
Reduce the representation of the reality ## Footnote Simplify reality
56
What does Pragmatic Property maps?
Constructured for special purpose
57
List out 3 Conceptual Models for Functional Perspective
1. Use Case Diagram 2. Activity Diagram 3. Data Flow Diagram
58
List out 2 Conceptual Models for Data Perspective
1. Class Diagram 2. Entity Relationship Diagram
59
List out Conceptual Models for Behavioral Perspective
1. State Diagram
60
What does it mean `Use case B includes A`?
1. Use case B is incomplete with the included functionality 2. Use case A is complete
61
What does it mean `Use case B extends A`?
1. Use case B is complete without the extension 2. Use case A is usually incomplete without use case B (Contains only supplementary fragments)
62
What is the difference between Aggregation and Composition?
1. Aggregation part can exist with whole 2. Composition part can exist without whole
63
What is Cardinality in ERD?
Amount of relations an entity can participate in with other entities ## Footnote 1:1 , 1:N , M:N
64
What is Partition in Activitiy Diagram?
A group with common characteristics. Typically use to define responsibilities
65
What is the relation type for Assiciation?
"has-a" ## Footnote Customer have Product
66
What is the relation type for Generalization?
"is-a" ## Footnote Local Student is a student
67
List out 4 steps of creating Use Case Diagram
1. Recognizing and Defining System Boundary 2. Identify Actors 3. Identify Use Cases 4. Specifying Use Cases
68
What is the Goal of Validating the Content Aspect?
Avoid development based on false information
69
What does Content Aspect search for?
1. Completeness 2. Traceability 3. Correctness & Adequacy 4. Consistency 5. No premature design decision 6. Verifiability 7. Necessity
70
What is the Goal of Validating the Document Aspect?
Avoid information gaps or the violation of agreed documentation guidelines
71
What does the Document Aspect search for?
1. Conformity (Documentation format, structure, rules) 2. Understandability 3. Unambiguity
72
What is the Goal for Validation Agreement Aspect?
Avoid that some of the stakeholders disagree with documented requirements
73
What does Agreement Aspect search for?
1. Agreed (With stakeholder) 2. Agreed after changes 3. Conflict resolved
74
List out 6 principles of Requirements Validation
1. Involvement of the **correct stakeholders** 2. Separating the** identification** and the **correction** of errors 3. Validation from **different views** 4. Adequate **change of documentation type** 5. Construction of development artifacts 6.** Repeated Validation**
75
List out items in Static Techniques
1. Reviews 2. Matching Different Notations
76
What is the most formal and informal static review techniques
1. Inspection 2. Informal Review ## Footnote 1. Inspection 2. Walkthrough 3. Audit/Commenting 4. Informal Review
77
List out Goals and Values of Inspection (7)
1. Focused validation using checklist 2. Clear collection of roles in the team 3. Moderation 4. High error detection rate 5. Known and accepted rules of the game 6. Appraisal, no problem resolution 7. Boosts team spirit
78
List out 6 roles in Inspection
1. Organiser (Plan and supervise inspection) 2. Moderator (Enforce rules and moderate meeting) 3. Inspector (Finding errors) 4. Reader (Present validated requirements) 5. Scribe (Minute taker) 6. Author (Provide requested information)
79
List out 2 benefits of using Checklist?
1. Guideline 2. Adequate Coverage
80
What is the Structure of the checklist? (2)
1. Grouped after the aspects 2. Evert reviewer checks different mix of aspects
81
What is Advantages and Disadvantages of Prototyping?
Advantages 1. Concrete **feedback** from usage and experience 2. Scalable (Wireframe, Throw-away, Evolutionary) 3. Improved expectation management Disadvantages 1. Create prototype can be **big effort**
82
List out 3 possible perspective from roles and quality criteria
Roles 1. User/Client 2. Software Architect 3. Tester Quality Criteria 1. Content 2. Documentation 3. Agreement
83
Who presents step-by-step the check item in Walkthrough?
Author
84
Where is 'Plus-Minus-Interesting(PMI)' used?
Conflict Resolution (Requirment Negotiation)
85
List out 4 tasks of Conflict Management
1. Conflict Identification 2. Conflict Analysis 3. Conflict Resolution 4. Documentation of the Conflict Resolution
86
What is Data Conflict?
Stakeholders given information differently or have information deficits
87
What is Interest Conflict?
Stakeholders have different needs or divergent personal interests
88
What is Value Conflict?
Stakeholders have divergent values and perferences
89
What is Relationship Conflict?
There are emotional problems in personal relationship between stakeholders
90
What is Structure conflict?
Conflict roots in stakeholders being on different hierarchy and decision power levels
91
How to resolve conflict using Agreement?
Negotiate the solution
92
How to resolve conflict using Compromise?
Found through combinations or alternative solutions
93
How to resolve conflict using Voting?
Each stakeholder gets to vote
93
How to resolve conflict using Definition or Variants?
Solve conflict through system variants or parameters
94
How to resolve conflict using Overruling?
Decision make by hierarchy
95
How to resolve conflict using Consider-all-Facts?
All influencing factors are considered
96
How to resolve conflict using Plus-Minus-Interesting?
All positive and negative effects are evaluated
97
How to resolve conflict using Decision Matrix?
Often named as benefit value analysis
98
What is the Purpose of Attributing the Requirements?
1. Structuring 2. Ensuring Consistency 3. Identification 4. Progress and State Control
99
List out 7 Attributes Scheme
1. Identifier 2. Name 3. Description 4. Source 5. Stability 6. Risk 7. Priority
100
Why Selective View is Different from Condensed View?
Selective View is just filtering out some values, while Condensed View create a chart that summarizes all the data
101
List out criteria for Prioritization
1. Cost of the Implementation 2. Risk of the Implementation 3. Benefit 4. Loss in Case of Incorrect or Missing Implementation 5. Volatility / Stability of Requirements 6. Importance 7. Time to Implement the Requirements
102
Where is Kano Classification being used in?
Project with great innovation, for relase planning
103
Where is Single Criterion Classification primarily used in?
Procurement projects, for evaluation
104
List out 4 techniques for Prioritization
1. Single Criterion Classification 2. Kano Classification 3. Ranking 4. Top-Ten Technique (Has n points - n = half of the evaluated objects)
105
What is the primary purpose of 'Pre-RS-Traceability'?
Demonstrate the reaching of goals and needs ## Footnote Trace toward origin
106
What is the primary purpose of 'Post-RS-Traceability'?
Evaluate result of changes ## Footnote Trace toward Solution
107
What is the primary purpose of 'Traceability between Requirements'?
Mange dependencies between requirements (Refinement, Generalization, Replacement)
108
List out 4 ways to represent requirements traceability
1. Text Based References () 2. Hyperlinks 3. Trace Matrices 4. Trace Graphs
109
Which becomes unmanageable with increasing number of items?
Traceability Matrix
Requirements Engineering
flashcards
Decks in class (9)
# Cards
Brainscape helps you reach your goals faster, through stronger study habits.
© 2026 Bold Learning Solutions. Terms and Conditions