Scribd
Upload
57 views15 pages

Comprehensive Guide to Requirements Engineering

Requirements engineering is the process of identifying stakeholders, eliciting requirements, analyzing and specifying requirements, and managing requirements throughout the development lifecycle. Key activities include stakeholder and user profiling, use case modeling, prototyping, requirements documentation in a software requirements specification, verification that requirements are met, and configuration management of requirements as the project evolves. The goal is to fully define the desired functionality and constraints of the system to be developed.

Uploaded by

TayYab ALi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Topics covered

  • Data Flow Diagrams,
  • Functional Requirements,
  • Stakeholder Identification,
  • Derived Requirements,
  • State-oriented View,
  • Non-functional Requirements,
  • Requirements Management,
  • Use Cases,
  • Communications Standards,
  • Regulatory Standards
57 views15 pages

Comprehensive Guide to Requirements Engineering

Requirements engineering is the process of identifying stakeholders, eliciting requirements, analyzing and specifying requirements, and managing requirements throughout the development lifecycle. Key activities include stakeholder and user profiling, use case modeling, prototyping, requirements documentation in a software requirements specification, verification that requirements are met, and configuration management of requirements as the project evolves. The goal is to fully define the desired functionality and constraints of the system to be developed.

Uploaded by

TayYab ALi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Topics covered

  • Data Flow Diagrams,
  • Functional Requirements,
  • Stakeholder Identification,
  • Derived Requirements,
  • State-oriented View,
  • Non-functional Requirements,
  • Requirements Management,
  • Use Cases,
  • Communications Standards,
  • Regulatory Standards

REQUIREMENTS ENGINEERING

Requirements Engineering

Requirements Elicitation

Requirements Analysis Requirements Verification

Requirements Specification Requirements Management

Requirements Engineering
Requirement engineering is the process or a set of task that consists of Stakeholder identification, Stakeholder interviews, Contract-style requirement lists, Measurable goals, Prototypes, Use cases.

Eliciting Requirements
Analysts can employ several techniques to elicit the requirements from the customer.
interviews, focus groups (requirements workshops) and creating requirements lists. prototyping, and use cases. combination of these methods

Requirements Analysis
Requirement Analysis contains 5 things which are: Defining Stakeholder profiles Defining User Profiles Defining User Work Environment Product Overview Other Product Requirements

Defining Stakeholder profiles


It defines the brief description of the stakeholder type. Type Qualifies stakeholders expertise, technical background, degree of sophistication, success criteria, Involvement & Responsibilities in the development of system as well as Deliverables(required by the stakeholder)

Defining User Profiles


It defines the brief description of the user type. Type Qualifies user expertise, technical background, degree of sophistication, success criteria, Involvement & Responsibilities in the development of system as well as Deliverables (Are there any deliverables the user produces? For whom?)

Defining User Work Environment


The work environment defines
The number of people involved in development of system? How long is a task cycle now? Which system platforms are in use today? What other applications are in use? Which can be integrated with system?

Product Overview
Product overview contains, Component of a larger system? How do the subsystems interact with this? Block diagram

Other Product Requirements Other product requirements include hardware platform requirements, system requirements, supported host (operating systems), peripherals. Environmental requirements such as temperature, shock, humidity, radiation, usage conditions, resource availability, maintenance issues, type of error recovery applicable standards -- legal, regulatory, communications

Software Requirement Specification


A software requirements specification (SRS) is a complete description of the behavior of the system to be developed. A document that clearly and precisely describes, each of the essential requirements of the software and the external interfaces.
(functions, performance, design constraint, and quality attributes)

Fundamental Techniques (Views) of making SRS contains functional view hierarchy - function tree process use cases information flow data flow diagram (DFD) data oriented view data structures data dictionary (DD), syntax diagram, Jackson diagram relations between entities entity relationship diagram (ER) object-oriented view class structure class diagram

algorithmic view control structures pseudo code, structogram, flow diagram, Jackson diagram conditions rules, decision table state-oriented view state machines Petri nets sequence charts

SRS document includes,


Customer Requirements Functional Requirements Non-functional Requirements Performance Requirements Design Requirements Derived Requirements Allocated Requirements

REQUIREMENTS VERIFICATION
To identify and resolve software problems and high risk issues early in the software cycle. The assurance that the software requirement specification is in compliance with the system requirements, conforms to document standards, and is an adequate basis for the architectural design.

REQUIREMENTS MANAGEMENT
Basic responsibility is to keep project within costs, within budget, and to meet customers needs. Estimate cost of system based on requirements. Control the volatility of the requirements. Manage the requirements configuration of the system Negotiate requirement changes Re-estimate cost of the system when requirements change.

You might also like