Contents

THE SOFTWARE REQUIREMENTS DOCUMENT I? What is including?...........................................................2

The Software Requirements Document (SRD):........................................................................................2
What are REQUIREMENTS SPECIFICATION?................................................................................................2
Requirements Specification:....................................................................................................................2
PROBLEMS WITH NATURAL LANGUAGE?....................................................................................................2
Problems with Natural Language in Requirements Specification:...........................................................2
A STRUCTURED SPECIFICATION OF A REQUIREMENT FOR AN INSULIN PUMP?..........................................2
A Structured Specification for an Insulin Pump Requirement:................................................................2
There are a number of generic activities common to all processes?...........................................................3
Generic Activities Common to All Processes:...........................................................................................3
REQUIREMENTS ELICITATION AND ANALYSIS?............................................................................................3
Requirements Elicitation and Analysis:....................................................................................................3
PROBLEMS OF REQUIREMENTS Analysis?...................................................................................................3
Problems of Requirements Analysis:.......................................................................................................3
REQUIREMENTS ELICITATION AND ANALYSIS Stages includes?...............................................................3
Requirements Elicitation and Analysis Stages:........................................................................................3
“Definitions and drawing”...........................................................................................................................4
System Modeling Definitions and Drawings............................................................................................4
UML DIAGRAM TYPES?................................................................................................................................4
UML Diagram Types.................................................................................................................................4
INTERACTION MODELS?..............................................................................................................................4
Interaction Models..................................................................................................................................4
USE CASE MODELING?.................................................................................................................................5
Use Case Modeling..................................................................................................................................5
SEQUENCE DIAGRAMS?...............................................................................................................................5
Sequence Diagrams.................................................................................................................................5
Chapter 4
REQUIREMENTS ENGINEERING
THE SOFTWARE REQUIREMENTS DOCUMENT I? What is
including?
The Software Requirements Document (SRD):

The SRD outlines the system’s functionalities and constraints in a detailed and structured way. It
includes:

1. Introduction: Purpose, scope, and definitions.

2. System Overview: General description of the system.
3. Functional Requirements: Features and services the system will provide.
4. Non-Functional Requirements: Performance, security, and usability constraints.
5. System Models: Data flow, use cases, and state diagrams.
6. Appendices: Glossary, references, and supporting information.
7. Index: A quick reference guide for document navigation.

What are REQUIREMENTS SPECIFICATION?

Requirements Specification:

 A detailed, structured description of the system’s functionality and constraints.

 Focuses on ensuring clarity, completeness, and consistency.
 Can use natural language, diagrams, or formal models.

PROBLEMS WITH NATURAL LANGUAGE?

Problems with Natural Language in Requirements Specification:

1. Ambiguity: Different readers may interpret the same requirement differently.

2. Over-flexibility: Statements might allow for too many interpretations.
3. Lack of Clarity: Informal expressions can lead to confusion.
4. Redundancy: Repeated information can cause inconsistencies.

A STRUCTURED SPECIFICATION OF A REQUIREMENT FOR

AN INSULIN PUMP?
A Structured Specification for an Insulin Pump Requirement:

 Requirement: The system shall monitor the user’s blood glucose level every 5 minutes and
deliver an appropriate dose of insulin when required.
 Constraints:
 o Blood glucose levels should remain between 80–120 mg/dL.
o The system must issue alerts if glucose is outside the range for more than 15 minutes.
o Insulin dose adjustment must occur within 1 second of detection.

There are a number of generic activities common to all processes?

Generic Activities Common to All Processes:

1. Specification: Define system requirements and constraints.

2. Design and Implementation: Develop system architecture and translate it into code.
3. Validation: Ensure the system meets user requirements.
4. Evolution: Adapt the system to meet evolving needs.

REQUIREMENTS ELICITATION AND ANALYSIS?

Requirements Elicitation and Analysis:

A process to discover, refine, and validate system requirements. It involves:

1. Stakeholder Identification: Determining who will provide and use the requirements.
2. Information Gathering: Using interviews, questionnaires, and observations.
3. Analysis: Understanding and prioritizing needs.
4. Validation: Ensuring requirements are correct and feasible.

PROBLEMS OF REQUIREMENTS Analysis?

Problems of Requirements Analysis:

1. Conflicting Requirements: Stakeholders may have differing needs.

2. Incomplete Requirements: Some requirements may be overlooked or vague.
3. Changing Requirements: Requirements evolve during the project.
4. Technical Constraints: Some requirements may not be feasible.

REQUIREMENTS ELICITATION AND ANALYSIS Stages includes?

Requirements Elicitation and Analysis Stages:

1. Discovery: Gather initial information from stakeholders.

2. Classification and Organization: Group and structure requirements logically.
3. Prioritization and Negotiation: Resolve conflicts and rank requirements by importance.
4. Documentation: Clearly and concisely record the agreed-upon requirements.
CHAPTER 5 – SYSTEM MODELING
“Definitions and drawing”
System Modeling Definitions and Drawings

System Modelling:

 A process of creating abstract representations of a system to better understand, analyze, and

communicate its functionality and structure.

UML DIAGRAM TYPES?

UML Diagram Types

1. Structural Diagrams:
o Class Diagram: Represents the static structure of a system (classes, attributes,
relationships).
o Component Diagram: Shows system components and their interconnections.
o Deployment Diagram: Illustrates the physical deployment of software on hardware.
o Object Diagram: Snapshot of objects and their relationships at a point in time.
o Package Diagram: Organizes system elements into groups.

2. Behavioral Diagrams:
o Use Case Diagram: Represents interactions between actors and the system.
o Activity Diagram: Models workflows and processes.
o State Diagram: Shows state transitions of an object.

3. Interaction Diagrams:
o Sequence Diagram: Visualizes object interactions in a sequence.
o Communication Diagram: Focuses on message exchanges between objects.

INTERACTION MODELS?
Interaction Models

 Represent how system components or users interact with each other.

 Includes:
1. Use Case Diagrams: Describe functional requirements and actor interactions.
2. Sequence Diagrams: Show the sequence of messages between objects.
3. State Diagrams: Depict system behavior based on events.
USE CASE MODELING?
Use Case Modeling

Definition:

 Identifies system functionalities by capturing interactions between external actors and the system.

Components of a Use Case Diagram:

1. Actors: Entities interacting with the system (users or other systems).

2. Use Cases: Functionalities or services provided by the system.
3. Relationships: Associations between actors and use cases.

Example:
A Library Management System use case may include actors like Librarian and Member with
use cases like Borrow Book and Return Book.

SEQUENCE DIAGRAMS?
Sequence Diagrams

Definition:

 A UML interaction diagram that shows how objects communicate with each other in a time-
ordered sequence.

Key Elements:

1. Actors and Objects: Represent participants in the interaction.

2. Lifelines: Dashed lines extending from objects to represent their lifespan.
3. Messages: Arrows indicating communication between objects.

Example:
For an Online Shopping System:

1. User sends a Search Request to the System.

2. System responds with Search Results.
3. User places an Order, and the System confirms.

Sequence diagrams are essential for visualizing workflows, understanding system interactions,
and identifying dependencies.