Software Engineering 101

Lecture 5.1

Javed Anjum Sheikh, PhD

Software Engineering: A Practitioner’s Approach, 7/e Slides copyright © 1996, 2001, 2005, 2009 by Roger S. Pressman & Software Engineering 9/e By Ian Sommerville
Functional Requirements:
Definition: Describe what the system should do to meet user needs.

Examples and Scenarios:

1. User Authentication:
• Scenario: Users to register and log in securely

• Functional Requirement: Authentication options, for enhanced security.

2. Product Search:
• Scenario: To search for products based on various criteria.

• Functional Requirement: Users should be able to filter search results

3. Checkout Process:
• Scenario: Checkout process, allowing customers to select items

• Functional Requirement: Users should be able to review their orders.

Significance: Ensuring that it meets user needs and performs as intended.

Non-Functional Requirements:
Definition: Specify system attributes like performance and usability.

Examples and Scenarios:

1. Performance:
• Scenario: Support a large number of concurrent users.

• Non-Functional Requirement: Gameplay even under heavy user load.

2. Usability:
• Scenario: User interface with clear navigation

• Non-Functional Requirement: Responsive layout for different screen sizes.

3. Security:
• Scenario: Multi-factor authentication to protect user data from cyber threats.

• Non-Functional Requirement: Encryption algorithms to secure data

Significance: The system meets user expectations.

Domain Requirements:
Definition: Provide context-specific constraints or regulations.

Examples and Scenarios:

1. Regulatory Compliance:
• Scenario: The software must comply with regulations to ensure privacy

Domain Requirement: Robust security measures of patient data

2. Interoperability:
• Scenario: Integrate with various payment gateways

• Domain Requirement: To enable secure and efficient fund transfers.

3. Cultural Considerations:
• Scenario: Must support multiple languages and cultural preferences.

• Domain Requirement: Localization features, and cultural preferences.

Significance: The system meets user expectations within its application domain.