SE Lecture Week3
SE Lecture Week3
Engineering
Evaluation Plan with tentative deadline
Evaluation component Date of evaluation
Quiz -1 01-02-2024
Quiz -2 19-03-2024
Quiz -3 16-04-2024
Project problem statement submission 03-02-2024
Project mid term evaluation 11, 13, 18, 20 (March)
Project end term evaluation 15, 17, 22, 24 (April)
https://www.javatpoint.com/software-engineering-requirement-engineering
Requirement
Elicitation and
Analysis Process
Functional requirements
• Services the system should provide
• What the system should do or not in reaction to particular situations
Non-functional requirements
• Constraints on the services or functions offered by the system
• Examples: Timing constraints, constraints on the development process (CASE, language, development
method…), standards etc
Domain requirements
• From the application domain of the system
• May be functional or non-functional
• Examples: Medicine, library, physics, chemistry
Functional Requirements
• Requirements that the end user specifically demands as basic facilities that
the system should offer.
• All these functionalities need to be necessarily incorporated into the system
as a part of the contract.
• Outputs for the given inputs and their relations must specify behavior of
invalid inputs too.
Example:
• What are the features that we need to design for this system?
• What are the edge cases we need to consider, if any, in our design?
Defines system properties (reliability, response time and storage)
and constraints (I/O device capability, system representations, etc.)
Categorized into:
• Product requirements
• Product behavior
Non- • E.g.: Timing, performance, memory, reliability, portability, usability
• Interviews
• Brainstorming Sessions
• Facilitated Application Specific
Techniques
• Quality Function Deployment
• The Use case Approach
Template for
writing use
cases
Template for
writing use
cases
Use case
diagram
Result
Management
System
RE.2: Requirement
Analysis
• Develop a context diagram
• Development of a prototype
• Model the requirements
• Finalise the requirements
RE.2:
Requirement
Analysis
RE2.1: Data Flow Diagram
RE2.2: Data Flow Diagram
RE2.3: ER
Diagram
RE2.4: Data dictionary
Function
Decomposition
Diagram (FDD)
RE.3: Requirements
Documentation
• The process of writing down the user and system
requirements in a requirements document.
• User requirements must be understandable by
end-users and customers who do not have a
technical background.
• System requirements are more detailed
requirements and may include more technical
information.
• The requirements may be part of a contract for
the system development
• It is therefore important that these are as
complete as possible.
RE.3: Requirements Documentation