Requirement Engineering in Software Engineering Presentation, Slides of Software Engineering

Download Requirement Engineering in Software Engineering Presentation and more Slides Software Engineering in PDF only on Docsity!

REQUIREMENTS

ENGINEERING

TOPIC:

GROUP MEMBERS

TALHA QAYYUM (CS-192)

HUSSAIN AFZAL (CS-87)

Steps in Requirements Engineering Process

Requirements Elicitation

Requirements Analysis

Requirements Specification

Requirements Validation

Requirements Management

Requirement Engineering

Requirements Elicitation

Definition : Gathering stakeholders' needs and expectations. Techniques : Interviews, surveys, focus groups. Importance : Foundation for understanding project goals. Example: In developing a new mobile banking app , the project team conducts interviews and surveys with bank customers to understand their preferences for features, such as account balance checking, fund transfers, and bill payments.

Requirements Specification:

Definition : Documenting requirements clearly and

unambiguously.

Importance : Provides a roadmap for software development.

Example: The team documents the identified features in a requirements specification document, detailing each feature's functionality, priority, and any technical constraints. For instance, the biometric authentication feature must support both fingerprint and facial recognition.

Requirements Validation:

Definition : Checking completeness, consistency, and accuracy of requirements. Importance : Ensures requirements meet stakeholder needs and are testable. Example: The team conducts reviews and walkthroughs of the requirements document with stakeholders to ensure completeness, consistency, and accurac y. They verify that the specified features align with customers' needs and expectations.

Requirement Engineering

Definition : Defining, documenting, and maintaining requirements. Importance : Critical step in ensuring developed software meets stakeholder needs, within budget, and to the required quality. Characteristics : Discipline, application of principles, methods, tools, and notations. Example: The team uses standardized notations like UML (Unified Modeling Language) to diagram the system's intended behavior, such as use case diagrams illustrating how users interact with the mobile banking app's features.

1.Observation report

2. Questionnaire ( survey , poll )

3. Use cases

4. User stories

5. Requirement workshop

6. Mind mapping

7. Role playing

8. Prototyping

Tools Involved in Requirement Engineering

TECHNIQUES USED TO ELICIT REQUIREMENTS

- Interviews: These are one-on-one conversations with stakeholders to gather information about their needs and expectations. - Surveys: These are questionnaires that are distributed to stakeholders to gather information about their needs and expectations. •Focus Groups: These are small groups of stakeholders who are brought together to discuss their needs and expectations for the software system.

• Prototyping : This technique involves creating a working model of the software system, which can be used to gather feedback from stakeholders and to validate requirements.

TYPES OF REQUIREMENTS SPECIFIED IN REQUIREMENT SPECIFICATION Functional Requiremaents: These describe what the software system should do. They specify the functionality that the system must provide, such as input validation, data storage, and user interface. Non-Functional Requirements: These describe how well the software system should do it. They specify the quality attributes of the system, such as performance, reliability, usability, and security. Constraints: These describeany limitations or restrictions that must be considered when developing the software system. Acceptance Criteria: These describe the conditions that must be met for the software system to be considered complete and ready for release.

INCEPTION (BETTER UNDERSTANDING) ELICITATION (CLEAR UNDERSTANDING OF REQUIREMENTS) ELABORATION (REFINEMENT & MODELLING) NEGOTIATION (SETTLEMENT & CONFLICTS) SPECIFICATION (SRS DOCUMENT) VALIDATION (VALIDATES REQUIREMENT) MANAGEMENT (MANAGE CHANGING REQUIREMENT) TASKS OF REQUIREMENTS ENGINEERING

PROCESS OF REQUIREMENTS ENGINEERING FEASIBILITY STUDY REQUIREMENT ELICITATION & ANALYSIS REQUIREMENT SPECIFICATION REQUIREMENT VALIDATION REQUIREMENT MANAGEMENT PROCESSES OF REQUIREMENT ENGINEERING

SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

ANY QUESTIONS?