system integration

Requirements Elicitation

Process of gathering and defining software requirements.

Stakeholders

→ People involved in or affected by the system.

Requirements Documentation

→ Records software requirements clearly.

Software Documentation

→ Written information about software.

Software Maintenance

→ Modifying software after delivery.

SRS (Software Requirements Specification)

→ Document containing software requirements.

FAST (Facilitated Application Specification Technique)

→ Team-oriented requirements gathering technique.

QFD (Quality Function Deployment)

→ Technique focused on customer satisfaction.

Use Case

→ Describes what the system does from the user's perspective.

Actor

→ External entity interacting with the system.

Use Case Diagram

→ Graphical representation of actors and use cases.

Corrective Maintenance

→ Fixes software bugs.

Adaptive Maintenance

→ Adjusts software to environmental changes.

Perfective Maintenance

→ Improves performance and functionality.

Preventive Maintenance

→ Prevents future software problems.

Patching

→ Emergency bug fix.

7 Requirements Elicitation Methods

① Interviews ② Brainstorming Sessions ③ FAST ④ Quality Function Deployment (QFD) ⑤ Use Case Approach ⑥ User Observation ⑦ Surveys

Interview Types

① Open-ended Interview ② Structured Interview

Three Types of QFD Requirements

① Normal Requirements ② Expected Requirements ③ Exciting Requirements

Components of Use Case Design

① Actor ② Use Case ③ Use Case Diagram

Steps of Requirements Elicitation

① Identify stakeholders ② List customer requirements ③ Prioritize requirements ④ Categorize final requirements

Features of Requirements Elicitation

① Stakeholder engagement ② Gathering information ③ Requirement prioritization ④ Requirements documentation ⑤ Validation and verification ⑥ Iterative process ⑦ Communication and collaboration ⑧ Flexibility

Advantages of Requirements Elicitation

✔ Clear requirements ✔ Improves communication ✔ Good quality software ✔ Avoids misunderstandings ✔ Identifies risks ✔ Accurate project planning ✔ Increases user confidence ✔ Identifies business opportunities

Disadvantages of Requirements Elicitation

✖ Time-consuming ✖ Requires skilled people ✖ Changing requirements ✖ Organizational factors ✖ Lack of stakeholder commitment ✖ Conflicting priorities ✖ Inaccurate requirements ✖ Increased development cost

Types of Software Documentation

① Requirement Documentation ② Architectural Documentation

Principles of Software Documentation

① Write from reader's point of view ② Avoid unnecessary repetition ③ Avoid ambiguity ④ Follow standard organization ⑤ Record rationale ⑥ Keep documentation updated ⑦ Review documentation

Key Aspects of Software Maintenance

① Bug fixing ② Enhancements ③ Performance optimization ④ Porting and migration ⑤ Re-engineering ⑥ Documentation

Types of Software Maintenance

① Corrective ② Patching ③ Adaptive ④ Perfective ⑤ Preventive

Requirements Modeling

→ Process of documenting analyzing and managing requirements.

Requirements Traceability Matrix (RTM)

→ Table showing relationships between requirements.

Use Case

→ Describes user interaction to achieve a goal.

User Story

→ Feature description from the user's perspective.

Process Flow Diagram

→ Shows process flow.

State Diagram

→ Shows different states of an object.

Sequence Diagram

→ Shows interaction between objects over time.

UML (Unified Modeling Language)

→ Standard graphical language for software modeling.

Three Main Activities of Requirements Modeling

① Analysis ② Documentation ③ Management

Benefits of Requirements Modeling

① Easy simulations ② Automatic document generation ③ Automatic testing ④ Tool integration ⑤ Easier requirement changes

Requirements Modeling Techniques

① Requirements Traceability Matrix ② Use Cases ③ User Stories ④ Process Flow Diagram ⑤ State Diagram ⑥ Sequence Diagram

Five Requirements Modeling Elements

① Scenario-Based ② Class-Based ③ Behavioral ④ Flow-Oriented ⑤ Pattern-Based

Benefits of UML

✔ Improves communication ✔ Visualizes systems ✔ Reduces ambiguity ✔ Finds design issues early ✔ Serves as documentation ✔ Easier to understand

Structural Diagrams

① Class Diagram ② Object Diagram ③ Package Diagram ④ Component Diagram ⑤ Deployment Diagram

Behavioral Diagrams

① Use Case Diagram ② Activity Diagram ③ Sequence Diagram ④ State Diagram ⑤ Communication Diagram ⑥ Timing Diagram

The process of gathering software requirements is called

Requirements Elicitation

The document that contains software requirements is called

Software Requirements Specification (SRS)

A Use Case describes how a user interacts with a

System

The external entity interacting with a system is called

Actor

FAST stands for

Facilitated Application Specification Technique

QFD stands for

Quality Function Deployment

Corrective Maintenance fixes

Software bugs

Adaptive Maintenance modifies software to adapt to

Environmental changes

Perfective Maintenance improves

Software performance and functionality

Preventive Maintenance helps prevent

Future software problems

RTM stands for

Requirements Traceability Matrix

UML means

Unified Modeling Language

The five requirements modeling elements include

Scenario-Based • Class-Based • Behavioral • Flow-Oriented • Pattern-Based

The symbol used for a decision in a flowchart is a

Diamond

The symbol used for a process is a

Rectangle

The symbol used for start/end is an

Oval

The symbol representing input/output is a

Parallelogram

Requirements Modeling consists of

Analysis • Documentation • Management

Software Maintenance is performed

After the software is delivered

Software Documentation helps improve

The quality of software