Lecture 2 - Introduction

Question 1

What is Software Crisis

Answer 1

A period in the history of software development when the industry faced significant challenges and difficulties in creating and maintaining software systems.

Question 2

What is Software Development

Answer 2

A systematic process that outlines the phases a software project goes through from its initiation to its completion and maintenance.

Question 3

Core Tasks of software development?

Answer 3

Analysis → Design → Construction → Test → Deliver

Question 4

What is reference architecture?

Answer 4

• a set of key decisions applied across multiple related systems in the same domain (e.g., healthcare, banking).
• standard framework for consistency, efficiency, and reliability.
• Includes points of variation, allowing for customization to meet specific system requirements

Question 5

What are design decisions?

Answer 5

• choices made during the creation or planning phase of a system

Question 6

Principal vs Temporal Design Decisions?

Answer 6

• Principal: critical choices that affects overall architecture / behavior
• Temporal: These involve time-based choices that can change or evolve over the system’s lifespan.

Question 7

What are stakeholders?

Answer 7

• individuals/groups interested in OR impacted by the development and deployment of a system architecture

Question 8

What is Requirements Engineering?

Answer 8

• process of gathering, documenting, analyzing, prioritizing, validating, and managing requirements
• Goal: ensure the project meets stakeholder needs while minimizing risks

Question 9

What are software requirements?

Answer 9

• specifications that define what a software system should accomplish and how it behaves

Question 10

2 types of Basic requirements?

Answer 10

• Functional: describe specific tasks the system must PERFORM
• Non-Functional: describe behaviors/CHARACTERISTICS (usability, security, availability)

Question 11

User Stories vs Use Cases?

Answer 11

• User Stories: short and simple descriptions of a feature from POV of customer (informal)
• Use Cases: identify, clarify, and organize requirements (has steps)

Question 12

Requirements Prioritization

Answer 12

MO → S → CO → W
Must → should → could → would