Scribd
Upload
8 views17 pages

Chapter 1

Uploaded by

Fedasa Eyob
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views17 pages

Chapter 1

Uploaded by

Fedasa Eyob
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

SOFTWARE REQUIREMENS ENGINEERING

JIMMA UNIVERSITY

JIMMA INSTITUTE OF TECHNOLOGY

FACULTY OF COMPUTING AND INFORMATICS

CHAPTER ONE

INTRODUCTION TO REQUIREMENTS ENGINEERING


Topics we will cover
2

What is requirements engineering?

what are requirements?

The requirements engineer

Requirements engineer roles

Roles of the customer in requirement engineering


What is a Requirement Engineering?
3

Discussion
Requirement Engineering
4

Requirements engineering is the process of defining,


documenting and maintaining requirements in the
engineering design process.

Requirements engineering is the branch of software


engineering concerned with the real-world goals
for, functions of, and constraints on software
systems.
Generally, requirements engineering is a process
of determining what is to be produced in a
software system.
The Focus Requirements Engineering
5

It focuses on:

• Assessing if the system is useful to the business (feasibility study),


• Discovering requirements (elicitation and analysis),
• Converting these requirements into some standard format
(specification), and
• Checking that the requirements define the system that the customer
wants (validation).

In practice, requirements engineering isn’t sequential


process, it’s an iterative process in which activities are
interleaved.
What is a Requirement?
6

Discussion
What is a Requirement?
7

Requirements are descriptions of how a


software product should perform.

The widely cited IEEE 610.12- 1990


standard defines a requirement as:
• A condition or capability needed by a user to solve a
problem or achieve an objective
• A condition or capability that must be met or
possessed by a system or system component to
satisfy a contract, standard, specification, or other
formally imposed documents.
Software Requirements
8

Therefore, requirements include not only user needs but also those
arising from general organizational, government and industry
standards.

Clearly, a requirement is a collection of needs arising from the user


and various other stakeholders(general organization, community,
government bodies and industry standards), all of which must be met.

The primary measure of success of a software system is the


degree to which it meets the purpose for which it was
intended.
Software requirements
9

Software requirements may be:


• Abstract statements of services
• Detailed mathematical functions
• Part of the bid of contract
• The contract itself
• Part of the technical document, which
describes a product
Defining Requirements
10

Software development starts with defining and


gathering business requirements.

The best way of defining software requirements


is just asking the following questions.
• Who are the users, developers, and stockholders?
• What does the system do?
• What are the main features?
• Why is the system needed?
• When do the users need/or want the solution?
• How will the system work?
• How many users will there be?
Why do requirements matter?
11

• Requirements are crucial to every project.


• Every project succeeds or fails on the quality of its
requirements.
• Requirements set the scope of all subsequent work
and tell the project team what the users want.
• Without good requirements, projects fail, are late,
Because: come in over budget, or produce systems that are
never used..
• Requirement issues should be fixed early, before
design.
• requirements errors tend to be deeply embedded
in the design and are difficult to remedy
afterwards.
What do you think are the challenges to
requirement engineering?
12

Discussion
Challenges to Requirements
13

• Stakeholders may be numerous and


distributed.
• Stakeholder's goals may vary and
conflicting.
• So Many “Requirements”
There are a number of • So many sources of
inherent difficulties in requirements(stakeholders, documents,
RE process. Existing Systems, Application Domain )
Requirements Engineer
14

A person who is concerned with establishing


and managing requirements.

To tackle the challenges the requirements


engineer should have competency in the
following areas:
• Requirements engineering
• Critical reasoning
• Innovation
• Attention to Detail
• Communication
• Interpersonal
Requirements Engineer Roles
15

Requirements engineers are responsible for the analysis, documentation,


coordination and management of requirements regarding new software
projects.
• Improving system quality by identifying issues and common patterns, and developing standard
operating procedures.
• Enhancing applications by identifying opportunities for improvement, making
recommendations and designing and implementing systems.
Roles of the Customer in Requirement Engineering

16

• Anyone who derives direct or indirect benefit from a


product/software is a customer.
Anyone:

• Helping the requirements engineer understand what they need.


• Helping the requirements engineer understand what they don’t
want.
Customers • Providing domain knowledge when necessary and possible.
: • Sticking to all agreements
17

Any Questions?

You might also like