Scribd
Upload
23 views

SWE Unit II

The document discusses software requirements including functional and non-functional requirements, user requirements vs system requirements, interface specifications, and the software requirements document. It also covers the requirement engineering process including feasibility studies, elicitation and analysis, validation, management, system models like context and behavioral models, and data/object models.

Uploaded by

RAJ KUMAR
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
23 views

SWE Unit II

The document discusses software requirements including functional and non-functional requirements, user requirements vs system requirements, interface specifications, and the software requirements document. It also covers the requirement engineering process including feasibility studies, elicitation and analysis, validation, management, system models like context and behavioral models, and data/object models.

Uploaded by

RAJ KUMAR
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

UNIT-II

SOFTWARE
REQUIREMENTS
Software Requirements

• The software requirements are description of features


and functionalities of the target system.
• Requirements convey the expectations of users from
the software product.
• The requirements can be obvious or hidden, known or
unknown, expected or unexpected from client's point
of view.
Functional and Nonfunctional requirements

• Functional requirements are those which are


related to the technical functionality of the
system.

• Non-Functional requirements specifies


criteria that can be used to judge the operation
of a system in particular conditions, rather than
specific behaviors.
Fig 1 :Functional and Non-Functional requirements
User Requirements and System Requirements

• User requirements: User requirements or user


requirement specification (URS) is a document
usually used in software engineering that specifies
what the user expects the software to be able to do.
• System Requirements: System Requirements are all
of the requirements at the system level that
describe the functions which the system as a
whole should fulfill to satisfy the stake holder
needs and requirements
Interface Specifications

• A User Interface Specification (UI specification) is a


document that captures the details of
the software user interface into a written document.
The specification covers all possible actions that an
end user may perform and all visual, auditory and
other interaction elements.
The Software Requirements Document

• This Document is taken as a benchmark from various


people in the project team like developers, testers,
Business Analysts, etc. to understand the functional
requirements of the application.
• It is also called an SRS document, which stands
for System Requirement Specification Document.
Requirement Engineering Process

• Software specification or requirements engineeringis


the process of understanding and defining what
services are required and identifying the constraints
on these services.
• Requirements engineering processes ensures
your software will meet the user expectations, and
ending up with a high quality software.
Feasibility Studies

• The requirements engineering process should start


with a feasibility study. The input to
the feasibility study is a set of preliminary business
requirements, an outline description of the system and
how the system is intended to support
business processes.
Requirement Elicitation and Analysis

• Requirements elicitation practices include interviews,


questionnaires, user observation, workshops,
brainstorming, use cases, role playing and
prototyping.
• Requirements elicitation is a part of the requirements
engineering process, usually followed by analysis and
specification of the requirements.
Requirements validation

• Validation is the process of confirming the


completeness and correctness of requirements.
• Validation also ensures that the requirements:
1) achieve stated business objectives,
2) meet the needs of stakeholders, and
3) are clear and understood by the developers.
Requirements Management

• The purpose of requirements management is to


ensure that an organization documents, verifies, and
meets the needs and expectations of its customers and
internal or external stakeholders.
• Requirements management begins with the analysis
and elicitation of the objectives and constraints of the
organization.
System Models

• System modeling is the process of developing


abstract models of a system, with each model
presenting a different view or perspective of that
system.
• Models help the analyst to understand the
functionality of the system; they are used to
communicate with customers.
Context Models and Behavioral Models
• Context Models :Context models are used to illustrate the
operational context of a system - they show what lies
outside the system boundaries.
• Behavioral Models: Behavioral models are used to
portray the overall behavior of the system.

Two most prominent types of behavioral models:


1. Data Flow Models: Data flow models, which model the
data dispensation in the system, Most business systems
are primarily determined by data.
2. State Machine Models: A state machine model describes
how a system reacts to internal or external events.
Data Models and Object Models

• Data Models: A semantic data model in software


engineering is a technique to define the meaning
of data within the context of its interrelationships
with other data.
• Object Models :A object model is a logical
interface, software or system that is modeled through
the use of object-oriented techniques. It enables the
creation of an architectural software or
system model prior to development or programming.
Structured Models

• StructuredModels:Structuralmodels of software displ


ay the organization of a system in terms of the
components that make up that system and their
relationships.

You might also like