Lecture 5

Question 1

Requirements

Answer 1

Needs of stakeholders that’ll be solved by software
- a condition or capability needed by a user to solve a problem/achieve an objective that must be met by a system or system component to satisfy a contract, standard, specification, or other formally imposed document

Question 2

[Requirements] Engineering

Waterfall vs Agile?

Answer 2

The process of defining, documenting, and maintaining requirements.

• Waterfall: 1st phase of SDLC
• Agile: Continues indefinitely throughout a system’s lifetime

Question 3

[Requirements] Types

Answer 3

• Architectural
• Business
• User(stakeholder)
• Functional
• Non-functional

Question 4

[Req Type] Architectural

Answer 4

Necessary systems structure and systems behavior.

Question 5

[Req Type] Business

Answer 5

High-level statements of goals, objectives, or needs of an organization.
Opportunities the organization wants to realize, or problems the they want to solve.

Question 6

[Req Type] User

Answer 6

Mid-level statements of needs of a (group of) stakeholder(s). Describe how someone wants to interact with the intended solution.

Question 7

[Req Type] Functional

Answer 7

Capabilities, behavior, and information the solution will need.
“What the system does”

Question 8

[Req Type] Non-Functional

Answer 8

The conditions under which the solution must remain effective, qualities the solution will have, or constraints under which the solution must operate. “ilities”.
“How well the system does it”

Question 9

[Requirements] Software Requirements Specification

Answer 9

Description of a software system to be developed.

• Establishes the basis for an agreement between customers and suppliers on what the software product is to do, and what it is not to do
• Permits a rigorous assessment of requirements before design can begin
• Should provide a realistic basis for estimating product costs, risks, and schedules

Question 10

[Requirments] Characteristics

Answer 10

• Unitary
• Complete
• Consistent
• Atomic
• Traceable
• Current
• Unambiguous
• Verifiable

Question 11

[Requirements] Tracability

Answer 11

• Forwards Traceability: Mapping requirements to test cases. VALIDATION.
• Backwards Traceability: Mapping test cases to requirements. VERIFICATION.

Question 12

[Requirements] Metrics

Answer 12

• Coverage: % of requests that are covered by tests
• Volatility:
  -a gauge of change of requests during SDLC (target
  under 10%)
  -[((# Reqs Added + Deleted + Modified) * 100) / (#
  Original Requirements)]