inf 113: exam 1

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/25

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

26 Terms

1
New cards

What are the stages of team formation?

Forming, Storming, Norming, Performing

2
New cards

What is the hardest part of SE?

The hardest part of software engineering is building the right thing

3
New cards

What is the contemporary definition of RE?

• systematic and disciplined approach to the specification and management of requirements
•  goal is understanding the stakeholders’ desires and needs

• minimizing the risk of delivering system that doesn’t meet desires and needs

4
New cards

What are the four major tasks of RE?

• Eliciting the requirements

• Analyzing and documenting the requirements

• Validating the requirements

• Managing and evolving the requirements

5
New cards

How would you describe the relationship between effort and risk in RE?

Inversely proportionate; the more effort, the lower the risk

6
New cards

What are the four types of requirements?

• Functional requirements

• Quality requirements

• Constraints

• Project/process requirements

7
New cards

What’s the definition of a functional requirement?

Requirement concerning a result of behavior that shall be provided by a system

8
New cards

What’s the definition of quality requirement?

Requirement related to quality concerns, specifics criteria not behavior

9
New cards

What’s the definition of a constraint?

limits solution beyond just fulfilling functional and quality requirements

10
New cards

What’s the definition of project/process requirement?

states how system must be developed, usually delivery schedule or development cost

11
New cards

What is the purpose of goal analysis?

• check alignment of project artifacts

• framework for requirements

• aligns of system-to-be with strategic objectives

• support for evolution, negotiation, risk management

12
New cards

What is the definition of context?

the part of system’s environment that is relevant for understanding the system and requirements

13
New cards

What does a context diagram identify?

• external entities that interface to the system

• flows between external entities and system

14
New cards

What is represented as a circle in the center of a context diagram?

System

15
New cards

What is represented as rectangles in a context diagram?

External entities

16
New cards

What is the definition of a stakeholder?

person or organization who influences a system’s requirements and/or is impacted by the system

17
New cards

What are the three approaches of identifying stakeholders?

• reference list
• business/operational context
• goals

18
New cards

What are the eight items to identify when making a stakeholder model?

• Motivation
• Authority
• Relation to other stakeholders
• Level of expertise
• Their expectations
• Your expectations of them
• Location/availability
• Priority (critical, major, minor)

19
New cards

What are the four types of stakeholder models?

• Textual
• Informal diagram
• Onion model
• Rich picture

20
New cards

What is the onion stakeholder model?

4-5 layers
• product/solution
• system
• containing system
• wider environment
• outer layer for stakeholders outside the layers

21
New cards

How would you describe the rich picture model?

Showcases the relationships between stakeholders and primary concerns of the stakeholders are shown as thought bubble

22
New cards

What is elicitation?

• activities to discover requirements of system
• determines stakeholders’ desires and needs

23
New cards

What are the main elicitation information sources?

• stakeholders
• documents
• existing systems

24
New cards

What are effective elicitation practices (ask)?

• interview stakeholders
• use questionnaires and polls
• follow up to user feedback

25
New cards

What are some other examples of effective elicitation practices?

• observe stakeholders in their work context
• analyze user feedback
• conduct market studies

26
New cards

What are signs of being “done”?

• stakeholders can’t think of anymore scenarios
• they repeat themselves
• suggested new features are all out of scope/low priority
• no gaps between checklist of common functional areas and current requirements